A cut-off moved and nobody noticed
The booking was confirmed three weeks ago. Since then the carrier has sent two amendments: one changing the vessel, one bringing the cargo cut-off forward by a day. Both are in the booking inbox. The operator updated the vessel but missed the cut-off. The shipper delivers the container on the original cut-off day, and it misses the ship.
Meanwhile, a different shipper asked to add a container to a booking and the request is sitting unanswered in a carrier's portal.
Why bookings and jobs drift apart
Every booking goes through several rounds: request, confirmation, amendments from either side. Each one arrives as a separate message, and the job in your forwarding system only changes when someone copies the change across.
- Carrier confirmations and amendments look different for every carrier.
- Changes to cut-offs, vessel, equipment and quantity are easy to miss in a long message.
- Requests made through portals and by email are tracked in different places.
- Shippers and hauliers need to be told when cut-offs or collection dates change.
- Nobody compares the latest confirmation with the job.
What the drift costs
Missed cut-offs mean rolled cargo, delays for the customer and sometimes extra charges. Equipment changes missed at booking lead to the wrong container being collected. Operators spend time rereading booking emails to be sure they have caught everything. And customers lose confidence when they learn about a change after it has already caused a problem.
The booking tracking we build
- Booking requests are created from the job and sent to the carrier by email, through its portal, or through a booking platform where you use one.
- Every confirmation and amendment is read, whatever the carrier's format, and matched to its booking.
- Key fields are extracted: vessel and voyage, ports, dates, cut-offs, equipment, quantity, booking number, and compared with the job.
- Differences are flagged to the operator with the old and new values side by side. Changes to cut-offs and collection dates are highlighted.
- With one click the operator accepts the change into the job and notifies the shipper and haulier, using message templates you control.
- Requests without a confirmation after a set time are listed for chasing.
| Event | Today | With booking tracking |
|---|---|---|
| Carrier amendment | Read and copied by hand | Compared with the job automatically |
| Cut-off change | Easy to miss | Highlighted and sent on |
| Unconfirmed request | Forgotten | Listed for chasing |
| Telling the shipper | Separate email | One click from the change |
After
Jobs stay in step with the latest carrier confirmation. Operators see only what changed, not the whole message again. Shippers and hauliers hear about new cut-offs in time to act. And the booking history for each job is in one place, which helps when there is a dispute with a carrier about what was confirmed.
Peak season is where this shows most. When carriers are blanking sailings and moving cut-offs every few days, the volume of amendments jumps, and so does the chance of missing one. The tracking handles the volume the same way on a busy week as a quiet one, and the operator's attention goes to the changes that need a phone call to the shipper.
Checklist
- Carrier amendments are read and copied by hand.
- Cargo has missed a cut-off because a change was missed.
- Booking requests go unconfirmed without anyone noticing.
- Shippers learn about vessel changes late.
- Booking history is scattered across inboxes and portals.