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 Compliance Officer
Intake anonymity is engineered rather than promised: submissions are anonymous by default, Tor integration is the documented way the reporter's identity stays out of the channel, and the pages state over 70 languages with WCAG 2.2 and European Accessibility Act design. I hold it just below the top because we found no public information on voice, phone or in-person intake, only the web channel deployed publicly or on intranets. 1 5