Basics
Review and Update a Report
Workflow for reading Report Detail, deciding whether edits are needed, saving Manage Report changes, and verifying revisions.
First created Last updated
reportsreviewupdaterevisions
Overview
Review starts in Report Detail and only moves to Manage Report when a field needs to change. This keeps operators from editing before they have read the current evidence, action state, and revision history.
Workflow
flowchart TD
detail["Open Report Detail"] --> read["Read evidence, action notes, appeal path, and revisions"]
read --> need{"Does a field need change?"}
need -- No --> handoff["Record current state and next owner"]
need -- Yes --> manage["Open Manage Report"]
manage --> edit["Edit status, severity, facts, evidence, or action"]
edit --> save["Save and create revision"]
save --> verify["Return to Detail and verify rendered result"]
click detail "../surfaces/report-detail/" "Open Report Detail docs"
click manage "../surfaces/manage-report/" "Open Manage Report docs"
Inputs to inspect before editing
| Input or record | What to confirm |
|---|---|
| Status | Whether the case is New, Triage, Investigating, Resolved, or Closed. |
| Severity | Whether urgency still matches current facts. |
| Evidence and violation detail | Whether facts are clear and supported. |
| Action types and local action type | Whether watchlist or ban state matches the actual decision. |
| Ban scope | Whether the restriction affects community only or community and events. |
| Appeal process | Whether the subject has a clear review path. |
| Cross-community recommendation | Whether network review is still justified. |
| Revision history | What changed before this review. |
Save checkpoints
| Checkpoint | Why it matters |
|---|---|
| Required fields still complete | Manage Report validation blocks incomplete required fields. |
| Action notes match selected actions | Future staff read action notes as the reason for restriction. |
| Ban scope matches intended impact | Event-impacting bans affect registration eligibility. |
| Markdown renders safely | Links and evidence must be readable after save. |
| Revision history updated | The audit trail should show changed fields. |
End-to-end operator runbook
- Open source record: Start from Detail, not from a remembered summary.
- Read revisions: Understand what changed before your edit.
- Edit narrowly: Change only fields supported by new facts or decisions.
- Save and verify: Return to Detail and check rendering plus revision history.
- Handoff: Share report number, new status, action state, and unresolved risk.
Common mistakes
Do not lower severity, close a case, or remove a ban without making the reason visible in notes or revision context.