When Normal Changes on Purpose

The largest brokerage deal on record was announced this month. Closing is expected next year. Between now and then, hundreds of thousands of carriers and tens of thousands of shippers will receive messages telling them that something has changed.

Every one of those messages will be legitimate. Every one is also a message someone else can send first.

This isn’t about one deal. Every acquisition opens the same window, including the small ones nobody reads about. This one is simply large enough that everyone hears about it at the same time, including the people who were waiting for it.

The control that breaks first

Most of what protects a freight desk from impersonation comes down to one question, asked by people who’ve done the job long enough to feel the answer: is this different from normal? A new contact on a familiar account. A new number. An email from a domain you haven’t seen. Each one is supposed to stop the work until someone checks.

An integration makes all of those true at once, on purpose. New contacts, new numbers, new domains, new portals, every week, all of them real. The check built to fire on the unusual now fires on everything. Nobody can stop the work 200 times a day, so people learn to wave it through. Not because they’re careless. Because the check has stopped telling them anything.

That is the window. A fraudulent message doesn’t have to look normal. It only has to look like the rest of the change.

The announcement is a briefing

Press releases name executives. Integration updates name the people taking over accounts. “Meet your new team” emails fill in the rest. Most operations work hard to keep exactly this information, who approves what and who talks to which carrier, away from outsiders. A transaction publishes it.

The new name matters too. Once a combined brand or a new division is public, nothing stops anyone from registering the obvious variations of it. Those domains then land in inboxes where staff have just been told to expect unfamiliar senders.

What the requests sound like

The scripts write themselves.

“We’re moving to a new payables platform. Please update your remit-to details.”

“All carriers must re-register on the new portal by Friday.”

And the quieter one: “We’ve moved freight for you before. Check your history.” Before the deal, a carrier who checked would find nothing. Afterward, the history may well be there. It is real. It just belongs to the other company.

A real integration team will send every one of these too. That’s the point. The content of the message can’t separate them.

The settings that loosen “temporarily”

The shortcuts are not dramatic. That is why they last. Moving mailboxes between companies is technical work done against a deadline, and deadlines produce shortcuts. Email authentication gets relaxed so the migration doesn’t bounce mail. Forwarding rules set up for the transition stay in place after it. Accounts get created in bulk, and the second login factor gets enrolled “later.” Each decision is reasonable on the day it’s made. Each one leaves a door open for whoever is watching for it.

The people side

Accounts get reassigned. A rep who worked a carrier for six years, who would have noticed the dispatcher sounded wrong, moves on. The new rep has no baseline to notice anything against. The relationship was a control, and nobody ever wrote it down as one.

Cost targets also mean people leave. Most leave cleanly. The exposure is access that outlives the last day. Addressing that doesn’t require assuming the worst about anyone. It requires treating access like inventory: counted, and closed the same day.

What holds up

None of this is solved by being more alert. Alertness is exactly what an integration wears out.

What holds up is a reference point that existed before the change.

• Verify against what you had before. Confirm any change request through a number on file before the announcement. Not the one in the message, not the one in the signature.
• One published directory. If you’re the company integrating, publish a single verified list of who your carriers and customers should hear from, and tell them to check against it. Memory can’t keep up with a reorganization. A list can.
• Two people on every banking change, especially while everything else is changing.
• Keep booking and payment approval apart. Reassignment is when they quietly end up with the same person.
• Close access the day someone leaves. Not at month-end.
• Get to your new name first. Register the obvious variations before someone else does.

For most of the people involved, a deal like this is good news. The integration is simply a long stretch in which normal is being rewritten. Whoever sends the new version of normal first gets believed.