Key takeaways
- Check contractual submission requirements at the start of the voyage file.
- Build the evidence index around the claim's actual disputed events.
- Preserve the submitted version, delivery record and subsequent changes.
Identify the correct claim and counterparty
Start with the contract under which the claim is proposed. Record the claimant, contractual counterparty, vessel, voyage and relevant ports. A shipping chain may contain several agreements, and the party that supplied an operational instruction is not necessarily the party to which this claim should be addressed.
Collect the agreed form, recap and amendments. Identify the demurrage, notice, supporting-document and dispute provisions requiring review. Do not borrow a deadline or recipient from another fixture. BIMCO's published CEMENTVOY comparison, for example, contains a form-specific claims presentation provision, illustrating why the actual contract must be checked. BIMCO CEMENTVOY comparison.
Ask the authorised reviewer to confirm the submission requirements and any legal deadline questions. Put the resulting actions into a calendar with a responsible person and backup. The preparation team should not assume that sending an invoice alone satisfies every contractual requirement.
Develop a claim narrative from the evidence
Write a short explanation of the voyage events giving rise to the proposed claim. Identify the commencement basis, relevant allowance, material interruptions and completion event. Keep the narrative consistent with the calculation and source records. An attractive summary that omits the actual point of dispute makes review harder.
Separate agreed facts from the claimant's position. If the other party disputes a notice or interruption, say what is disputed and identify the evidence supporting the proposed treatment. Avoid describing a contested conclusion as an uncontested event in the statement of facts.
The narrative should guide a reviewer to the documents without reproducing the whole contract or every email. Use precise references to the relevant calculation lines and exhibits. A reviewer should be able to follow the claim's reasoning without guessing which of several similarly named attachments contains the supporting record.
Assemble documents around material questions
Begin with the calculation and work backwards. For each material input, identify the source document and check that the file contains the complete relevant version. This often exposes a missing notice response, an incomplete statement of facts or a quantity document that differs from the workbook input.
Collect operational records needed to explain disputed events. A broad interruption label may require the underlying ship or terminal report. Preserve qualifications and reservations rather than removing them to simplify the package. The claim should withstand review of the full evidence, not depend on a selectively shortened extract.
Check legibility and document identity. A scanned page without the vessel name, date or signature attachment may be difficult to connect to the call. Request a complete copy where possible and identify any remaining limitation in the internal review notes. Do not create missing evidence by rewriting an unsigned working note as an agreed record.
Use a submission-readiness table
| Claim component | Readiness test | Typical corrective action |
|---|---|---|
| Contract basis | Relevant approved wording is identified | Retrieve recap or rider revision |
| Calculation | Inputs and disputed treatments are visible | Add source references or scenarios |
| Port chronology | Material events reconcile with records | Obtain clarification or correction |
| Required documents | Actual submission provision has been checked | Request missing supporting material |
| Recipient and channel | Address and delivery method are verified | Clarify through authorised contact |
| Submission record | Exact package can be retained and reproduced | Freeze the release version |
Apply the checklist before release, with a separate reviewer for material claims where practical. The reviewer should look beyond arithmetic to the relationship between the claim narrative and supporting evidence. A formula check will not catch a package sent under the wrong contract reference.
Keep a list of documents requested but not received. That list supports escalation and explains the status of the file. Whether a submission can proceed without an item is a contractual decision for the authorised reviewer, not a conclusion drawn from the checklist score.
Control transmission and later correspondence
Save the exact outgoing package, including attachments and the covering message. Record the recipient, channel, transmission time and available delivery evidence. If a portal is used, retain the submission confirmation and the files uploaded, subject to the platform's permitted procedures.
Do not replace the saved submission when a corrected calculation is later issued. Create a revision with an explanation of what changed and why. A revised amount may arise from corrected arithmetic, new evidence or a negotiated adjustment; those are different reasons and should not be merged into an unexplained new invoice.
Maintain a response register that separates requests for documents, factual disagreements, contractual arguments and settlement proposals. Assign the appropriate reviewer to each. This prevents routine document follow-up from becoming an accidental concession on the substantive claim.
Keep settlement authority clear. The preparer may assemble a comparison of positions, but should not imply acceptance of a reduced amount or final settlement unless authorised. Document coordination and commercial compromise are separate tasks even when handled in the same email chain.
Fictional case: a complete calculation with an incomplete notice file
In this fictional case, an operator prepares a demurrage claim supported by a detailed workbook and statement of facts. During the readiness review, a colleague notices that the workbook uses a notice event whose original email is absent from the submission folder.
The team retrieves the message and its response from the operational archive. The response contains a qualification that was not reflected in the initial claim narrative. The authorised reviewer considers the issue and directs the team to make the claimant's position explicit, with the relevant evidence attached.
The released package is therefore easier to examine and less dependent on an unexplained commencement assumption. Its completeness does not decide whether the position is correct. It ensures that the actual issue, rather than a missing attachment, becomes the focus of the counterparty's review.
Common mistakes
Treating an invoice as the whole claim can overlook required evidence and submission procedures. Another mistake is using a counterparty's operational address without checking the agreed notice channel. Both should be caught before release through a fixture-specific review.
Avoid overwriting earlier submissions or removing adverse correspondence from the evidence file. Preserve the history and explain revisions. Finally, do not allow a payment chase to introduce a new legal assertion that the claims reviewer has not approved. Consistency between the initial claim and later correspondence matters.
Where Zeaclub fits
Zeaclub offers digitalised procedures across the voyage workflow.
Zeaclub provides 24/7 operating systems and worldwide coverage.
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
When should claim preparation begin?
Begin by identifying evidence and submission requirements during voyage handover. The final amount may only be known later, but document collection can start immediately. Early preparation is especially useful for terminal records and notice evidence that may be harder to retrieve after the port call closes.
Is a demurrage invoice enough?
Check the particular agreement and obtain guidance on its requirements. An invoice states an amount but may not explain the basis or supply required documents. A reviewable package ordinarily links the amount to the calculation and evidence, with its status and recipient clearly identified.
What if a supporting document is missing?
Record the gap, request the document and escalate before the relevant submission decision. Preserve evidence of the retrieval effort. The authorised reviewer should assess the consequences and available steps; the preparer should not assume that a partial package either preserves or defeats the claim.
How should a corrected claim be issued?
Retain the earlier submission and create a dated revision explaining the changed input or reasoning. Attach the corrected materials and preserve transmission evidence. This allows both parties to distinguish a correction from a settlement proposal or a new substantive position.