Reporting
Reports
| Rule | Meaning |
|---|---|
| who can report | Signed-in rated Codeforces users can report any valid handle except their own. |
| status effect | A report creates or joins a private report case. The report itself is not a public accusation. |
| review | Assigned reviewers inspect report evidence directly and vote clear, not enough evidence, or cheater. Reports do not open Reviews cases. |
| external matches | External cheater database matches come from outside data. They create external-match cheater status, not reviewer report cases. |
| reviewer skip | A report reviewer can skip an assigned report case. A skip is not a vote. If the reviewer pool cannot fill the case, it closes uncertain. Uncertain report-case closure does not change the target's public status. |
| clear result | A target cleared through a report case enters the ranking only if eligibility checks pass. If those checks fail for ordinary reasons, the target becomes not eligible. If an external cheater database matches the target, the status is external-match cheater. |
| repeat reports | If a report case was closed as clear, the same target cannot be reported again for 24 hours. The report page asks for new evidence after the wait. |
Report visibility
| Role | Can see | Cannot see |
|---|---|---|
| admins | Final result, decision source, report notes, evidence, reporter identity, reporter status and role, target handles, submission time, report counts, admin report notes, and admin report actions. | none |
| reviewers | Final result, decision source, assigned report cases, target handle, evidence, and admin report notes. | reporter identity, reporter status, reporter role, reporter history, report counts, report-group actions, open application context, and admin report-triage notes |
| other users | Final result and decision source. | report notes, evidence, reporter identity, reporter status and role, target handles, submission time, report counts, admin report notes, and admin report actions |