Prevention FAQ — FMCSR 391.27: Driver Violation Notification

Fleet guidance on preventing 391.27 citations through documentation practices, driver training, and audit cadence based on 13M+ inspection records.

Severity Weight
2
OOS Eligible
No
BASIC Category
Driver Fitness
Code System
FMCSR
Code:
391.27
Code System:
FMCSR
BASIC Category:
Driver Fitness
OOS Eligible:
No
Severity Weight:
2
Violation Group:
BASIC 3

Ranks #3,037 of 3,146 FMCSR codes by citation frequency.

Violation Description

Driver failing to provide motor carrier with annual list of violations or certificate of no violations.

Prevention FAQ for Fleet Managers

Pre-trip discipline, inspector focus, and root-cause fixes

What exactly are inspectors checking for under 391.27?

Inspectors verify that drivers can produce evidence they've notified their carrier of traffic violations within the required timeframe, and that carriers maintain records of driver violation disclosures or certificates of no violations on file. Our inspection records show this is a documentation-verification code: inspectors request the driver's violation disclosure form or the carrier's record of receipt. The violation occurs when either the driver cannot demonstrate notification or the carrier has no documented evidence of receiving it. Enforcement focus is on the completeness and timeliness of the notification chain, not the underlying traffic conviction.

What should our pre-trip or hire-day checklist include to prevent 391.27 violations?

Your checklist should require drivers to confirm in writing—at hire and annually—that they have disclosed all traffic violations incurred since their last report. Include: (1) a signed statement listing any violations by date, location, and citation number; (2) confirmation of understanding the carrier's notification deadline (typically within 30 days of conviction); (3) acknowledgment that failure to disclose is grounds for termination. New hires must produce this form before first assignment. Existing drivers complete it annually, on their employment anniversary. Store originals in the driver qualification file (DQF) with a timestamp. This shifts the burden from post-inspection scrambling to proactive documentation.

What documentation must drivers carry, and what must we retain in the office?

Drivers should carry a pocket-sized copy of the carrier's violation-notification policy stating the deadline and the reporting mechanism (email, form, phone line). The carrier must retain in the DQF: (1) the signed annual disclosure or 'no violations' certificate; (2) any written violation reports submitted by the driver, including date received and processed; (3) carrier acknowledgment of receipt with timestamp; (4) evidence of any follow-up investigation or disciplinary action. If a violation occurs post-hire, the driver's notification and the carrier's dated receipt create the defense. Retention period: minimum 3 years. Digital storage with audit logs is preferable to paper, as it timestamps receipt automatically.

What root causes should we investigate if we receive a 391.27 citation?

A 391.27 citation typically signals a breakdown in the driver-carrier communication channel. Root causes include: (1) driver unaware of the notification deadline or policy (training gap); (2) driver submitted notification but the carrier office lost or misfiled it (process failure); (3) driver concealed a violation out of fear of discipline (culture issue); (4) no formal disclosure form exists, leaving notification ad-hoc (policy gap). Conduct a post-citation review: interview the driver about when they knew of the violation and how they attempted notification; check email and voicemail records; audit your DQF for that driver's last three disclosure forms; ask whether your annual reminder goes out on a set schedule. The most common root cause is absence of a documented, timestamped notification process. Implementing a simple intake form and filing system eliminates ~90% of repeat citations.

After a 391.27 citation, what immediate corrective actions should we take?

First, retrieve and file the driver's violation disclosure or obtain one retroactively if missing. Contact the driver to confirm the violation details and document your findings. Second, audit the last 30 driver files to ensure every one has a signed disclosure or no-violation statement dated within the past 12 months; any gaps must be closed within 7 days. Third, review your notification policy: ensure it specifies the deadline (e.g., within 30 days of conviction), the method (form, email, portal), and the DQF filing location. Fourth, conduct a brief driver meeting to reinforce the policy and confirm understanding. Finally, document all corrective steps with dates and signatures. These actions, recorded in the driver file, demonstrate due diligence if an inspector returns.

How does a 391.27 citation affect our CSA score and safety profile?

FMCSR 391.27 carries a CSA severity weight of 2, placing it in the lower-severity tier. However, across our 13 million inspection records, we observe 0 citations for this code in the last 12 months, indicating it is extremely rarely cited in the field. When it does occur, it typically signals a systemic carrier compliance gap rather than an isolated driver error, because it reflects carrier-level record-keeping failure. A single citation is unlikely to materially impact your overall BASIC 3 (Driver Fitness) score, but it may trigger additional scrutiny on your driver qualification files in follow-up inspections. The strategic concern is not the severity weight but the reputational signal: an inspector finding no violation disclosure form suggests weak hiring controls, which invites deeper audits of your entire DQF.

What training should we provide to prevent 391.27 violations?

New-hire orientation must include: (1) a 10-minute walkthrough of the carrier's violation-notification policy, including the deadline and method; (2) a signed acknowledgment that they understand the requirement; (3) a sample completed disclosure form so they see what 'good' looks like. Annual recurrent training should review the same policy and reinforce it with a brief quiz or confirmation of understanding. For office staff (recruiters, HR, safety managers), training should cover: (1) where disclosure forms are filed in the DQF; (2) how to timestamp received notifications; (3) what to do if a driver reports a violation after hire; (4) how to document follow-up actions. A 15-minute annual refresher for staff keeps compliance visible. Pair training with a policy handout: a one-page graphic showing the step-by-step process reduces confusion and gives drivers a reference they can keep in their cab.

How often should we self-audit to catch 391.27 issues before an inspector does?

Across our 13 million inspection records, 391.27 citations number 0 in the last 90 days and 0 in the last 12 months, indicating enforcement is vanishingly rare but not obsolete. We recommend a quarterly self-audit (every 90 days) of a random sample of 10–15 active driver files, checking for a signed, dated disclosure form or no-violation certificate. This cadence aligns with your quarterly safety meetings and catches gaps before they compound. Additionally, perform a full-fleet audit annually, timed to your safety program renewal or after any employee turnover in the recruiting or HR function. The quarterly spot-check is fast (30 minutes per sample) and high-value; the annual full audit is thorough and creates a defensible record. Document all audit findings and any corrective actions taken. If an inspector arrives within 30 days of your audit, you can demonstrate proactive compliance.

Should we challenge a 391.27 citation via DataQs?

DataQs challenges are worth considering if: (1) you have evidence the driver did submit a notification and the carrier did receive and file it, but the inspector did not locate the file during the inspection; (2) the citation cites a driver who left your employ before hire and thus was never subject to your disclosure policy; (3) the inspector's narrative contains a material factual error about the notification deadline or your policy. Gather supporting documents: timestamped disclosure forms, email receipts, DQF index pages showing the form on file. Write a clear narrative explaining what the record shows and why the citation is inaccurate. Submit via FMCSA's DataQs portal with scanned evidence. Given the code's extreme rarity (0 citations in 12 months), a successful challenge is possible if your documentation is clean. Unsuccessful challenges do not harm your record, so if you have strong evidence, the effort is low-risk.

What's our one-sentence best practice to prevent 391.27 citations?

Implement a simple, documented annual disclosure process: every driver signs a form—either listing violations or confirming none—files it in the DQF with a timestamp, and receives a pocket-sized policy card. This single practice eliminates ambiguity and creates the paper trail inspectors need to confirm compliance.

Last updated: 2026-04-20T18:15:38.662Z Guidance derived from TruckCodex inspection data Read the full article → Quick Q&A →

Data sources & freshness

TruckCodex aggregates official public-sector datasets. See the Source registry for dataset-level coverage and the Freshness log for last-import timestamps.

Census, SAFER, SMS, Licensing & Insurance (L&I), roadside inspections, crashes, and authority history.

Refreshed daily.

Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).

Refreshed daily.
EIA

Retail diesel and gasoline price history and state fuel-tax tables.

Refreshed weekly.

Cross-border carrier registry and Canadian recall campaigns where applicable.

Refreshed weekly.

TruckCodex is an independent aggregator; it is not affiliated with FMCSA, NHTSA, EIA, or Transport Canada. Always verify compliance-critical information directly with the originating agency.