Launching an anonymous reporting channel, and training people to use it

What does a reporting channel launch have to achieve?

Three things: people know the channel exists, believe it is safe, and know what happens next. A channel nobody remembers is the same as no channel, and those three jobs are usually confused with one another.

1. People know it exists, at the moment they need it, which is rarely at a desk and never during the week you announced it.
2. People believe it is safe, which comes from specifics about what is collected and who reads it, not from the word confidential.
3. People know what happens next, because most of the reluctance to report is not fear, it is the assumption that nothing will come of it.

What order should a reporting channel launch follow?

Four stages: get ready, announce it, reinforce it through the first month, then keep it alive. Everything in the first stage has to be true before anyone is told the channel exists, because a report arriving into an unprepared team is the most expensive kind of first impression.

Two details from that list are worth their own sentence. Run three test reports end to end before launch, including one anonymous one, so the team has replied to a reporter they cannot identify at least once before it matters. And put posters where breaks happen rather than only at the entrance: the people least likely to have a work inbox are the ones the poster is for.

What to tell everyone, and what not to say

The announcement is the whole programme for most of your colleagues. Six lines do the work.

• What it is for, in examples: harassment, safety, discrimination, fraud, anything that feels wrong and has nowhere to go.
• How to reach it: a link, and a code on the poster by the kitchen. No account, no app, no work email needed.
• What is collected: nothing that identifies you unless you choose to give your name.
• Who reads it, by role, and who cannot: say plainly that senior leaders do not get access by default.
• When you will hear back, with the dates from the policy.
• Keep your report number and password. They are the only way back into your report, and nobody can recover them for you.

What to avoid: promising complete anonymity, listing what counts as a valid report in legal language, and any hint that reports will be judged on whether they turn out to be right. The honest version of all three is in how anonymous it really is.

Training the people who handle reports

This is the training most often skipped, and the one where mistakes cost the most. An afternoon covers it.

• Acknowledge first, investigate second. The first reply is due long before the answer is. A short acknowledgement with a date beats a considered response three weeks later.
• Write to an anonymous reporter carefully. Ask one question at a time, explain why you need it, and say what they do not have to answer. Never ask a question whose answer would identify them unless the case genuinely cannot move without it.
• Know the difference between a note and a message. Internal notes are for the team and the reporter never sees them; messages go to the reporter. Teams that are unsure of the difference write nothing, and the case ends up with no record at all.
• Declare a conflict immediately. A handler who knows the people in a report hands it over, and the rule for that is agreed before launch, not during the first awkward case.
• Confidentiality is a rule, not a courtesy. No discussing a case outside the team, including with the people it concerns. The organisation's credibility is decided here more than anywhere else.
• Close properly. Tell the reporter what happened, within the limits of what can be shared, and say it in the channel rather than assuming they heard.

What do managers need to know about the reporting channel?

Four things, and none of them takes long. Most concerns still reach a manager first, so managers decide whether the channel is used well or worked around.

• What to do when someone tells you something serious. Listen, do not promise secrecy you cannot keep, and tell them about the channel and what it does.
• Do not investigate it yourself. A well-meant private enquiry destroys evidence and exposes the person who spoke up.
• Say the channel exists, out loud, more than once. Five minutes in a team meeting from a manager beats any all-staff email.
• Understand what retaliation looks like, including the quiet kinds: a changed shift, a withdrawn project, exclusion from a meeting. In ECI's 2023 survey, 46% of people who reported misconduct said they experienced retaliation afterwards, which is a management problem before it is a legal one.

Reaching people without a desk, and without English

The people a reporting channel exists for are often the least likely to see an email about it: shift workers, drivers, site and store staff, and anyone whose first language is not the head office's.

• Print the poster and put it where people stop: the same places that work for reaching frontline teams. Break rooms, locker areas, the back of a door. In CultureMonkey's Speak Up the poster carries your logo and a code that opens the portal with no login.
• Brief supervisors to say it aloud at shift handovers. On a site, that is the announcement.
• Enable the languages your workforce actually reads, and check the category names and questions read naturally in each one.
• Reprint if you ever regenerate the link. Regenerating invalidates every printed code, which is the point, but it means a poster run has to follow it.

The page on the anonymous reporting hotline covers the link and the poster in detail.

Measuring the first ninety days

• Reports arriving at all. NAVEX's benchmark of 2025 data puts the median at 1.65 reports per 100 employees a year. A new channel starts below that; if it stays near zero past a quarter, awareness is the problem, not the workplace.
• Where they come from. Reports from one site and silence everywhere else is a rollout gap, and usually a poster gap.
• Time to first response, against the number in your policy. This is the one the case team controls and the one reporters judge you on.
• Whether people come back. Reporters returning to answer a follow-up question means they believe the conversation is real.

If volume is low after three months, re-announce rather than redesign. Most channels are not distrusted; they are forgotten. Our guide to anonymous reporting in the workplace covers the wider programme, and the page on the anonymous reporting policy covers the promises the launch has to keep.

Launching a channel, answered