Clean Product Acceptance: Review the Evidence Scope

Overview

The coordinator's role is to organise that evidence and make open questions visible. It is not to prescribe tank preparation, interpret inspection findings or determine contamination risk from a brief cargo-history summary. Those assessments belong with the appropriate vessel, cargo and specialist reviewers.

Key takeaways

• Identify the exact product specification and programme under review.
• Obtain relevant history and condition information through authorised sources.
• Record what the reviewer concluded, not just which documents were received.
• Preserve the scope and limits of condition-related evidence.
• Recheck affected responses when the product or proposed programme changes.

Define the product-specific decision

Start with the controlled product information pack and the intended movement. Record the specification issue, parcel reference and relevant receiving proposition.

Ask the accepting party what evidence it needs to make its decision. The commercial team should not assume that a document set used for a previous product answers every question for the current one.

Gard reports liquid-cargo contamination cases involving previous cargo residues. This supports treating relevant cargo-history questions as matters for informed review. Gard cargo-contamination discussion.

The commercial lesson is to route evidence appropriately, not to derive an operating procedure from a published case. The responsible specialists should determine what information and assessment the actual proposal requires.

A clear review request identifies the product pack, candidate and programme reference. The response can then be recorded against a definite proposition rather than a broad label such as clean trade.

Track evidence without turning it into a conclusion

The coordinator may collect vessel particulars, requested cargo-history information, condition records and other material specified by the reviewer. Record the source and issue of each item.

Receipt does not establish adequacy. A reviewer may ask for clarification or explain that a document has a narrower scope than the commercial team assumed. Keep that response visible rather than marking the evidence complete based only on the number of attachments.

Where a record describes a condition at a particular point, preserve that context. Do not turn a scoped observation into a promise about every later stage of the movement.

Also distinguish information supplied by the operator from conclusions issued by another reviewing party. Both may be relevant, but they play different roles in the decision trail.

The table helps the desk distinguish a well-organised file from a completed acceptance process.

Make clarification requests precise

If the reviewer asks about cargo history or condition evidence, preserve the specific question. A summary saying further assurance required may be too vague for the responsible source to answer effectively.

Identify who can supply the information and who will determine whether the answer closes the issue. The coordinator should not place itself between those roles as an informal technical interpreter.

Where the information is unavailable, state that limitation explicitly and ask the reviewer what it means for its decision. Do not substitute a generic statement of good practice for evidence requested about the actual candidate.

If a reply is conditional, record the condition and next action. A positive response with an open dependency should not become an unconditional acceptance status in the commercial comparison.

Distinguish review stages from contractual consequences

A condition-related question may affect the commercial timetable or offer basis, but its contractual effect is a separate matter. Check the current agreement and obtain the appropriate commercial or legal review where rights or obligations are involved.

The coordinator can assemble the factual sequence: what was requested, supplied, reviewed and answered. It should avoid deciding that a delay or additional request automatically falls to one party's account.

This separation helps the team communicate clearly during an unresolved review. The business can describe the open evidence question without prematurely asserting a claim or conceding a position.

It also prevents a commercial compromise from being misrepresented as a technical conclusion. If parties agree how to manage a cost or timing issue, retain the relevant specialist decision separately.

Fictional case: the condition record is overextended

A fictional clean-products trader receives a condition-related document for a nominated candidate. The coordinator saves it in the acceptance file and reports that the vessel is suitable for the product. The responsible reviewer's actual response has not yet arrived.

During a check, the commercial lead asks what the document establishes and who has accepted the candidate for the current specification. The coordinator discovers that the record addresses a limited scope and that the reviewer has requested additional cargo-history clarification.

The team corrects the status, routes the question to the designated source and preserves the document's original limits. The reviewer later issues a scoped response on the current proposal, which is recorded separately from the supporting evidence.

The problem was not the existence of the condition record. It was the commercial summary giving that record a broader meaning than its issuer and reviewer had established.

Revisit the evidence after product changes

If the buyer changes the specification, parcel combination or receiving proposition, identify which earlier responses relied on the original information. Ask the relevant parties whether their decisions remain applicable.

Do not assume that a small commercial amendment is technically immaterial. Equally, do not automatically restart every review without asking what changed within its scope. The goal is a targeted recheck supported by the responsible source.

Retain superseded product packs and their associated responses. This makes it possible to explain why a candidate's status changed and prevents an older positive answer from being reused against the new proposal.

Before handover, reconcile the current product reference, candidate and programme across the acceptance map. Assign any remaining question to a named owner with an authorised response route.

Keep the final summary narrow and useful

A reliable status note identifies the decision owner, proposal reference, response and conditions. It should not make broader claims about future cargo quality or universal suitability.

The commercial team can then assess readiness alongside the offer and timetable. A precise conditional status is more useful than a reassuring label that hides the next action.

Common mistakes

Treating receipt of a condition record as completion of acceptance confuses evidence with the responsible party's decision.

Another mistake is to summarise a detailed clarification request so broadly that the information source cannot tell what answer is needed.

Finally, avoid carrying an earlier response across a changed specification without checking its scope. Reconcile the product basis before relying on the status.

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