A laytime claim can turn on a single disputed hour: when a valid notice was tendered, whether a berth was available, or whether cargo operations stopped for a charter-party exception. This guide to laytime evidence collection sets out how owners, charterers, terminals, and cargo interests can build a contemporaneous record that supports a fair calculation of demurrage or dispatch.
The objective is not to assemble paperwork after a dispute has formed. It is to preserve objective evidence while the vessel call is underway, align it with the governing charter party, and identify gaps before they become expensive assumptions. A properly supported Statement of Facts is valuable, but it is only one part of the evidentiary file.
Start With the Laytime Clause, Not the Port File
Evidence collection should begin with the operative terms. The charter party determines what must be proven, when time starts, which periods count, and which events interrupt or exclude time. A port record that is accurate but not connected to the contractual wording may still fail to resolve the claim.
Before arrival, the responsible operations or claims team should identify the key contractual triggers: the notice of readiness requirements; berth, port, or dock wording; weather working day definitions; shifting terms; time allowed; and exceptions for weather, strikes, equipment breakdown, congestion, holidays, or cargo-related delay. The relevant fixture recap, rider clauses, and incorporated terms should be retained with the evidence file.
This review also establishes what timestamps matter. Under one charter party, time may start after a stated period following valid notice of readiness. Under another, time may depend on berthing, free pratique, customs clearance, or cargo readiness. A record of vessel arrival alone does not answer those questions.
Build the Evidence File in Real Time
The strongest laytime records are created during the port call by people who understand the operational significance of each entry. Waiting until completion to reconstruct events from emails, terminal logs, and recollection creates avoidable conflicts over sequence and causation.
Use one controlled time standard throughout the file. Local port time is usually practical, provided every record clearly identifies the time zone and daylight-saving status where applicable. Do not mix vessel time, terminal system time, and email-server time without reconciling them. A one-hour discrepancy can materially alter a demurrage calculation.
The core file should preserve the notice of readiness and all transmission evidence, including the tender time, recipient, method of service, acknowledgments, and any rejection or qualification. Keep the vessel’s arrival message, anchorage or pilot-station position, berth nomination, pilot orders, free pratique status, and communications concerning berth availability. Where validity of notice is likely to be disputed, these documents are often more important than the final laytime worksheet.
A contemporaneous Statement of Facts should record each operational event in sequence, with the source of the entry identified where possible. It should distinguish between vessel arrival, tendering of notice, acceptance of notice, all fast, gang commencement, cargo commencement, stoppages, resumptions, completion, and sailing. Entries should be factual. Avoid conclusions such as charterers’ delay or owners’ fault unless the source document supports that finding.
What a Defensible Statement of Facts Must Show
A Statement of Facts should make the port call understandable to a party who was not present. It needs enough detail to establish not just that time passed, but why it passed and who controlled the relevant operation.
For every interruption, record the start and end time, stated reason, location, affected hold or hatch if relevant, and the source of the information. A stoppage described only as weather may be insufficient. Was loading physically prevented by rain? Did the terminal suspend operations under its rain policy? Was the hatch open? Was the cargo moisture-sensitive? Did another operation continue at a different hatch? These facts can affect whether time is excepted.
The same discipline applies to mechanical and terminal delays. A notation such as crane breakdown should identify the crane, the time reported out of service, repair or replacement activity, whether alternative equipment was available, and whether the failure stopped cargo work entirely or only reduced the rate. Where several causes overlap, record each cause separately rather than assigning a single broad label.
Supporting documents should correspond to major entries in the Statement of Facts. Depending on the trade and the dispute exposure, the file may include terminal loading logs, gang sheets, crane records, berth schedules, vessel deck logs, engine logs, weather observations, rain gauges, port notices, cargo tally sheets, draft survey records, surveyor reports, photographs, and relevant email or radio communications. The goal is corroboration, not volume.
Separate Facts From the Laytime Calculation
The operations record and the legal or commercial calculation should remain distinct, even when prepared by the same team. The Statement of Facts reports what occurred. The laytime calculation applies charter-party rules to those occurrences.
This separation protects the credibility of the factual record. If the Statement of Facts is revised to characterize every delay in favor of one commercial interest, counterparties are more likely to challenge the document as advocacy rather than evidence. A neutral, signed, and well-supported account is more useful to owners, charterers, insurers, and claims handlers.
The calculation sheet can then apply the agreed time count. It should state the contractual clause used, the notice time, commencement of laytime, time used, excluded intervals, and the basis for each exclusion. If an item is disputed, show the competing treatment rather than concealing it. For example, identify a rain period as excluded subject to proof that weather stopped cargo work under the applicable clause.
Control Documents, Signatures, and Revisions
Port-call evidence frequently comes from several parties with different commercial interests. The vessel may prepare a Statement of Facts, the terminal may issue its own log, and the agent may circulate a separate timeline. Differences are not automatically evidence of bad faith, but they must be identified early.
Obtain signatures where customary and practical, while understanding what the signature means. A signature may confirm receipt, attendance, or agreement with the facts. If a party signs under protest or refuses to sign, preserve that qualification and the reason given. Do not replace the original document with a clean version that removes objections.
Document control matters. Save original emails and attachments in their native form, retain photographs with metadata where available, and preserve version history for amended Statements of Facts and calculations. Each revision should show what changed, when, and why. A late alteration without an audit trail can weaken otherwise reliable evidence.
Independent attendance can be justified when exposure is material, cargo operations are complex, weather exceptions are anticipated, or the parties already disagree on delay causes. An independent marine surveyor can observe operations, review time records, document cargo and terminal conditions, and issue a neutral report focused on verifiable facts. This is particularly useful where a local record may not fully capture berth congestion, cargo readiness, shifting delays, or operational restrictions.
Common Evidence Failures That Create Claims Friction
The most costly errors are usually ordinary administrative failures. Notice of readiness is tendered but proof of receipt is missing. The time zone is unstated. A stoppage is recorded without a cause. A terminal log shows cargo work continuing while the vessel’s Statement of Facts records a full stoppage. The final calculation excludes time without citing the controlling clause.
Another recurring problem is treating all delay as laytime delay. Delays before valid notice, delays outside the contractual counting period, and events governed by a specific exception require different treatment. It depends on the charter wording and the evidence of what actually prevented performance. A detailed file allows the commercial team to make that distinction before the claim reaches arbitration, litigation, or P&I review.
For Gulf Coast calls and other weather-sensitive trades, preserve the operational context alongside the weather data. Rainfall alone may not establish that cargo work could not proceed. Conversely, a terminal shutdown log, hatch status, cargo sensitivity records, and independent observations may establish the connection clearly.
Make Collection Part of Port-Call Control
Laytime evidence should be treated as a port-call control function, not an end-of-voyage accounting task. Assign responsibility before arrival, establish a shared document checklist, and require prompt review of material stoppages and notice-related events. Escalate inconsistencies while the vessel, terminal personnel, and original records remain available.
When the file tells a consistent, time-stamped story, the laytime calculation becomes easier to audit and harder to challenge. That discipline protects commercial relationships as much as it protects a claim: the parties can address the facts promptly, reserve their positions where necessary, and keep the vessel’s next operation moving.

