Reporting channels & reporter experience
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialogue, phone or voice message, languages, accessibility — and whether anonymity survives first contact.
0 — Not a reporting channel; a general contact or survey form with no anonymous route and no way to reach the reporter afterwards.
3 — A web form that accepts anonymous reports, with a case number or access code the reporter can use to check the report later.
5 — Anonymous two-way dialogue through a protected mailbox or access code, the reporting page in several languages, and use on mobile devices without an app or account.
8 — Several channels (web, voice message or phone hotline, in-person meeting requests, QR or intranet entry points), broad language coverage with translation of messages, accessibility addressed, and voice distortion or another anonymity measure for spoken reports.
10 — Intake engineered around the frightened reporter: every channel usable anonymously, dozens of languages, WCAG conformance stated, no app or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Skeptic
The captured pages document real intake breadth: a 24/7 live-answer hotline in English, French and Spanish with interpretation in 150 additional languages, a web reporting system, and three engineered anonymity levels under which the organisation never sees a strictly anonymous reporter's name or email. That last design is a burden — the reporter must log in manually every 24–48 hours to follow the case — but it keeps identity out of the channel itself. We found no public information on accessibility conformance, on languages of the web reporting page itself, or on translation of ongoing two-way messages. 1 3 4