top of page

DnA Testing. Risk Management or Morality Police?

Oct 23
4 min read

Once upon a time, drug and alcohol testing had a fairly straightforward purpose.

Keep people who were drunk or stoned well away from work where they could hurt themselves or someone else.


Fair enough, right? Nobody wants someone who's three sheets to the wind operating a 50-tonne loader. Entertaining as the TikTok reel might be, there's a pretty compelling risk management argument for making sure that doesn't happen.


But somewhere along the way, things got complicated. We've gone from managing impairment at work to worrying about what substances people are taking.


And those are two very different things.


These days, the person triggering a drug screen might not be the bloke who had a big weekend. It might be the bloke who took his prescribed pain medication so he could get out of bed and come to work. It could be the woman taking medication to manage her long-term chronic condition, the person on anxiety medication or the manager taking prescribed ADHD medication. As the list of medicines that 'could cause impairment' grows, so too does the list of people affected.


Some medications can impair people. Some people experience little or no impairment. For others, managing their condition with medication makes them more capable of working safely.


So what do we do? Ban everyone taking something that might affect their performance?


The monthly lottery nobody wants to win

Imagine taking medication prescribed by your doctor, following the instructions and getting on with your job. In some cases a note from the GP has confirmed that the medication will not cause impairment when taken at the prescribed rate.


Then comes random drug testing day. Every month, you wonder whether this is the month your name will be called.


You know your medication might trigger a non-negative screening result for whatever reason. Depending on the workplace policy, you could be stood down while your sample goes to the laboratory. Note from the GP or not. (because who's to say you were taking it at the right amount? or that it was just an over the counter cold remedy, or a false positive on a known medication or any number of other reasons for a non-negative result)


Eventually, the lab results come back and a negative result is confirmed. Job done. All sorted, right?


Except everyone remembers that you were taken off the job because you 'failed' a drug test. Not that the initial screen wasn't a confirmed result. Not that you hadn't necessarily done anything wrong.


Just that you failed and just like that you've become 'that person'.


The test might clear your name. The rumour doesn't necessarily follow.


And that applies to the companies that bother to send the sample to the lab. Many companies stop at the screening test and take a non-negative as a 'positive'. No questions, zero tolerance call, yadayadayada.


All in the name of health and safety.


Meanwhile, back on site...


Old mate's had three hours' sleep. The supervisor's running on stress and caffeine. The operator's mind is somewhere completely different. The apprentice is battling the flu but turned up because they're short-staffed and the mechanic's running on energy drinks and cold-and-flu tablets, hoping one cancels out the other.


No positive drug tests there.


Doesn't mean they're fit for work.


And here's another problem.


If telling your employer about your medication might mean being stood down, questioned or becoming the subject of the smoko conversation, how keen are you going to be to disclose it?


And just like that, we've made silence safer than honesty.

Which is a pretty spectacular own goal for something that's supposed to keep people safe.


So what are we trying to achieve?

None of this means we should abandon drug and alcohol testing. It has a place, particularly in safety-critical work. Nor does having a prescription give someone a free pass to work while impaired.


But testing is a risk management tool. Not a verdict on someone's character.

A non-negative screening result isn't a confirmed positive. A confirmed positive doesn't necessarily establish impairment. And a negative result certainly doesn't guarantee someone is fit for work.


Imagine if we had a reliable way to determine whether someone was fit to perform their job safely, regardless of what might be affecting them?


How much of our current substance testing would we still need? If someone is fit to do the job, what safety purpose is served by investigating what they took last hour, last night or last weekend?


The goal isn't to catch people doing something we disapprove of. It's to stop people getting hurt.


We're testing for what we can detect, rather than what we need to know to manage a risk. A positive drug test doesn't necessarily mean someone is impaired. And a negative one doesn't mean they're safe to work. If we're serious about managing risk, we need to stop confusing the two.


There's a hell of a difference between keeping people safe at work and interfering with people's right to manage their own health and private life.

Comments


Liked that? Sign up for Straight-talking H&S for contractors. No spam.

bottom of page