The customer’s message arrives mid-afternoon: reduce the booking from two containers to one. The temptation is to open the carrier portal, click Amend and change the count before the depot collects the wrong equipment. A minute spent checking first avoids the harder conversation later: a second amendment, an unquoted change fee, or a revised booking confirmation nobody can match to an approval.

Use this checklist before submitting any ocean freight booking amendment request — a container count, an equipment type, a sailing, a port pair or a commodity detail. It is the step before our amended booking confirmation checklist, which handles what the carrier sends back.

1. Confirm what is actually changing

  • Write the change in one sentence: which field moves from what value to what value (for example, container count from two 40HC to one 40HC).
  • Name the source of the change — customer, supplier or internal team — and keep the original message.
  • Separate bundled changes into individual instructions. A quantity reduction and an equipment-type substitution are two amendments even in one email, as our container quantity and equipment playbook shows.
  • Confirm what stays the same: ports, vessel, commodity, contract number, shipper and consignee.
  • Check whether the change can be amended online at all, and which fields the carrier’s flow covers. Maersk’s Spot amendment guidance, for example, lists schedule changes, adding or removing containers, haulage, inland and store door attachment, and weight or commodity changes among the parts of a Spot booking that can be amended online. Confirm the equivalent scope for your carrier and booking product.

2. Check the equipment and shipment state

  • Confirm whether equipment is unreleased, released but uncollected, or already collected. A container already moving changes the request and its urgency.
  • Confirm the full container has not gated in. Once it has, the request may no longer be a simple amendment.
  • Identify equipment still assigned to the booking that the change would orphan, and decide whether it needs cancelling or releasing.
  • Save the current booking confirmation, its reference and issue date, so the request is tied to the version you actually hold.

3. Know the costs and deadlines before you submit

  • List the applicable cut-offs — cargo, shipping instructions, VGM — and where each date came from. An amendment landing after a cut-off is a different conversation.
  • Establish which charges the change triggers. Maersk’s Spot amendment guidance, for instance, shows vessel availability with deadlines, any new freight charges and any change fee before you decide to proceed.
  • Mark each cost as quoted, estimated or unknown. Never submit a request carrying a charge you cannot explain to the customer.
  • Record the carrier’s stated confirmation route, so the team knows what to expect back. Maersk’s Spot guidance describes instant confirmation on the portal with a PDF copy following.

4. Attach the approval to the exact request

  • Name the person authorised to approve this change and its known cost basis.
  • Keep the approval next to the specific field change and booking reference — not in a separate thread.
  • If the approval is conditional (“yes, if there’s no change fee”), record the condition and who resolves it before submission.

5. Submit and set up the check that follows

  • Submit through the carrier’s stated amendment route, keeping a copy of what was submitted and when.
  • Note every field you expect to see changed in the revised confirmation.
  • Give the follow-up an owner and a due time: who compares the returned confirmation against this request, and by when.

Example

Example. Booking EX-001 covers one 40HC container, with the cargo-ready date moving from 8 to 12 November and no empty collected. The operator obtains approval for Option B with the equipment unchanged, then writes down, before submitting, the values the revised confirmation must show: the approved option and one 40HC. When the amended confirmation comes back naming Option B but showing one 40GP, the mismatch is caught at once because the expected values were on paper before the request went in. The amendment stays open until the equipment is corrected or a new approval covers it — the discipline the booking amendment record exists to keep.

Comparing the written request, the approval, the submitted values and the returned confirmation is mechanical work a system can prepare, while the decision to submit, accept or escalate stays with a named person.

If your team’s amendments keep coming back wrong, or approvals cannot be traced to the requests they covered, Let’s talk. Bring one recent booking change — the request, the approval and the returned confirmation — and we can review where the record breaks and scope a workflow that closes the gap. See the proposed approach in our booking rescheduling workflow.