How to document a denied carrier so the next desk can replay it

write the actual reason

"Looks sketchy" does not help the next broker on your desk. "L&I pending cancellation 12 Sep 2026" or "census phone reached a different legal name" does.

Cite the system, the field, and the date. That is enough. Adjectives are not evidence. The next person should be able to open the same door and see the same fact or see that it changed.

If you denied on identity, name the mismatch: rate con versus FMCSA legal name, phone versus census, driver not acknowledged. If you denied on authority, name the L&I status. If you denied on credit, say credit.

Time zones and date formats belong on the note. "Pending cancellation Friday" without a year is how two Fridays get confused. Copy the date as L&I shows it.

keep it internal and factual

Denied-carrier lists are your records. They are not FMCSA findings. Do not publish them as if they were a government action. Do not forward the list to a shipper as a watchlist.

Facts you copied from L&I or SAFER are public record. Your conclusion "do not use" is internal policy. Keep those layers distinct in the note.

Do not paste peer accusations into the denial field. See community-flag practice. Convert or omit.

If a regulator or court later asks for the list, you want dates and public-system fields, not insults. Write the note as if it will be read aloud. That keeps it short and checkable.

what a usable denial note contains

DOT, MC, legal name as filed, date of the check, system used, field that failed, and the desk rule applied (for example: first-time after hours, pending cancellation, name mismatch).

Attach or point to the screenshot. A note without an artifact is a memory. Memories drift on night desks.

If multiple reasons applied, list them. Do not hide a name mismatch under a vague "safety" word when you never opened SMS.

re-check if they return

Filings reinstate. Phones get updated on the MCS-150. A denial is a timestamp too. If they return with a reinstatement story, open L&I again. Do not cover on the old no, and do not cover on their email claim without the new screen.

If the original denial was identity, a new filing does not fix a still-wrong callback. Repeat the census call.

If the original denial was credit, a clean L&I does not create a credit approval. Keep the categories honest so you do not accidentally launder a credit no into a safety yes.

consistency across the desk

Two brokers denying the same MC for different unstated reasons is how exceptions sneak in. Shared notes, same fields. If your rule is 30-day re-check, the note should show the last check date that failed the rule.

Do not keep a shadow list in personal chat that the rest of the desk cannot see. The load file and the denial log should match.

When you reverse a denial, write why and attach the new L&I or snapshot. Reversal without an artifact is how a chameleon gets back on the board inside your own company.

what not to store as if it were proof

Anonymous screenshots, Facebook comments, and "everyone knows" lines are prompts. They are not the denial reason unless you converted them into a record match.

Do not store a fabricated shared-phone count. If you googled the number and found another company, write the URL and the name you saw, not a fake statistic.

Do not store an SMS percentile as the sole denial without the rest of the file. Percentiles are questions. Unsatisfactory is a rating. Keep the words straight.

who can see the list, and how long you keep it

Internal access is a company rule. The desk needs the list. Sales should not paste it into a customer Slack. IT should not publish it on a public status page. Treat it as operational records.

Keep the artifact as long as you keep load files that relied on the denial. A denial without the screenshot is the first thing that goes missing in a dispute. Same retention thinking as the load folder.

If a carrier asks why they were refused, you can state the federal fact: pending cancellation, name mismatch, no callback to the census phone. You do not owe them a tour of peer flags. You do not owe them a fake safety rating.

If they fix the fact, a new check can reverse the denial. Put the new screen in the same log. The history of no-then-yes is useful. It shows you respond to filings, not to grudges.

desk checklist

• Denial note cites the system, the field, and the date.
• DOT, MC, and legal name as filed are in the note.
• Screenshot or print is kept with the note.
• Peer gossip is not the written reason unless converted to a record fact.
• Re-check if they return with a reinstatement.
• Reversal gets a new artifact, not a chat emoji.

what belongs in the load file

• Denial note with system, field, date, DOT/MC/name.
• L&I or snapshot that shows the failing field.
• Rate con or email that showed the mismatch, if identity.
• Re-check artifact if they returned.

fail closed

• Covering a previously denied MC without a new L&I and identity check.
• Publishing the denial list as if it were FMCSA.
• Denial reason that cannot be opened on a public system or a call log.
• Reversal with no new dated screen.