Loading...
safety

Drug & Alcohol Test Consent

Drug & Alcohol Test Consent is a workplace form for documenting notice, consent or refusal, and the start of chain of custody before a regulated test. Use it to capture the right participant details, specimen information, and signature in one auditable record.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Transportation And Logistics · Construction · Manufacturing · Healthcare · Utilities

Overview

Drug & Alcohol Test Consent is the intake form you use when a workplace test needs to be documented before collection begins. It captures the test notice, the basis for testing, the participant’s identity, the consent or refusal decision, and the first chain-of-custody details so the event can be tracked from the start.

This template is a good fit for regulated programs, including DOT-related workflows, as well as employer policies that require a signed acknowledgment before a specimen is collected. It is especially useful when you need a clean audit trail, a clear refusal path, and a consistent way to record who initiated the test and where it happened. The structure supports progressive disclosure, so refusal fields only appear when the participant declines, and test-basis fields can branch based on the reason for testing.

Use this template when you want one record that is easy to review, store, and hand off to the collector or compliance team. Do not use it as a general employee health form, a medical intake, or a disciplinary document. It is also not the right place to collect unnecessary PII, medical history, or broad statements about substance use. Keep the form focused on notice, authorization, specimen handling, and signature.

Standards & compliance context

  • For DOT-related workflows, align the notice, collection, and refusal language with DOT 49 CFR Part 40 and your employer’s testing program requirements.
  • Use data minimization by collecting only the participant details and test-event fields needed to document the consent and chain of custody.
  • If the form is public-facing or self-service, make required and optional fields clear and ensure the controls meet WCAG 2.1 AA accessibility expectations.
  • If the form is used in a health-related context, limit collection to the minimum necessary principle and avoid unrelated health disclosures.
  • Keep consent language specific to the test event so the signature reflects informed acknowledgment rather than a broad, open-ended authorization.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Test Notice

This section documents why the test is happening and confirms the participant saw the notice before collection starts.

  • I have read and understand the testing notice (required)

    You must acknowledge the notice before proceeding.

  • Reason for test (required)
  • If other, describe the reason
  • Test type (required)

Participant Information

This section identifies the person being tested with only the minimum necessary fields needed for matching and follow-up.

  • Full name (required)
  • Employee ID or badge number

    Use an internal identifier if available. Do not enter SSN.

  • Date of birth

    Collect only if required by your testing program or chain-of-custody process.

  • Phone number

Consent and Authorization

This section captures the participant’s decision and creates a clear path for either consent or refusal documentation.

  • Do you consent to the requested drug and/or alcohol test? (required)
  • Consent acknowledgment (required)

    By consenting, I authorize specimen collection, testing, laboratory analysis, and release of results to authorized parties as permitted by law.

  • Reason for refusal

    Provide a brief reason if the individual refuses the test.

  • Refusal acknowledgment

    I understand that refusal may have employment, regulatory, or safety consequences under applicable policy and law.

Chain of Custody Initiation

This section starts the specimen record so the collection event can be traced from the site, time, and collector onward.

  • Collection site (required)
  • Collection date (required)
  • Collection time (required)
  • Collector name (required)
  • Specimen type (required)

Acknowledgment and Signature

This section finalizes the record with a signed acknowledgment that ties the participant to the completed form.

  • I certify that the information provided is true and complete to the best of my knowledge (required)
  • Signature (required)
  • Date signed (required)

How to use this template

  1. 1. Set up the test notice section with the exact test basis options your policy allows, and use conditional logic so any “other” basis requires a short explanation.
  2. 2. Configure the participant information fields to collect only the minimum necessary identifiers, using the correct field types for date of birth, phone number, and employee ID.
  3. 3. Add consent and refusal paths so the form shows either consent language and signature capture or refusal reason and refusal acknowledgment, but not both at once.
  4. 4. Assign the form to the supervisor, coordinator, or collector who initiates the test, and require them to enter the collection site, date, time, collector name, and specimen type before submission.
  5. 5. Review the completed record for missing fields, confirm the acknowledgment text matches your policy, and route the submission into your audit trail or case file.

Best practices

  • Use dropdowns for test basis and specimen type so staff do not improvise wording during a time-sensitive collection.
  • Keep the participant section limited to fields needed to identify the person and contact them, and do not add medical questions unless they are required.
  • Show refusal fields only when the participant declines, so the form stays short for the common consent path.
  • Use a date picker for date of birth and collection date, and a time field for collection time, rather than free-text entry.
  • Include a plain-language disclosure that explains what the consent covers, who will receive the record, and what happens after submission.
  • Require the collector or coordinator to complete chain-of-custody initiation immediately after the notice is acknowledged, not later in the day.
  • Store the signed form in a controlled location with an audit trail so you can show who submitted it and when.
  • If you operate across sites, standardize site names and specimen types to reduce validation errors and cleanup work.

What this template typically catches

Issues teams running this template most often surface in practice:

The test basis is left vague, which makes later review harder and weakens the audit trail.
Participants are asked to type dates or specimen types into free text, creating inconsistent records and validation errors.
Refusal reasons are not captured when the participant declines, leaving the record incomplete.
Too many fields are marked required, which slows the process and increases abandonment at the collection site.
The form collects extra PII, such as unrelated medical details, that are not needed for the test event.
The chain-of-custody section is completed after the fact instead of at initiation, which creates timing gaps.
The acknowledgment text does not clearly explain what happens after submission, so participants are unsure who sees the record.

Common use cases

Fleet Safety Coordinator — DOT Pre-Employment Testing
A coordinator uses the form to document the applicant’s notice, consent, and collection-site details before the specimen is sent for testing. The template helps keep the record consistent across hiring locations and reduces missing chain-of-custody fields.
Plant Supervisor — Reasonable Suspicion Event
A supervisor records the test basis, the time the employee was notified, and the collector information after a safety concern is observed. Conditional logic keeps the form focused on the actual event instead of exposing every possible test path.
HR Compliance Lead — Return-to-Duty Workflow
An HR lead uses the template to capture the participant’s acknowledgment and the required specimen details before the return-to-duty process continues. The signed record becomes part of the audit trail for later review.
Third-Party Collection Site — Multi-Employer Intake
A collection site uses the same template for multiple client employers while standardizing fields like specimen type, collector name, and collection time. Dropdown validation and site naming controls help prevent inconsistent records across programs.

Frequently asked questions

When should this consent form be used?

Use it before a drug or alcohol test when you need a documented notice, consent decision, and chain of custody initiation. It fits pre-employment, random, reasonable suspicion, post-incident, return-to-duty, and follow-up testing when your policy or governing rule requires a signed record. It is not a substitute for the actual laboratory or collection-site procedures.

Does this template work for DOT-regulated testing?

Yes, the structure supports DOT-style documentation by capturing the test basis, collection details, and refusal acknowledgment. You should still align the wording and workflow with DOT 49 CFR Part 40 and your employer policy. If your program is non-DOT, you can simplify the notice language and remove any fields you do not need.

Who should complete this form?

The participant should review the notice and consent decision, while the collector or designated coordinator should complete the collection-site and chain-of-custody fields. A supervisor may enter the test basis for reasonable suspicion or post-incident testing if your process allows it. Keep roles clear so the record shows who confirmed what and when.

What happens if the participant refuses to sign or consent?

The form should still record the refusal reason, refusal acknowledgment, and the date and time of the refusal. That creates an audit trail for the employer and helps show that the participant was informed. Do not leave the refusal path blank; use conditional logic so the refusal fields appear only when needed.

What information should be collected, and what should be avoided?

Collect only the minimum necessary fields needed to identify the participant, document the test basis, and start the collection record. Avoid collecting extra PII such as SSN, medical history, or unrelated notes unless your policy and legal basis require them. If you collect contact information or date of birth, include a clear disclosure about how it will be used.

How often is this form used in practice?

It is used each time a test is initiated, not as a recurring annual form. Some organizations reuse the same template across multiple test events, while others tailor it by test type or jurisdiction. The key is that each submission should produce a single, time-stamped record tied to one test event.

Can this template be customized for different test types or sites?

Yes, the test basis, specimen type, and collection-site fields are good places to add conditional logic. You can also adapt the participant section for contractor, applicant, or employee workflows. If you operate multiple sites, add site-specific validation and dropdowns to reduce free-text errors.

How does this compare with an ad hoc email or paper signoff?

A structured form gives you consistent fields, validation, and an audit trail instead of scattered emails or handwritten notes. It also makes refusal handling, signature capture, and chain-of-custody initiation easier to standardize. That reduces missing information and makes the record easier to review later.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Drug & Alcohol Test Consent with your team — pricing built for small business.

Ask AI Product Advisor

Hi! I'm the MangoApps Product Advisor. I can help you with:

  • Understanding our 40+ workplace apps
  • Finding the right solution for your needs
  • Answering questions about pricing and features
  • Pointing you to free tools you can try right now

What would you like to know?