Reporting a suspected cheater is most useful when it gives moderators a clear, verifiable account of what happened. This checklist explains how to collect match IDs, timestamps, clips, usernames, and observable behavior without exaggerating, exposing private information, or wasting evidence in the wrong report channel.
Overview
A strong player report is not a verdict. It is a concise record that helps a game’s moderation or anti-cheat team investigate. Your job is to describe what you observed and preserve the context needed to verify it; the platform or tournament operator decides whether the behavior violated its rules.
Start with the game’s own reporting tools whenever they are available. In-match reports, post-match menus, replay-review forms, and official support pages may route evidence differently. A public social-media post can draw attention, but it is usually a poor substitute for the designated report system and may encourage harassment or pile-ons.
Before submitting, separate facts from interpretation. “The player tracked an opponent through a solid wall for several seconds and pre-fired as soon as the opponent became visible” is an observation. “This player is definitely using wall hacks” is a conclusion. Include the first and, if useful, say that the behavior appeared suspicious rather than presenting an unverified accusation as fact.
For background on how investigations can produce both detections and false positives, see How Anti-Cheat Software Works. The practical lesson is simple: provide enough context for review, then allow the appropriate team to make the determination.
Checklist by scenario
Suspected cheating in a normal match
- Record the player’s exact username. Copy it from the scoreboard or match history if possible. Preserve capitalization, spelling, numbers, and any visible identifier or platform tag.
- Save the match ID or equivalent. This may be called a match number, game ID, replay code, lobby ID, or session reference. If none is shown, record the date, approximate start time, region, mode, map, and your own account name.
- Note precise timestamps. Write down the round, death, encounter, or replay time for each relevant incident. A moderator can review a 20-second window much more efficiently than an entire session.
- Capture the original clip. Use a replay, killcam, spectator view, or recording when available. Keep the unedited file, and make a shorter copy only for convenience. Do not crop out the scoreboard, HUD, audio, or other context that may explain the incident.
- Describe repeatable behavior. List two or three specific moments if they occurred. Patterns are more useful than a general statement that the player “looked impossible.”
When the evidence comes from a replay or killcam
Say which perspective you are using. Killcams and spectator views can simplify or delay information, while replays may reconstruct movement differently from the live match. Note whether the clip shows your own perspective, the suspected player’s perspective, a spectator camera, or a replay system.
Include the replay code or access instructions if the game provides them. If a replay expires, download or preserve the permitted reference details promptly. For examples of systems designed to support review, see Games With Trusted Replay and Killcam Systems.
When the incident affects a tournament or organized event
Follow the event’s rules before using a public accusation. Contact the tournament administrator, referee, or designated integrity channel listed in the event materials. Include the team or player name, match and map, round or game number, timestamp, video link, and your relationship to the event. If you are a competitor, state whether you were a player, coach, observer, or spectator.
Do not privately confront the accused if doing so could interfere with an investigation. Tournament officials may have their own submission format, deadlines, evidence rules, or appeal process, and those can differ from the game publisher’s report system.
When the issue may be account abuse rather than cheating
Some suspicious activity involves account sharing, boosting, smurfing, impersonation, or unauthorized access rather than prohibited software. Describe what you actually saw and use the category that best matches it. A guide to these distinctions is available in Account Sharing, Smurfing, Boosting, and Cheating. Do not attempt to access another player’s account or gather private information to strengthen a report.
What to double-check before submitting
- Correct destination: Confirm whether the game wants an in-client report, a support ticket, an esports integrity form, or a platform-level complaint. Some channels may not share the same evidence limits or follow-up process.
- Complete identifiers: Check the username, platform, region, match ID, date, and time. One incorrect character can make a report difficult to locate.
- Evidence access: Open every link in a private browser or signed-out window if appropriate. Make sure the moderator can view the clip without requesting access to your personal account.
- Privacy: Remove unrelated voice chat, real names, direct messages, or other personal information when it is not needed. Do not publish someone’s identifying details as part of a report.
- File integrity: Keep the original recording and note whether the submitted clip has been trimmed, compressed, or annotated. Labels can help, but annotations should not replace the unedited source.
- Rules and limits: Check current file-size, link, character-count, and retention requirements on the official form. Interfaces and moderation workflows can change after patches or platform updates.
A useful report usually answers five questions: who was involved, which match or event was affected, when the behavior occurred, what was observable, and where the supporting evidence can be reviewed.
Common mistakes
Submitting a montage without context. A dramatic clip may be difficult to assess if it lacks the match identifier, perspective, or timestamp. Attach the short clip only after preserving the full recording or replay reference.
Reporting every strong play. Good aim, sound awareness, unusual timing, lag, a spectator bug, and a replay error can all look suspicious. Report a pattern or a clearly unusual incident, but acknowledge reasonable alternative explanations where they exist.
Using inflammatory language. Insults, threats, and claims about a player’s identity do not improve the evidence. They can distract from the relevant facts and expose you to moderation action on community platforms.
Posting personal information or contacting an employer, team, or family member. This is harassment, not evidence gathering. Use the official process and let the responsible team investigate.
Filing duplicate reports everywhere. Reposting the same accusation across game support, social media, community forums, and tournament channels can create noise. Submit one complete report to the correct authority, then use an official escalation route only if the rules provide one.
Trying to investigate with prohibited tools. Do not install suspicious software, access another account, interfere with a match, or attempt to “test” a player by exploiting the game. For wider context on cheat categories and terminology, see A Plain-English Guide to Cheat Types.
When to revisit your reporting checklist
Return to this checklist before filing a report after a major patch, ranked-season reset, anti-cheat update, platform migration, or tournament-rule change. These events can alter replay availability, report menus, evidence limits, account identifiers, and escalation contacts. It is also worth checking again if a game introduces a new spectator system, killcam, cross-play setting, or moderation dashboard.
Keep a reusable note with the following copy-and-paste template, then fill it in from your own records:
Subject: Suspected cheating report — [game] — [match or event ID]
Player: [exact username and platform ID, if visible]
Date and approximate time: [include time zone]
Mode, map, round, or game: [details]
Observed behavior: [neutral description of what happened]
Timestamps: [list each relevant moment]
Evidence: [replay code, original clip, or permitted link]
Perspective and limitations: [your view, killcam, spectator, replay; note any missing context]
Additional context: [repeat incidents, connection issues, or other relevant facts]
After submitting, save the confirmation number and avoid publicly naming the player while waiting. A report can be complete even if you never receive the outcome; many moderation systems limit what they disclose for privacy and operational reasons. The goal is not to win an argument in the community. It is to give the right reviewers a precise, safe, and usable starting point for an investigation.
