What Happens When You’re the One Who Raises the Flag

What actually happens when you’re the one who raises the flag.

The policy says concerns are welcome. Almost every organisation’s does. The honest test of that sentence is not whether it was written sincerely, but what happens on the specific day someone takes it literally.

Raising an ethical concern often looks like a Slack message asking whether anyone checked the training data for a protected characteristic. It looks like a meeting where one person says the numbers look too good for the sample size. What happens next is the entire content of whether a “concerns are welcome” policy is real.

The three ways it actually goes

In the best case, genuinely, the concern gets investigated on its merits, by someone that can act on what they find, and the person who raised it faces no challenges. This does happen, more often than the discourse around whistleblowing suggests: raising a question and being taken seriously is not automatically a story about courage against the odds, sometimes it is just a system working as designed! In the more common case, the concern is heard politely, thanked, and not acted on (quietly), with no decision ever made and no one accountable for having made it. This is the version that erodes trust fastest, because it is deniable… Nobody rejected the concern. It simply stopped moving, and the person who raised it is left unable to point to a decision they can now contest. In the worst and least common case, raising the concern has a real, personal cost:

• being quietly excluded from the next project,
• having the concern reframed as not being a team player, or,
• in the cases that actually reach employment tribunals, formal retaliation!

This is the case the law tries to address, and the case an organisation’s actual culture is tested against, instead of its policy document.

What separates a real protection from a page

A whistleblowing policy that functions has a few concrete, checkable features:

• a route to someone outside the raising person’s direct management chain. (the person deciding whether the concern has merit is not the same person whose project it threatens)
• A documented response with a reason, even if the answer is no. (a decision actually gets made rather than the concern simply going quiet)
• And, critically, some visible evidence that raising a concern has not, in this organisation’s actual history, correlated with being sidelined afterward… (this can only be observed, which is exactly why a policy alone can never prove it)

None of this is a reason to stay quiet. It is a reason to document what was raised, when, and to whom, in writing, at the time, regardless of how the organisation responds, because this record is what protects a person’s judgement afterward, whatever was decided in that moment.

Written by us at Ethics Directive. If anything here needs correcting, we will say so in the open, dated.