
Key takeaways
- Describe the actual service required when the event occurred.
- Preserve operational observations separately from technical explanations.
- Identify the factual boundaries supporting the proposed period.
- Explain gaps and conflicting evidence instead of filling them with assumptions.
- Give the adviser a focused question before the account team implements a position.
Start with the service, then examine the incident
Steamship Mutual's off-hire guidance explains the relevance of the service immediately required, rather than merely the service the charterer hoped to undertake. Check the current text of the charter and obtain advice on how that distinction applies to the particular clause and facts.
For evidence preparation, begin with the instructions that were actually in force. Establish what the vessel was expected to do at the relevant stage and who issued the instruction. Avoid reconstructing this solely from a later commercial plan, which may describe an intended employment that had not yet become the immediate operation.
A voyage plan, a port movement instruction and a cargo-operation report can describe different stages of the same employment. The evidence file should locate the alleged interruption within those stages. A reader should understand the operational setting before encountering the proposed financial consequence.
This approach also makes missing information visible. If the current instruction is unclear, record that uncertainty and seek clarification from the appropriate person. Do not make a technical incident appear contractually decisive by silently assuming the service against which it will be assessed.
Preserve what each witness can actually establish
An operational report may establish that an activity stopped or continued at a reduced level. A technical report may explain a condition, investigation or repair. An agent may establish a movement or a communication with the port. Each source contributes differently.
Do not ask one document to prove every link. A repair completion entry might be useful evidence of a technical milestone, but the adviser may need additional information about the vessel's ability to perform the relevant service. Conversely, an operational resumption entry does not necessarily describe the underlying defect or its cause.
Keep the author's scope clear. If a message repeats information received from someone else, preserve that attribution. A summary written by the commercial desk should not be presented as an independent observation merely because it appears in a formal chronology.
Where a specialist explanation is needed, frame a factual question within that specialist's competence. Ask what was observed, what function was affected and what qualification applies. Avoid asking the specialist to endorse a hire conclusion that belongs to a separate contractual review.
Map the evidence to a decision
| Review question | Useful factual material | Limitation to preserve |
|---|---|---|
| What service was required? | Effective employment instructions and operational sequence | A future plan may not describe the immediate requirement |
| What happened? | Contemporaneous incident and activity reports | A label may omit the actual effect |
| What function was affected? | Qualified technical explanation | The author may address equipment rather than contract performance |
| When did the condition change? | Relevant observations and completion reports | A report's sending time may differ from the event time |
| What happened after the change? | Resumption, movement or activity records | Continued delay may have a different explanation |
| What treatment is proposed? | Clause reference and reviewed analysis | Evidence collection does not itself determine entitlement |
The matrix is an original preparation tool. Tailor it to the disputed question rather than requesting every possible vessel record. The aim is to make the necessary connection inspectable without burying the relevant evidence inside a large, undifferentiated attachment bundle.
Include a short explanation when a source is unavailable. A gap can materially affect confidence in the proposed start or end point. It should remain visible to the decision-maker even if the surrounding chronology appears complete.
Treat time boundaries as factual propositions
The beginning of a reported defect, the interruption of an activity and the first message to the desk can occur at different moments. Identify which event each entry represents. A convenient timestamp should not become the start of a proposed period simply because it is the first one available electronically.
Apply the same discipline at the other end. Completion of work, confirmation of capability and actual resumption are different descriptions. The evidence preparer should preserve the sequence and let the contractual reviewer identify the relevant boundary under the applicable wording.
If a source gives an approximate time, keep it approximate. Ask whether a more precise contemporaneous record exists, but do not create precision through interpolation. A calculation can display exact arithmetic while its underlying event time remains uncertain.
Where records conflict, state the competing observations and their origins. The discrepancy may require clarification or an expressly provisional assessment. Concealing it behind a single polished timeline makes the account harder to defend later.
Fictional case: the repair file misses the operation
In a fictional charter, the account desk receives a report describing equipment work and assumes that the entire reported work period should be treated as off-hire. The report is detailed about the equipment but says little about the service the vessel was required to perform.
The reviewer asks for the operative instructions and activity record. Those documents reveal that the employment sequence changed while the work was underway. The commercial question cannot be answered simply by copying the work report's opening and closing entries into a hire calculation.
The desk prepares a segmented factual chronology. It identifies the required operation at each stage, the reported effect of the condition and the evidence of subsequent capability. The adviser reviews the wording against that fuller account before any final position is implemented.
The example does not establish that any particular interval qualifies for off-hire treatment. Its lesson is evidential: a technically detailed file can still omit the operational link needed for the commercial question.
Make uncertainty useful to the reviewer
An evidence request should identify what decision the missing fact could change. Asking whether an activity resumed can be more useful than requesting “all correspondence” when the disputed endpoint is already known. Focused requests reduce unnecessary disclosure and help the source provide a meaningful answer.
Separate facts that are agreed from facts merely unchallenged so far. Silence in a busy operational exchange should not be rewritten as a factual concession. Similarly, a counterparty's acknowledgement of receipt does not mean acceptance of the proposed account treatment.
The reviewer may be able to assess alternative factual scenarios while clarification remains outstanding. Label those scenarios and explain their assumptions. They support a decision under uncertainty; they do not replace evidence or convert a preferred narrative into an established event.
Send finance a conclusion with its boundaries
Once an authorised position is available, the account preparer needs the accepted factual basis, the relevant period and the scope of the decision. If a boundary remains provisional or disputed, that status should accompany the calculation.
Do not send a collection of operational documents with an unexplained instruction to deduct. Finance should understand whether it is preparing an internal estimate, a claim presentation or an approved account action. Those outputs have different purposes even when they draw on the same evidence.
Common mistakes
A frequent mistake is treating repair duration as a complete answer to the off-hire question. Another is substituting a later voyage plan for the service actually required at the time. Establish the operational sequence before proposing the account consequence.
Avoid treating report transmission as the event itself, removing qualifications from specialist evidence or silently choosing between conflicting timestamps. Preserve uncertainty in a form the reviewer can assess and resolve.
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 technical report enough to establish off-hire?
It may provide important evidence, but its scope must be understood. The review also needs the relevant contractual wording and operational context before reaching a conclusion about hire treatment.
Why retain the instructions in force at the time?
They help identify what service was actually required. A later plan or hoped-for employment may describe a different commercial expectation and should not silently replace the operative instructions.
Should approximate event times be made exact for calculation?
No. Preserve their stated precision and seek better evidence where necessary. Any calculation using an assumed boundary should disclose that assumption rather than present it as an observed fact.
What should happen when records disagree?
Identify the conflicting sources and the decision affected. Seek focused clarification or obtain a reviewed assessment of the alternative scenarios. Do not hide the discrepancy inside a single unexplained timeline.