Best Practices
Report Writing
How to write summaries, details, evidence, action notes, appeal process, and cross-ban recommendations clearly.
First created Last updated
reportswritingevidencebest-practices
Overview
Good report writing makes a safety decision repeatable. A reviewer should be able to read the report, find the evidence, understand what staff did, and know how appeal review works.
Writing workflow
flowchart TD facts["Facts and source material"] --> summary["Write short summary"] summary --> detail["Write ordered violation detail"] detail --> evidence["Link evidence and prior history"] evidence --> action["Write action notes"] action --> appeal["Write appeal process"] appeal --> review["Read as a future reviewer"]
Field writing guide
| Field | Write this way | Avoid |
|---|---|---|
| Summary | One factual sentence with subject, issue, and context. | Conclusions without details. |
| Platform detail | Enough location context for review. | Private venue/DM details that are not needed. |
| Victim statement | The affected person’s account, clearly marked when paraphrased. | Rewriting their statement as staff certainty. |
| Violation detail | Ordered facts: who, what, when, where, how observed. | Vague labels such as “bad behavior” without examples. |
| Prior history | Confirmed older reports or warnings, separated from memory. | Hearsay presented as fact. |
| Evidence | Links, screenshots, logs, photos, witness names, and access notes. | Unreachable links or unexplained filenames. |
| Witness notes | What each witness saw or can clarify. | Broad sharing of private contacts. |
| Action notes | Who acted, when, what action, and why. | ”Handled” without outcome. |
| Appeal process | How the subject can request review. | Leaving appeal path blank for restrictions. |
| Cross notes | Why FPH-admin network review may be needed. | Treating recommendation as an automatic ban. |
Inputs and controls affected
Use this guidance when completing the markdown-ext fields in New Report or Manage Report: victim statement, violation detail, prior history, evidence, witness notes, action notes, and appeal process.
End-to-end operator runbook
- Write facts first: Describe observable events before conclusions.
- Use specific labels: Match violation categories to evidence.
- Separate roles: Keep victim statement, witness notes, and staff conclusions distinct.
- Explain action: Make the restriction reason and appeal path visible.
- Preview by reading Detail: Confirm the rendered report is clear and link-safe.
Common mistakes
Do not use severity or violation categories as a substitute for evidence. Labels help filter the case; prose and source material prove why the label was chosen.