Key takeaways
- Build the evidence around the contractual questions that matter.
- Keep arrival, readiness, tender, receipt and subsequent conduct distinct.
- Preserve the contents of the communication alongside its transmission record.
- Explain conflicting timestamps before using them in an account.
- Mark evidential gaps rather than filling them with assumptions.
Begin with the notice provision under review
Gard's NOR guidance identifies destination, readiness and requirements concerning form, timing and recipient as relevant to the notice inquiry. The precise requirements depend on the charter and applicable law. Check the current text before deciding which evidence is necessary or drawing a conclusion about validity.
The evidence request should follow that inquiry. If the dispute concerns the recipient, collecting more vessel-position screenshots may add little. If it concerns the asserted readiness, a complete email log does not answer the underlying factual question. Start by identifying the alleged defect or unresolved point.
This does not mean collecting only evidence that supports one preferred position. Ask what would test the proposition fairly. A strong package makes the relevant uncertainty visible, including information that may qualify the proposed account. The commercial principal needs to understand the strength of the position before adopting it.
Keep the relevant events separate
Arrival describes a vessel event whose contractual significance requires review. Readiness concerns the state asserted for the intended operation. Tender concerns the notice communication. Receipt concerns what reached the relevant recipient. Subsequent conduct may be relevant for a separate legal analysis. These concepts should not be collapsed into a single port-call status.
An operational system may contain a field called “arrived” that serves a planning purpose. That label does not settle the contractual arrival question. Preserve the source definition and obtain the necessary factual clarification. Similarly, an agent's “NOR received” entry may establish the agent's record of receipt without deciding the notice's legal effect.
The team should identify the event behind every time used. A message creation time, sending time and recorded receipt time can differ for ordinary reasons. The reviewer needs to understand which is being relied on and why. Do not choose the earliest visible timestamp merely because it produces a favourable account.
Where time zones differ, preserve the original values and explain any conversion in the working chronology. A conversion should make the sequence clearer, not erase the source record. If the source is ambiguous, obtain clarification or label the uncertainty.
Build a source-to-decision matrix
| Question | Useful evidence | Limit to preserve |
|---|---|---|
| What notice was communicated? | Transmitted message and attached notice | Editable drafts may differ from the sent version |
| To whom was it directed? | Addressing and recipient records | A copied address does not alone prove required service |
| What factual readiness was asserted? | Responsible source confirmation and relevant records | Commercial summaries are not independent technical assessments |
| What location was reported? | Contemporaneous source material with context | A tracking display does not decide contractual arrival |
| What happened after tender? | Replies, reservations and operational communications | Conduct needs legal assessment before assigning effect |
| Which time is relied on? | Original timestamp, time-zone basis and explanation | An unexplained dashboard entry may serve another purpose |
The matrix should point to the evidence rather than reproduce every document. This lets an adviser or account preparer test a specific proposition efficiently. It also reveals where a claim of certainty rests on a secondary summary instead of the original record.
Use plain descriptions of evidential status. “Original transmission available” is more useful than a broad confidence score. “Receipt recorded by agent; contractual recipient disputed” tells the reviewer both what is known and what remains open.
Reconcile conflicts without manufacturing agreement
Conflicting records require explanation, not automatic averaging or selection. Determine whether they describe the same event. An agent's port-arrival entry and a vessel's anchoring entry may have different purposes. A later summary may round a time or use a different source. Ask the responsible parties to explain the discrepancy.
If the difference is resolved, retain a brief reconciliation note with the source of the clarification. If it remains unresolved, show both records and the decision affected. The account preparer may need advice on how to present alternative positions rather than silently deciding the factual dispute.
Avoid rewriting third-party records to make the chronology consistent. A corrected source should come from the appropriate issuer or be clearly identified as a separate explanatory note. The distinction matters because the reviewer must be able to tell original evidence from subsequent interpretation.
The goal is a reliable sequence, not a visually perfect timeline. A timeline with an honest gap can support better decisions than one whose apparent completeness depends on an unsupported assumption.
Fictional case: the dashboard records the wrong event
In a fictional voyage, a commercial dashboard imports the time an agent opened a message into its NOR field. The actual message had been sent earlier. A separate arrival report records another event, but the dashboard labels all of them as part of the same port-call milestone.
The account preparer uses the dashboard value without checking its origin. When the counterparty asks for supporting evidence, the desk discovers that the field does not represent the event it was assumed to represent. The dispute is now obscured by a data-definition problem.
The team retrieves the transmitted notice, recipient record and relevant operational reports. It identifies each event and explains how the dashboard value was produced. The legal reviewer then considers the contractual requirements using the actual communication history, while the account preparer corrects the working chronology.
The case does not establish which time should govern. It illustrates why data provenance matters commercially: an apparently precise field can create misplaced confidence if nobody knows what event it measures.
Prepare the package for a decision
A useful evidence package opens with the question to be decided and the proposed factual sequence. It then identifies supporting records, material contradictions and missing information. The reviewer should not need to read an entire voyage archive to discover the issue.
Keep the factual summary distinct from the requested conclusion. For example, the summary can state that a message was transmitted to identified addresses at a recorded time. Whether that communication satisfied the charter's requirements belongs in the analysis, not inside the description of the evidence.
Once a decision is made, retain its assumptions. If new evidence later changes an important fact, the team can identify which conclusion needs reconsideration. This is particularly useful where a commercial settlement, provisional account or reserved position proceeds before every factual question has been resolved.
Common mistakes
Using one timestamp as a substitute for the full tender event is the main mistake. Another is treating an operational status label as a contractual conclusion. Identify what each source actually records.
Do not infer receipt, acceptance or validity merely because a message appears in a sent folder. Equally, do not dismiss a record without investigating its meaning. Finally, avoid collecting unrelated port-call material in bulk. The evidence request should target the disputed proposition while preserving material information on both sides of it.
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
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
Is a sent email enough evidence of a valid NOR?
It can support the communication history, but validity involves other questions under the charter and applicable law. Preserve the contents, recipients and relevant factual basis, then obtain the necessary analysis.
Can vessel tracking establish contractual arrival?
Tracking information may provide contextual position evidence. It does not independently decide the contractual test. Identify the source, limitations and relevant charter wording before relying on it.
What should happen when two timestamps conflict?
First determine whether they describe the same event and use the same time basis. Seek clarification from the source. If the conflict remains material, preserve both records and identify the consequence for review.
Should an evidence summary include the preferred legal conclusion?
Keep the factual summary and legal position distinguishable. A reviewer should be able to see what the records establish before evaluating the conclusion being proposed on the basis of those records.