Report Lifecycle

Overview

The report lifecycle is the path from first intake to a reviewed, maintained record. Status is only one part of the lifecycle. Evidence, people fields, local action state, appeal process, revisions, and network-review state also need to agree.

Dashboard routes

Route	Purpose
/reports/new	Creates the report.
/reports/detail?id=:incidentId	Shows the source record and revision history.
/reports/manage?id=:incidentId	Updates status, facts, evidence, people fields, local actions, and appeal process.
/reports/all	Finds visible records across the current user scope.
/reports/my-reports	Works the current partner’s queue.

Flowchart

flowchart TD
  intake["New report filed"] --> newStatus["Status: New"]
  newStatus --> triage["Status: Triage"]
  triage --> investigating["Status: Investigating"]
  investigating --> action["Local action: watchlist or ban"]
  action --> resolved["Status: Resolved"]
  resolved --> maintenance["Record maintenance and appeals"]
  triage --> closed["Status: Closed"]
  investigating --> closed
  resolved --> closed
  action --> cross{"Network review needed?"}
  cross -- Yes --> fph["Cross-ban Requests"]
  cross -- No --> maintenance
  fph --> maintenance
  click action "../surfaces/manage-report/" "Open Manage Report docs"
  click fph "../surfaces/cross-bans/" "Open Cross-ban Requests docs"

Lifecycle stages

Stage	What is true	Main surfaces	Completion evidence
Intake	Report has been filed and assigned a report number.	New Report	Detail page loads with created revision.
New	Report is recorded but not fully reviewed.	My Reports, Report Detail	Owner and next review step are known.
Triage	Staff are checking validity and priority.	Detail, Manage Report	Severity, evidence, and scope are confirmed or corrected.
Investigating	Staff are actively reviewing facts.	Manage Report, Person Profiles	Evidence, witness context, and identity links are updated.
Action	Watchlist, local ban, or network recommendation is decided.	Manage Report, Watchlists, Bans	Action notes, ban scope, and appeal process are complete.
Resolved	Local action is complete and no immediate work remains.	Manage Report, Detail	Record shows action result and current restriction state.
Closed	Record is intentionally ended, invalid, or historical.	Manage Report, Detail	Closure reason is understandable from notes/revisions.

Inputs that drive lifecycle state

Input	Why it matters
Status	Declares current workflow state.
Severity	Sets urgency.
Action types and local action type	Determine monitoring or restriction behavior.
Ban scope and action ends at	Define duration and event-registration impact.
Appeal process	Makes restriction review possible.
Cross-community recommendation	Routes the case to FPH-admin review.
Revision history	Proves how lifecycle state changed.

End-to-end operator runbook

1. Start with status: Identify whether the case is New, Triage, Investigating, Resolved, or Closed.
2. Check evidence: Confirm the written facts support the current state.
3. Check action: Verify watchlist or ban state, scope, notes, and appeal process.
4. Check network state: See whether cross-ban review or appeals are active.
5. Handoff: Record report number, status, owner, next action, and unresolved risk.

Common mistakes

Do not mark a report Resolved or Closed just to remove it from the active queue. The record must explain why that state is valid.