DOT Drug Testing Software: How to Manage Your Testing Program Without the Paperwork (2026)
Quick Answer
DOT drug testing software is a compliance platform that helps motor carriers and other DOT-regulated employers manage their federally mandated drug and alcohol testing program under 49 CFR Part 382 (FMCSA) and 49 CFR Part 40 (the DOT procedural rule covering all modes).
A DOT drug and alcohol testing program under 49 CFR Part 382 generates more individually tracked records per driver than any other area of FMCSA compliance. Pre-employment tests, random draws, post-accident tests, refusals, MRO results, SAP evaluations, return-to-duty plans, Clearinghouse queries — every one is a dated record with a retention requirement and an audit exposure. This guide explains exactly what software needs to do, what records it must manage, and how to run a compliant testing program without drowning in paper.
49 CFR
Part 382 governs FMCSA testing
50%
Minimum annual random testing rate
$16,550
Max penalty per violation
FileFlo
Tracks it all — $299/mo flat
In This Guide
What DOT Drug Testing Software Actually Does
Most carriers understand that they are required to drug test their drivers. Fewer understand the full scope of what that requirement generates in terms of records, ongoing management obligations, and audit exposure. DOT drug testing software addresses a specific gap: the testing itself is administered by your TPA or consortium, but the carrier remains 100% responsible for the records.
That distinction is where compliance failures happen. A carrier that enrolls in a consortium, pays the monthly fee, and assumes the consortium handles everything is likely operating with a recordkeeping deficiency that will surface in the first FMCSA compliance review. The consortium selects drivers for random testing and coordinates specimen collection. It does not maintain your FMCSA compliance records. That responsibility stays with you.
What the Software Must Track That Your TPA Does Not
Your TPA manages test scheduling, specimen collection, laboratory coordination, and MRO result routing. DOT drug testing software tracks your internal records: which drivers were tested and when, what the results were, whether annual rates were met, whether Clearinghouse queries were completed, whether any driver is on a follow-up schedule, and whether your documentation is complete enough to survive an FMCSA audit request. These are your obligations, not your TPA's.
DOT drug testing software serves four primary functions:
Record Storage and Organization
Centralized repository for chain-of-custody forms, MRO result letters, refusal documentation, SAP evaluations, and return-to-duty plans — organized by driver and retrievable by test type, date, or result status.
Random Pool Management
Tracks which drivers are in the random testing pool, logs each selection draw and its outcome, monitors annual testing rates against the 50% drug / 10% alcohol minimum, and documents the selection methodology.
Compliance Alerts and Reminders
Automated alerts when annual Clearinghouse full query is due, when a driver on a follow-up schedule has a pending test, when the annual MIS report deadline approaches, and when any driver's testing file is incomplete.
Audit Packet Generation
On-demand export of complete testing records per driver, by test type, or by date range — formatted for FMCSA compliance review or off-site investigation response.
For a complete overview of how drug testing compliance fits into the broader FMCSA compliance picture, see our guide on FMCSA compliance software.
The 5 Records Every DOT Drug Testing Program Must Maintain
The records required under 49 CFR § 382.401 and the DOT's procedural requirements under 49 CFR Part 40 can be grouped into five categories. Each category has its own retention schedule, access rules, and audit risk profile.
1. Test Results — Positive, Refusal, and Cancelled
5-Year RetentionRecords related to positive drug test results, alcohol confirmations at 0.04 BAC or above, and refusals to test must be retained for 5 years. This includes the chain-of-custody form, the MRO's written result, the laboratory's certified report, and any documentation of a refusal (including observed behaviors if applicable). Cancelled tests are retained for 2 years.
Audit risk:
A positive test without complete CCF and MRO documentation is treated as a recordkeeping violation in addition to whatever follow-up action was required. The test happened — but without the paper trail, you cannot prove the program responded correctly.
2. Negative Test Results
1-Year RetentionNegative drug test results and negative alcohol test documentation (results below 0.02 BAC on a screening test) must be retained for 1 year. Pre-employment negatives are critical — a driver who begins safety-sensitive functions before a verified negative result is a per-driver compliance violation, regardless of the outcome.
Common gap:
Carriers that rely on verbal confirmation from their TPA before a new driver's first trip, without retaining the written negative result, cannot prove the pre-employment test was completed and verified before safety-sensitive work began.
3. Random Pool Selection Records
2-Year RetentionDocumentation that random selection was performed using a scientifically valid methodology — including each selection draw, the names or IDs selected, the dates tests were administered, and a running count of tests completed against the annual rate requirement. This is how you prove you hit the 50% minimum drug testing rate at year-end.
Audit question:
An FMCSA auditor will ask: "How did you select which drivers to test, and can you show me the selection records and test dates?" A spreadsheet listing random tests you remember conducting is not a documented random pool.
4. SAP Evaluation and Return-to-Duty Documentation
5-Year RetentionWhen a driver tests positive or refuses, they must be immediately removed from safety-sensitive duties and referred to a Substance Abuse Professional (SAP). The SAP's initial evaluation, treatment/education recommendations, and clearance for return-to-duty must all be retained. The return-to-duty test result and the follow-up testing schedule (minimum 6 unannounced tests in the first 12 months) must be documented and monitored.
Ongoing obligation:
The follow-up testing schedule can extend up to 60 months. A driver who completes return-to-duty and returns to work does not exit the special monitoring process — they remain on it until the follow-up schedule is complete.
5. Annual MIS Summary Data
2-Year RetentionThe Management Information System (MIS) annual report summarizes your testing program results for the prior calendar year. The underlying data used to compile it — test counts by type, results, refusals — must be retained for 2 years. The filed report itself should be retained as proof of timely submission to FMCSA.
Deadline:
MIS reports for the prior calendar year are due March 15. Late submission is a § 382.403 violation. Carriers that do not track test counts throughout the year often scramble in February and March to reconstruct data from TPA records.
Are Your Fleet's Docs Current?
Free 3-minute check shows exactly which medical cards, CDLs, and DQF docs are expired or at risk. No signup. No email. Just answers.
Random Pool Management: What the Software Must Handle
FMCSA requires motor carriers to conduct random drug testing at a minimum annual rate of 50% of the average number of driver positions subject to testing (49 CFR § 382.305). Alcohol testing is required at a minimum annual rate of 10%. These are minimums — FMCSA can increase them based on industry-wide data, and has done so in prior years.
The random selection must use a scientifically valid method — the regulation specifically requires equal probability of selection in each draw. Manual systems like "picking a name out of a hat" or rotating through an alphabetical list do not satisfy the scientifically valid methodology requirement and do not provide the documentation an auditor needs.
The Rate Calculation Is Not As Simple As It Sounds
The 50% rate applies to the average number of driver positions, not just the number of drivers you have at year-end. If you had 10 drivers in Q1, hired 2 in Q2, terminated 1 in Q3, and ended the year with 11 — your average driver count is calculated quarterly. Underestimating the required number of tests is one of the most common ways carriers discover they are short of the annual requirement in December.
Effective random pool management in software covers the full cycle:
Random Pool Management: Full Cycle
Pool setup and enrollment. Every driver in a safety-sensitive CDL position is added to the random pool. New hires are added before their first safety-sensitive trip. Terminated drivers are removed from the active pool.
Annual rate calculation. Track average driver count quarterly. Calculate the minimum number of drug tests and alcohol tests required for the year. Set selection quotas per quarter or per draw cycle.
Documented random selection draws. Each draw produces a timestamped record of the selection methodology used, the date of the draw, and which driver IDs were selected. This document must survive an audit years later.
Immediate notification tracking. Record the date and time each selected driver was notified. Drivers must proceed immediately to testing with no advance notice. Delays between selection and notification are a documentation gap.
Test completion and rate tracking. Log the test completion date and result for each selected driver. Running count of tests completed vs. required to confirm the annual rate will be met before year-end.
Year-end rate reconciliation. Confirm total drug tests conducted equals or exceeds 50% of average driver count, alcohol tests equal or exceed 10%. Produce summary for MIS report filing.
Pre-Employment, Post-Accident, and Reasonable Suspicion Test Tracking
Random testing generates the highest volume of records, but the non-random test types carry higher individual compliance risk. A missed pre-employment test or a post-accident test that was not conducted within the required timeframe are both per-instance violations with no defense. The driver either tested before safety-sensitive work, or they did not.
Pre-Employment Testing
Required for every driver before the first performance of a safety-sensitive function (49 CFR § 382.301). A driver must receive a verified negative result — not just complete a test, not just provide a specimen — before beginning work. The carrier must retain both the pre-employment test result and, for drivers transferring from another DOT-regulated employer, the prior employer's drug testing records obtained under 49 CFR § 40.25.
What software tracks:
- - Pre-employment test ordered date vs. driver start date
- - Test completion and MRO result verification date
- - Clearinghouse pre-employment full query completion
- - Prior employer drug test history request status under § 40.25
Post-Accident Testing
Post-accident testing under 49 CFR § 382.303 has strict time windows that make it the highest-pressure test type to administer. Drug testing must be completed as soon as practicable; if it cannot be completed within 32 hours, the carrier must document why and cease attempts. Alcohol testing must be completed within 2 hours if practicable, and no later than 8 hours — if not completed within 2 hours, the delay must be documented.
Post-accident testing triggers:
- - Any accident involving a fatality (always required)
- - Accident where driver received a citation AND bodily injury requiring immediate medical treatment away from scene
- - Accident where driver received a citation AND vehicle required towing
What software tracks:
Accident date/time, test ordered date/time, test completion date/time, result, and documentation of any delay reason if the 2-hour or 8-hour alcohol windows were not met.
Reasonable Suspicion Testing
Reasonable suspicion testing under 49 CFR § 382.307 requires a trained supervisor to make a contemporaneous written record of the specific observations justifying the test — the driver's appearance, behavior, speech, or body odors indicating drug or alcohol use. The documentation must be completed within 24 hours of the observed behavior or before the results are released, whichever is earlier.
What software tracks:
- - Supervisor observation documentation date/time
- - Supervisor training certificate status (required under § 382.603)
- - Test ordered and completed dates
- - Result and follow-up actions if positive
How audit-ready are you for DOT drug testing software?
Free 3-minute FMCSA audit readiness check. No signup, no credit card. See exactly which documents are expired or at risk.
Related DOT Compliance Guides
DOT Compliance Checklist (47 Items)
DOT ComplianceFailed DOT Audit Recovery
DOT ComplianceSurprise FMCSA Audit Prep
DOT ComplianceOwner Operator Compliance Checklist
DOT ComplianceExplore FileFlo
MIS Annual Report: What You Must Submit to FMCSA
The DOT Management Information System (MIS) annual report is required under 49 CFR § 382.403. Motor carriers must submit MIS data for the prior calendar year to FMCSA by March 15 of each year. The report summarizes your testing program statistics — not individual results, but aggregate counts by test type and outcome.
What the MIS Report Requires You to Report
Driver Count Data
- - Number of drivers subject to testing
- - Average number of driver positions (for rate calculation)
- - Number tested by test type
Random Test Data
- - Number of random drug tests conducted
- - Number of random alcohol tests conducted
- - Positives, negatives, and refusals by substance
Other Test Types
- - Pre-employment tests: conducted and results
- - Post-accident tests: conducted and results
- - Reasonable suspicion tests: conducted and results
- - Return-to-duty and follow-up tests
Result Breakdown
- - Positive results by drug type (marijuana, cocaine, opioids, PCP, amphetamines)
- - Refusals to test
- - Cancelled tests
Carriers with fewer than 50 drivers may submit MIS data on paper using FMCSA's MCS-5 form. Carriers above that threshold submit electronically. The key data problem most carriers encounter is that they do not track test counts throughout the year — they attempt to reconstruct them from TPA records in February. Software that counts tests in real time, organized by type and result, makes MIS reporting a 20-minute exercise rather than a two-week data recovery project.
Failure to File MIS Is Its Own Violation
Under 49 CFR § 382.403, failure to submit an MIS report by the March 15 deadline is a violation subject to civil penalties. During a compliance review, auditors verify whether MIS reports were filed for the years within the review scope. A carrier that says "we did the tests but didn't file the report" has both a documentation failure and a filing failure — two separate violation categories.
FMCSA Drug and Alcohol Clearinghouse: What Software Must Track
The FMCSA Drug and Alcohol Clearinghouse, established under 49 CFR Part 382, Subpart G, became mandatory on January 6, 2020. It is a federal database that records drug and alcohol program violations by CDL holders — positive tests, refusals, and certain other violations — and makes that information available to current and prospective employers conducting required queries.
Motor carriers have two distinct Clearinghouse obligations that generate trackable compliance records:
Query Obligations
Pre-Employment Full Query
Required before a CDL driver performs a safety-sensitive function for the first time. A full query requires the driver's electronic consent in the Clearinghouse. The carrier cannot allow safety-sensitive work until a negative (no record) result is received.
Annual Limited Query
Required at least once per year for every driver in active service. A limited query does not require driver consent each time (covered under a consent agreement) but returns only a "record" or "no record" result. If a record exists, a full query must follow.
Reporting Obligations
Positive Test Results
MROs are required to report positive drug test results and refusals directly to the Clearinghouse within 2 business days of verification. Employers must report actual knowledge of driving under the influence and other qualifying events.
Return-to-Duty Completion
When a driver with a Clearinghouse violation completes the SAP-directed process and returns to safety-sensitive duty, the employer must report the return-to-duty test result and initiate the follow-up testing schedule in the Clearinghouse system.
Compliance software must track query due dates for every active driver. The annual limited query requirement means that a carrier with 20 drivers has 20 annual Clearinghouse query deadlines rolling through each calendar year — each tied to the driver's start date or the date of their last annual query. Missing an annual query is a compliance violation; driving a driver who has an unresolved Clearinghouse entry is a more serious one.
Clearinghouse Violation: The Carrier's Liability
If a driver with an unresolved Clearinghouse violation — a positive test they have not completed the SAP return-to-duty process for — is allowed to perform safety-sensitive functions, the carrier bears full regulatory liability regardless of whether they knew about the violation. The annual query requirement exists precisely so carriers cannot claim ignorance. A carrier that missed the annual query for a driver later found to have a Clearinghouse entry has both a query violation and a prohibited use violation.
Supervisor Training Records: The Often-Missed Compliance Requirement
Motor carriers are required under 49 CFR § 382.603 to ensure that supervisors who are authorized to determine whether a driver is subject to reasonable suspicion testing receive a minimum of 60 minutes of training on controlled substances and 60 minutes of training on alcohol — 2 hours total, completed before exercising this authority.
This training requirement generates a compliance record that most carriers do not track consistently: the supervisor training certificate or completion record. In a compliance review, an investigator who finds that a reasonable suspicion test was ordered by a supervisor for whom no training record exists will cite both the missing training record and question the validity of the reasonable suspicion determination.
Supervisor Training Compliance Checklist
60 minutes of controlled substances training completed
Required under § 382.603(a) — covers the physical, behavioral, speech, and performance indicators of probable drug use
60 minutes of alcohol misuse training completed
Required under § 382.603(b) — covers indicators of probable alcohol misuse
Training completion certificate retained per supervisor
Must be available for FMCSA inspection. No specific retention period stated — retain for duration of supervisor's tenure at minimum
Training occurred before first reasonable suspicion determination
Timing matters — a supervisor who orders a reasonable suspicion test before completing training has not satisfied § 382.603
Compliance software that tracks supervisor training certificates alongside drug testing records closes a gap that paper-based systems routinely miss. When an auditor asks "who authorized this reasonable suspicion test and can you show me their training documentation," the answer should take 30 seconds, not an archive search.
Prior Employer Drug Testing Records: The § 40.25 Requirement
Before a new driver can perform safety-sensitive functions, motor carriers must investigate the driver's prior drug and alcohol testing history under 49 CFR § 40.25. This requires contacting each DOT-regulated employer the driver worked for in the past 2 years and requesting specific testing records.
What § 40.25 Requires You to Request from Prior Employers
- Alcohol test results showing a concentration of 0.04 or greater in the past 2 years
- Positive controlled substance test results in the past 2 years
- Refusals to be tested in the past 2 years
- Other violations of Part 382 subpart B in the past 2 years
- Documentation of RTD completion if any violation in the past 2 years resulted in a return-to-duty process
The prior employer must respond within 30 days. The prospective employer must make "good faith efforts" to obtain the information — meaning documented attempts if the prior employer does not respond. Carriers must retain the request, the prior employer's response (or documentation of non-response), and the driver's written authorization for the release.
This creates a per-driver compliance record that must exist before the driver's first trip. Compliance software that includes a prior employer query tracking workflow — documenting when the request was sent, when it was responded to, and what the response contained — closes a gap that most carriers leave as an informal email thread or a verbal check with a dispatcher.
For small fleets that primarily hire experienced drivers moving between carriers, the § 40.25 prior employer process is one of the highest-frequency compliance interactions in the drug testing program. Software that manages this per-driver, per-hire generates the paper trail that survives an audit 2 years later.
Consortium vs. TPA: Which One Needs the Software
The distinction between a consortium and a TPA matters for how you think about your recordkeeping obligations. Understanding it also clarifies why outsourcing to a consortium does not eliminate your need for compliance software.
Consortium
Multiple employers pool their drivers into a combined random testing pool managed by a consortium administrator. Each employer's drivers have equal probability of selection from the combined pool. The consortium calculates and conducts the random draws, ensuring each employer meets their proportional share of the annual minimum rate.
Best for:
Owner-operators and fleets under 5-10 drivers where maintaining a statistically valid independent random pool is impractical
What the consortium does NOT provide:
Your FMCSA-required compliance records. The consortium provides selection and testing services — you must maintain your own test records, retention-compliant files, and audit packet capability.
TPA (Non-Consortium)
A TPA manages your testing program independently — collection scheduling, laboratory coordination, MRO result routing — but your drivers are in their own separate pool. You are responsible for all random selection documentation, rate calculations, and internal recordkeeping.
Best for:
Fleets with 10+ drivers who want administrative support without pooling drivers with other companies
What the TPA does NOT provide:
Proof to FMCSA that your program was administered correctly. The TPA has records — but they are the TPA's records, not your compliance file. You need your own.
Both arrangements require internal recordkeeping software. The common misconception is that paying a consortium or TPA means compliance is handled. It is not. The TPA handles testing logistics. You handle regulatory compliance — which means maintaining the records, monitoring the rates, filing the MIS report, and producing the documentation if FMCSA asks for it.
For a deeper analysis of the structural differences and which option is right for your fleet size, see our guide on DOT drug testing consortium vs. TPA.
FileFlo vs. Other DOT Drug Testing Platforms (2026)
Most competitors in this space are TPAs first and software second — they sell testing services and bundle a portal as a side product. FileFlo is purpose-built compliance recordkeeping software designed to live alongside any TPA or consortium relationship. Here is how the major platforms compare on the records carriers actually need for an FMCSA drug and alcohol audit.
| Platform | Clearinghouse Query Mgmt | Random Selection Mgmt | Pre-Employment Tracking | Post-Accident Workflow | 49 CFR 382 Coverage | Pricing | Free Trial |
|---|---|---|---|---|---|---|---|
| FileFlo | Yes — full + annual limited query tracking, alerts | Yes — pool roster, draws, 50%/10% rate tracking | Yes — blocks first-trip until verified negative | Yes — 2hr / 8hr / 32hr window documentation | Full — Subparts B–G + Part 40 | $299/mo flat, unlimited drivers | Yes — 5 days, no card |
| Foley | Yes — bundled with their TPA service | Yes — consortium-managed | Partial — within their hiring product | Limited — testing only, not records workflow | Drug & alcohol module only | Per-driver/month tiered bundles | No |
| CarrierShield | Yes — query logs | Yes — consortium pool | Limited — manual entry | Limited — no window enforcement | Drug & alcohol focused | Per-driver/month + setup fees | No |
| National Drug Testing | Bundled with TPA | Yes — pool only | Test scheduling, not records | Test coordination only | Drug & alcohol services only | Per-test pricing + monthly fee | No |
| Drug-Free Compliance | Manual query support | Yes — consortium | Manual onboarding | Phone-based coordination | Drug & alcohol focused | Per-driver/month consortium fee | No |
| TPAs (generic) | Varies — query service | Pool management (no carrier-side records) | Test scheduling | Collection only | Testing logistics, not recordkeeping | Per-test + monthly admin fee | No |
| Paper / manual files | Spreadsheet, no alerts | Manual log, no scientifically valid method | Email confirmation, no enforcement | Notes in driver file | As good as your filing | Time cost | N/A |
Comparison reflects publicly available platform features as of May 2026. Most competing platforms bundle drug testing services with a portal — FileFlo is the carrier-owned recordkeeping layer that lives alongside any TPA or consortium and produces the records FMCSA actually requests during a compliance review.
What FMCSA Auditors Look for in Your Drug Testing Program
During a compliance review, the drug and alcohol testing compliance factor is evaluated under 49 CFR Parts 382 and 40. The investigator is not looking for a perfect record — they are looking for a documented program. A carrier that tested every driver as required but has no records to show for it fails. A carrier with one historical positive test that is fully documented with CCF, MRO result, SAP referral, RTD test, and follow-up schedule may pass this factor entirely.
Understanding what auditors specifically request during the drug and alcohol review helps you build a records system that matches the audit structure:
Drug & Alcohol Compliance Review — Common Document Requests
Written drug and alcohol testing policy
Required under § 382.601. Must be provided to each driver before testing begins. Policy must cover the testing program, prohibited conduct, consequences of violations, and information resources.
Pre-employment test results for all active drivers
Verified negative result and Clearinghouse full query for each driver before their first safety-sensitive function. Investigators verify that the test date precedes the first trip date in employment records.
Random selection documentation for the review period
Selection draw records, pool roster at time of each draw, test completion dates, and annual rate calculation showing the 50% drug / 10% alcohol requirement was met.
MIS annual reports for years within the review scope
Filed MIS reports with confirmation of timely submission. Investigators may cross-reference the MIS data against the test records to verify consistency.
Any positive test files with complete RTD documentation
For any positive test in the review period: CCF, MRO result, immediate removal documentation, SAP referral, SAP evaluation, treatment/education completion, RTD test, and follow-up schedule — all must be present.
Annual Clearinghouse query records for active drivers
Clearinghouse query history showing that limited annual queries were conducted for all active drivers within the required 12-month window. Investigators have direct access to verify this in the Clearinghouse system.
The key insight from this audit structure: every document request maps to a specific record that must exist in your compliance system. An auditor who cannot find a required record in the first review will systematically check whether the same record is missing for other drivers. A single missing pre-employment test suggests a systemic gap. A missing MIS report for one year suggests it was never filed.
How Investigators Use the Clearinghouse During a Review
FMCSA investigators have direct access to the Clearinghouse database during a compliance review. They can verify your query history independently — they can see whether your annual limited queries were conducted on time and whether any driver in your fleet has an unresolved Clearinghouse entry. If a driver in your fleet has a Clearinghouse violation that you did not detect because you missed an annual query, the investigator will find it. The query record requirement is not a documentation formality — it is a compliance obligation with real-time verification capability.
The Most Common DOT Drug Testing Violations Cited in Compliance Reviews
FMCSA compliance review data consistently shows the same drug testing violations appearing across carriers of all sizes. Understanding the most common violations helps you prioritize which gaps to close first and which features to require in your compliance software.
§ 382.301 — No pre-employment drug test before first safety-sensitive function
Most frequently found when carriers rely on verbal TPA confirmation rather than written verified result. Software fix: require verified negative result document upload before driver's first trip date can be entered.
§ 382.305 — Failure to meet minimum annual random testing rate
Carriers that do not track their running rate during the year discover in December that they are short. A 12-driver fleet needs at least 6 random drug tests in the calendar year. If draws were delayed or tests were missed, catching up in December on a full test cycle is operationally difficult. Software fix: quarterly rate tracking with alerts when on track to fall short.
§ 382.401 — Failure to maintain required test records for the specified retention period
Missing chain-of-custody forms, MRO result letters not on file, no record of random selection draw. Most commonly found in carriers that rely entirely on their TPA's records. Software fix: systematic upload of each test result document at time of receipt, not retrospectively during an audit response.
§ 382.403 — Failure to submit MIS annual report by March 15
Late filing or non-filing. Often discovered because the carrier did not track test counts throughout the year and could not compile accurate data in time. Software fix: running MIS data aggregation so the report is a data export on March 1, not a reconstruction effort.
§ 382.407 / § 40.25 — Failure to request prior employer drug testing records
Common in fleets with high driver turnover that hire experienced drivers quickly. The 2-year prior employer query must be completed before first safety-sensitive function. Software fix: required workflow step at driver onboarding that blocks first-trip entry until § 40.25 request is documented as sent.
How FileFlo Manages Your DOT Drug Testing Program
FileFlo is built around the premise that compliance document management should work the same way for a 3-truck owner-operator as it does for a 40-truck regional carrier — complete, organized, and auditable at any moment. The drug testing module reflects that: it covers all six test types, manages the random pool, tracks MIS data, and integrates drug testing records into the broader compliance picture alongside your DQFs and vehicle maintenance files.
FileFlo Drug Testing Features
- All six test types per driver: Pre-employment, random, post-accident, reasonable suspicion, return-to-duty, and follow-up — each with its own document storage, date tracking, and result status
- Random pool management: Driver enrollment and removal, documented selection draws with timestamps, quarterly rate tracking against the annual 50% drug / 10% alcohol minimum, and year-end rate reconciliation
- Document storage with retention enforcement: Chain-of-custody forms, MRO result letters, SAP evaluations, and return-to-duty plans stored with automatic retention period tracking and destruction scheduling
- Clearinghouse query tracking: Records pre-employment full queries and annual limited queries per driver, with alerts when annual Clearinghouse checks are due
- Follow-up schedule monitoring: Tracks return-to-duty drivers through their complete follow-up testing schedule, alerting on upcoming required tests so no follow-up window is missed
- MIS report data aggregation: Running count of test types and results throughout the year so MIS filing in March is a data export, not a research project
- Audit packet generation: On-demand export of all drug testing records per driver, organized by test type and date, formatted for FMCSA compliance review response
- Integrated with DQF management: Drug testing records appear alongside DQF elements in the driver dashboard — one view shows a driver's complete compliance status, not just one dimension of it
At $299/month flat for unlimited drivers, FileFlo's per-driver cost decreases as your fleet grows. A 10-driver fleet pays $29.90 per driver per month for the full compliance platform. There are no per-test charges, no per-driver seat fees, and no annual contract.
See FileFlo In Action
Try our interactive demo with real compliance scenarios. See exactly how FileFlo works. Takes 2 minutes, no signup required.
Key Takeaways
- Your TPA does not maintain your FMCSA compliance records. Whether you use a consortium or a standalone TPA, the carrier is responsible for retaining test records, documenting the random selection process, and producing records for FMCSA on request. Outsourcing the testing does not outsource the recordkeeping obligation.
- FMCSA requires random drug testing at 50% of average driver count annually. That is 50% of the average — carriers who calculate against current headcount at year-end often discover they are short. Track the running rate throughout the year.
- Failure to maintain required drug testing records is a per-record violation under 49 CFR § 382.401. A missing chain-of-custody form or undocumented MRO result is not a technicality — it is a compliance violation with penalty exposure.
- Post-accident testing has the strictest time windows in the regulation. Alcohol testing within 2 hours (document if you cannot), no later than 8 hours. Drug testing within 32 hours or cease attempts and document why. Missing these windows is a violation regardless of the test result.
- The MIS annual report is due March 15 every year. The underlying test count data used to complete it must be retained for 2 years. Carriers who do not track test counts throughout the year scramble to reconstruct data before the deadline.
- Return-to-duty drivers require ongoing monitoring for up to 60 months. The follow-up testing schedule does not end when the driver returns to work — it continues for the duration prescribed by the SAP. Missing a follow-up test is a separate violation from the original positive.
- Annual Clearinghouse queries are required for every driver. Full queries at pre-employment, limited queries annually. A driver with an unresolved Clearinghouse entry who continues in safety-sensitive service is an active violation. Tracking query completion dates is part of the drug testing program record set.
DOT Drug Testing Software: FAQ
Answers to common questions about DOT drug testing records, random pool management, MIS reporting, and what software must do to keep your program audit-ready.
DOT drug testing software is a compliance platform that helps motor carriers and other DOT-regulated employers manage their federally mandated drug and alcohol testing program under 49 CFR Part 382 (FMCSA) and 49 CFR Part 40 (the DOT procedural rule covering all modes). It tracks every test type per driver — pre-employment, random, post-accident, reasonable suspicion, return-to-duty, and follow-up — stores chain-of-custody documents and MRO results, manages the random testing pool, and generates the data needed for the annual MIS report. The core function is ensuring that all testing records exist, are complete, and are retrievable for FMCSA audits.
Under 49 CFR § 382.401, motor carriers must retain: positive test results and refusals for 5 years; negative and cancelled test results for 1 year; records related to the testing process (SAP evaluations, return-to-duty plans, follow-up schedules) for 5 years; and random pool selection documentation and annual MIS summary data for 2 years. Employer records must be kept at a principal place of business and be available for FMCSA inspection within 48 hours of a request. The regulation specifies what can be shared with other parties — notably, prior employers can receive certain records under § 40.25.
FMCSA requires random drug testing at a minimum annual rate of 50% of the average number of driver positions subject to testing (49 CFR § 382.305). Alcohol testing is required at a minimum 10% annual rate, though FMCSA can lower this based on industry-wide positive test rates. The random selection must be made by a scientifically valid method — typically a computer-based random number generator — and must ensure that each driver has an equal probability of selection in each period. Drivers selected must proceed immediately to testing with no advance notice. Pool management software handles the selection draws, documents the process, tracks which drivers have been tested in the current period, and ensures the carrier meets the annual rate requirement.
The DOT Management Information System (MIS) annual report is a summary of your drug and alcohol testing program results submitted to FMCSA each year by March 15 for the prior calendar year. It covers the number of drivers in your random pool, the number of each test type conducted, positive results, refusals, and cancelled tests — broken down by substance (drug vs. alcohol). FMCSA uses MIS data to calculate industry-wide positive rates, which in turn determine the minimum random testing rate for the following year. Carriers with fewer than 50 drivers may submit MIS data on paper; larger carriers submit electronically. The underlying data used to complete the MIS report must be available for audit for 2 years.
Software cannot pass an audit for you — but organized records can prevent you from failing one. The most common drug testing audit failure is not a positive test or an active violation: it is missing documentation. Auditors request chain-of-custody forms, MRO result letters, random pool selection records, and annual MIS summaries. Carriers that outsource to a TPA without maintaining their own internal records frequently discover during an audit that they cannot produce required documents. Software that stores all test records, tracks MRO results, and generates exportable audit packets organized by compliance factor puts you in the best possible position when FMCSA requests records.
A Third-Party Administrator (TPA) is any company that provides drug and alcohol testing services to DOT-regulated employers — including collection scheduling, laboratory coordination, and MRO result routing. A consortium is a specific type of TPA arrangement in which multiple employers — typically small carriers — pool their drivers together into a single random testing pool. The consortium manages the random selection draws and ensures each employer meets the minimum testing rate based on their proportional share of the combined pool. Owner-operators and very small fleets almost always use a consortium because maintaining a random pool with fewer than 5 drivers is statistically unworkable. Both options use a TPA for administration, but a consortium adds the pooling component.
Retention requirements under 49 CFR § 382.401 are: 5 years for records of positive drug test results, alcohol confirmations of 0.04 BAC or greater, refusals to test, and documentation related to SAP evaluations and return-to-duty processes. 2 years for random pool records and MIS annual summaries. 1 year for negative and cancelled drug test results and documentation of negative alcohol tests. Records must be kept at the principal place of business and available for FMCSA inspection on request. If a carrier uses a TPA or consortium, the carrier remains responsible for ensuring these records exist and are accessible — the TPA is not your FMCSA filing agent.
Yes. FileFlo tracks all six DOT test types per driver, stores chain-of-custody documents, MRO result letters, and refusal documentation. The platform manages your random pool — recording selection draws, test completion dates, and annual rate tracking against your 50% requirement. FileFlo generates an audit packet organized by driver that includes all drug and alcohol testing records with dates, results, and document status. Expiration reminders alert you when annual Clearinghouse queries are due, when follow-up testing schedules need to be actioned, and when any documentation is incomplete. At $299/month flat, there are no per-driver charges regardless of how many drivers are in your testing pool.
Related Articles
Continue learning about compliance and operational excellence
DOT Drug Testing Requirements for Small Fleets
The complete guide to 49 CFR Part 382 requirements for carriers with fewer than 10 drivers — random pool options, consortium enrollment, record retention, and the owner-operator exception.
Return-to-Duty DOT Drug Test: The Complete Process
What happens after a positive DOT drug test: the SAP evaluation, treatment, return-to-duty test, and follow-up testing schedule — and the documentation required at each step.
DOT Drug Testing Consortium vs. TPA: Which Do You Need?
How consortiums and TPAs differ, when owner-operators and small carriers must use a consortium, and what records each arrangement requires you to maintain independently.
Stop Rebuilding Your Drug Testing Records Before Every Audit
FileFlo tracks all six DOT test types, manages your random pool, monitors Clearinghouse query due dates, and generates complete audit-ready drug testing records per driver — organized by type and date. Combined with DQF management, vehicle maintenance compliance, and CSA monitoring, it is the complete FMCSA compliance platform for carriers under 50 trucks. Flat $299/month, no per-driver fees, no annual contract.
$299/month — No annual contract — 5-day free trial