DOT Safety Performance History Records Request Guide
Key takeaways
- Under 49 CFR 391.23, you must send a safety performance history records request to every DOT-regulated employer a CDL driver worked for in the past three years before they operate a CMV for you.
- The request form must include the driver's written consent, a three-year employment history, and specific authorization to release drug and alcohol data under 49 CFR Part 40; a generic employment-records signature line fails.
- If a previous employer does not respond within 30 days, you must document the non-response and repeat the request, keeping proof of both attempts in the driver qualification file.
- The PSP report is not a substitute: it covers five years of crash data and three years of inspections from FMCSA, while the 391.23 request surfaces employment and drug/alcohol violations from previous employers.
- The driver must receive a copy of all returned history before operating a CMV and may submit a written rebuttal that stays attached to the record in the DQ file.
A safety performance history records request is the letter you send to each of a prospective driver's previous DOT-regulated employers to verify their crash and violation history for the past three years, as required by 49 CFR 391.23. You must send it before the driver operates a CMV for you, using a written form that documents their consent and the specific data you're requesting. This walkthrough covers what that form must contain, the 30-day follow-up rule, and how to keep the whole process out of your DQ file's way.
What is a safety performance history records request and when is it required under 49 CFR 391.23?
A safety performance history records request is the formal inquiry you send to a CDL driver's previous DOT-regulated employers to verify their crash and violation history before you put them in a truck. It is a mandatory part of the driver qualification file, not an optional reference check. The FMCSA requires it under 49 CFR 391.23: you must request safety performance history from every DOT-regulated employer the driver worked for in the previous three years, covering the two years before the driver's application. The request applies specifically to CDL drivers applying to operate a commercial motor vehicle. If a driver has no prior DOT-regulated employers in the past three years, you document that in the DQF instead. Missing or incomplete history requests are among the most common DQF audit findings, which is why many carriers track them through a compliance workflow like net360's.
What information must the safety performance history records request form include?
Under 49 CFR 391.23(d), your request to each previous DOT-regulated employer must contain three data elements: the driver's written consent, a three-year employment history, and authorization to release drug and alcohol information under 49 CFR Part 40.
The written consent requirement
The prospective driver must authorize the release in writing. Your application or an attached form must state that the driver can review the previous employer's response and contest any inaccuracies, and that the response may include a rebuttal if they do. Without documented consent, the request fails the 391.23 check and your DQ file is incomplete. Keep the signed authorization with the driver qualification file.
Authorization for drug and alcohol data under Part 40
The consent must also authorize previous employers to release verified positive drug or alcohol test results, refusals to test, and SAP return-to-duty completion from the past three years. A generic signature line covering "employment records" is not enough; the authorization must specifically cover Part 40 data. Automated workflows like net360 capture this consent during onboarding, and you can review how driver data is handled in our Privacy Policy before you send the first request.
How do you request safety performance history from a previous DOT-regulated employer?
Step 1: Verify the prior employer is DOT-regulated
Only prior motor carriers required to hold FMCSA operating authority count toward your 49 CFR 391.23 obligation. Use the prospective driver's application history, then confirm the carrier's USDOT number and status before sending anything. A non-DOT employer does not require a safety performance history records request, though you should still document why you treated it that way.
Step 2: Send the request and log the date
Send the request to the prior employer's safety or HR contact, including the driver's written consent and the data elements covered in the form section above. Record the date sent, the method, and the contact used. If no response arrives within 30 days, FMCSA guidance on driver qualification files expects you to document the follow-up attempt in the DQF rather than leave a silent gap. Tools like Tenstreet route these requests electronically and timestamp each attempt.
Step 3: File the request and response in the DQF
Place the request copy, the consent form, any response, and your non-response notes in the driver qualification file. Retention runs alongside the DQF itself, and auditors look for the dated trail. Automating the paper trail is where net360 fits, but even a spreadsheet beats an undocumented phone call.
What must previous employers disclose within 30 days, and what happens if they don't respond?
What the initial response must contain
Under 391.23(e), a previous DOT-regulated employer must respond with three categories of information: general employment details covering dates of employment and the position held, a record of accidents the driver was involved in over the prior three years, and any verified positive drug or alcohol test, refusal to test, or completion of return-to-duty through a SAP. The accident disclosure applies to crashes the employer knows about, including those where the driver received a citation.
The 30-day follow-up obligation
The initial response is not the end of your obligation. If a previous employer does not reply within 30 days of your request, you must document that non-response and repeat the request. That second request is not optional. 391.23 requires you to make the follow-up attempt and keep proof of it in the driver qualification file, because the safety performance history records request is only complete once you have either the data or a documented trail showing you pursued it.
Documenting a non-response
Keep the original request, the 30-day gap, and the follow-up request on file, whether those are emails, certified letters, or timestamps from a fax or portal. If the follow-up also goes unanswered, your file should show both attempts with dates. An auditor reading the DQ file wants to see that you acted within the regulation's timeline, not that you gave up after one email. Note that the prospective driver's right to review and dispute the returned information still applies, so whatever arrives late must be handled the same way as a timely response.
What are the prospective driver's rights to review and dispute the safety performance history?
Under 391.23(e)(4)-(6), the driver owns the paper trail, not you. You must give the applicant a copy of all safety performance history information you obtain from previous DOT-regulated employers, and you must do it before the driver operates a commercial motor vehicle for you. Get the driver's written acknowledgment that they received it, and file that in the DQ file.
Right to review the data received
The driver may review everything you received, including crash data and any DOT-recordable accident details. Note that PSP reports, which drivers can pull themselves, contain five years of crash data and three years of inspection history, per the FMCSA PSP program site.
Disputing inaccurate information
If the driver believes information from a previous employer is wrong, they can submit a rebuttal in writing, and you must attach it to the safety performance history in the DQ file. You cannot withhold the history from the file pending the dispute. If the previous employer corrects the record, both the correction and the rebuttal stay on file together.
How does the FMCSA PSP report differ from the safety performance history records request?
The PSP report comes from FMCSA and covers five years of crash data and three years of inspection history. The safety performance history records request goes to previous DOT-regulated employers and covers employment dates, positions, reasons for leaving, and any drug or alcohol violations with return-to-duty status. You need both: PSP shows inspection and crash patterns, while the 391.23 request surfaces violations that never generated a roadside inspection, including Clearinghouse-reportable events.
| PSP report | 391.23 records request | |
|---|---|---|
| Source | FMCSA | Previous employers |
| Contents | Crashes (5 yrs), inspections (3 yrs) | Employment, drug/alcohol history, refusals |
| Authorization | Driver purchases and authorizes | Applicant signs consent; carrier requests |
| Deadline | Immediate download | Employers respond within 30 days |
Run both checks before you close the DQ file, since each one catches what the other misses.
What are common mistakes that make a safety performance history request non-compliant?
The most frequent audit failure is requesting verification without the driver's written authorization on file. Under 49 CFR Part 40 §40.25, the prospective driver must specifically authorize release of alcohol and drug history from prior employers, and a generic consent form does not satisfy that requirement (see the eCFR text of 49 CFR Part 40 §40.25).
Three more mistakes draw citations: treating non-DOT-regulated employers as verifiable sources and logging them as if they were, failing to document follow-up attempts when a prior employer does not respond within the 30-day window, and scoping the search to less than the full three years required under 391.23. Each one is easy to catch in a DQ file review, because the gap shows up as a missing date, a missing signature, or an unexplained hole in the employment timeline.
How can mid-size carriers automate the safety performance history records request?
What to look for in an automation tool
Judge any tool against 391.23 requirements, not marketing claims. It must generate compliant requests with the driver's written consent attached, send them to every DOT-regulated employer in the last three years, track the 30-day initial and follow-up deadlines, and store responses in the DQ file. If it cannot document non-responses, you still own that compliance risk.
How net360 compares, honestly
net360 automates the request, consent capture, deadline tracking, and DQ file storage, cutting verification from weeks to hours. Tenstreet, Zeus Platform, Double Nickel, FileFlo, and Vertical Identity cover similar or adjacent ground with different workflows.
Where net360 falls short: it is built for verification and onboarding, not full DQF management, so carriers wanting one system for expirations, drug and alcohol records, and annual reviews will still need another tool. If your volume is under a few hires a month, manual requests with a spreadsheet tracker may cost you less than any subscription.
FAQ
Do I need a safety performance history records request for non-CDL drivers?
No. The obligation under 49 CFR 391.23 applies to CDL drivers applying to operate a commercial motor vehicle, so non-CDL hires require no request. If a CDL applicant has no DOT-regulated employers in the past three years, you still document that fact in the driver qualification file rather than skipping the check silently.
Can I hire a driver before the previous employer responds to the request?
No. You must complete the request process before the driver operates a commercial motor vehicle for you. If a prior employer misses the 30-day window, you document the non-response and repeat the request, but a documented trail does not substitute for completing the process before dispatch. The driver must also receive the returned information first.
What form should I use, or can I write my own driver safety performance history request form?
You can write your own, as long as it contains the three required elements: the driver's written consent, a three-year employment history, and authorization to release drug and alcohol data under Part 40. A generic employment-records signature line fails. Many carriers use electronic tools like Tenstreet or net360 to generate and timestamp compliant requests automatically.
Who pays for the safety performance history records request?
The requesting carrier bears the cost. Sending the request itself is typically free, especially by email or an electronic portal, though certified mail adds postage fees. PSP reports are a separate expense, purchased by the driver or the carrier depending on your arrangement, and automation subscriptions are also a carrier cost.