Handle a rolled booking without leaving downstream teams on the old plan

The carrier moves a booking to another sailing. The planning screen updates the vessel, but the warehouse pickup still follows the old schedule and the documentation team assumes every cutoff has moved later.

Treat the rollover as a new plan version with an impact review. The team needs to know which commitments changed, which remain valid and which are still unconfirmed. Updating the booking header alone does not coordinate the operation.

Establish what the carrier has actually confirmed

Record the original booking, notice, proposed replacement, acceptance status and current carrier reference. A proposed alternative sailing is not the same as confirmed space on it.

Collect the revised vessel or service, voyage, routing, equipment instructions, terminal and applicable cutoffs. Preserve the source and timezone for each. If a field is absent from the notice, mark it as needing confirmation rather than copying the old value silently.

DCSA's Booking standard provides a common framework for booking exchanges. The actual carrier's supported process and response determine which amendment is accepted. DCSA — Booking standard

The booking owner should distinguish a carrier-initiated change from a shipper-requested alternative and record any commercial decision that follows.

A later sailing with an earlier document cutoff

This illustrative plan is reviewed at 09:00 Asia/Kolkata on 18 October 2026. It is a teaching scenario, not a carrier schedule.

The revised sailing is thirty-six hours later, while the document cutoff is eighteen hours earlier and the cargo cutoff twenty-two hours earlier. A rule that shifts every deadline by the departure change would produce the wrong instructions.

Assume document preparation and authorised review require six elapsed hours from the 09:00 review point. Completion at 15:00 leaves three hours before the new 18:00 document cutoff, provided the required inputs are available.

For cargo, the illustrative path needs two hours for the approved stuffing activity and three hours to reach the gate. To meet 20:00 with no additional buffer, work must begin by 15:00. If the earliest suitable vehicle can start at 16:00, arrival is 21:00 and the plan misses by one hour.

The answer is an approved alternative plan or an explicit exception decision, not an optimistic status change.

Recheck the commercial clocks separately

A rollover may affect storage, equipment use and other charges. Do not assume that a later vessel departure extends every free period. Identify the governing contract or tariff, its start event, scope and any written extension.

OOCL's India guidance illustrates movement-specific demurrage, detention and storage treatment. Those terms cannot be generalised into an automatic free-time extension for every rolled booking. OOCL India — Demurrage and detention free time and charges

Keep projected exposure separate from an accepted charge. Finance needs the relevant dates, tariff or agreement and any waiver or extension evidence. A carrier's operational notice may not resolve the commercial issue.

If the revised booking changes terminal or equipment return instructions, check the actual permitted movement and associated commitments. The transport team should not follow the old location merely because it remains in a cached work order.

Build an impact register with decisions

Keep “reviewed, unchanged” as a valid result. Not every dependency changes, but each material one should have an explicit disposition.

A document amendment may need its own accepted external response. Updating an internal shipping-instruction file does not prove that the carrier's current draft reflects it.

Reconcile the instructions already sent

List the outstanding pickup orders, appointments, document submissions and customer notifications tied to the original plan. For each, record the required amendment, who is authorised to send it and the acknowledgement.

If a cancellation or reschedule request has an uncertain outcome, do not assume the original instruction is inactive. Two trucks or two conflicting appointments can result from treating a lost response as a failed request.

Use stable instruction identities and plan versions. A downstream system should reject or flag an old-version update that arrives after the revised plan, while retaining it for audit.

Choose a coordination control the team can maintain

A shared change register can work when bookings are few and ownership is clear. A native forwarding or transport system can link dependencies to the booking. An integration is useful when it can propagate specific changes and reconcile responses, rather than broadcast a generic “booking updated” event.

Test an earlier cutoff, a rejected replacement booking, an unchanged free-time clock and an unacknowledged pickup cancellation. Include a notice arriving while documentation is being approved.

Measure unresolved dependencies, instructions still on an old plan and commitments missed after the notice. Do not measure success solely by how quickly the vessel field changed.

For a rollover-workflow review, start with the downstream instruction that most often remains active after the booking changes.

Make the revised plan executable

The useful result is an accepted set of coordinated commitments with the remaining gaps visible. A later sailing can create more time for one activity and less for another; the dependency review makes that difference actionable.

Next actions

1. Preserve the original booking and establish the confirmed replacement state.
2. Recheck each cutoff, location, resource and commercial clock.
3. Calculate the remaining preparation and transport path.
4. Reconcile all affected instructions and acknowledgements before treating the revision as complete.