Key Takeaways:
- Post-incident testing needs to happen as soon as reasonably practicable, because delay directly weakens what the result can prove.
- A non-negative screening result is not proof of impairment or fault, and it must go through confirmatory testing before any conclusions are drawn.
- The collection process itself, not just the test result, is what determines whether the outcome is defensible if challenged.
- Documentation should be built into the process from the first minute after the incident, not reconstructed afterwards from memory.
An incident on-site changes everything about how fast a business needs to move. Amid first aid, incident reports, and notifying the right people, drug and alcohol testing has to happen too, and it has to happen correctly. Get the timing or the paperwork wrong, and a genuinely necessary test can end up unusable if it is ever challenged.
This guide walks through when post-incident testing should happen, how to run the process properly, and what documentation actually needs to exist afterwards, using workplace compliance testing kits that meet Australian Standards.
What Actually Triggers a Post-Incident Test, and What Doesn’t
Post-incident testing applies after a specific workplace event, an injury, a near miss, property damage, or any incident where impairment is a reasonable line of inquiry. It differs from random testing, which happens on a scheduled or unannounced basis regardless of any event, and from reasonable suspicion testing, which is triggered by observed behaviour rather than an incident itself.
The trigger should be defined clearly in the workplace drug and alcohol policy before any incident occurs, not decided on the spot. A policy that specifies exactly which categories of incident require testing removes ambiguity and protects against claims that testing was applied selectively or unfairly to a particular individual.
Why Testing Speed Directly Affects Whether a Result Holds Up
The phrase “as soon as reasonably practicable” appears in most workplace drug and alcohol policies for a specific reason: detection windows are finite, and the value of a test result depends heavily on how closely it reflects the person’s state at the time of the incident.
Alcohol, in particular, metabolises quickly, meaning a breath test taken hours after an incident may show a materially lower reading than one taken immediately. Some drugs have similarly narrow windows in saliva compared to urine, which can affect what a delayed test is actually able to establish.
A test conducted well after the incident is more vulnerable to challenge, since it becomes reasonable to ask whether the result truly reflects the person’s condition at the relevant time, or something that changed in the hours since. This is precisely why testing speed is not just a procedural nicety, it is part of what makes a result meaningful in the first place.
Practically, this means having testing kits and a trained collector available on-site or on-call, rather than relying on an appointment booked for later in the day.
Choosing the Right Test Method for an Incident Situation
Different methods suit different incident scenarios, and the right choice depends on what happened and what needs confirming.
- Breath alcohol testing: the fastest option for alcohol, with fuel-cell technology giving an immediate, reliable reading on-site, making it the appropriate first step whenever alcohol involvement is a possibility.
- Saliva testing: suits incidents where a fast result for a broad drug panel is needed, since it reflects more recent use and the collection is quick and less invasive than urine.
- Urine testing: offers a longer detection window and remains the gold standard for many workplace policies, though it takes slightly longer to administer and requires appropriate facilities for a compliant collection.
- Combination testing: many post-incident situations benefit from testing for both alcohol and drugs simultaneously, since ruling one out does not rule out the other.
Whichever method is used, it should be the one specified in the workplace policy, applied consistently, rather than chosen ad hoc based on what happens to be on hand.
Running the Collection So the Process Stays Defensible
The result is only as reliable as the process used to obtain it. A properly conducted collection protects both the business and the employee being tested.
Collection should be carried out or supervised by a certified collector, following the procedure set out in the relevant Australian Standard for the test type. The person being tested should be given privacy appropriate to the method, while maintaining the integrity checks the standard requires, such as tamper-evident seals on urine samples and correct chain of custody documentation from the moment of collection.
Any adulteration checks, such as temperature strips on urine samples, should be completed and recorded at the time, not assumed or skipped under incident-related time pressure.
Consistency matters here as much as correctness. A process followed properly for one employee and loosely for another creates grounds to challenge the fairness of the outcome, regardless of what the actual result shows.
What a Non-Negative Result Means, and What It Doesn’t
An initial screening result showing non-negative is not the same as a confirmed positive, and it is certainly not proof that a substance caused or contributed to the incident. Initial on-site screens are designed to be fast and sensitive, which means they can occasionally flag results that don’t hold up under laboratory confirmation, including cross-reactivity with legitimate prescription medications.
A non-negative screen should trigger confirmatory testing at a NATA-accredited laboratory before any employment decision is made. This is also the point at which a Medical Review Officer typically becomes involved, reviewing the laboratory result alongside any disclosed prescription medications before the result is finalised.
Even once confirmed, a positive result establishes that a substance was present, not automatically that it impaired the person’s ability to perform their role or that it caused the incident in question. Treating presence and impairment as interchangeable is one of the more common mistakes employers make when responding to post-incident results.
The Documentation That Actually Protects Your Business
This is where post-incident testing most often falls short, not in the testing itself but in what gets recorded around it.
- Incident report timing: record exactly when the incident occurred and when testing was initiated, since the gap between the two is often the first thing scrutinised if a result is challenged.
- Consent and notification records: document that the employee was informed testing was required under policy, and that consent, where applicable, was properly obtained.
- Chain of custody documentation: a complete, signed record of who collected the sample, how it was sealed, and who handled it at every stage until laboratory receipt.
- Collector certification records: confirmation that the person conducting the collection held current, valid certification at the time of the test.
- Result notification and confidentiality records: documentation of who was informed of the result, when, and how confidentiality was maintained throughout.
- Retention: records should be stored securely for the period specified in company policy or relevant industrial instruments, not discarded once the immediate matter is resolved.
Building these records as the process happens, rather than reconstructing them afterwards from memory, is what separates a defensible process from one that falls apart under scrutiny.
Where Employers Commonly Get Post-Incident Testing Wrong
A few mistakes show up repeatedly. Testing gets delayed while other incident response tasks take priority, quietly weakening the result before it is even collected. Employers sometimes treat a non-negative screening result as final, acting on it before confirmatory testing has occurred. Documentation gets treated as an afterthought, assembled days later from fragmented notes rather than captured in real time. And in some cases, the testing method used is whatever was convenient rather than what the policy specifies, which undermines consistency across incidents and employees.
Each of these is avoidable with preparation done well before any incident occurs, which is really the core of good post-incident testing: the process is designed in advance, not improvised under pressure.
Building Post-Incident Testing Into Your Existing Policy, Not Around It
Post-incident testing works best as a clearly defined part of an existing drug and alcohol policy, not a separate process invented after something goes wrong. That means specifying triggers, timeframes, methods and documentation requirements in advance, training collectors properly, and keeping compliant workplace compliance testing kits on hand so testing can happen immediately rather than being delayed by logistics.
Getting the timing right protects the value of the result. Getting the process right protects its integrity. Getting the documentation right protects the business if any of it is ever
