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

Last month, a junior geotechnical engineer noticed something odd in the piezometer readinDoes your GISTM compliance system make it easy to track, investigate, and act on concerns raised?s. The numbers were trending in the wrong direction, but subtly—nothing dramatic, nothing that screamed emergency. She mentioned it to her supervisor during a busy shift change. He was dealing with a equipment breakdown and said they’d “circle back to it later.” They never did. Three months later, that trend had become a crisis.

This story is a composite of real incidents from mining operations worldwide—illustrates a fundamental truth: the most sophisticated monitoring systems in the world are worthless if the people operating them are afraid to speak up. me post 1 The Hidden Cost of Silence: Why Your Mine’s Whistleblower Program Could Save Lives Last month, a junior geotechnical engineer noticed something odd in the piezometer readings. The numbers were trending in the wrong direction, but subtly - nothing dramatic, nothing that screamed emergency. She mentioned it to her supervisor during a busy shift change. He was dealing with a equipment breakdown and said they’d “circle back to it later.” They never did. Three months later, that trend had become a crisis. This story is”a composite of real incidents from mining operations worldwide - illustrates a fundamental truth: the most sophisticated monitoring systems in the world are worthless if the people operating them are afraid to speak up. Beyond the Checkbox: What Whistleblower Protection Really Means When most operations approach GISTM Principle 12, they see it as a legal requirement: establish a process, protect against retaliation, move on to the next requirement. But here’s what the standard is really asking: Can your organization hear bad news before it becomes catastrophic news? The Global Industry Standard on Tailings Management doesn’t mandate whistleblower protections because regulators thought it would be nice to have. It’s there because catastrophic tailings failures have a pattern: someone knew something was wrong, and the organization failed to listen. The Three Types of Silence That Kill

1. “I Don’t Want to Cause Trouble” Silence This is the most common - and most dangerous - form of organizational silence. It happens when:

Workers fear being labeled as “not team players” Contractors worry about losing future business Junior staff assume senior engineers “must already know” Local operators don’t trust that corporate will take them seriously

Real-world impact: A contractor notices unusual seepage during construction but doesn’t report it because “it’s not in my scope of work.” Six months later, that seepage pattern contributes to slope instability. 2. “I Already Told Someone” Silence Information gets lost in the organizational maze:

Reports get filed but never escalated Concerns are mentioned verbally but not documented The RTFE hears about it but assumes the EOR knows The Accountable Executive never gets the full picture

Real-world impact: Multiple people observe the same concerning pattern, but because the dots are never connected across shifts, departments, or organizational levels, no one realizes the urgency. 3. “Nothing Will Change Anyway” Silence This is the silence of learned helplessness:

Previous concerns were dismissed or ignored People who spoke up faced subtle retaliation (being passed over for promotions, given less desirable assignments) Management says they want to hear problems but their actions say otherwise

Real-world impact: Your most experienced operators stop sharing their observations. You lose the benefit of decades of practical knowledge because people have learned that speaking up is career-limiting. What a World-Class Whistleblower System Actually Looks Like It’s Not Anonymous - It’s Confidential (And There’s a Difference) Many operations rush to set up anonymous hotlines and think they’re done. But anonymous systems have a fatal flaw: there’s no way to follow up, ask clarifying questions, or close the loop with the reporter. Better approach: Confidential reporting where the Accountable Executive (and only the Accountable Executive or designated investigator) knows who raised the concern, but this information is protected. The reporter knows their concern is being taken seriously and can provide additional context when needed. It Has Multiple Entry Points Your RTFE should be one avenue. Your EOR should be another. But what if the concern is about them? World-class systems include:

Direct line to the Accountable Executive Independent ITRB members as potential contacts Third-party hotlines for sensitive matters Worker safety representatives Community grievance mechanisms for external observers

Critical insight: The person working night shift maintenance on a remote facility needs just as much access as your head office engineers - maybe more, because they’re seeing things in real-time. It Responds Quickly and Visibly Here’s the test: If someone reports a concern on Monday, what happens by Friday? Poor systems: The concern disappears into an investigation black hole. The reporter hears nothing. Eventually they assume nothing matters. Excellent systems:

Acknowledge receipt within 24 hours Provide a timeline for investigation (even if it’s “we need 30 days to properly assess this”) Update the reporter at regular intervals Close the loop by explaining what was found and what action was taken (or why no action was needed)

It Rewards, Not Just Protects Here’s where most operations get it wrong: they focus solely on “non-retaliation” language. That’s defensive thinking. Offensive thinking asks: How do we make speaking up the obvious career move? Leading organizations:

Include “identification of potential issues” in performance reviews Publicly recognize (with the person’s permission) concerns that led to improvements Make problem-finding as valued as problem-solving Reward the supervisor who creates an environment where people feel safe raising concerns

The Accountable Executive’s Role: More Than a Signature The standard specifically requires the Accountable Executive to establish this process. Not HR. Not the legal department. Not the site manager. Why? Because effective whistleblower systems require someone with three things:

Authority to ensure concerns are investigated and acted upon Access to cross-functional information to see patterns Accountability that means they personally answer for how concerns are handled

When the Accountable Executive personally reviews quarterly summaries of concerns raised (not individual details, but themes and patterns), something powerful happens: the organization learns where its weak points are. Questions they should be asking:

Why are we getting zero concerns from this particular site? (That’s often a red flag, not a green one) Why do concerns from contractors never lead to action? What’s the average time from concern raised to resolution? Are we seeing the same types of concerns repeatedly? (That suggests systemic issues)

Integration With Your Compliance System This is where a sophisticated GISTM compliance tool becomes invaluable. Your whistleblower program shouldn’t exist in isolation - it should integrate with: Risk Management Systems: When someone raises a concern, does it automatically trigger a review of related risks in your register? Should it update your risk assessment? Change Management: If a concern reveals that field conditions differ from design assumptions, does that flow into your formal change management process? Knowledge Base Updates: Concerns about site conditions, material properties, or performance should inform your evolving knowledge base. Training Needs: Patterns in concerns can reveal where additional training or communication is needed. The Cultural Indicator You Can Measure Today Want to know if your whistleblower system is working? Ask yourself: When was the last time someone raised a concern that turned out to be nothing serious, and they were thanked for it anyway? If your answer is “I don’t know” or “never,” you don’t have a working system - you have a policy document. In high-reliability organizations (think nuclear power, aviation), “good catches” are celebrated even when they turn out to be false alarms. Because the behavior you want is vigilance and communication, not perfect judgment. Building the Program: Five Steps to Start Monday Step 1: Audit Your Current Gaps (Week 1)

Map every potential concern pathway - who would people currently tell? Identify the gaps (night shift? remote sites? contractors? community members?) Review the last 12 months: how many concerns were raised? How were they handled?

Step 2: Create Crystal-Clear Processes (Week 2-3) Document:

Exactly how someone raises a concern (multiple methods) What happens in the first 24 hours, first week, first month Who investigates (never the person being complained about) How protection from retaliation actually works in practice

Step 3: Train Everyone - Differently (Week 4-6)

Workers/contractors: How to raise concerns and what to expect Supervisors: How to receive concerns without becoming defensive Executives: How to investigate and respond appropriately RTFE/EOR: Their specific responsibilities in the process

Step 4: Test It (Month 2-3)

Run tabletop scenarios Have a trusted person raise a low-stakes actual concern to see how the system responds Time each step of the process

Step 5: Close the Loop Publicly (Ongoing)

Share anonymized examples of concerns raised and actions taken Quarterly reporting to all staff on themes and patterns Annual review by the Accountable Executive presented to the Board

The Hard Truth About Retaliation The standard says you can’t “discharge, discriminate against, or otherwise retaliate” against whistleblowers. But retaliation is rarely that obvious. More common forms:

Suddenly increased scrutiny of the whistleblower’s work Being left out of meetings or communications Subtle social exclusion Being labeled as “negative” or “not a team player” Future concerns being dismissed more quickly

The antidote: Make speaking up so normalized that there’s no target on anyone’s back. When problems flow up regularly from all levels, individual reporters blend into the background. Why This Matters More for Tailings Than Almost Anything Else Tailings facilities are:

Long-lived: Decisions made today play out over decades Complex: No single person understands every aspect Dynamic: Conditions change, sometimes subtly High-consequence: When things go wrong, they go catastrophically wrong

This combination means you need information flowing from everywhere:

The operator who works around the facility daily The engineer reviewing monitoring data The community member who notices something from outside The contractor who saw something during a short-term project The environmental scientist tracking downstream impacts

Your whistleblower system is actually your early warning system. The Question That Should Keep You Up at Night Right now, today, someone at your operation probably knows something important. Maybe it’s:

An unusual observation that doesn’t quite make sense yet A concern about whether procedures are being followed A question about whether design assumptions still hold A worry about whether the right people have the right information

The only question that matters is: Will that person tell you? Because the difference between a near-miss and a catastrophe often isn’t technical - it’s cultural. It’s whether your organization can hear bad news, investigate it honestly, and act on it decisively. Making It Real: Your Compliance Tool’s Role A sophisticated GISTM compliance platform should:

Track concerns raised, investigations completed, and actions taken Alert the Accountable Executive to patterns or delays Link concerns to related requirements (if someone reports seepage issues, flag related monitoring requirements, design assumptions, and risk assessments) Generate reports for Board review and external audits Remind investigators of follow-up timelines Document how concerns were resolved, creating institutional memory

But more importantly, it should make the system easy to use. If raising a concern requires navigating complex software or filling out a 10-page form, people won’t do it. The Bottom Line The Global Industry Standard on Tailings Management includes whistleblower protections not as a nice-to-have HR policy, but as a critical safety system. Because the standard’s ultimate goal - zero harm to people and the environment - depends on information flowing freely. Your monitoring instruments can detect physical changes. Your risk assessments can identify technical vulnerabilities. But only your people can detect organizational dysfunction, procedural shortcuts, communication breakdowns, and the subtle warning signs that something isn’t quite right. The hidden cost of silence isn’t measured in dollars - it’s measured in lives. The question isn’t whether you have a whistleblower policy in your compliance documentation. The question is: would someone at your operation, right now, feel comfortable telling you something you don’t want to hear? If the answer is anything other than “absolutely yes,” you have work to do. And that work might be the most important safety investment you make this year.

Does your GISTM compliance system make it easy to track, investigate, and act on concerns raised? [Learn how modern compliance tools can strengthen your whistleblower program]