Magellan
Annual MVR review: record the decision behind the report
Separate the annual MVR inquiry, review and file note. Use a practical review record and keep unresolved driver questions visible.
The report is in the folder. The invoice from the screening provider has been paid. The annual reminder has disappeared from the task list. Ask who reviewed the motor vehicle record, however, and the answer becomes less certain.
That gap matters because obtaining information and making a qualification decision are different pieces of work. An automated delivery can prove that a document arrived. It cannot, by itself, explain what the carrier considered, who made the decision or whether a finding required follow-up. If the annual review process ends at “download complete,” it stops before the most useful part.
Subject to its exceptions, 49 CFR 391.25 (https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-391/subpart-C/section-391.25) requires an inquiry at least once every 12 months to each licensing authority where the driver held a commercial motor vehicle license or permit during the relevant period. The MVR must cover at least the preceding 12 months. A review is also required at least once every 12 months, with the MVR and a note naming the reviewer and review date kept in the qualification file.
The review determines whether the driver meets minimum safe-driving requirements or is disqualified under 391.15. Consider evidence of Federal Motor Carrier Safety Regulations or Hazardous Materials Regulations violations, the accident record and motor-vehicle-law violations. The rule gives great weight to conduct indicating disregard for public safety, including speeding, reckless driving and driving under the influence. Record how relevant findings affect the determination; a report's arrival date cannot answer those questions.
Those are separate actions: obtain, evaluate and document. Your internal checklist should make each action visible. A report that arrived on time may still be waiting for evaluation. A completed evaluation may still be missing its note. Combining everything into a single “MVR done” box makes those differences disappear.
Write a review record another qualified person can understand without calling its author.
Give the reviewer a defined job. They should confirm that the record belongs to the correct driver, covers the relevant inquiry and can be read. They should identify information requiring a qualification decision or additional investigation, then document the outcome under the carrier's approved process.
Do not ask an administrative employee to interpret unfamiliar restrictions simply because that employee downloads the reports. The employee can flag the issue and route it. The person making the determination needs appropriate knowledge and authority. A fast escalation is better than an unsupported answer copied from last year's note.
Be equally careful with company standards. A carrier's own eligibility criteria and applicable legal disqualifications are not the same thing. Document which basis controls a decision. If an insurer, customer or internal policy adds a condition, identify it accurately rather than presenting every condition as a federal requirement.
A practical review record can identify the driver, report source and date, review date, reviewer, determination and any follow-up. If there is an exception, note where it is recorded and who is responsible. If the review requires additional information, keep the task open and explain what remains unresolved.
Avoid empty language such as “reviewed and approved” when the supporting record contains a question that nobody addressed. Conversely, do not copy a driver's entire history into a broadly visible task comment. The decision record should be clear and proportionate, with sensitive supporting information kept in its appropriate location.
An internal template might ask: What information was considered? What decision followed? Does anyone else need to act? These questions make the reviewer think through the work. A signature line alone can become another place where people click without evaluating anything.
A review note another employee can understand
Illustrative review record: “Driver ID 104; licensing-state MVR dated May 5, reviewed May 7 by Riley Chen, the qualification manager. Identity matches the driver. The report adds a March 12 speeding conviction, but its offense code and speed information need clarification from the licensing authority. Reviewer examined the conviction entry, accident history and available regulatory-violation information; the qualification determination remains open pending the source response. Under this company's procedure, dispatch must not make a new CMV assignment until the authorized reviewer records that determination. Qualification manager requested clarification May 7; next review May 8 at 10:00. MVR and request are linked in the restricted case file.”
The operating instruction is explicit without treating every speeding entry as an automatic federal disqualification. Once the source response arrives, the reviewer records the supported determination and communicates any changed assignment instruction. If an insurer or company policy adds a separate restriction, name that basis in its own decision field.
For an ordinary completed review, retain the actual determination and any follow-up along with the reviewer and date. Reviewer name and review date are required elements of the note; the additional fields above are recommended to make the decision traceable.
Imagine a hypothetical annual batch containing 18 reports. Seventeen move through the normal review process. One contains a newly listed event that the reviewer needs to understand. If the whole batch is marked complete because the provider delivered every report, the unresolved driver disappears into a successful dashboard.
Split the result. Record 17 completed reviews and one open exception with an owner. Establish the current operating decision through the authorized reviewer and identify what evidence is needed next. The unresolved item should be visible because it needs action, not because the employee failed to clear an arbitrary productivity target.
Topics
- Driver Files
- MVR
- Annual review
- Driver records