Furries PH Docs
Dashboard
Report system docs

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 recordWhat to confirm
StatusWhether the case is New, Triage, Investigating, Resolved, or Closed.
SeverityWhether urgency still matches current facts.
Evidence and violation detailWhether facts are clear and supported.
Action types and local action typeWhether watchlist or ban state matches the actual decision.
Ban scopeWhether the restriction affects community only or community and events.
Appeal processWhether the subject has a clear review path.
Cross-community recommendationWhether network review is still justified.
Revision historyWhat changed before this review.

Save checkpoints

CheckpointWhy it matters
Required fields still completeManage Report validation blocks incomplete required fields.
Action notes match selected actionsFuture staff read action notes as the reason for restriction.
Ban scope matches intended impactEvent-impacting bans affect registration eligibility.
Markdown renders safelyLinks and evidence must be readable after save.
Revision history updatedThe audit trail should show changed fields.

End-to-end operator runbook

  1. Open source record: Start from Detail, not from a remembered summary.
  2. Read revisions: Understand what changed before your edit.
  3. Edit narrowly: Change only fields supported by new facts or decisions.
  4. Save and verify: Return to Detail and check rendering plus revision history.
  5. 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.

All docs