Safety Scoring
Safety Rating Upgrade: How to Request a Change After Conditional
By Editorial Team · Updated August 25, 2026 · 10 min read · Editorial standards
On this page 7 sections
The snapshot still says Conditional. A shipper’s onboarding form bounced. Your broker wants a letter you cannot honestly write. Someone on the leadership call says “just request a safety rating upgrade” as if there is a button on SAFER. There is not. There is a written request, a pile of evidence that the deficiencies are actually gone, and an agency that will not relabel you because the commercial pain is real.
This page is the procedure. It is not a primer on what Satisfactory, Conditional, and Unsatisfactory mean — that map already lives in FMCSA safety rating. Here you pick the right path, build the packet, file it in the right place, and know what still will not move even if the label changes.
Rules change. Verify current requirements at fmcsa.dot.gov before you act on anything in this guide.
What you are actually asking for
A safety rating is a one-word fitness label assigned after a rated investigation. It sits on the public snapshot until FMCSA changes it. It does not age off. It does not improve because your CSA percentiles cooled down. Percentiles and the rating are different systems; if you are mixing them, stop and read FMCSA safety rating first, then come back.
An upgrade request asks the agency to replace that label. In practice you are asking for one of two things:
- Change based on corrective action. You accept that the findings were real. You changed the process. You can show current compliance. You want the rating updated to match the operation you run now.
- Administrative review. You do not accept the rating as issued. You think the investigator got a fact wrong, applied the wrong provision, or scored a factor incorrectly. You want the existing record re-read, not a medal for later cleanup.
Do not staple both theories into one letter and hope the nicer one sticks. The reviewer will not rebuild your argument for you.
Most Conditional carriers want the first path. They know the files were thin. They rewrote the policy, trained the people, and now need the public word to catch up so a bid will open. That is a corrective-action request.
If your problem is a CSA percentile and you have never had a rated investigation, you are on the wrong page. Unrated is normal. There is nothing to upgrade. Use how to improve CSA score and SAFER score lookup instead.
Pick the path before you write a sentence
Corrective action — you fixed the findings
Use this when the investigation report is basically right and the operation has changed. FMCSA’s own planner describes this as a request to change a proposed or final safety rating based on corrective actions. The live rules live on fmcsa.dot.gov; do not copy a deadline or a form name from a vendor blog.
What this path requires in plain language:
- A written request
- A description of what you corrected
- Documentation that the deficiencies are gone
- Evidence that current operations meet the fitness standard the investigator used
What this path is not:
- A promise that you will fix it later
- A complaint about the investigator’s tone
- A CSA DataQs filing
- A new-entrant audit
You may request this after a proposed rating or a final rating. You do not have to wait for a calendar date to “serve time” on Conditional. What you do have to wait for is enough post-fix evidence that a stranger can see the pattern stopped.
Administrative review — you think the rating is wrong
Use this when the packet should have produced a different result on the facts as they existed during the investigation. You are not bringing new training records from last month. You are showing that a cited file was complete, a violation was not a violation, or a factor was scored against the wrong standard.
FMCSA describes this path separately from the corrective-action path. Confirm the current filing window and destination on fmcsa.dot.gov or the CSA Safety Planner section on rating changes. This page will not invent those clocks.
If you lost on the facts and later cleaned up the files, that is not administrative review. That is corrective action. File the one you actually have.
Build the packet in this order
Get the investigation report and list every finding that scored
What you do: obtain the report from the review, not the one-word snapshot. Line up each cited violation against its factor and whether it was treated as acute or as a pattern. Required or just smart: smart, and you cannot write an honest request without it. The gotcha: carriers fix the embarrassing items and skip the ones that actually produced the Conditional. Fix by what scored, not by what is easy to photograph.
If you cannot reconstruct why the rating landed where it landed, you are not ready to ask for a change. You are ready to request the report.
Change the process, not the memo
What you do: for each scored finding, write the root cause, the new control, the person who owns it, and the date it took effect. Then run the new control long enough to produce records. Required or just smart: the request has to rest on corrective action that already happened. The gotcha: “we counseled the driver” is not a control. A written rule plus a monitoring step plus a file that proves both happened is a control.
Hours-of-service patterns and driver-qualification gaps are where packets usually lie. A new policy in a binder and the same thin DQ files is not an upgrade request. It is a reprint of the last investigation.
Hiring discipline is a full slice of the rating surface. If the Driver factor scored, the packet has to show how applications, driving-record inquiries, medical certificates, and drug-and-alcohol pieces are built now — not that you intend to care. The underlying duties still live in 49 CFR §391.21, 49 CFR §391.23, 49 CFR §391.25, 49 CFR §391.51, 49 CFR §382.301, and 49 CFR §382.701. Cite the file you can produce, not a slogan.
Assemble evidence a stranger can audit
What you do: attach proof of current compliance. Corrected files. Training that happened. Maintenance that happened. Post-fix samples with dates after the process change. A short index that maps each old finding to the exhibit that closes it. Required or just smart: required in substance even if nobody hands you a form. The gotcha: a sample that starts the week you wrote the plan proves you can assemble a sample. It does not prove the pattern stopped.
Make the packet boring. Name files so a reviewer can find Exhibit C without a phone call. If you need a consultant to explain your own exhibits, the exhibits are not ready.
File in writing with the right Service Center
What you do: send the request to the FMCSA Service Center that covers the area where you maintain your principal place of business. Describe the corrective actions. Attach what you want considered. Keep a copy of what you sent and how you sent it. Required or just smart: required. The gotcha: the destination matters. A beautifully indexed packet in the wrong office is not filed.
Do not treat a portal message, a voicemail, or a conversation at the close-out as the request. The planner’s language is a written request. Confirm the current address list on fmcsa.dot.gov rather than from a blog that still lists a closed street.
Track the answer and do not freeze the operation
What you do: watch for a written decision. Keep running the new controls while you wait. If the request is denied, read whether the next move is more evidence on the corrective-action path or a separate administrative review of that denial. Required or just smart: operationally essential. The gotcha: carriers stop supervising the new process the week the packet goes out. The next investigation will sample that week.
FMCSA reviews some Unsatisfactory requests on a shorter guaranteed clock than others, especially passenger and placardable-hazmat operations. Conditional requests do not get the same commercial luxury of a published countdown that you can manage from a spreadsheet. Confirm current handling with the Service Center. This page will not invent a number of days.
What the request will not do
It will not stay an Unsatisfactory prohibition. If you are on a proposed Unsatisfactory, filing a corrective-action request is not a pause button. Passenger and hazmat operations sit on a shorter fuse than everybody else. Read the notice you were handed and verify the current rule on fmcsa.dot.gov. Do not let a vendor tell you that “the upgrade filing buys time.”
It will not change CSA percentiles. Those move with inspections and crashes, not with a rating letter. If the commercial problem is a BASIC, you are doing CSA work, not rating work.
It will not erase the investigation. A successful change replaces the public label going forward. Brokers who already coded you Conditional may still ask what happened. Keep a one-page explanation that matches the packet, not a story.
It will not fix a hiring standard you do not have. If the Driver factor scored because files were empty, an upgrade that leaves the same recruiters making the same exceptions will not survive the next review. Write the MVR bar — what is a bad MVR score — and stop treating a campus pre-hire letter as a completed DQ file.
It will not tell you how drivers behaved as employees. Formal checks show convictions, tests, and prior-employer safety history. They do not show the Monday no-show or the truck left at a fuel desk. After the required stack, search that gap on CDLScan. An upgrade packet built on the same people who produced the last Conditional is a request to be surprised again.
A desk checklist before you hit send
If two people on the safety team cannot reconstruct the request from this block, you are not ready:
- Proposed or final rating, and the date on the notice
- Path: corrective action or administrative review — pick one
- Investigation report in hand, every scored finding listed
- Process change for each scored finding, with an owner
- Exhibits dated after the change, indexed to those findings
- Service Center for the principal place of business, not a guess
- Copy of what was sent, how it was sent, who signed
- Commercial list of who still sees Conditional while you wait
- Hiring controls that will still be true after the letter arrives, including a CDLScan pass on the people you keep putting in trucks
That is the whole job. A safety rating upgrade is paperwork about an operation that already changed. If the operation has not changed, do not file.
Frequently asked questions
How do I request a safety rating upgrade?
In writing, to the FMCSA Service Center for your principal place of business, with a description of the corrective actions and the evidence that current operations meet the safety fitness standard. Confirm the current address and any special handling on fmcsa.dot.gov.
Is a safety rating upgrade the same as improving a CSA score?
No. The rating is a fitness label from an investigation. CSA percentiles come from roadside data and update on their own cycle. One request does not move the other.
Can I upgrade an Unrated snapshot?
No. Unrated means FMCSA has not completed a rated investigation. There is no label to change. Do not file an upgrade request to “get a Satisfactory.”
Do I have to wait before I can ask?
Not as a punishment period on Conditional. You can ask once you have actually corrected the deficiencies and can prove current compliance. Asking the week you wrote the policy, with no post-fix files, is how packets get denied.
What if FMCSA denies the request?
Read the denial. You may be able to send a stronger corrective-action packet, or you may have a separate administrative-review path if you think the decision itself was wrong. Confirm the current options on fmcsa.dot.gov instead of guessing a deadline from memory.
Will the request stop a shipper from seeing Conditional?
No. The public snapshot stays until FMCSA issues a written change. File because the operation is fixed, not because a bid is due this afternoon.
Should I file corrective action and administrative review at the same time?
Only if you truly have both theories, and even then keep them distinct. Most carriers have one. A mixed letter reads like you are not sure what you fixed.
Where does CDLScan fit in an upgrade packet?
It does not replace a finding, an exhibit, or an FMCSA request. CDLScan is how you stop restocking the Driver factor with people prior carriers would not take back — the part no rating letter can see.