Notice of Readiness Preparation Checklist: Evidence Before Transmission

Key takeaways

• Check the actual notice provisions and amendments before arrival.
• Distinguish vessel readiness, notice transmission and acknowledgement.
• Preserve every version and the facts supporting it without rewriting the chronology.

Read the notice requirements before the port call

Collect the charter, recap and riders, then identify the provisions concerning arrival, readiness, notice recipients and transmission. Record any referenced definitions. BIMCO's laytime definitions are designed for incorporation into charter parties; their existence alone does not make them the agreed rules for every fixture. BIMCO laytime definitions.

Prepare a reference sheet that points to the wording rather than replacing it with unexplained abbreviations. Include the intended port and any unresolved berth information. If a term is ambiguous, seek guidance before arrival while there is still time to clarify the instructions.

Ask the contractual reviewer to identify which facts will matter to the notice assessment. The operator can then arrange to obtain those facts from the master, agent or terminal. This is more useful than sending the vessel a generic notice template and assuming the template itself deals with the charter's conditions.

Build a readiness evidence file

Separate location evidence from readiness evidence. The vessel's arrival at a reported position does not describe the state of cargo spaces, equipment, documents or other matters relevant to the agreed readiness test. Obtain the relevant factual reports through the vessel's normal procedures and retain the underlying messages.

Record the source and timing of each readiness statement. A message saying an inspection is scheduled differs from a report saying it has been completed. Likewise, a preliminary agent forecast about clearance is not a substitute for the relevant authority's or attending party's actual record.

The commercial team should not certify physical readiness from photographs or an incomplete checklist. Technical determinations belong to competent vessel personnel and other authorised participants. Its responsibility is to ensure that their findings reach the people preparing the notice and that material qualifications are not dropped during summarisation.

Create an open-conditions list when an item remains unresolved. Describe the missing evidence, who is obtaining it and what decision depends on it. This helps the duty team distinguish a clerical delay from a substantive readiness issue requiring immediate escalation.

Confirm recipients, channels and time references

Check the contractual recipient details against current operational contacts. A familiar agent address may not be the address specified for a notice. Where clarification is needed, obtain it through the authorised commercial channel and retain the response with the notice instructions.

Prepare the message using a clear vessel identity, voyage reference, port or berth description and stated time reference. Avoid ambiguous local-time abbreviations when the port, vessel and office use different clocks. Preserve the original local time and any explanatory conversion in separate fields so the record remains traceable.

Arrange to save transmission evidence and subsequent responses. A sent message, a delivery acknowledgement and an acceptance response are different records. The legal effect of each depends on the agreement and circumstances, so the evidence file should preserve the distinction rather than putting all three under a single “accepted” checkbox.

Use a notice release checklist

The checklist should be applied to the actual proposed notice, not completed in advance as a blanket approval. Information can change between preparing a template and transmitting the message. A final factual check helps prevent an accurate draft from becoming an inaccurate notice through delay.

When the situation is uncertain, retain the available evidence and obtain a decision from the responsible reviewer. Do not invent facts to fill a template. The notice process is more defensible when an unresolved issue is visible than when a confident statement has no supporting record.

Handle rejection, changes and further notices transparently

If a notice is rejected or queried, retain the response in its original form and circulate it to the responsible desk. Record the reason given without adopting it as an agreed conclusion. Ask for the operational facts needed to understand the issue and route questions of validity to the contractual reviewer.

Where a further notice is instructed, keep it as a separate document with its own transmission record. Do not replace the original in the folder. A later reviewer may need to understand what the parties knew when each message was sent and how the underlying conditions changed.

Avoid changing dates or descriptions retrospectively to match a preferred laytime outcome. Corrections should be explicit, attributed and traceable. The statement of facts and notice log should preserve the actual sequence, including disputed notices, subsequent inspections and acknowledgements.

Fictional case: arrival before an inspection result

In this fictional case, a bulk carrier reaches the waiting area while a cargo-space inspection is still pending. The agent asks whether the usual notice can be sent immediately. The operator checks the charter instructions and obtains a factual update from the master instead of assuming arrival settles readiness.

The inspection later produces a report and the authorised desk issues instructions about the notice process. The file retains the arrival message, inspection sequence, notice transmission and the counterparty's response. Each record has its own time reference and source.

When the voyage account is reviewed, the analyst can distinguish the physical arrival from the subsequent readiness evidence. The chronology does not itself decide when laytime commenced. It supplies the facts needed to examine that question against the agreement without reconstructing events from memory.

Common mistakes

Using the previous port's notice template can leave the wrong recipient, berth description or time reference in the message. Check the fields against the current fixture and call. Another mistake is treating an acknowledgement as an unqualified agreement about validity.

Do not overwrite an earlier notice after receiving a rejection. Preserve the original and identify any later notice separately. Finally, avoid asking an agent to remove an inconvenient event from the chronology. The usefulness of the file depends on its factual integrity, including points that may support the other party's position.

Where Zeaclub fits

Zeaclub offers digitalised procedures across the voyage workflow.

Zeaclub provides 24/7 operating systems and worldwide coverage.

Explore Zeaclub

Learn about Zeaclub