Broker guideReviewing a carrier contact change after approval
Treat changes to reported contact details as a reason to review the relationship and its context.
Updated 2026-09-13 · CarrierTrail product workflow
Compare the changed fields
Begin with what actually changed: the reported phone, physical location, company name or another census field. Check when CarrierTrail observed the change and the publication date of the underlying source. An observation time is not necessarily the time the carrier submitted its update.
Verify through an established channel
A new contact detail can have an ordinary explanation. Use your team’s established verification process and previously trusted contact channels to resolve uncertainty. Do not label a carrier fraudulent because a field changed, and do not let a newly supplied contact be the only basis for resolving a concern.
Leave a useful trail for colleagues
Describe the changed field, what your team checked and why the carrier remains approved or needs review. Notes belong to your workspace. CarrierTrail does not publish another broker’s private rejection or approval as a public risk label.
Use a before-and-after review note
Copy this structure into your note: USDOT; field changed; previous source value; new source value; source publication date; observation date; verification channel used; explanation received; unresolved questions; reviewer and next action. Keeping the previous and new values together prevents a colleague from having to reconstruct the issue.
Example: a phone update after approval
Illustrative example: a watched carrier’s reported phone changes after your approval. Review the source change, then use a previously established contact channel to ask about it. Record whether the explanation was confirmed and whether other details also changed. The change can prompt a review without automatically changing your carrier decision.
Worked review example
Illustrative scenario. An approved carrier's phone number changes in the next census observation. Dispatch says the company moved offices last week. The explanation is plausible, but the source publication date and the claimed move date are different. Your task is to document the change and verify the explanation, not infer motive.
A practical review sequence
Compare
Save the old and new values with the observation and publication dates. Identify whether the phone, address or several fields changed together.
Verify
Use a contact route established before the change where possible. Record the person's role and what they confirmed about the new details.
Update
Once the discrepancy is resolved, update your team's operational contact record and explain why. Keep the earlier value in the review history instead of erasing the trail.
What to put in the review record
The note should connect the changed field to the explanation, verification source and next review date. Separate a carrier's statement from facts your team independently checked.
Before closing this review
If the original contact cannot be reached, record that limitation and assign follow-up. Repeated calls to the same newly supplied number are not independent confirmation.
What if dispatch provides a reasonable explanation immediately?
Save the explanation as a statement from dispatch, then record the independent check your team used to confirm it. Plausibility can guide the investigation but should not be confused with confirmation. For example, a claimed office move can explain why several fields changed together, yet the reviewer still needs to connect the new contact details to the intended company. This distinction makes the note useful if another colleague later needs to understand what was actually established.
Should every change produce a rejection?
A changed field is an observation, not a decision. Review its relevance, the available explanation and the evidence. Record the team's conclusion in its own terms instead of converting every update into the same outcome.
Use these steps alongside your organization’s verification process. CarrierTrail presents public records and saves team decisions; it does not certify carriers or insurance coverage.
Read the data methodology → · All broker guides →