Your drug and alcohol policy probably works fine.

Until 6am on a Tuesday when your operations manager rings asking if they should send someone home right now.

Most policies I see aren't badly written. They're thorough. Comprehensive, even. The documentation covers testing procedures, consequences, appeals processes, confidentiality requirements. All correct. All necessary.

But when I ask HR teams what happens the day after a positive test, there's usually a pause.

Because the policy tells them what to do. It doesn't prepare them for the conversation with someone they've worked alongside for eight years, or how to balance duty of care when the site's already running three people short.

The gap between written and ready

I've reviewed hundreds of workplace drug and alcohol policies over the years. The quality varies, but most of the recent ones are solid. They reference the right legislation. They outline clear procedures. They specify what constitutes reasonable suspicion.

What they don't do - what they can't do, really - is prepare someone for that specific moment when protocol meets person.

The operations manager who rings at 6am isn't asking about policy clauses. They're asking: Do I send them home now or wait until the shift handover? Who else needs to know? What do I say to the rest of the team who've noticed something's off? Can I tell them why someone's leaving mid-shift, or does confidentiality mean I say nothing and let speculation fill the gap?

Those questions don't have policy answers. They have situation answers.

What confidentiality actually means at 6.15am

Confidentiality looks straightforward in a policy document. A paragraph. Maybe two. Clear obligations. Legal requirements.

Then someone tests positive, and confidentiality stops being a clause and becomes the only thing holding everything together.

The person who tested positive has a right to privacy. The team has a right to work safely. The manager has a duty of care to both. And somewhere in that tension, someone needs to make decisions that protect everyone without violating anyone.

Most policies address confidentiality as a legal requirement - which it is. What they don't address is how it works when the warehouse team has already noticed their colleague was pulled aside for twenty minutes, when the shift is three people short and everyone can see who's missing, when the manager needs to explain a sudden absence without explaining anything at all.

That's not a documentation problem. That's a preparation problem.

The difference between tested and pressure-tested

A policy is tested when HR reviews it annually and confirms it still reflects current legislation.

A policy is pressure-tested when it's used at 6am by someone who hasn't slept properly, who's worried about the person involved, who's trying to keep a site running safely, and who needs to make a decision in the next ten minutes that could have legal, safety, and human consequences.

Most policies pass the first test. Not all of them survive the second.

The ones that do have usually been through it before. Someone's already made that 6am call. Someone's already navigated the gap between what the handbook says and what the situation needs. And critically, someone's taken the time afterwards to work out what would have made it easier.

If your policy hasn't been pressure-tested yet, it will be. The question isn't whether that call comes, it's whether the person taking it feels prepared when it does.

What prepared actually looks like

It's not a longer policy document.

It's the operations manager knowing exactly who to ring when they're standing in the car park at 6am with a situation unfolding. It's the HR team having already talked through what "reasonable suspicion" looks like in practice, not just in principle. It's everyone understanding that confidentiality isn't about saying nothing, it's about knowing exactly what you can say and to whom.

Prepared means the person making the decision has seen the scenario before, even if not this exact version of it. They've thought through the competing priorities. They've practised the conversation. They know what comes next, not just what comes now.

That doesn't happen by accident, and it doesn't come from reading the policy one more time.

It comes from working through the messy bits before they're urgent. From talking about what happens when someone you've worked with for years tests positive and you need to have a conversation that's both compassionate and clear. From understanding how to maintain confidentiality while still managing a team who've noticed something's changed.

The work nobody sees

The effective part of workplace drug and alcohol screening isn't the test itself. It's what happens in the seventy-two hours afterwards.

How the initial conversation is handled. How quickly the situation is resolved. How confidentiality is maintained while the process runs. How the person involved is supported. How the team is managed. How the site keeps running safely while all of this unfolds.

None of that appears in the policy. Most of it happens in the background, handled by people who know what they're doing because they've either done it before or been properly prepared for it.

When it's done well, nobody notices. The situation is resolved, duty of care is maintained, confidentiality holds, and work continues. When it's done badly, everyone notices - even if they don't know the details.

Making the policy work when it matters

The policies we help businesses develop aren't dramatically different from the ones already in place. Longer, sometimes. More specific in places. But the real difference isn't the document.

It's the management awareness workshops where we work through the scenarios that don't fit neatly into clauses. The 6am calls. The complicated situations. The moments where three different responsibilities pull in different directions and someone still needs to make a decision.

It's the incident protocols that account for what the documentation doesn't say. Who rings who. What gets communicated when. How confidentiality is maintained in practice, not just in principle.

It's the support that stays available when things get complicated. When the straightforward case becomes something messier. When the person who needs to make the call isn't sure what the right answer is.

The work isn't writing better policies. Most of those are already fine.

It's making sure they hold up when someone rings at 6am and needs an answer now.

If your workplace drug and alcohol policy hasn't been pressure-tested yet, we can help you prepare before that call comes.

Our management awareness workshops cover the practical realities of handling positive tests, maintaining confidentiality under pressure, and balancing competing duties of care. Contact Lemon Cherry to discuss how we support businesses in making their policies work when it matters most.