The yes-to-JO gap is the stretch between a customer accepting your quote and a complete, booked job order. Done manually it costs 15–30 minutes of pure data entry per booking — re-typing the lane, cargo, rates and terms that already exist in the quote — plus the queue time the “yes” spends in an inbox before anyone starts. Across a few hundred bookings a month, the gap is an unbudgeted headcount line and the birthplace of most job-file errors.
Why does re-keying still exist in 2026?
Because the yes arrives in one system and the job lives in another. The quote is a PDF or an email; the job order is a TMS record; the carrier booking is a portal form. DCSA — the carrier-owned standards body, with no software to sell you — characterises ocean booking plainly: multiple rounds of manual data entry may be required for a single booking. The same body reported that only 1.2% of carrier bills of lading were digital in 2021. The industry’s default integration layer is still a coordinator’s keyboard.
How much coordination does one container actually take?
The Maersk/IBM shipment study traced a single container move through ~30 organisations and 200+ interactions, and put the paperwork at roughly $300 of a ~$2,000 container move. The study is from 2014; the ratio has proven durable. The booking desk sits at the centre of those interactions — every one of them reads from, or writes to, the job file. Which is why the minutes spent building it are only the visible cost.
What does the gap cost a mid-size forwarder?
Run the arithmetic: 300 bookings a month at 15–30 minutes each is 75–150 coordinator-hours per month spent re-typing known data — before counting the chase for missing fields or the amendments that re-keying errors trigger. Automation vendors put the reclaimable time between 15 minutes per booking (cargo.one) and up to two hours per shipment (Raft) — vendor figures, but the direction is unanimous. Put your own volumes and salary costs into the calculator and see what the gap costs you specifically.
The data-entry minutes are only half the gap. The other half is latency: the “yes” that lands at 6:40 pm and waits until tomorrow’s inbox triage. On tight sailings, the queue time — not the typing time — is what costs the vessel.
What does closing the gap look like?
The desk reads the go-ahead where it lands — an email thread, a WhatsApp “ok pls proceed” — matches it to the quote it accepts, and builds the job order from the quote’s own data. Zero fields re-keyed, one ask for anything missing, booking pushed to the carrier, and your coordinator reviews a built JO instead of building one. The end-to-end run takes 5 minutes 42 seconds — the whole flow is on how it works.
From reading to watching.
Everything on this page runs live in a working booking desk. Bring one accepted quote and watch it become a booked job order.
Book the working session