New Report

Overview

New Report creates the first formal safety record for an incident. It captures urgency, status, incident facts, people, evidence, witnesses, actions taken, appeal instructions, a possible cross-community ban recommendation, and the reporting officer signature.

Submit only when the form can stand on its own. Future reviewers should be able to understand what happened, why the local action exists, and where to find supporting evidence without relying on private memory.

Dashboard route

• /reports/new

Inputs and controls

Input or control	What it changes	Before submitting
Back	Returns to All Reports.	Use if you opened intake by mistake.
Severity: Low	Marks a minor issue with no urgent danger right now.	Still record enough facts for later review.
Severity: Medium	Marks a concern needing follow-up soon.	Make the next owner obvious in the notes.
Severity: High	Marks serious harm or clear safety risk.	Confirm immediate safety actions have an owner.
Severity: Critical	Marks urgent danger.	Act operationally before relying on documentation alone.
Status: New	Starts the report as recorded but not reviewed.	Use for most fresh intake.
Status: Triage	Starts the report in first review.	Use when staff are already checking validity or priority.
Status: Investigating	Starts the report in active investigation.	Use only when review work has already begun.
Status: Resolved	Starts the report as action complete.	Include action notes and appeal process.
Status: Closed	Starts the report as intentionally ended.	Use rarely; closed records are not active safety work.
Summary	Short description used in lists and cards.	Keep it factual and under the field limit.
Filed at	Filing timestamp.	Use the actual filing time, not the incident time.
Occurred at	Incident timestamp.	If uncertain, record the best known time and explain uncertainty in detail.
Platform	Primary place where the incident happened.	Use a clear label such as Discord, Telegram, or in-person event.
Platform detail	Server, channel, DM, venue, room, or event detail.	Avoid exposing private location details unless needed for safety review.
Organisation type	Group type involved in the incident.	Use a phrase another partner can understand.
Reported person fursona name	Main community name of the person being reported.	Prefer the name reviewers will recognize.
Reported person legal family/given/middle names	Legal identity fields when known and relevant.	Do not add unverified legal identity.
Reported handle platform	Platform label for the main account reference.	Match the link or handle entered beside it.
Reported handle / profile URL	Main account, username, or profile URL.	Confirm spelling and URL ownership where possible.
Alt handles add/remove rows	Adds or removes extra platform plus handle/URL rows.	Include aliases that help identify the same person; remove duplicates.
Reported email	Email for the reported person.	Add only if relevant and reasonably verified.
Reported location	City, region, country, or online-only context.	Avoid unnecessary sensitive location data.
Community standing	Relationship to the community.	Use as context, not proof.
Victim fursona/legal names	Identifies the affected person when appropriate.	Protect sensitive identity and consent expectations.
Victim handle platform and URL	Victim account reference.	Use only as needed for follow-up.
Victim email / other contact	Contact path for support or investigation.	Limit to staff who need follow-up access.
Victim relation to reporter	How the victim relates to the reporter or incident.	Use the closest available option.
Victim statement	Markdown-ext field for the affected person’s account.	Preserve their words and mark paraphrases clearly.
Violation types	Checkbox categories such as harassment, sexual misconduct, assault, threats, boundary violation, stalking, underage conduct, theft, fraud, hate speech, intoxication, or other.	Select every category supported by facts, then explain in prose.
Violation detail	Markdown-ext description of what happened.	Write ordered facts: who, what, when, where, and how it was observed.
Prior history	Markdown-ext field for older reports, warnings, or known patterns.	Separate confirmed records from memory or hearsay.
Evidence	Markdown-ext field for screenshots, logs, links, photos, and witness evidence.	Confirm evidence is reachable by authorized reviewers.
Witness 1/2 name and contact	Up to two direct witness references.	Add enough to find them without overexposing private contact data.
Witness notes	Markdown-ext witness context.	Keep witness statements distinct from staff conclusions.
Action types	Checkbox actions such as warning, mute, temporary ban, permanent ban, escorted out, investigation, police involvement, or probation.	Make action notes match every selected action.
Action date	Date/time of local action.	Needed for chronology and appeal review.
Action ends at	Optional end date/time for temporary action.	Leave blank for permanent or indefinite restrictions.
Furries PH action type	Watchlist or Ban.	Use Watchlist for monitoring or temporary suspension; use Ban for formal restriction.
Ban scope	Appears when action type is Ban. Community spaces only does not block event rego; events and community does.	Use event-impacting bans only after serious review.
Action notes	Markdown-ext record of who acted, what was done, and outcome.	Required for future accountability.
Appeal process	Markdown-ext instructions for how the subject can request review.	Required for fairness when a restriction exists.
Recommend cross-community ban	Flags the report for FPH-admin network review.	Use only after team discussion and strong evidence.
Reporting officer fields	Read-only profile-derived name, role, contact, and email.	Update Settings / Profile before filing if these are wrong.
Signature pad	Captures the officer declaration signature.	Sign only after reviewing high-risk fields.
Cancel	Leaves the form without filing.	Use when intake is not ready.
Floating save bar Submit report	Validates the form and creates the incident report.	Required fields, checkboxes, and signature must be complete.

Option meanings

Option group	Options	Meaning
Severity	Low, Medium, High, Critical	Urgency and risk label for triage.
Status	New, Triage, Investigating, Resolved, Closed	Starting lifecycle state.
Handle platform	Telegram, Discord, Twitter/X, Bluesky, Instagram, FurAffinity, Weasyl, Inkbunny, Facebook, TikTok, Other	Labels account evidence.
Community standing	Known member, new attendee, first-time visitor, regular, organizer/staff, vendor/artist, guest of honour, online member, other	Context for identity and access, not proof.
Victim relation	Witness, colleague/co-organizer, friend, fellow attendee, staff/security, stranger, other	Relationship context for follow-up.
Local action type	Watchlist, Ban	Watchlist preserves local safety context; Ban creates a formal restriction.
Ban scope	Community spaces only, events and community	Events and community can block event registration.

Workflow

flowchart TD
  start["Open New Report"] --> scope["Resolve active partner scope"]
  scope --> facts["Enter severity, status, incident facts, people, evidence, witnesses"]
  facts --> actions["Record local actions and appeal process"]
  actions --> network{"Cross-community ban recommended?"}
  network -- No --> sign["Officer signs declaration"]
  network -- Yes --> warning["Read network-ban warning and confirm evidence"]
  warning --> sign
  sign --> submit["Submit report"]
  submit --> created["API creates incident, revision, and local action records"]
  created --> detail["Redirect to Report Detail"]
  click detail "./report-detail/" "Open Report Detail docs"

Validation and state behavior

State	What happens
Missing required text/select/date field	The field is marked invalid and submission stops.
Missing severity or status	The radio group is marked invalid.
No violation or action type selected	The checkbox group is marked invalid.
No signature	Submission stops with a signature error.
Action type is not Ban	Ban scope is hidden and disabled.
Ban scope is event-impacting	A serious-decision warning appears.
Cross-community recommendation checked	A network-review warning appears.
Submit succeeds	The browser redirects to /reports/detail?id=:incidentId.

Related pages

• File a Report for the intake workflow.
• Report Detail for the submitted record.
• Report Writing for evidence and wording guidance.

End-to-end operator runbook

1. Prepare evidence: Gather timestamps, people, context, screenshots or links, and current safety action.
2. Confirm scope: Make sure the active partner is the organization filing the report.
3. Complete fields: Fill every required field and avoid unverifiable identity data.
4. Review restrictions: Check local action type, ban scope, action notes, and appeal process.
5. Submit and verify: Submit, then open Report Detail and confirm report number, status, evidence, action, and revision history.

Common mistakes

Do not file a report with a strong restriction but vague action notes or no appeal process. The restriction may be correct, but future reviewers need to understand why it exists and how review can happen.