A long-distance move has 15 things that need to happen before the truck leaves the yard. Scope confirmed. Rental truck reserved. Hotels booked for the driver. Driver’s license on file. DOT medical current. 1099 and contracts signed. Customer packet signed. Bill of lading ready. Itinerary checklist complete. End-of-move checklist complete.
Nobody has a checklist for this. The dispatcher remembers some of it. The ops manager remembers different ones. The driver remembers the ones that bite him. Things fall through. The truck leaves without the signed customer packet. The driver arrives without a hotel reservation. The DOT medical expired last month and nobody caught it until the weigh station turned him away.
MoveRight now tracks every one of them — and turns red when something’s overdue.
The OTR Ops Readiness Dashboard
As of the August 2026 release (Changelog_2608.md !2263), the ymm-interstate-usa zone has a new dashboard tab: Ops Readiness. It’s a per-day checklist for every long-distance move on the board, grouped by how many days out the move is.
Each row is a job. Each column is a readiness item. The columns are grouped by the day the item is due:
- Booking — scope confirmed, rental reserved
- 10 days out — hotels, driver DL, DOT medical, 1099/contracts
- 7 days out — customer packet signed
- 5 days out — BOL origin ready
- 2 days out — itinerary checklist, EOM checklist
When an item is incomplete and its due day has passed, the row turns red. The dispatcher sees red, knows exactly what’s missing, and fixes it before the truck leaves — not after.
The dashboard is scoped to the ymm-interstate-usa zone. It doesn’t appear in local-move zones, where these items don’t apply.
Manual Checkboxes That Persist Per Job
Six of the readiness items are manual checkboxes. The dispatcher or ops manager checks them off:
- Scope confirmed
- Rental truck reserved
- Hotels booked
- Driver’s license on file
- DOT medical current
- 1099 and contracts signed
These persist per job. If the job has three events (load, transport, unload), checking the box on one event syncs it across all events on the same job. You don’t check “hotels booked” three times for the same move. You check it once. The dashboard knows.
Document Signing Status, Auto-Resolved
Four of the readiness items are document signing statuses — and these don’t need a manual checkbox. They auto-resolve from Aegis artifact metadata:
- Customer packet signed
- BOL origin signed
- Itinerary checklist complete
- EOM checklist complete
When a customer signs the customer packet through Aegis, the dashboard updates. When the BOL is signed at origin, the dashboard updates. Nobody has to check a box. The signing event updates the artifact, the artifact metadata flows into the dashboard, and the column goes green.
This is the difference between a checklist and a system. A checklist relies on someone remembering to check the box. A system reads the artifact and knows.
The Document Matching Fix
Here’s the honest engineering moment. When we shipped the dashboard (!2263), the “Customer Packet Signed” column was blank for every OTR job. The reason: the dashboard’s Cypher query only matched two document types — “Customer Packet” and “Moving Contract.” But OTR jobs use “OTR Customer Packet.” Same document, different name. The query missed it.
We shipped the fix in !2268. The docType matching now recognizes every supported document variant:
- OTR Customer Packet
- Customer Contract
- Washington Moving Contract
- Oregon Moving Contract
- Bill of Lading — Full Value Protection (FVP)
- Bill of Lading — Released Value (RV)
- Bill of Lading — Platinum Value Protection (PVP)
- Visual inventory PDFs uploaded without docType metadata (matched by artifact name)
If a franchise uses a state-specific contract (Washington, Oregon), the dashboard catches it. If a driver uploads a visual inventory PDF without tagging the docType, the dashboard catches it by artifact name. The red row goes green when the document exists and is signed — regardless of which variant it is.
Spreadsheet Checklist vs. Ops Readiness Dashboard
| Spreadsheet Checklist | Ops Readiness Dashboard | |
|---|---|---|
| Where it lives | A shared Google Sheet, emailed around | Inside MoveRight, on the job |
| Who updates it | Whoever remembers | The dispatcher, and the Aegis signing events |
| Document status | Manual entry — someone types “signed” | Auto-resolved from artifact metadata |
| Overdue visibility | You have to scroll and look | Rows turn red |
| Per-event sync | No — each event is a separate row | Synced across all events on the same job |
| State-specific contracts | You have to add a row for each | Matched automatically (!2268) |
| Visual inventory PDFs | Manual upload log | Matched by artifact name (!2268) |
| Zone scoping | One sheet for everyone, or one per zone | Scoped to ymm-interstate-usa |
The spreadsheet is a list. The dashboard is a system. The list relies on discipline. The system relies on data.
MoveRight is the moving company CRM that tracks the 15 things that need to happen before the truck leaves — and turns red when one of them is overdue, so the truck doesn’t.
References: