Document the unanswered driver-history request

A hiring coordinator sends a driver’s safety-history request and receives nothing back. What belongs in the file when the reply remains missing? The answer is a documented investigation, with the unanswered part still visible. This resource examines existing federal requirements for covered motor carriers, subject to Part 391’s exceptions. It announces no new rule and does not determine whether any applicant may drive. Our proposed follow-up workflow is editorial analysis; all other applicable qualification and testing requirements still need their own review.

Section 391.23(c) requires replies or evidence of good-faith efforts in the driver investigation history file within 30 days after employment begins. Paragraph (g) gives the former employer 30 days after receiving a request to respond. Those starting points differ. The rule also requires a response when there is no safety-history information to report. Silence therefore cannot be recorded as confirmation of no crashes. Send the request early and give the recipient clear return contact details; paragraph (d) requires those details.

Build a contact trail someone else can follow. The rule calls for the former employer’s name and address, contact or attempted-contact dates, information received and documented failures. Our suggested working record also identifies who sent the request, the channel used, evidence of delivery when available and the next person responsible for follow-up. Preserve a returned message rather than replacing it with a green completion flag. A bounced address and a delivered request awaiting an answer are different problems; the next action should reflect which one actually occurred.

Consider a hypothetical request first received by the former employer late in the new driver’s first month. Its response deadline may extend beyond the hiring carrier’s file deadline. Our recommendation is to track both dates and review the evidence before the earlier deadline arrives. Do not wait for the recipient’s clock to expire before documenting your own work. Section 391.23(c)(3) says prospective employers should report failures to respond to FMCSA under section 386.12 and retain the report. The rule does not specify a magic number of unanswered calls that automatically proves good faith.

Industry sponsor Connect the records, conversations, and follow-up that keep a carrier moving. See how it works ↗

A successful Clearinghouse query does not replace the employment-verification and accident-history investigation in section 391.23(d). For covered employers, the current drug-and-alcohol inquiry route uses the Clearinghouse for FMCSA-regulated employment. Section 382.413 preserves direct requests for an unfinished follow-up testing plan and for relevant employment regulated by another DOT agency. Our practical suggestion is to show these as separate statuses. A completed electronic query should never silently close an outstanding request for accident information. Equally, a missing employment-history response should not be used to infer a drug or alcohol violation.

Keep the working trail inside the appropriate access controls. Section 391.53 requires a secure investigation-history file, restricts access and limits use of its data to the hiring decision. It requires safety histories received for a hired driver to be kept throughout employment and for three years afterward. Our workflow recommendation is to give dispatch only the operational status it legitimately needs through the carrier’s authorized process, rather than forwarding the investigative packet. Use a controlled location where the hiring reviewer can retrieve the original request, replies and unresolved items together.

The useful closeout question is whether a different authorized reviewer could reconstruct what was requested, what came back and what remains unknown. Assign the next action before the coordinator goes off duty. If a response later arrives, preserve it and route it to the hiring decision maker rather than treating the earlier attempts log as the final evidence. An unanswered request needs an honest record of the work performed and the information still missing; an empty checkbox cannot supply either.