Free · No account · 1–5 drivers
DQF Expiration Tracker
Know your next estimated DQF expiration date before it becomes a problem. Enter the dates you already have and see what is overdue, what is due in 30 or 60 days, and what is still on file.
Start trackingSee how it works
Your driver data stays in this browser. No account, no upload.
Example output
What a result card looks like
Sample dates only. Your own results are calculated from the dates you enter and your device date.
Driver 1 · CDL holder
- Medical examiner's certificateMar 14, 2027
- MVR pullNov 1, 2026
- CDL expirationDec 1, 2026
- Annual reviewDec 30, 2026
Estimated based on FMCSA Part 391. Not legal advice. Example output is static and does not use your data.
Start your file · local only
Enter the dates you already have
Dates are calculated locally and compared with your device date. Use a nickname if you prefer. Names and dates are never sent to us. Last rule update: 2026-11-13.
Your DQF working file
Up to 5 drivers. Partial dates are allowed. Nothing leaves this browser.
Rule index
Document expiration rules used by this tracker
Each row shows the period, the date anchor, and the regulation the tracker uses for its estimate. Medical certificates use the expiration date you enter first; the 24-month figure is only a fallback estimate.
| Document | Period | Anchor | Rule | Notes |
|---|---|---|---|---|
| Medical examiner's certificateRecurring | 24 months (certificate expiry first) | Certificate expiry | 49 CFR 391.45(b) | Uses the expiration date printed on the certificate when you provide it. If only the issue date is known, the tracker estimates issue date + 24 months and marks the result as estimated. |
| Motor vehicle record (MVR)Recurring | 12 months | Last pull | 49 CFR 391.25(c)(2) | The next MVR pull is estimated at 12 months after the last pull date you enter. |
| CDL expirationRecurringCDL only | Certificate expiry (state-issued) | Certificate expiry | 49 CFR Part 383 | CDL validity is set by the issuing state. The tracker uses only the expiration date you enter and does not assume a fixed federal cycle. |
| Annual review of driving recordRecurring | 12 months | Completion date | 49 CFR 391.25(a) | The next annual review is estimated at 12 months after the review date you enter. |
| Road testOne-time | One-time document | Completion date | 49 CFR 391.31 | A road test certificate is a one-time document. The tracker shows whether it is on file and does not calculate a recurring due date. |
| Employment verificationOne-time | One-time document | Verification date | 49 CFR 391.51(b)(2) | Employment verification is a one-time document. The tracker shows whether it is on file and does not calculate a recurring due date. |
| Drug & alcohol random testingOne-timeNot tracked | Program-level requirement | — | 49 CFR Part 382 | Random testing is a program-level requirement and does not have a single expiration date. It is listed for reference only and is not part of the date inputs or calculations. |
Last rule update: 2026-11-13 · Rules can change. Verify with FMCSA or your safety consultant.Read 49 CFR Part 391 on eCFR.
How it works
Three steps, no account
Add a driver
Use a name or a nickname. Labels stay in your browser and are never uploaded. Turn the CDL switch off if the driver does not hold a CDL.
Enter the dates you already have
Medical certificate issue or expiration, MVR pull, CDL expiration, annual review, road test, and employment verification. Partial dates are allowed.
Read the next due date
Each driver gets an estimated next due date plus overdue, 30-day, and 60-day groups. The fleet summary shows the three most urgent items.
The calculation, in plain terms
next due = anchor date + rule period. Dates are date-only and calculated in UTC, so a time zone cannot shift them by a day. Month-end dates are clamped: January 31 plus one month becomes February 28, or February 29 in a leap year.
For the medical certificate, the expiration date you enter is always used first. If you only have the issue date, the tracker estimates issue date + 24 months and labels the resultEstimated. CDL expiration is never estimated: it uses only the state-issued date you enter.
Status boundaries: a date one day in the past is overdue; 0–30 days is due within 30 days; 31–60 days is due within 60 days; 61 days or more is on track. The device date is used for the comparison.
Why it matters
The file is only useful if the dates are current
49 CFR Part 391 requires a motor carrier to keep a driver qualification file for each driver. The file is not a one-time hire document: medical certificates, MVR pulls, CDL credentials, and annual reviews all move forward on their own schedule. When one of those dates slips, the gap is usually discovered during a review or a roadside interaction, not on the day it happened.
A paper folder and a desk calendar can work, but they depend on someone remembering to flip the page. A spreadsheet can calculate dates, yet the formula is easy to break and the file is often stored somewhere other than the browser you use every day. This tracker keeps the arithmetic in one place, shows each document's citation, and puts the next date in front of you as soon as you enter the record.
The goal is not to replace your safety consultant or your compliance software. It is to make the next date visible for a one-person operation or a small fleet, without creating an account or uploading driver information. You can use a nickname, enter only the dates you know, and export a backup whenever you want.
FAQ
Questions drivers ask
What is a DQF, and what does this tracker do?
A driver qualification file (DQF) is the record a motor carrier keeps for each driver under 49 CFR Part 391. This free tracker lets you enter the document dates you already have and shows an estimated next due date for each one, so nothing quietly expires.
Which expiration dates does the tracker calculate?
The tracker estimates a next date for the medical examiner's certificate, MVR pulls, and the annual review of driving record, and it shows the CDL expiration date you enter. Road tests and employment verification are shown as one-time documents. Drug and alcohol random testing is listed for reference only because it is a program-level requirement, not a single date.
Where is my driver data stored?
Driver labels and dates are stored only in your browser using localStorage. They are not uploaded to a server, and analytics never include names, dates, or backup files. Optional analytics are off until you choose: if you allow them, the page records anonymous events with bucketed counts, page path, device type, and referrer host; if you reject, only event names and counts are sent. You can export a JSON backup at any time, and clearing your browser data removes the tracker data.
Are the dates legal advice or a guarantee of compliance?
No. The dates are estimates based on the information you enter and 49 CFR Part 391. This is not legal advice and does not guarantee compliance or audit results. Rules can change, so verify with FMCSA or your safety consultant.
Can I track more than five drivers, and can I export my data?
The free tracker supports up to five drivers. You can export all entered drivers to a JSON backup file and import it later on the same browser or another device. Import replaces the current data after you confirm.
Disclaimer
These are estimated dates based on the information you entered and 49 CFR Part 391. This is not legal advice and does not guarantee compliance or audit results.
- Dates are compared with the date set on your device. A wrong device date produces wrong status labels.
- The tracker covers six date-based documents; it is not a complete DQF or an audit-prep system.
- Regulations and state-issued credentials can change. Last rule update: 2026-11-13.
- Nothing on this page is legal advice or a guarantee that an audit will pass.
Keep reading