A Practical Checklist for Preparing Complaint Evidence

A clear complaint is easier to assess when it separates confirmed details from assumptions. Before submitting anything, readers can organise their records, identify the exact issue and verify which complaint pathway applies. This checklist focuses on preparation and does not predict whether a complaint will be accepted or what result may follow.

Define the issue clearly

Start with a short description of what happened and the outcome being requested. Keep the wording factual and avoid guessing about motives, systems or internal decisions. Readers can check whether the issue concerns account access, gameplay records, a transaction, promotional terms, customer support or another specific matter.

Create a simple sequence of events using dates and actions. Where a detail is uncertain, label it as uncertain rather than presenting it as established. This makes it easier to distinguish records from recollections.

Gather relevant evidence

Readers can collect material directly connected to the complaint, such as:

• account or case reference details;
• relevant transaction references;
• screenshots showing the full page context;
• copies of messages sent and received;
• the terms displayed when the event occurred;
• notes of contact attempts and responses; and
• records showing the requested resolution.

Evidence should remain in its original form where possible. Readers can retain unedited copies and create separate working copies for annotations. Check that screenshots are readable and that important context has not been cropped out.

Review the complaint pathway

Before sending personal information, readers should verify who operates the submission channel, what categories it accepts and how information may be handled. The complaint evidence pathway checklist can be used as a starting point for reviewing what to organise and which details to confirm independently.

Readers can also compare the issue against the published complaint scope. If an initial support process is expected, record any reference supplied during that process. Do not assume that one submission automatically reaches another organisation or review channel.

Protect sensitive information

Only include information that is relevant to the issue and requested through a verified channel. Redact unrelated personal details from working copies, but keep complete originals securely. Avoid sharing passwords, access codes or unnecessary financial information.

Check every attachment before submission. File names should be descriptive without exposing sensitive details. Readers can also prepare a brief index explaining what each item shows and how it relates to the sequence of events.

Complete a final review

Before submitting, readers can verify that the complaint:

• identifies the specific issue without unsupported claims;
• explains the requested outcome;
• presents events in a consistent order;
• links each key statement to relevant evidence;
• uses a channel whose purpose and recipient have been checked; and
• retains copies of the final text and attachments.

A structured evidence pack cannot guarantee any particular result. Its purpose is to present the issue clearly, preserve relevant records and help readers follow the appropriate process with fewer gaps or ambiguities.