An employee drug testing policy template gives employers a starting point for explaining who may be tested, when testing can occur, and how results are handled. A template is not a plug-in legal document: employers need to adapt it to their workforce, locations, testing program, and applicable requirements. Use the guide below to build a clear process, then have qualified compliance or legal professionals review it before use.
Discuss your workplace testing program
What should an employee drug testing policy cover?
A useful policy answers practical questions before an employee or supervisor has to make a decision under pressure. It explains the employer’s purpose and process without promising a particular outcome or implying that every role is governed by the same rules. Include the policy in a broader workplace safety and compliance program, and make sure its language matches the procedures actually used by the organization.
At a minimum, address the policy’s purpose, who is covered, testing circumstances, notice and consent, collection and result handling, confidentiality, prescription or other medication concerns, consequences, and how the policy will be reviewed. The Tennessee Department of Labor and Workforce Development offers sample substance-abuse policy statements that employers can use as reference material, but a sample is not a substitute for reviewing the rules that apply to your locations and workforce: Tennessee sample substance abuse policy statement.
How should you define the policy’s purpose and scope?
Start with a short statement about why the organization maintains a testing policy. Keep it tied to real business needs, such as maintaining a safe workplace, meeting applicable program requirements, and applying workplace procedures consistently. Avoid broad claims that testing guarantees safety or prevents every incident.
Then identify the people and settings covered. Be precise about whether the policy applies to applicants, current employees, temporary workers, contractors, or only specified categories. If different groups are handled under separate procedures, say so and point readers to those procedures. For example, an employer may have one general workplace policy and separate rules for workers in regulated, safety-sensitive positions. Do not suggest that a general company policy replaces a role-specific regulatory program.
- State the covered entities and worker categories, including any stated exclusions.
- Describe the locations, worksites, and job classifications included.
- Explain whether separate procedures apply to regulated or safety-sensitive roles.
- Identify the department or role responsible for policy administration, using a functional title rather than a person’s name when possible.
Employers with multiple sites should check that the policy can be applied consistently while allowing for jurisdiction-specific addenda. A central policy can set common expectations, but local requirements may call for changes to notices, testing circumstances, collection methods, or response steps. A policy should tell supervisors where to find the correct version, not leave them to guess.
Which testing circumstances should the policy explain?
List only the testing circumstances the employer actually uses and is authorized to use. Common categories may include pre-employment testing, random testing, post-incident testing, reasonable-suspicion testing, return-to-duty testing, and follow-up testing. Which of these apply depends on the employer, job, location, and any governing program. Define each term in plain language and describe who may authorize the test.
For instance, a post-incident rule should explain the process for deciding whether an event falls within the policy and how the employer will arrange testing. It should not imply that a test automatically establishes the cause of an incident. For suspicion-based testing, explain the internal escalation and documentation steps, and train designated supervisors on the procedure. Avoid vague language that gives managers unlimited discretion or encourages inconsistent treatment.
| Policy element | What the policy should clarify | Practical drafting check |
|---|---|---|
| Pre-employment | Which applicants or roles are covered, and when testing is required in the hiring process. | Match the written rule to the actual offer and onboarding workflow. |
| Random | Whether a random program applies, which group is included, and how selections and notices are administered. | Document the program method and any separate regulatory requirements. |
| Post-incident | Which defined events may trigger testing and who reviews the circumstances. | Separate testing decisions from assumptions about fault or impairment. |
| Reasonable suspicion | Who can refer an employee, what observations are documented, and how the referral is reviewed. | Use training and consistent records; do not rely on labels or rumor. |
| Return-to-duty or follow-up | Whether these steps apply and which process governs them. | Coordinate with any applicable regulated program and qualified advisors. |
This table is a drafting aid, not a list of testing rights or legal permissions. If the employer operates a regulated program, use the governing program’s terminology and procedures rather than relying on a general template. Patriot’s overview of DOT and non-DOT compliance can help employers distinguish the service context, while the organization should confirm its own obligations with qualified advisors.
What should notice, consent, and refusal language say?
Explain how people will learn about the policy and how the employer will document acknowledgment. Tell applicants and employees when they receive the policy, where they can ask questions, and whether a separate authorization is required for a particular process. Have counsel review consent forms and disclosures for the relevant jurisdictions and screening activity. A signature acknowledging receipt should not be described as a waiver of rights unless qualified counsel has approved that specific language.
Set out the process for a person who declines or does not complete a required test. Be careful not to label every delay, collection difficulty, or refusal the same way. Applicable rules and the circumstances matter. State what the employer will do next, who will review the situation, and how the person can raise an immediate concern. Avoid writing a blanket penalty that could conflict with a controlling program or local law.
A sample acknowledgment can confirm that the person received the policy, understands how to ask questions, and knows that procedures may differ for certain roles. The sample language should be reviewed alongside the policy itself. The Tennessee Department of Labor and Workforce Development also provides a sample policy statement intended as a starting point for employers: sample policy statement for a drug-free workplace program. Adaptation and legal review are essential; the document does not establish requirements for every employer or state.
How can a policy describe collection and chain of custody?
Employees should know what to expect after a test is ordered. Describe how the employer directs a person to an authorized collection process, what identification or paperwork may be needed, and where questions or collection problems should be reported. Do not include technical instructions that conflict with the laboratory, collection provider, or applicable program’s procedures.
Explain that the collection process uses required documentation to track the specimen and related records. The specific chain-of-custody steps depend on the testing method and applicable procedures. Name the role responsible for coordinating the process, such as a designated employer representative or HR contact, and make clear that supervisors should not handle or discuss sensitive records beyond their assigned duties.
Set a process for unusual events, such as a missed appointment, an incomplete collection, or a question about how the collection was conducted. Identify who receives the report and who decides on next steps. Avoid promising that every issue can be resolved in the same way; an employer may need to follow the instructions of the collection provider or a controlling program.
How should confidentiality and results be handled?
Write down who may receive testing information, why access is limited, where records are stored, and how a result is communicated. Use role-based access: a manager may need a work-status update, while detailed medical or testing information may require narrower access. Coordinate the policy with privacy, record-retention, and information-security procedures. Do not promise absolute confidentiality if disclosure may be required by law, a legitimate business process, or an applicable program.
Clarify how a result is reviewed before an employment decision is made. If a medical review officer, laboratory, or other qualified reviewer is part of the applicable process, describe that role accurately and follow the program’s procedure. Give the employee a clear contact path for questions or for providing relevant information. Avoid declaring that an initial finding is automatically a final determination.
Employers should use consistent, limited-access records rather than informal notes spread across email, chat, or personnel files. Decide who maintains documentation, how long it is retained under applicable requirements, and how access is reviewed when responsibilities change. Confirm that all vendor and internal processes match the promises in the policy.
How should the policy address prescriptions and other medication concerns?
Do not ask employees to disclose more medical information than the process requires. A policy can explain that an employee who has a concern about a medication or test result should use the designated confidential review channel. It should not tell a supervisor to collect medication details or decide whether a prescription is legitimate. Route health-related information to the person or professional authorized to review it, and keep it separate from routine management discussions.
Use neutral language. The existence of a prescription, a lawful medical treatment, or a test result should not be reduced to a simple assumption about impairment or job fitness. Employers should have qualified counsel review the policy and any accommodation or fitness-for-duty process for the jurisdictions and positions involved. If an employee raises an immediate safety concern, follow the employer’s established safety and escalation procedures rather than improvising a medical assessment.
What consequences and follow-up steps belong in the policy?
Describe the range of potential responses without guaranteeing a particular outcome in every case. Depending on the applicable rules and circumstances, the employer may need to consider a confirmed result, refusal, policy violation, or required return-to-duty process. Explain who reviews the information and who makes decisions. Avoid language that suggests an unreviewed result alone always dictates discipline.
If the employer offers an opportunity to explain, appeal, or participate in a support or return-to-duty process, state the steps and limits clearly. Do not promise treatment, continued employment, or reinstatement unless the organization is prepared and legally able to honor that commitment. Ensure the policy aligns with employment agreements, collective bargaining obligations where relevant, and separate regulatory procedures.
Employers can compare the policy to their broader workplace drug testing policy practices and review drug testing methods and what to expect when aligning employee-facing explanations with the operational process. These resources do not replace advice tailored to a particular location or workforce.
How can employers review state and local requirements?
Before adopting the policy, list every state and locality where covered employees work, including remote or mobile workers where relevant. Have qualified compliance or legal counsel assess the rules that apply to each location, job category, and testing circumstance. Requirements can differ, and the correct approach may depend on details such as the reason for testing, the worker’s role, and the employer’s program.
Review related requirements too. Depending on the employer and situation, these may include applicable federal or state program rules, privacy and employment laws, notice requirements, record handling, collective bargaining terms, and rules affecting applicants or employees. Do not assume a policy written for one state can simply be used nationwide. Maintain a current master policy with reviewed local addenda when needed.
For employers using a written substance-abuse program, the Associated General Contractors of America has published an employee acknowledgment sample that can be used as a reference: AGC employee policy acknowledgment sample. It is a sample document, not a universal legal form. Confirm that any reference document remains appropriate for the employer’s industry, jurisdiction, and procedures.
What checklist can you use before rollout?
- Confirm the policy has a specific purpose and clearly identifies covered workers, roles, and locations.
- List only testing circumstances the employer uses, and define them in plain language.
- Identify who can authorize testing, answer questions, review records, and make employment decisions.
- Check that notice, acknowledgment, consent, collection, and result-review workflows match actual practice.
- Explain limited access to records, secure handling, and retention under applicable rules.
- Address how employees raise concerns about collection, results, or medication through a confidential route.
- Describe potential consequences without making automatic promises or conclusions.
- Review state and local requirements, regulated-program procedures, and role-specific addenda with qualified advisors.
- Train supervisors and HR staff; set a date and owner for periodic review and updates.
Once the document is approved, distribute the same current version to the people who need it and remove outdated copies from routine use. Explain where the policy is stored and whom employees should contact. A well-written template only works when the organization’s actual practice, records, and training follow it.
Talk with Patriot about employer testing support
Frequently asked questions
Can an employer use one drug testing policy in every state?
A common policy can provide a consistent framework, but employers should not assume identical wording works everywhere. Have qualified advisors review the laws and program requirements for each location and add jurisdiction-specific language where needed.
Does an employee acknowledgment form replace the policy?
No. An acknowledgment records receipt or understanding of a policy, as defined by the employer’s process. It does not explain all procedures on its own or replace required notices, authorizations, or legal review.
Should a policy list every substance or test method?
Include accurate information that matches the employer’s actual testing program and applicable rules. If the details vary by position or program, explain where the employee can find the correct procedure rather than using one broad statement that could mislead.
How often should employers review the policy?
Set a recurring review schedule and revisit the policy when the organization changes its workforce, locations, testing process, or governing requirements. Assign an owner to check that written language, forms, training, and vendor procedures remain aligned.
This template framework is educational information, not legal advice; employers should adapt it with qualified compliance guidance before putting it into effect.