Community-submitted
The record presents a submitted account that has not been independently verified.
How to read the evidence
Every public record passes through classification, review and safety decisions. The visuals below show what the labels mean, how priorities are formed and when location details can appear.
The publication journey
A submitted report stays distinct from the public record created from it.
Community members submit an account and any supporting evidence. This information is not automatically a finding.
Issue groups and impacts are cleaned from Kobo fields. Any unresolved category stays marked “not specified.”
The review level is labelled, sensitive details are edited, and location consent is checked before public use.
A separate, safety-edited record is published. It may combine relevant context from several sources.
Triage, not proof
Five submitted or derived signals are combined to help teams see where a response may be most urgent.
Read the label first
The record presents a submitted account that has not been independently verified.
Some material elements have been checked, while others remain unconfirmed.
The published record has completed the applicable verification review.
The record summarises patterns across multiple reports rather than one incident.
Location and suppression
Submitted incident GPS is considered separately from the rest of the report.
Only when the public record is separately approved.
The public record does not show the submitted point.
Fairness and corrections
Suggested duty bearers identify institutions that may need to coordinate a response. They are not findings of fault.
Named institutions receive a right of reply where policy requires it.
Material corrections are versioned and explained rather than silently replaced.
Urgent removal is available when publication creates a safety risk.
Before drawing a conclusion