For years the two boards had a working handshake. You posted a load once, and the other board picked it up. It was never elegant, but it was one entry, one truth, one place to update a rate.
That link is gone. Since the integration lapsed, every broker running both boards — which is most of you — is doing the same job twice. Not conceptually twice. Literally twice: the same VIN, the same origin ZIP, the same rate, typed into two windows.
What actually broke
Nothing about your workflow changed. What changed is that the second board no longer knows the first one exists. Post a Camry from Dallas to Phoenix on Central Dispatch and Super Dispatch has no idea. Raise the rate by $75 because it has been sitting three days, and you now have two prices on the market for one car.
That last part is worth sitting with. Two live prices for the same load is not an inconvenience. It is a negotiation you already lost. A carrier who finds the cheaper post has no reason to call you about the other one.
The boards didn’t break your process. They broke the assumption your process was built on — that a load exists in one place.
The math on one load
We instrumented a five-agent shop for one week and timed every duplicate action. Not estimates — a stopwatch and a spreadsheet. Here is the life of a single load.
| Action | Times per load | Duplicate time |
|---|---|---|
| Initial post to second board | 1 | 1:50 |
| Rate update | 1.4 | 0:56 |
| Status / notes edit | 1.1 | 0:38 |
| Takedown after delivery | 1 | 1:16 |
| Per load | — | 4:40 |
Four minutes forty seconds. It sounds survivable, and that is exactly why it survives. But a solo broker moving 300 orders a month is spending 23 hours on it. A fifteen-agent shop working 1,200 loads is spending 93 hours — more than two full-time weeks — on keystrokes that produce nothing.
The costs you don’t see
Loads that never came down
The takedown is the last thing anybody does and the first thing anybody forgets. The load delivered. The customer paid. The post is still up. Now your phone rings for a car that has been in a driveway in Phoenix for six days.
In the week we measured, 11% of delivered loads were still live on at least one board 48 hours after delivery. Every one of them was generating calls.
Stale rates
Board A says $850. Board B says $925, because someone repriced on Tuesday and only had one window open. The carrier books at $850. You just paid $75 for a data-entry problem.
The agent who stops posting to the second board
This is the failure mode nobody reports. Faced with 4:40 of retyping, a busy agent quietly decides that one board is enough. Your coverage halves. Nobody tells you. You find out when a load ages out.
What to do about it
Three options, in ascending order of how much you will like them.
- 1.
Pick one board. Cheap, immediate, and it costs you carrier coverage. Viable only if your lanes are dense enough that one board fills them.
- 2.
Assign takedowns to one person. Does not fix the posting duplication, but it kills the 11% zombie-post problem, which is the one your carriers feel. Do this today.
- 3.
Post from a system that talks to both. One entry, both boards, one place to reprice.
How TheCarGo handles it
We hold official two-way API integrations with both Super Dispatch and Central Dispatch. Not a scraper, not a browser extension — the broker initiates, and the broker keeps control of pricing.
In practice: you dispatch a load once. It appears on both boards. You raise the rate in TheCarGo and both posts move together. The order is marked delivered and both posts come down without anyone remembering to do it. The 4:40 goes to zero, and the 11% goes to zero with it.
That is the whole feature. It is not clever. It is the thing that used to work, put back.