Demurrage evidence: build the submitted claim package

Key takeaways

• Review the actual claim and documentary requirements before assembling the submission.
• Distinguish notification from the documented claim where the agreement does so.
• Match supporting material to the components of the calculation.
• Preserve evidence of the package actually transmitted to the appropriate recipient.
• Escalate missing or disputed requirements promptly instead of assuming that a covering email resolves them.

Build the requirement list from the actual agreement

Steamship Mutual's demurrage time-bar guidance notes that notice and documented-claim requirements can differ, and that supporting-document obligations depend on the charter wording. Its discussion is framed from an English-law perspective. Check the current text and obtain advice on the actual requirements, timing and recipient.

Do not begin with a universal folder checklist and assume that completing it satisfies the agreement. Standard internal lists are useful prompts, but they may omit a specific requirement or include material irrelevant to the actual claim. The operative list should identify its contractual basis and the scope of review.

The reviewer should also distinguish the requirements for presenting a claim from the evidence supporting its merits. A document can matter to the submission obligation even if the desk believes the calculation is understandable without it. Conversely, a well-organised submission does not prove the underlying entitlement.

Identify uncertainty early. If the wording raises a question about a category of documents, ask the adviser to resolve that question while the operations team obtains the relevant factual records.

Connect each claim component to support

Break the demand into its material components. For each, identify the event evidence, calculation basis and supporting explanation. A large attachment pack can still leave a central component unsupported if nobody checks the relationship between the documents and the amount claimed.

The account preparer should be able to point from a material interval to its source. The contract reviewer should be able to identify the adopted counting provision. The commercial principal should understand which premise the counterparty disputes. These are complementary views of the same claim.

Avoid relying on a document merely because its title sounds relevant. Confirm that it covers the correct operation, period and version. A report from a different call or an earlier provisional statement may not support the input being used.

If a document contains a qualification inconsistent with the claim narrative, resolve or disclose the issue appropriately. Do not remove the qualification from the summary while leaving it buried in the attachment. The package should present a coherent, accurately supported position.

Distinguish available, reviewed and submitted material

A document may exist in the voyage folder without having been reviewed for the claim. It may have been reviewed without being included in the outgoing package. It may have been sent previously in a different context. Those states should not be collapsed into a single “complete” status.

The submission record should identify the exact files and versions transmitted. Where the transmission uses links or another delivery method, establish what access and evidence the process provides and whether the method is appropriate under the reviewed requirements. Do not assume that an internal link is accessible to the recipient.

If material was supplied earlier, preserve that communication history for the adviser. Whether it satisfies the relevant obligation is a contractual question. The desk should not resolve it by marking the document as submitted without recording when, how and in what context.

The same care applies to a later supplement. Identify what is new and which component it supports. A supplemental package should not obscure what was included in the original submission.

Use a source-to-decision evidence matrix

This is an analytical matrix, not a universal list of mandatory documents. The actual agreement determines the requirements. In a live claim, name the specific source and responsible reviewer for each material question.

The matrix should expose gaps rather than hide them behind a percentage-complete score. A missing document central to the submission may matter more than numerous peripheral records already collected. The principal needs to know the significance of the missing item, not just how many files are available.

Fictional case: the folder is complete but the package is not

In a fictional demurrage claim, the operations team has collected the relevant port records in a shared folder. The claim preparer sends an invoice and calculation, assuming that the supporting records were included by a colleague. The internal tracker marks the claim as complete because the folder contains the expected documents.

The counterparty later asks for material that was never attached to the outgoing message. The team initially responds that the documents were available all along. That answer confuses internal availability with the actual submission history.

The reviewer identifies the original transmitted package, checks the applicable requirements with an adviser and prepares an accurate account of the missing material and subsequent communications. It does not declare the claim preserved merely because the documents existed internally.

A better process would have verified the outgoing package against the reviewed requirement list and retained its contents as sent. The fictional case does not determine whether the later supply cures any issue; it shows why submission evidence must describe an external communication rather than an internal folder state.

Escalate gaps according to their consequence

A missing factual clarification, an unavailable document and an ambiguous contractual requirement need different responses. The operations source may resolve the first. The principal may need assistance obtaining the second. The adviser should address the third.

Where a requirement cannot be met as expected, seek prompt advice on available steps. Do not assume that a reservation, placeholder or explanation automatically substitutes for the required material. Record the issue accurately so the decision-maker can assess it on the actual facts.

After submission, preserve acknowledgments and substantive responses separately. Receipt confirmation is useful evidence of communication, but it should not be described as acceptance of completeness, validity or liability unless that is actually established.

The completed claim file should let a new reviewer identify the demand, its support and the submission history without guessing. That clarity supports both commercial negotiation and any later specialist assessment.

Common mistakes

The main mistake is treating documents in a shared folder as documents submitted. Another is using a generic checklist without reviewing the actual claim provision. Both can produce misplaced confidence in a package that has not been properly assessed.

Do not equate acknowledgment with acceptance of liability. Avoid sending large unsorted packs without connecting evidence to the calculation. Finally, escalate missing material with its significance; a vague “documents pending” note gives the principal little basis for a timely decision.

Where Zeaclub fits

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Zeaclub offers digitalised procedures across the voyage workflow.

Explore Zeaclub

Explore Zeaclub