Prevention FAQ — FMCSR 391.21 (No Application for Employment)
Fleet safety guidance on employment documentation requirements, inspection focus areas, and prevention strategies for FMCSR 391.21 violations.
- Code:
- 391.21
- 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 employed without completing and submitting required application for employment.
Prevention FAQ for Fleet Managers
Pre-trip discipline, inspector focus, and root-cause fixes
› What do roadside inspectors specifically look for when checking 391.21 compliance?
Inspectors verify that every driver on duty has a completed, signed employment application on file with the carrier. The check typically happens during Level 1 or Level 3 inspections as part of the driver fitness category review. Our inspection records show this violation falls under the Driver Fitness group alongside high-enforcement codes like CDL validity (47,123 citations) and medical certificate status (49,539 citations). Because 391.21 citations are rare in our database—zero citations in the last 12 months across 13 million records—inspectors encounter it only when systematic hiring documentation is missing entirely. Focus your audit on whether applications are signed, dated, and retained in driver personnel files before the first day of operation.
› What pre-trip checklist item prevents this violation?
Before any driver operates a commercial motor vehicle, the driver should confirm and document that their signed employment application is in the carrier's office file. The checklist entry should read: 'Verified: signed employment application on file with carrier.' This is distinct from medical certificate or CDL checks; it focuses on the onboarding paperwork itself. Since this code is employment-focused rather than vehicle-focused, the check belongs in the hiring workflow, not the daily vehicle inspection. Include this as part of new-hire orientation sign-off, not a recurring pre-trip item. Failure to document this upfront is the root cause—once the application is properly filed, the violation disappears.
› What employment documentation must be retained and for how long?
Retain the completed, signed Application for Employment (typically FMCSA Form MCS-5) or equivalent carrier form in the driver's personnel file for the duration of employment plus three years after separation. The application must include the driver's full legal name, address, date of birth, and driver's license number. Store originals in a secure location with controlled access; digital scans are acceptable as backup but the original should be retained. Include evidence of the date the driver was hired and first authorized to operate a CMV. Cross-reference the application file with the driver's medical certificate file and CDL file to ensure all three onboarding documents are complete. Annual audits should verify that 100% of active drivers have signed applications on file.
› What root causes lead to 391.21 citations, based on co-occurring violations?
Because 391.21 has zero citations in our recent data, it typically surfaces only in fleets with severe systemic hiring failures. When it does occur, it often co-occurs with other driver fitness violations: CDL validity issues (47,123 citations, 98.6% OOS rate) suggest drivers were hired without verifying current licensing; medical certificate violations (49,539 citations, 97.1% OOS rate) indicate missing pre-employment physicals; and physical qualification gaps (42,270 citations, 16.2% OOS rate) suggest incomplete fitness-for-duty screening. The pattern suggests a single root cause: the absence of a documented onboarding process. If 391.21 appears, audit whether new hires are starting work before background checks and application reviews are complete.
› How should we verify a driver's employment status before return to service after citation?
If a driver is placed out of service for missing employment documentation, the remedy is simple: locate or recreate the signed employment application and file it with the carrier immediately. Once filed, the driver may return to service. Verify: (1) the application is signed and dated; (2) it contains all required fields (legal name, address, DOB, license number, hire date); (3) it is stored in the driver's personnel file with version control and file timestamp; (4) a copy is electronically scanned into your driver management system. Have the safety manager and driver sign a corrective action statement acknowledging receipt and understanding of the requirement. This should take less than one hour per driver to resolve.
› What post-citation review should the fleet conduct?
After a 391.21 citation, conduct an immediate audit of all active drivers' personnel files. Check: (1) Does every driver have a signed employment application on file? (2) When was each application filed relative to the driver's hire date? (3) Are missing applications due to lost files, failed scanning, or drivers who started work before paperwork was completed? (4) Is the onboarding workflow documented in writing? Create a corrective action log, assign accountability for file recovery or re-signing applications, and set a completion deadline of 14 days. Then conduct a second audit to confirm. Root-cause analysis should focus on whether your hiring process requires applications before or after the driver's first shift—it must be before.
› How does this violation affect our CSA Vehicle Maintenance BASIC score?
FMCSR 391.21 is classified under the Driver Fitness category with a CSA severity weight of 2. Unlike high-severity vehicle maintenance violations, this is a driver-level administrative citation that does not directly impact the Vehicle Maintenance BASIC. However, if 391.21 appears alongside CDL or medical certificate violations (which carry weights of 3–4), your Driver Fitness BASIC will rise. Because zero citations appear in our recent 12-month database, this violation is exceptionally rare and typically does not materially affect composite scores unless it signals a broader hiring process collapse. Prevention is the most cost-effective approach: ensure every driver has a signed application on file before dispatch.
› What driver training topics prevent 391.21 violations?
Driver training on 391.21 itself is minimal—drivers do not create or maintain employment applications; carriers do. Instead, focus training on onboarding clarity: every new hire should understand that no CMV operation is authorized until hiring paperwork is complete and filed. Include this in the orientation agenda, and have the driver acknowledge receipt in writing. For safety managers and HR staff, conduct quarterly training on the filing requirements and the critical importance of completing applications before a driver's first shift. Include a walkthrough of your digital filing system and backup procedures. This is primarily a carrier and HR function, not a driver function, so frame training accordingly.
› How often should we self-audit for employment documentation compliance?
Conduct a full audit of all driver personnel files at least quarterly (every 90 days). Because our inspection records show zero 391.21 citations in the last 90 days and zero in the last 12 months, this violation is not a current enforcement focus. However, the absence of enforcement does not indicate absence of risk—it indicates that most fleets have implemented basic hiring controls. A quarterly cadence ensures new hires are processed correctly and dormant files are verified. Include a spot-check audit of new hires within 7 days of their start date, before they operate a CMV unsupervised. Document audit results, corrective actions, and completion dates. This preventive approach costs far less than remedying a citation.
› When should we file a DataQs challenge for a 391.21 citation?
File a DataQs challenge if the citation states that no employment application exists on file, but you have evidence (signed, dated original or scanned copy with timestamp) that one was filed before or on the driver's first date of operation. Include the application itself and a letter from your HR manager stating the filing date and location of the driver's file. Challenges succeed when inspectors fail to properly verify your filing system or when there is a legitimate document management issue beyond your control. However, because 391.21 has zero citations in our database, disputes are rare. Focus instead on preventing citations through robust documentation practices rather than contesting them after the fact.
Related Records
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.
Vehicle recall campaigns, defect investigations, and consumer safety complaints (SCRS).
Cross-border carrier registry and Canadian recall campaigns where applicable.
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.