Manage Report

Overview

Manage Report edits an existing incident report. It can change lifecycle status, severity, incident facts, people fields, evidence, local action type, ban scope, appeal process, and cross-community ban recommendation.

Every save should make the record clearer. The page writes revision history, so edits should explain the current truth without hiding why earlier staff acted.

Dashboard route

• /reports/manage?id=:incidentId

Inputs and controls

Input or control	What it changes	Before saving
Back / Cancel	Returns to Report Detail for the same report ID.	Use if the intended change is not ready.
Status	New, Triage, Investigating, Resolved, or Closed.	Closed means the report is no longer active or valid safety work.
Severity	Low, Medium, High, or Critical.	Add a reason in notes when changing urgency.
Action types	Updates selected staff actions.	Keep action notes consistent with selected actions.
Action date	Records when the local action happened.	Confirm chronology before changing.
Action ends at	Optional end date/time for temporary action.	Leave blank for permanent or indefinite action.
Furries PH action type	Watchlist or Ban.	Watchlist preserves context; Ban creates formal restriction behavior.
Ban scope	Appears only when local action type is Ban.	Event-impacting bans require stronger review.
Action notes	Markdown-ext record of who acted, why, and outcome.	This is the operational reason future staff will read.
Appeal process	Markdown-ext instructions for review request.	Required when restrictions are active.
Recommend cross-community ban	Flags or unflags FPH-admin network review.	Use only with strong evidence and local team agreement.
Summary	Updates the short report description.	Keep it factual and searchable.
Platform / Platform detail	Updates where the incident happened.	Avoid overexposing private locations.
Occurred at	Updates the incident time.	Explain uncertainty in detail fields when needed.
Organisation type	Updates the group/event context.	Use wording another partner understands.
Reported person fields	Updates fursona, legal names, handle, email, alt handles, location, and standing.	Avoid unverified legal identity or irrelevant PII.
Victim fields	Updates fursona, legal names, handle, email, other contact, relation, and statement.	Preserve the affected person’s wording and privacy.
Violation types	Updates violation category checkboxes.	Select categories supported by facts.
Violation detail	Markdown-ext fact narrative.	Keep conclusions separate from evidence.
Prior history	Markdown-ext older warnings or reports.	Separate confirmed history from memory.
Evidence	Markdown-ext evidence list.	Confirm links remain reachable by authorized reviewers.
Witness fields	Updates two witness names/contacts and notes.	Limit contact data to what follow-up needs.
Reporting officer fields	Read-only submitted officer identity and contact.	These cannot be changed after submission.
Signature display	Read-only signature captured at submission.	Use to confirm declaration provenance.
Floating save bar Save	Validates and saves dirty fields.	Confirm report number and changed sections.
Floating save bar Revert	Restores the last loaded values.	Use when editing the wrong report or abandoning a draft change.

Save and validation behavior

State	What happens
Missing required field	Save stops and the field is marked invalid.
No violation or action type	Save stops until at least one option is selected.
Action type is not Ban	Ban scope is hidden, disabled, and cleared.
Ban scope is event-impacting	A serious-decision warning appears.
Cross-community recommendation checked	A network-review warning appears.
User lacks edit access	The page redirects to Report Detail.
Save succeeds	A success alert appears and dirty indicators clear.
Revert	Current unsaved field values are replaced by the last loaded snapshot.

Workflow

flowchart TD
  detail["Open Report Detail"] --> manage["Open Manage Report"]
  manage --> permission{"Can edit this report?"}
  permission -- No --> back["Redirect to Detail"]
  permission -- Yes --> edit["Edit fields and action state"]
  edit --> validate["Validate required fields, checkboxes, and ban scope"]
  validate --> save["Save report"]
  save --> revision["API writes revision history"]
  revision --> verify["Return to Detail and verify rendered evidence"]
  click detail "./report-detail/" "Open Report Detail docs"

Related pages

• Report Detail for read-only verification.
• Review and Update a Report for process guidance.
• Record Maintenance for closure and revision expectations.

End-to-end operator runbook

1. Open the right record: Confirm the report number, subject, and partner before editing.
2. Make narrow edits: Change only fields supported by current evidence.
3. Check restrictions: Review action type, ban scope, action notes, and appeal process together.
4. Save once ready: Let validation catch missing required fields.
5. Verify rendered record: Open Detail and confirm markdown, links, badges, and revision history.

Common mistakes

Do not close a report just because no one is working it today. Use New, Triage, or Investigating for unfinished work; Closed means the case is intentionally ended or no longer valid.