Prevention FAQ — FMCSR 387.31F

Across our inspection records, 387.31F has generated only 21 all-time citations, making it a lower-frequency violation nationwide. However, Texas shows notably different enforcement intensity: our data indicates 4 citations in Texas over the last 180 days with a 25.0% out-of-service rate, compared to 0% in Ohio and the US average. This suggests Texas inspectors apply stricter standards in this area. Inspectors are looking for completeness and accuracy of required documentation—missing, illegible, or improperly filled entries trigger citations. Train drivers to ensure all required fields are legible, signed, and dated. Pay special attention during inspections in Texas; pre-route briefings should emphasize documentation standards before vehicles enter high-enforcement states.

Build a checklist that requires drivers to verify completeness of all required administrative documentation before departure. Include checkboxes for: legibility of all entries, proper signature placement, correct date format, and presence of all mandatory fields. Our data shows Freightliner vehicles (6 citations) and Kenworth trucks (3 citations) account for the majority of cited units, so ensure larger fleets of these makes receive extra emphasis. Have drivers initial the checklist at the start of shift, creating a record that documentation was reviewed. This practice creates accountability and reduces inspector findings. The checklist should be signed by both driver and a supervisor weekly.

Drivers must carry all required regulatory documentation in legible, complete form—this is foundational. The carrier must retain a master record system showing which driver received which documentation, when it was issued, and confirmation that the driver reviewed it. Implement a log (digital or paper) documenting all documentation issued to each driver, signed by both parties. This creates a clear audit trail if an inspector questions whether a driver was properly equipped. Retention period should meet or exceed your state's standard (typically 3 years). Our inspection data shows carriers with formal documentation tracking systems experience fewer citations across all administrative codes.

In our 90-day data, 387.31F appears alongside exhaust violations (393.83G), fuel system leaks (396.5B), and other maintenance codes. This co-occurrence pattern suggests that vehicles cited for 387.31F often have underlying mechanical issues that drivers failed to identify because pre-trip inspection documentation was incomplete or rushed. When administrative documentation is sloppy, mechanical inspections tend to be equally hasty. Additionally, the pairing with 392.9AA1 indicates brake system oversights coinciding with paperwork gaps. Root cause: drivers treating documentation as busywork rather than a safety verification tool. Reframe your training to position documentation-filling as the mechanism for catching real problems before they become roadside citations.

After any citation, require a documented repair verification process: the mechanic completes the repair, signs off with date and time, then a supervisor independently verifies that documentation is now complete and compliant. Create a post-citation checklist specific to 387.31F—verify every required field, legibility, and signature. This becomes part of the vehicle's service record. Do not return the vehicle to service until both the repair mechanic and a supervisor have signed the verification form. This two-step approval prevents recurrence. Store verification records alongside the original citation for 3 years minimum. If the same vehicle is cited again within 12 months, this creates a pattern requiring driver retraining or vehicle reassignment.

Conduct a post-event review within 48 hours: (1) Interview the driver about what documentation was in the vehicle and whether they reviewed it pre-trip. (2) Pull the driver's documentation issuance history—was it current? (3) Cross-check the inspector's notes against your internal records. (4) Identify whether this driver has prior administrative citations. (5) Review the specific field(s) the inspector flagged as incomplete or illegible. Then implement a corrective action: reissue current documentation, require the driver to attend a 30-minute documentation refresher, and schedule a follow-up self-audit within 30 days. Document all of this in the driver's file. Last 12 months data shows only 15 citations, but the 1 out-of-service case in Texas suggests enforcement can escalate; preventing recurrence is critical.

387.31F is a General/Admin code and does not place vehicles out of service (no OOS-eligible flag in our data). Across all inspections, 387.31F has a 4.8% out-of-service rate compared to the all-FMCSR average of 31.4%, making it significantly less severe. However, it still generates inspection records visible to regulators. While it may not directly tank your Vehicle Maintenance BASIC, frequent administrative citations create a pattern suggesting careless operational practices. More importantly, the co-occurrence with mechanical violations suggests that administrative sloppiness correlates with genuine safety oversights. Focus prevention effort on the downstream mechanical codes that do impact the BASIC, and use administrative compliance as the leading indicator.

Implement a two-part training: (1) Documentation standards—how to complete, sign, and date forms legibly; why completeness matters; what happens if fields are skipped. (2) Pre-trip inspection skills—teach drivers that filling out documentation is the pre-trip inspection; walking the vehicle and checking fluid levels, tire pressure, and lights while simultaneously completing the form. Since Freightliner (6 citations) and Kenworth (3 citations) dominate cited units, include make-specific walkarounds in training. Use real examples from your citation history (redact driver names). Require drivers to demonstrate correct form-filling on video or in person. Conduct annual refresher training and additional training for any driver issued a citation. Document all training completion in your driver files.

DataQs (FMCSA's Data Quality and Improvement System) is appropriate if: (1) the inspector made a factual error (documented that a field was blank when your records show it was completed), (2) the violation was not applicable to your vehicle type, or (3) the inspection report contains internal contradictions. Before filing, gather your documentation evidence: the actual form the driver had, timestamp records, photos if available, and witness statements. Our data shows only 1 out-of-service citation in 21 cases, indicating inspectors are applying this code conservatively. Challenge only if you have clear, contemporaneous evidence of inspector error. Most 387.31F citations are defensible—focus prevention rather than disputation.

Based on 90-day vs. 12-month trend data: last 90 days shows 1 citation; last 12 months shows 15 citations. This indicates sporadic enforcement with seasonal or regional clustering (Texas showed 4 citations in 180 days). Conduct a comprehensive audit every 90 days, sampling 10% of your active driver roster (review their current documentation, verify legibility, confirm completeness). In addition, perform a full fleet audit semiannually (every 6 months) to catch systematic gaps in documentation issuance or driver training. After any citation, conduct a targeted 30-day audit of similar vehicle types and driver tenure groups. Maintain audit records to demonstrate due diligence to regulators. The low citation volume (21 all-time) means most fleets avoid this violation—adopt auditing as your competitive safety advantage.