# How to Build a Clear Complaint Evidence Timeline

A well-organised timeline can help readers explain a gaming-related complaint without relying on assumptions or emotional language. The aim is to present what happened, what remains unclear and what response would resolve the issue. Readers can use this checklist before approaching a verified submission channel.

# Start with a concise summary

Write a short description of the concern in plain English. Identify the action being questioned and the clarification or remedy being requested. Avoid making claims about intent, responsibility or wrongdoing that cannot be supported.

Readers can consult the complaint evidence timeline guide for a structured way to review the sequence before submitting a complaint.

# Put events in order

Create one entry for each relevant interaction or account event. Each entry can include:

• the date shown in the reader’s own records;
• the action taken by the reader;
• the message or status displayed at that point;
• the response received, if any; and
• the next step requested or attempted.

If a date or detail is uncertain, label it as an estimate rather than presenting it as confirmed. Keep the original wording of important messages where possible, but remove unrelated personal information from working notes.

# Separate facts from questions

For every timeline entry, distinguish between what the reader can directly observe and what still needs clarification. A displayed status, for example, should be recorded as displayed rather than interpreted as proof of an underlying decision.

Useful questions may include:

• Which published term or process appears relevant?
• Was the same explanation provided across different interactions?
• Is there an unresolved request that can be stated clearly?
• What specific response would allow the reader to understand the outcome?

Readers should compare any applicable terms with the current version available through an official channel. They should not assume that wording remembered from an earlier visit remains current.

# Review evidence safely

Before sharing anything, readers should consult current official requirements and confirm that the submission channel is verified. Only information relevant to the complaint should be considered. Unrelated details can be removed or obscured where doing so does not change the meaning of the material.

Never send card images, security codes, PINs, one-time passcodes, passwords or recovery codes in verification files, screenshots, email, chat or support messages. If ordinary payment entry is necessary, readers should use only a verified payment form and check the destination carefully.

# Check the final complaint

Before submission, readers can verify that the complaint:

• follows a clear chronological order;
• uses neutral, specific language;
• identifies uncertain details honestly;
• avoids unsupported conclusions;
• states the desired clarification or remedy; and
• contains no unnecessary sensitive information.

Keep a private copy of the submitted wording and note any reference shown by the verified channel. If a response arrives, add it to the timeline without rewriting earlier entries. This preserves a clear record and makes any later follow-up easier to understand.