Accountability

Overview

Accountability means a later reviewer can see what changed, who changed it, why the action exists, and how review can happen. The Report System preserves this through required action notes, appeal process fields, report revisions, network decision reasons, appeal review notes, and person-profile audit logs.

Accountability map

flowchart TD
  intake["New Report signature and officer fields"] --> report["Incident report"]
  report --> revisions["Revision history"]
  report --> actions["Action notes and appeal process"]
  report --> cross["Cross-ban decision reason"]
  cross --> appeals["Appeal reasons and review notes"]
  report --> profiles["Person profile audit log"]

Inputs that carry accountability

Input or record	Where	Accountability role
Reporting officer fields	New Report	Names who filed the report.
Signature pad	New Report	Captures declaration at submission.
Action notes	New/Manage	Explains who acted, why, and outcome.
Appeal process	New/Manage	Explains how restriction review can happen.
Status and severity	New/Manage	Shows current urgency and lifecycle state.
Revision history	Report Detail	Shows field changes after creation.
Cross-ban decision reason	Cross-ban Requests	Explains FPH-admin network decision.
Appeal reason and review notes	Network Ban Appeal, Ban Appeals	Preserve partner request and FPH response.
Profile changelog	Person Profiles	Shows identity grouping edits and links.

Workflow

flowchart TD
  action["Safety action proposed"] --> notes["Write action notes and appeal process"]
  notes --> save["Save report"]
  save --> revision["Revision history records changed fields"]
  revision --> review["Second reviewer opens Detail"]
  review --> enough{"Can reviewer repeat decision?"}
  enough -- Yes --> handoff["Handoff complete"]
  enough -- No --> update["Update report with missing proof"]
  update --> save

End-to-end operator runbook

1. Write for reviewers: Assume another person will audit the decision later.
2. Keep facts separate: Separate direct evidence, witness statements, staff conclusions, and old history.
3. Name appeal path: Never leave a restriction without a review route.
4. Verify revisions: After edits, open Detail and check revision history.
5. Protect privacy: Add only identity and contact data needed for safety work.

Common mistakes

Do not erase uncertainty by rewriting a report as if every claim is proven. Clarify the record, but preserve what is known, what is alleged, and what was decided.