SHELLVOY cargo evidence: trace a condition allegation

Key takeaways

• Define the cargo-condition allegation precisely.
• Identify which stage of the cargo movement each source describes.
• Preserve sample and report identity through the review.
• Keep technical findings, causal explanations and contractual consequences distinct.

Start with the allegation and the relevant cargo

A complaint may concern a particular quality characteristic, a description in a document or an asserted change between loading and discharge. Ask the party raising it to identify the cargo and the result or observation on which it relies.

Obtain the actual SHELLVOY-based agreement and relevant amendments for the contractual review. Check the current text with the responsible adviser. The form name alone does not establish the parties' complete cargo responsibilities or the treatment of a particular claim.

The evidence task should follow the specific question. A broad request for every cargo document may produce a large archive without clarifying the disputed characteristic, the relevant stage or the source of the allegation.

Preserve the connection between samples and reports

Gard highlights the value of load-port samples when reviewing liquid-cargo contamination claims. The actual sampling and technical assessment should be handled by qualified personnel under the applicable procedures.

For commercial preparation, identify the sample or observation to which each report relates. Preserve the reference, stated location, date, responsible source and any qualifications. A report without a clear connection to the relevant cargo event may be difficult for the specialist to interpret.

Do not relabel a sample or infer its origin from a familiar filename. If the reference is unclear, ask the responsible source to clarify it. The coordinator should make the evidence chain understandable without inventing a missing link.

Map the evidence across the cargo movement

The matrix does not determine a claim. It helps the reviewers see where the evidence is complete, where a technical question remains and which contractual issue requires separate assessment.

Distinguish a finding from an explanation

A report may identify a condition without establishing its cause. A later commercial summary can inadvertently turn that finding into a statement that the vessel, terminal or another participant caused it. Preserve the distinction.

Ask the qualified reviewer which explanations are supported, which are possible and which cannot be assessed from the available material. The coordinator should not select a preferred explanation merely because it fits the principal's commercial position.

Likewise, a difference between reports should not be treated automatically as evidence of deterioration. The records may concern different stages, methods or samples. Their comparability needs appropriate assessment before the commercial team draws a conclusion from the apparent contrast.

Keep the operational chronology relevant

Prepare the sequence of material cargo events and communications needed to understand the allegation. The aim is to support technical and contractual review, not to reproduce every routine update from the voyage.

Identify changes to the cargo plan, reported interruptions and relevant instructions, preserving their source and status. Where an explanation was added retrospectively, show that it was a later account rather than a contemporaneous observation.

Do not turn the chronology into an operational prescription. The commercial preparer should not recommend sampling methods, cargo treatment or technical adjustments. It should obtain the responsible reports and make the relevant sequence available to the people qualified to assess it.

Fictional case: a report is linked to the wrong cargo stage

A fictional receiver raises a cargo-condition complaint after discharge. The commercial team finds a report in the voyage folder and assumes it describes the cargo at loading because the filename contains the vessel's name.

During evidence preparation, the coordinator checks the report reference and asks the issuing source to clarify its scope. The report concerns a different stage from the one assumed. It may still be relevant, but it cannot answer the loading-condition question on the basis originally proposed.

The team corrects the evidence map and obtains the missing source information. The specialist can then assess the actual comparison without relying on a false document connection. The case illustrates why locating a report is not the same as establishing what it proves.

Coordinate the technical and contractual reviews

The technical reviewer needs the relevant observations and material to assess the cargo question. The contractual adviser needs the actual agreement, the allegation and the reliable factual findings. Neither review should be forced to substitute for the other.

Ask the reviewers to identify what additional evidence would materially affect their assessment. This helps the coordinator prioritise specific requests rather than repeatedly sending the whole file. Keep unanswered questions visible with a responsible source.

The principal should obtain appropriate advice before making admissions, agreeing a financial adjustment or directing a settlement response. A well-organised file supports those decisions but does not confer authority on the person who prepared it.

Preserve the distinction between evidence and negotiation

Parties may explore a commercial solution while the technical or legal issues remain unresolved. Record the scope of that discussion through authorised channels. Do not alter the factual record to make it consistent with a proposed compromise.

Similarly, a correction to a cargo document should be described accurately. It may resolve an administrative error without accepting the full allegation. The responsible advisers should assess the effect of the actual communications and wording.

Keep the financial treatment separate from the evidence status. An amount entered in a working account may represent a proposal rather than an agreed liability. The decision-maker should be able to see that distinction without reading hidden spreadsheet notes.

Close the preparation with a precise review question

The final note should identify the allegation, relevant cargo, source map, established observations and unresolved technical or contractual issues. State the decision required and why the available evidence matters to it.

Ask the adviser to identify any applicable notice or submission conditions promptly. Do not assume a universal claim period or that informal exchanges satisfy the actual requirements. The commercial coordinator should organise the facts needed for that assessment and preserve evidence of authorised communications.

A useful file leaves the next reviewer able to investigate the claim without inheriting unsupported assumptions about sample identity, causation or liability.

Common mistakes

A familiar filename can create a false link between a report and a cargo stage. Other errors include treating a technical finding as proof of causation, comparing unlike records without review and allowing settlement discussion to rewrite the facts. Trace each source and preserve the limits of what it establishes.

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

Explore Zeaclub