Monitoring address and contact changes

mcs-150 updates are a signal

Carriers update physical and mailing addresses on the MCS-150. A move can be ordinary. A move three days after you approved them, plus a new cell, is a re-check.

Physical address is where the census says they are. Mailing address is where paper goes. Identity theft and chameleon files often keep one and change the other. Store both if the snapshot has both.

A shared bookkeeper suite used by several DOTs is weak evidence by itself. Pair it with phone and officer overlap before you call it reincarnation. Write the match, not the theory.

MCS-150 updates are carrier-filed. They can lag a real move or precede a paper move. Either way, the snapshot you stored is the baseline. Compare to the snapshot you pull now, not to a memory of the city.

compare addresses yourself

Store the address from the snapshot at approval and compare it on the next lookup.

Do not tell a shipper that you get an alert when a carrier moves unless you actually compared the two snapshots.

A new lookup will show the current census address. It will not highlight a diff unless you kept the old one. Keep the old one.

what to compare on the next dispatch

Street, city, state, ZIP on physical address. Telephone. Legal name and DBA. If any of those moved, repeat identity verification before you cover. Call the census number on the new record.

A new state on the physical address is not illegal. It is a reason to confirm the people and the trucks. Authority can remain active while the yard moves. Your callback still has to reach the same legal entity.

If the rate con still shows the old city as if it were a legal name, fix the paper. Addresses are not DBAs. Do not let a city nickname replace the FMCSA name.

ordinary moves versus stacked changes

One field changing — new suite number, new mailing PO box — is usually operations. Three fields changing at once — address, phone, officers — is a stacked change. Treat stacked change as a new identity job.

If they volunteer a rebrand or a prior MC, look that MC up before you cover. Compare the old snapshot to the new one. Same trucks and same cell with a new DOT is the chameleon pattern.

Do not publish the stacked change as a government finding. Document it internally. Cover only after the current legal entity is the one on L&I and on the rate con.

process agents are not the yard

BOC-3 process agents are a 49 CFR Part 366 filing. They are not the physical address of the carrier. A change of process agent is a different event from a yard move.

Missing BOC-3 is a revocation trigger. Do not ignore a BOC-3 failure because the street address looks stable. Open L&I.

If L&I shows process-agent problems and the census address just changed, you have two problems. Either one is enough to pause cover.

put the old and new lines in the file

Save physical address at approval. On the next dispatch, compare to a fresh QCMobile snapshot. If it changed, keep both strings and the two dates.

The load folder should show you noticed. "Address updated" without the before/after is not useful to the next broker on the desk.

If you cannot find the stored approval address, you cannot monitor change. Re-baseline: store today's snapshot and do identity again if anything about the thread feels new.

factor, shipper, and yard addresses are not the census

A factoring company address on an NOA is not the carrier's physical address. A shipper warehouse is not the carrier's physical address. Do not "confirm identity" by matching those.

Google Maps on the census street is a hint. An empty lot can be a virtual office or a lag in Street View. It is not, by itself, a chameleon finding. Pair it with the phone call.

If the census city is far from the driver's pickup ETA, ask. Owner-operators run long. A California DOT sitting in a New Jersey thread with a brand-new MC is a slower conversation than a California DOT picking up in Oakland.

Mailing PO boxes are common. They are not a substitute for a physical address on the snapshot. If physical is blank on QCMobile, say it is not on the snapshot. Then call. Do not invent a street from the email footer.

desk checklist

• Save physical address (and mailing if present) at approval.
• On the next dispatch, compare to a fresh QCMobile snapshot.
• If address or phone changed, repeat identity verification before cover.
• Stacked changes (address + phone + officers) get a prior-MC look if they rebranded.
• BOC-3 is separate from yard address; still read L&I.
• Do not treat a saved address as current without a fresh snapshot.

what belongs in the load file

• Approval snapshot with physical address and telephone.
• Current snapshot with the same fields and a new timestamp.
• Before/after note if anything moved.
• Census callback note after a change.

fail closed

• Address or phone changed and you did not repeat identity.
• Stacked change plus a new MC story you did not look up.
• BOC-3 missing or rejected on L&I.
• No stored baseline address, so you cannot tell what moved, and this is a first cover in a long time — re-check identity fully.