Key takeaways
- Separate the overall commitment from individual shipment instructions.
- Track changes against the remaining programme.
Build a programme ledger
A useful COA record links each shipment to the broader agreement. Without that link, a desk may handle individual nominations correctly while losing sight of cumulative quantities or scheduling commitments.
- Record the overall cargo and scheduling framework from the agreement.
- Log nominations, responses and any approved changes by shipment.
- Reconcile completed movements with the programme still outstanding.
For a recurring coal movement, a deferred shipment should remain visible in the programme ledger. Do not automatically treat it as cancelled or transfer it into another period without the necessary confirmation.
Common mistakes
Avoid copying a previous shipment instruction without checking quantity, dates and port details. Do not use a completed-shipment total as a substitute for reviewing the contract's treatment of shortfalls or changed timing.
Where Zeaclub fits
Zeaclub supports agentic, AI-assisted operations with a human in control.
Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.
Explore Zeaclub
Educational information only; not legal, financial or trading advice. Contract wording and applicable rules control. Verify current requirements and obtain qualified advice before acting.
Frequently asked questions
Must the same ship perform every shipment?
Read the agreement; vessel nomination and substitution depend on its provisions.
Is every shipment a separate planning task?
Yes. Each still needs current cargo, vessel, timing and port information.
What is the key administrative record?
A programme ledger connecting nominations and completed shipments to the overall commitment.
How should a deferral be recorded?
Keep the original requirement, authorised change and revised programme position together.