Prevention FAQ — FMCSR 382.405: Annual Summary Report

Inspectors verify that your carrier has prepared and maintained a calendar-year summary of all controlled-substance and alcohol testing results. They will request:

• A consolidated report covering January through December
• Records showing all DOT-mandated tests (pre-employment, random, reasonable-cause, return-to-duty, follow-up)
• Test dates, driver names, results (negative/positive), and substance type
• Certification that the report was completed and retained

The inspector does not need to cite 382.405 frequently — across our 13 million inspection records, we see zero citations for this violation in the last 12 months. However, the absence of enforcement does not mean non-compliance is invisible. Audits often surface incomplete or missing annual summaries during broader controlled-substance program reviews. Have a complete, signed summary ready before each calendar year closes.

This is a program-level compliance task, not a vehicle inspection item. Instead, build a monthly and year-end checklist into your safety management workflow:

Monthly (ongoing documentation):

• Verify all test results from the prior month are logged in your tracking system
• Confirm chain-of-custody documents are filed
• Flag any missing lab reports or driver-signed consent forms

Quarterly (compliance check):

• Audit your tracking system for data gaps
• Reconcile the number of tests conducted with your testing plan
• Ensure each positive result shows proper follow-up action

Year-end (30 days before calendar closes):

• Compile final annual summary report
• Have compliance officer or medical review officer sign and date it
• Store in your controlled-substances program file

Make these tasks non-negotiable calendar events. Assign ownership to a specific role — safety director or HR lead — and require written sign-off.

Drivers carry: Nothing specific to 382.405. However, they should understand that all test results (negative and positive) become part of your annual summary, so they may see requests to acknowledge or sign records.

Carrier retention (minimum 1 year):

• Original or certified copies of all test results
• Chain-of-custody forms
• Driver consent and authorization forms
• Laboratory reports with specimen IDs and analyst initials
• Medical review officer (MRO) reports and determinations
• Documentation of any positive confirmations and split-specimen requests
• A signed, dated annual calendar-year summary report
• If positive: return-to-duty evaluations and follow-up test schedules

Best practice: Store the completed annual summary in your FMCSA-regulated document file, separate from routine HR records. Label it with the year and the compliance officer's signature. During roadside inspections, when asked to produce your testing program, lead with the annual summary — it demonstrates organization and intent to comply.

Although we record zero citations for 382.405 in the past 12 months, our data reveals the controlled-substances violations that co-occur most frequently in the same category:

• Use of drugs (392.4A-DOSP): 3,947 citations, 95.9% OOS rate
• Use of drugs (392.4(a)): 3,919 citations, 96.9% OOS rate
• Use of drugs (392.4A-DOSU): 1,648 citations, 98.5% OOS rate

This pattern suggests that failure to document and summarize tests often goes undetected until a driver tests positive. Once a positive result surfaces, inspectors investigate the carrier's entire testing program, including whether an annual summary was prepared. Root causes typically include:

1. Decentralized testing records — multiple sites or contractors without consolidated tracking
2. Manual spreadsheets — prone to omission or loss of older records
3. No designated owner — testing responsibility falls between HR and safety with no accountability
4. Lab report delays — waiting for confirmatory results and delaying entry into the annual tally

Prevent by assigning a single compliance lead and using a dedicated testing-management system.

382.405 is a documentation and record-keeping violation, not a vehicle defect. It does not trigger an out-of-service order. However, if a driver was cited for a controlled-substance or alcohol violation (e.g., 392.4), the citation review should include verifying that your testing program is intact:

Post-citation verification steps:

1. Pull the driver's test history from your tracking system
2. Confirm all prior results (pre-employment, annuals, random, reasonable-cause) are documented
3. If this is a positive result, verify the MRO follow-up and return-to-duty plan are in the file
4. Run a completeness audit: count total tests conducted that year and compare to your annual summary draft
5. Have your compliance officer sign off that the annual summary, once finalized, will include all records

Before the driver returns to safety-sensitive duty: Confirm the return-to-duty process has been completed (if positive) and that no testing backlogs exist. Then resume normal controlled-substance monitoring per your policy.

Even though we see zero citations for 382.405 in the last 12 months, an inspector audit or internal compliance review that flags missing annual summaries warrants immediate action:

Immediate response (within 7 days):

• Notify your MRO and any testing contractors that the annual summary is under review
• Compile all testing records from the calendar year in question
• Identify any missing or delayed lab reports and request them immediately
• Cross-check driver names and test dates against your payroll to catch records for terminated employees

Root-cause analysis (within 14 days):

• Interview the person responsible for collecting and storing test results
• Review your testing policy for gaps in documentation procedures
• Audit your tracking system for data-entry errors or omissions
• If using multiple contractors, confirm they provide timely reports

Corrective action (ongoing):

• Draft and sign the completed annual summary
• Update your testing policy to require monthly reconciliations
• Implement a centralized, auditable testing database
• Train HR and safety staff on the annual summary deadline (Dec. 31)
• Schedule quarterly compliance reviews going forward

FMCSR 382.405 carries a CSA severity weight of 2 — a low weight that reflects the violation's procedural nature rather than immediate driver or vehicle safety impact. It does not trigger an out-of-service determination, so it will not directly damage your Vehicle Maintenance BASIC.

However, 382.405 resides in the Controlled Substances/Alcohol category, which is part of your broader safety profile. If an inspector cites 382.405 alongside drug-use violations (e.g., 392.4(a), which carries a 96.9% OOS rate and 3,919 citations), the cumulative pattern will elevate your BASIC score and may trigger a FMCSA warning letter or audit.

The strategic implication: Maintain a defensible annual summary as insurance against follow-up scrutiny. When an inspector finds your testing program well-organized and your annual summary complete, they are less likely to investigate further or cite co-occurring documentation gaps. Think of 382.405 compliance as a preventive control that protects your entire controlled-substances program from escalating enforcement.

Build a controlled-substances compliance curriculum that goes beyond driver education:

For safety managers and compliance leads:

• The requirement to prepare an annual calendar-year summary and the deadline (Dec. 31)
• How to aggregate results from multiple testing contractors or labs
• Proper document retention (minimum 1 year) and secure storage
• What to do if a lab report is delayed or missing
• How to reconcile test counts against your written random-testing plan

For HR and medical review officers:

• Chain-of-custody procedures and why they matter
• The difference between negative, positive (unconfirmed), and confirmed results
• Return-to-duty and follow-up testing documentation requirements
• How to track and retain MRO reports and determinations
• Record retention timelines and legal holds if a driver is litigating

For front-line supervisors:

• When to trigger reasonable-cause testing and how to document the reasonable cause
• How to inform a driver of a positive result respectfully and professionally
• Their role in ensuring timely referrals to the MRO

Delivery: Host an annual session in November, before year-end, and have each attendee sign a training log. Include a quiz on annual summary requirements.

DataQs challenges are appropriate when you believe an FMCSA safety event record is factually inaccurate or procedurally improper. For 382.405:

Consider a challenge if:

• You can produce a complete, signed annual summary that was in your possession before the inspection and covers the alleged compliance gap
• The inspector misidentified which calendar year was incomplete (e.g., cited 2025 when you had prepared 2024)
• You can show that all test results cited as "missing" were actually on file and provided to the inspector; the citation reflects a miscommunication

Do not challenge if:

• Your annual summary is incomplete, unsigned, or missing entirely
• Test records exist but were not compiled into a formal summary report
• You cannot produce contemporaneous documentation that the summary existed at the time of inspection

Practical note: We record zero 382.405 citations in the last 12 months, so DataQs challenges for this code are extremely rare. Focus instead on building a complete, auditable file now so that if an inspection surfaces the issue, you have evidence of good-faith compliance. A strong record often prevents citation in the first place.

Audit cadence: Quarterly internal reviews + one comprehensive annual audit (by Nov. 30).

Justification: Our inspection data shows zero citations in the last 90 days, zero in the last 12 months. This low enforcement does not indicate a non-issue; rather, it suggests that carriers are either compliant or violations are caught during broader program audits. A quarterly rhythm catches drift early; the comprehensive annual audit ensures your final summary is complete and defensible before Dec. 31.

Quarterly audit (15–30 minutes per review):

• Log all test results received that quarter
• Verify each driver's name, test date, and result type
• Confirm consent forms and chain-of-custody are present
• Check that any positive results triggered MRO follow-up
• Flag any missing lab reports and follow up with contractors

Annual comprehensive audit (2–4 hours, by Nov. 30):

• Pull the complete list of all drivers tested that year
• Cross-check against your written random-testing plan to confirm sample size
• Verify every test result (negative and positive) is documented
• Ensure all positive confirmations have MRO reports and return-to-duty plans
• Draft and sign the final annual summary
• Store in your program file and keep until Dec. 31 of the following year

Assign ownership: Your compliance officer or safety director must own and sign each audit report.