US Notice of Readiness Records: Prepare the Facts for a Proper Review
Preserve what happened before deciding what it means
A US cargo team reviewing a notice of readiness should assemble the actual notice, the relevant communications and the supporting event chronology before summarizing its effect. A timestamp alone does not establish every fact needed for review. The useful first task is to make the evidence clear enough that the responsible advisers can assess the actual charter requirements.
BIMCO's 2013 definitions connect notice of readiness with arrival and readiness under the charter's required notification. BIMCO Laytime Definitions.
Those definitions apply in their stated incorporation context. They should not be used as a shortcut to declaring a particular notice valid. The commercial team can contribute by separating observed events, the content of communications and interpretations that still require specialist review.
Keep the notice and its transmission together
Retain the actual notice as sent, including attachments and the message carrying it. Record the sender, intended recipients and the time basis shown. A retyped entry in a spreadsheet can help organize the chronology, but it should lead back to the original evidence rather than replace it.
Distinguish the time a notice was prepared, sent, received and acknowledged. Those may be different events. If the available records establish only one of them, say so. Do not populate missing fields with the same timestamp merely to make a complete-looking table.
A reply should be read for what it actually says. An acknowledgment of receipt may not resolve every question about the notice's effect. A qualified response should retain its qualification in the review package. Ask advisers to assess the significance under the actual terms rather than converting every positive-sounding email into an unqualified acceptance.
If a later notice is sent, retain both versions and explain the sequence. The reviewer needs to know whether it was a corrected document, a repeated transmission or a notice following a changed event. A folder containing only the latest file can conceal facts important to understanding the earlier communications.
Build a chronology that separates related events
Identify the events relevant to the enquiry, such as reported arrival, the location stated, inspection activity, notice transmission and commencement of cargo work. Use the descriptions in the underlying records. Avoid replacing a precise event with a broader label that implies more than the source establishes.
BIMCO publishes a Standard Statement of Facts recommended jointly with FONASBA. BIMCO Standard Statement of Facts.
A statement of facts can help organize a port-call history, but the team should still examine supporting records where a material event is disputed or unclear. A summary document and an individual message may use different terminology or time bases. The task is to expose and investigate that difference, not silently choose whichever version produces the preferred result.
Mark the source of each important entry. A vessel report, terminal message and agent's summary may describe different aspects of the same period. Preserve their attribution so that a reviewer can ask the appropriate party for clarification. Do not combine them into a single apparent observation without explaining how the entry was assembled.
A hypothetical chronology with a missing distinction
Consider a hypothetical Gulf loading call. A vessel message reports arrival at an anchorage at 08:00. A notice is transmitted at 08:20, and the cargo team's mailbox records receipt at 08:27. An inspection report records completion of a relevant inspection at 10:15. Cargo work begins at 14:00. All times are assumed to use the same stated local time basis for this example.
An internal summary lists only readiness at 08:00 and loading at 14:00. That summary has merged arrival with readiness and omitted the notice and inspection sequence. Even if its author intended a harmless abbreviation, it no longer provides an adequate factual basis for reviewing the notice.
The corrected package should show each event separately and attach the supporting records. It should not decide that the notice was valid or invalid merely because an inspection occurred later. The significance depends on the actual facts, requirements and contractual provisions, which the responsible reviewers must assess.
If the inspection record is incomplete, identify the missing information and ask the relevant party for clarification. Do not infer a favorable result from the absence of an adverse comment. Equally, do not turn an unanswered factual question into a conclusion that the vessel failed a requirement.
Resolve discrepancies without rewriting the history
When two records disagree, describe the discrepancy and seek a documented explanation. A corrected chronology should preserve the distinction between the original record and the later clarification. That makes it possible to understand what the parties knew at each stage and why the current summary differs.
Check time zones and dates before treating apparent differences as substantive. A message forwarded through several offices may display times differently. Preserve the original time expression and document any conversion used in the working chronology. If the basis is unknown, leave the point open until it is established.
Keep commercial calculations separate from the source chronology. A laytime analysis may use or exclude periods according to reviewed contractual assumptions. The event record should not be altered to match that calculation. Otherwise, a later change in interpretation can require reconstructing facts that were available at the outset.
The final package should make the review question explicit. Is the team asking about the notice's effect, the start of a calculation or an inconsistency in reported readiness? A focused question helps advisers identify which missing facts matter and prevents a large document bundle from obscuring the decision required.
Zeaclub's proposed readiness-record workflow should help cargo teams assemble that factual package and keep open questions visible. Bring Zeaclub the original notice, relevant communications and event records to discuss a clearer chronology. The objective is evidence that supports competent review, with observations preserved and contractual conclusions made by the responsible advisers.
Sources
- BIMCO: Laytime Definitions 2013, checked October 24, 2026; NOR definition context only.
- BIMCO: Standard Statement of Facts, checked October 24, 2026; document identity only.
Related articles
- 0994: US Demurrage Evidence Checklist: Organize Events Without Deciding Rights
- 0743: US Laytime Estimates: State the Counting Assumptions Before the Result
- 0744: US Demurrage Discussions: Isolate the Issue Before Negotiating the Amount


