When a head contractor or project owner sets drug and alcohol testing requirements for a project, those requirements must flow down to every subcontractor and their workers. In theory, this is straightforward: the subcontract includes a clause requiring compliance with the project’s drug and alcohol management plan, and the subcontractor complies. In practice, alignment is far more complex — and the gaps between project requirements and subcontractor practices are where compliance failures most commonly occur.

This article examines how to set, verify, and enforce testing standards across your subcontractor network, and what to do when standards fall short.

Setting Minimum Standards in Contracts

The contractual framework is the foundation of subcontractor testing alignment. Drug and alcohol testing requirements should be addressed explicitly in every subcontract — not as a vague reference to “compliance with applicable policies” but as specific, measurable obligations.

Essential Contractual Provisions

• Policy compliance — The subcontractor must comply with the project’s drug and alcohol management plan, a copy of which should be attached to or referenced in the contract.
• Testing types and frequency — Specify the types of testing required (pre-access, random, for-cause, post-incident) and any minimum frequencies.
• Standards — Reference the applicable Australian Standards (AS/NZS 4308, AS 4760) and any project-specific requirements that exceed those standards.
• Approved providers — If the project mandates specific testing providers or laboratories, state this clearly.
• Reporting requirements — Define what information the subcontractor must provide to the head contractor (testing status, compliance rates, incident notifications) and in what format.
• Consequence management — Specify how positive results, refusals, and non-compliance by the subcontractor or its workers will be managed.
• Audit rights — Reserve the right to audit the subcontractor’s testing records, procedures, and provider arrangements.
• Indemnity — The subcontractor should indemnify the head contractor for any loss arising from the subcontractor’s failure to comply with testing requirements.

The Verification Process

Contractual provisions are only effective if they are verified. Many head contractors assume that including testing requirements in the contract is sufficient, only to discover during an incident investigation that the subcontractor was not testing at all.

Pre-Mobilisation Verification

Before a subcontractor’s workers arrive on site, verify:

• The subcontractor has a drug and alcohol policy that meets or exceeds project requirements
• All workers have valid pre-access test results within the required timeframe
• The subcontractor’s testing provider is approved or meets the project standard
• The subcontractor has a process for ongoing random and for-cause testing

Request documentary evidence for each item. A signed declaration is a start, but certificates, test records, and provider agreements provide stronger assurance.

Ongoing Monitoring

Verification is not a one-time event. Throughout the project, monitor subcontractor compliance through:

• Regular reporting — Require monthly or quarterly compliance reports showing the number of tests conducted, results summary, and any incidents.
• Site audits — Conduct periodic audits of subcontractor testing records during site visits. This can be integrated into broader safety audits.
• Random spot checks — Occasionally request testing records for specific workers to verify that records exist and are complete.
• Participation in project-wide testing — Include subcontractor workers in project-wide random testing events to provide an independent verification layer.

When Subcontractors Fall Short

Despite clear contractual requirements and verification processes, subcontractors sometimes fail to meet testing standards. Common shortfalls include:

• Workers arriving on site without valid pre-access tests
• Failure to conduct random testing at the required frequency
• Using a non-approved testing provider
• Incomplete or missing chain of custody documentation
• Failure to report positive results or incidents

Graduated Response

A graduated response framework provides clarity for both parties:

• First instance (minor) — Written notification of the non-compliance, requirement to rectify immediately, and request for a corrective action plan.
• Repeated or significant non-compliance — Formal breach notice under the subcontract, meeting with subcontractor management, and potential restriction of site access until compliance is demonstrated.
• Persistent or serious non-compliance — Suspension or termination of the subcontract, in accordance with contractual provisions.

Document every instance of non-compliance and every action taken in response. This record protects the head contractor’s position if the subcontractor disputes the consequences.

Mutual Recognition

Where a subcontractor has a robust testing program that meets or exceeds project requirements, mutual recognition can reduce duplication and administrative burden. Under a mutual recognition arrangement:

• Tests conducted under the subcontractor’s own program are accepted as meeting project requirements
• The subcontractor provides evidence of their testing standards (policy, provider accreditation, sample records) for verification
• The head contractor retains the right to conduct additional testing at any time
• Mutual recognition is documented in writing and can be revoked if standards are not maintained

Mutual recognition works best between organisations with mature testing programs and established relationships. It should not be extended to subcontractors whose programs have not been verified.

Shared Platforms

The most efficient approach to subcontractor testing alignment is a shared digital platform where all testing records for the project are maintained in a single system. Benefits include:

• Real-time visibility — The head contractor can see the testing status of every worker on the project, regardless of employer.
• Automated compliance tracking — The system automatically flags workers whose testing status has expired or who are overdue for random selection.
• Consistent documentation — All records are created in the same format using the same workflow, eliminating the variability that comes from each subcontractor using its own system.
• Reduced administrative burden — Subcontractors do not need to generate separate compliance reports; the data is already in the system.
• Access control — Each subcontractor can access only their own workers’ detailed records, while the head contractor has an overview of all workers.

Communication and Culture

Technical systems and contractual provisions are necessary but not sufficient. Achieving genuine alignment requires a culture of shared commitment to testing standards:

• Include testing requirements in pre-start meetings and toolbox talks.
• Explain the “why” behind the requirements — worker safety — not just the contractual obligation.
• Recognise and commend subcontractors who consistently meet or exceed standards.
• Address non-compliance promptly and constructively, focusing on improvement rather than punishment (unless the non-compliance is serious or repeated).

A project where testing standards are understood, respected, and consistently applied by all parties is a safer project — and a more defensible one.

Need a platform that gives you visibility across your entire subcontractor network? Visit fairtest.com.au to start your free trial and bring all your project testing data into one place.