The Hidden Cost of Silence: Why Your Mine's Whistleblower Program Could Save Lives

This is a composite, illustrative scenario. A junior geotechnical engineer notices an unusual piezometer trend during a busy shift change. The numbers are moving in the wrong direction, but not dramatically. She mentions it to her supervisor, who is dealing with an equipment breakdown and says they will return to it later. They do not. Months later, the trend has become a crisis.

The point is simple. Even the best monitoring system is useless if the people who operate it are afraid to speak up.

Beyond the checkbox: what whistleblower protection means

When operations address GISTM Principle 12, they can treat it as a legal requirement: establish a process, protect people from retaliation, and move on. The harder question is whether the organisation can hear bad news before it becomes catastrophic news.

Catastrophic tailings failures often share a pattern. Someone noticed that something was wrong, and the organisation failed to listen.

Three kinds of silence

”I do not want to cause trouble”

Workers may fear being labelled poor team players. Contractors may worry about future work. Junior staff may assume senior engineers already know. Local operators may not trust corporate teams to take them seriously.

An illustrative example: a contractor notices unusual seepage during construction but decides it is outside their scope. Months later, the pattern contributes to slope instability.

”I already told someone”

Reports can be filed without escalation. Concerns can be mentioned verbally and never documented. The RTFE may assume the EOR knows, while the Accountable Executive never receives the full picture. The same pattern can appear across shifts and departments without anyone connecting it.

”Nothing will change anyway”

Previous concerns may have been dismissed. People who speak up may face subtle retaliation, such as exclusion from meetings or less desirable assignments. When management says it wants problems raised but acts defensively, experienced operators stop sharing what they see.

What a useful reporting system looks like

Confidential, with protected follow-up

An anonymous hotline is not enough if nobody can ask clarifying questions or close the loop. A confidential process lets a designated investigator know who raised the concern while protecting that information. The reporter can add context, receive updates, and learn what action was taken.

Several ways to report

The RTFE and EOR can be contacts, but they should not be the only ones. A practical process may include a direct line to the Accountable Executive, independent ITRB members, a third-party channel for sensitive matters, worker representatives, and community grievance routes.

The person on a night shift at a remote facility needs the same access as the head-office engineer. They may have more useful information because they see the facility in real time.

Fast, visible responses

Set clear expectations. Acknowledge a report, explain the investigation timeline, provide updates, and close the loop with the findings and actions. If a report does not require action, explain why.

Recognition for good catches

Non-retaliation is the minimum. Organisations should also recognise concerns that lead to improvements, with the reporter’s permission, and value problem-finding alongside problem-solving. The goal is to make speaking up a normal part of safe work.

The Accountable Executive’s role

GISTM assigns the Accountable Executive responsibility for establishing this process. That role requires authority to ensure concerns are investigated, access to information across functions, and personal accountability for how concerns are handled.

Quarterly summaries should show themes and delays without exposing individual reporters. Useful questions include:

• Why are no concerns coming from a particular site? That may be a warning sign.
• Why do contractor concerns fail to produce action?
• How long does it take to resolve a concern?
• Are the same types of concerns recurring?

Integrate reporting with compliance work

A reporting process should connect to the rest of the GISTM system. A concern may require a review of the risk register, a change-management record when field conditions differ from design assumptions, an update to the knowledge base, or targeted training.

One useful cultural test is to ask when someone last raised a concern that turned out to be harmless and was thanked for raising it. If the answer is “I do not know” or “never,” the organisation may have a policy but not a working system.

Five steps to start

1. Map every reporting route and identify gaps for night shifts, remote sites, contractors, and communities.
2. Document how to raise a concern, what happens in the first day and first week, who investigates, and how protection works.
3. Train workers, supervisors, executives, RTFE staff, and EORs for their different responsibilities.
4. Test the process with tabletop scenarios and a low-stakes concern. Record how long each step takes.
5. Share anonymised themes and actions with staff, then have the Accountable Executive review the programme annually with the Board.

Retaliation is rarely obvious

The standard prohibits discharge, discrimination, and other retaliation, but retaliation can look like increased scrutiny, exclusion from communications, social pressure, or future concerns being dismissed. The best protection is a culture where concerns are raised regularly from every level and no one person becomes a target.

Why this matters for tailings

Tailings facilities are long-lived, complex, dynamic, and potentially high consequence. Safe management depends on information from operators, engineers, contractors, communities, and environmental specialists. A reporting process is part of the early-warning system.

Someone at the operation may have noticed an unusual observation, a procedure being skipped, a design assumption that no longer holds, or a gap in who has the right information. The question is whether that person will tell you.

The bottom line

GISTM whistleblower protections are a safety control, not a human-resources ornament. Instruments detect physical change and risk assessments identify technical vulnerabilities. People detect communication failures, procedural shortcuts, and organisational problems.

The hidden cost of silence is measured in lives. Review whether a person at your operation would feel safe telling you something you do not want to hear.

Use GISTM.net to organise reported concerns, investigations, and actions as you work through GISTM requirements and evaluate conformance.