Your Dispatch Board Is Lying to You.

The whiteboard says the truck is there. The truck disagrees.

EDITOR'S NOTE: This issue uses a fictional, synthetic dispatch scenario to explain a practical process. It does not report measured results at a client, promise improvements, or contain client records.

DIRECTION DROP | The roster is not the mission

The customer calls for an ETA. Dispatch checks the board. The board says "loaded." The driver says he's still at the rack. The second dispatcher says somebody changed the stop order. Nobody knows who did it.

Congratulations: you have built a real-time misinformation system with dry-erase markers.

The whiteboard is not the villain. Neither is the dispatcher who spent half the morning keeping it alive. The problem is a workflow that allows the same load to exist in three different states at once. Dispatch cannot steer a truck with information nobody trusts.

Mission: Make one operational status trustworthy, and make every exception belong to a person. Keep the ERP as the order system of record. Use the dispatch board to control the work, not invent a competing accounting universe.

COMMAND DROP | One load. One state. One owner.

Start with six plain-language states: NEW -> VERIFIED -> ASSIGNED -> DISPATCHED -> DELIVERED -> CLOSED. Add HOLD and EXCEPTION as visible stop points, not places to hide yesterday's mess.

Before the truck rolls: Verify the delivery location, product, requested quantity or quantity limits, time window, and any required handling instructions. If a safety-critical or order-critical field is missing, put it on HOLD. Do not make the driver solve an office data problem in a customer's yard.

When dispatch assigns it: Record the order ID, truck, qualified driver, planned sequence, and assigned owner. Assignment is not proof that the truck loaded. "I told Dave" is not a status code.

When loading changes the plan: Record the actual load or terminal reference, revised quantity where available, and the timestamp. If the planned and actual details diverge, mark an exception and notify dispatch. Do not silently overwrite history.

When delivery finishes: Capture actual delivered quantity, completion time, and required delivery evidence. Then reconcile the order and delivery record before anyone marks the job CLOSED.

What an honest dispatch record needs

Don't show customer street addresses or employee details in public demos. Use synthetic IDs. In production, restrict who can read, export, or change those values.

FIELD BUILD | A handoff test that isn't theater

Here is a synthetic exercise, not a published TNDS performance claim. Four trucks share 36 stops. At shift change, 15 remain active. Two are on HOLD: one for an unverified tank location and one for an unresolved product change.

Give the second dispatcher only the board and the written operating rules. No whispered side briefing. No phone call to the person who went home. Can they identify each truck's next stop, the two held orders, the owner of each exception, and the evidence required to resume?

If the answer is no, the system failed the handoff test. Fix the process before buying another giant television for the wall.

Acceptance test: Every active stop has an accountable status, a last update time, and one exception owner when something is blocked. The next operator can take over using documented information.

SIGNAL CHECK | Three warning lights

• The board and ERP disagree. The ERP owns orders and invoices; the dispatch board owns work-in-progress status. Reconcile by stable IDs and escalate mismatches.
• A status can be changed without evidence. Require the supporting event or a documented manual override. Preserve who changed it and when.
• The import stalls and nobody notices. Add a last-success timestamp, schema/header checks, and an alert. A green dashboard showing yesterday's dispatch plan is worse than an honest error message.

For regulated hazardous-material movements, shipping-paper duties still apply; a digital board is not a substitute for required documentation. Check the actual applicability and requirements before changing a shipping-paper workflow. See 49 CFR 177.817 and 172.200 in the sources.

TOOL OF THE WEEK | Google Sheets is fine. Pretending it is magic isn't.

A well-structured Sheet with Apps Script can run a useful first dispatch board. Use one source import, controlled columns, data validation, audit records, error alerts, and a manual fallback. Then test with two dispatchers touching the same work. If you need real concurrent writes and reliable event histories, a transactional database may be the cleaner next step.

Apps Script has execution and service quotas. They change, and exceeding them can stop a script. Check Google's current quotas rather than promising a trigger will "just run forever." A silent failure is not automation; it's a delayed surprise party.

FREE DROP | Ten-minute shift handoff

1. Count open orders and active deliveries against the ERP source.
2. Identify trucks, drivers, current stops, and next planned stops.
3. Name every HOLD and EXCEPTION with an owner and a next action.
4. Check the last successful import and any unmatched order IDs.
5. Have the incoming dispatcher explain the situation back using the board alone.

STOP POINT: If a safety-critical instruction or required shipment document cannot be verified, stop the assignment and follow the approved escalation process.

THE LAST WORD

Your best dispatcher is not supposed to be the company's RAM. If the operation crashes when they go home, you don't need more loyalty from them. You need a better damn system.

WORKS CITED / CHECK THE RECEIPTS

• PHMSA highway shipping-paper requirements, 49 CFR 177.817
• Applicability and exceptions, 49 CFR 172.200
• Google Apps Script quotas and limitations
• Google installable triggers

Pipeline Punks is the workshop side of True North Data Strategies LLC. Editorial and training only. Verify current regulations and customer-specific requirements before operational use. No client data is included.

Jacob Johnston | 719-204-6365 | jacob@truenorthstrategyops.com

Back to top