Psychosocial Safety & WHS

Managing drug and alcohol risks in the workplace

Workplace drug and alcohol risks sit at the intersection of WHS, conduct and wellbeing. This briefing outlines a measured, policy-led approach.

By the AWS Editorial Team
Alcohol and drug testing equipment used in workplace safety risk management

Key points

  • Drug and alcohol risk sits at the intersection of WHS, conduct and worker wellbeing.
  • A clear policy supported by a WHS rationale is foundational before testing is contemplated.
  • Procedural fairness applies when a concern arises — notice, response and consistent treatment.
  • Support pathways and confidentiality should be designed into the response, not added later.
  • Document decisions, training and assurance to demonstrate the program is operating as intended.

Workplace drug and alcohol risks sit at the intersection of WHS, conduct and wellbeing. This briefing outlines a measured, policy-led approach.

This briefing forms part of the Psychosocial Safety & WHS stream in the AWS Information Centre. It focuses on practical, employer-facing guidance — not legal advice — and is written for HR, safety, risk and executive readers responsible for managing workplace issues.

Why drug and alcohol risk is a WHS question first

Drug and alcohol risk in the workplace is, before it is anything else, a work health and safety question. The organisation has a duty to provide a safe place of work; drug and alcohol impairment can compromise that duty across the workforce, not just for the individual concerned. Framing the program as a WHS control — rather than primarily a disciplinary one — produces clearer thinking about what is being managed and why.

The framing also matters for proportionality. A safety-critical operation will reasonably take a different approach to drug and alcohol risk than a low-risk office environment. The starting point for any program is a risk assessment specific to the organisation's actual work, not a generic policy borrowed from another setting.

Scope: safety-sensitive roles and the broader workforce

Most programs need to distinguish between safety-sensitive roles — where impairment carries a direct safety consequence for the individual, colleagues, customers or the public — and the broader workforce, where the consequence profile is different. The standards applied, the testing approach (if any), and the consequence framework can reasonably differ between the two.

The scope decision should be documented. Where the organisation decides that a role is safety-sensitive, the reasoning should be clear and the role should be on a list that is maintained as the organisation changes. Roles drift across that line as work changes, and a list that is set once and not revisited becomes inaccurate.

Policy foundations and consultation

A clear policy is the foundation. It should set out the WHS rationale, the standards expected, the testing approach (if any), the consequence framework, the support pathways and the privacy framework. Each of these elements is reinforced when the policy was developed with workforce consultation, particularly through health and safety representatives or committees.

Consultation also matters operationally. Policies that workers have not seen, have not been trained in, or do not believe are applied consistently are harder to operate. A policy that is well-communicated, with worked examples and clear expectations for managers, is materially more effective than a document that exists in the policy library.

Testing protocols where they are used

Testing programs — pre-employment, random, for-cause, post-incident — are tools, not the program. Where used, they should be designed against the policy and the WHS rationale, applied consistently across the population to which they apply, supported by trained collectors and accredited laboratories, and connected to a clear consequence framework.

Testing programs that are not supported by training, by consistent application or by a credible support framework rarely achieve their stated objectives. Programs that are well-supported, transparent and connected to genuine pathways for those who disclose issues tend to be both more effective and better received.

Impairment, observation and for-cause response

Impairment in the workplace can arise from drug or alcohol use, prescription medication, fatigue, illness or other factors. Programs that treat all of these only as drug and alcohol matters miss part of the safety picture. A fitness-for-work framework that encompasses the broader set is generally more useful and less stigmatising.

Where impairment is suspected, the immediate response is a safety response: remove the person from the safety-sensitive task, support them safely, and address the matter through the defined process. Trained observation, scripted manager guidance and a clear escalation pathway prevent the response from depending on improvisation in difficult moments.

Privacy and proportionate handling of information

Information collected through a drug and alcohol program — test results, disclosures, EAP engagement — is sensitive. Access should be limited to those who need it for a specific purpose, storage should be appropriate, and retention should be aligned with the privacy framework and the organisation's records policy.

Disclosure outside the program — to other managers, to other employees, to external parties — should occur only where there is a clear basis. Inappropriate disclosure damages trust in the program and exposes the organisation to a separate set of risks unrelated to the original matter.

Support pathways, EAP and consistency

Support pathways — employee assistance programs, return-to-work frameworks, treatment leave arrangements, supervisory adjustments — are part of the control environment, not an add-on. Workers who know that early disclosure carries support rather than only consequence are more likely to come forward, and that early engagement is itself one of the most effective controls.

Consistency in how the program is applied across the workforce is what gives the support pathway credibility. Where the framework is applied to some teams and not others, or to some grades and not others, the support component loses its meaning.

How AWS supports drug and alcohol programs

AWS supports employers in developing fit-for-purpose drug and alcohol programs, training managers in observation and response, and reviewing individual matters where independent input is useful. See related work on psychosocial safety and workplace advisory.

What employers should put in place

  • A risk assessment specific to the organisation's actual work, with safety-sensitive roles identified.
  • A clear policy developed with consultation, covering standards, testing, consequences, support and privacy.
  • Trained manager observation and a defined for-cause response that does not depend on improvisation.
  • Testing protocols (if used) that are consistent, accredited and connected to support pathways.
  • Privacy controls that limit access to information and align with the records framework.
  • A consistent consequence framework and credible support pathway applied across the workforce.

Frequently asked questions

Is workplace drug and alcohol testing always lawful?
Testing must be supported by policy, an applicable instrument and a clear WHS rationale. Each program should be designed and reviewed in light of jurisdictional requirements.
How should a positive result be handled?
Responses should follow a documented process that includes support pathways, procedural fairness and consistent application across the workforce.

Discuss this matter with AWS

Briefings can be scoped on a confidential basis. We respond within two business days.

Contact AWS