Dirty Product Acceptance: Match Requirements to Evidence

Overview

The coordinator should make the review question clear, identify the source of each answer and preserve any limitations. It should not determine technical suitability from broad vessel descriptions or prescribe how the cargo should be carried. The commercial value lies in establishing a reliable path from requirement to decision.

Key takeaways

• Identify the current cargo pack and the specific requirements under review.
• Distinguish a requested capability from evidence supplied about the candidate.
• Ask the responsible reviewer what conclusion it has reached on the actual proposal.
• Keep commercial undertakings separate from technical assessments.
• Recheck decisions when supplier information or receiving requirements change.

Create a requirements-to-evidence map

Start with the supplier's controlled information and the buyer's stated receiving proposition. Identify the requirements that the responsible reviewers need to consider, preserving their source references.

Do not create a technical checklist from memory. Ask the appropriate cargo, vessel and receiving specialists what information is necessary for the proposed movement.

The coordinator's map should show each requirement, the evidence source and the decision owner. This helps avoid a common gap: a requirement appears in the enquiry, an operator supplies general vessel information, and the desk assumes the relationship between them has been assessed.

A completed map does not mean the vessel is accepted. It means the business can see which questions have been answered, which remain open and who can close them.

Distinguish statements by their purpose

A supplier instruction describes the cargo source's requirement. An operator's statement describes information or a position about the candidate within its stated scope. A review response applies the responsible party's assessment to the proposal. A commercial undertaking establishes something different again and may need agreement review.

Keep these categories linked but separate. The coordinator should not turn a broad operator statement into a wider technical or contractual promise through its summary.

Where the meaning of a proposed undertaking is uncertain, check the current wording and obtain authorised commercial or legal review. The evidence map should record the result or open question rather than resolve the issue by assumption.

The table helps the commercial lead understand why a file with many positive statements can still contain an unanswered decision.

Route technical questions without dilution

When a reviewer requests additional information, preserve the question accurately and send it to the designated source. A generic request for more assurance may not tell the responder what evidence is needed.

Record the expected response route and identify who will decide whether the answer is sufficient. The coordinator can chase the action without interpreting the technical content itself.

If the requested evidence is unavailable, state that fact and ask the reviewer how it affects its position. Do not substitute a statement about previous successful trades for information requested about the actual proposal.

Also avoid treating a clarification request as a rejection. The commercial team needs to know whether the next step is information supply, reconsideration of the programme or development of another candidate. Accurate status language helps it choose the appropriate action.

Keep receiving assumptions in the review basis

The candidate is being considered for a defined movement, not in isolation. Record the receiving information supplied and identify the party responsible for confirming it.

If the receiver's requirement differs from the supplier's information or the operator's response, route the discrepancy to the appropriate owners. The coordinator should not decide which technical statement governs through a commercial convenience judgment.

Where the receiving arrangement remains provisional, show that limitation in the acceptance map. A response on one proposal should not be assumed to cover every destination option under consideration.

When the programme changes, identify the responses tied to the earlier arrangement and ask whether they remain applicable. This targeted recheck is more useful than either ignoring the change or automatically restarting every task without understanding scope.

Fictional case: a broad capability statement is overread

A fictional dirty-products trader receives a general candidate description from an operator. The cargo pack also contains supplier requirements that the commercial team has forwarded separately. The coordinator marks the candidate suitable because the description appears to address the broad service category.

A reviewer asks which response confirms the relationship between the actual cargo requirements and the proposed movement. The file contains no such scoped decision; it only contains the requirement and the general statement side by side.

The coordinator builds a requirements-to-evidence map and sends the defined proposal to the responsible reviewer. The reviewer requests clarification from the operator and cargo source. Those answers are tracked separately, and the final response is recorded with its conditions.

The improvement is not a new technical test devised by the commercial team. It is the missing link between information supplied and a decision issued by the party responsible for making it.

Reconcile commercial terms after the review

A review response may identify a condition with commercial consequences. Preserve the condition and ask the authorised parties to resolve any associated price, timing or responsibility question.

Do not assume that a technical confirmation settles the commercial allocation. Equally, a negotiated commercial arrangement should not be presented as if it answers a technical question that remains open.

Keep the offer and acceptance records on the same programme version. If the owner revises its commercial basis after clarification, identify that change explicitly in the recommendation.

The commercial lead should see the candidate's readiness, terms and unresolved dependencies together. A lower price should not conceal an unfinished review, and a positive review should not conceal an unagreed obligation.

Prepare a scoped handover

Before transfer, identify the current cargo pack, candidate information, receiving proposition and decision map. Highlight conditions and the next action for each open item.

Retain original evidence through authorised access arrangements. A handover can point to a controlled source without reproducing every underlying document in an unrestricted folder.

Obtain acknowledgment of the open-action transfer so that the next coordinator owns the follow-up. A technically precise unanswered question can still be lost if its commercial owner disappears during a shift change.

The final status note should be narrow: name the responsible decision, its scope and any conditions. Avoid broader statements about universal suitability or future performance that the evidence does not support.

Common mistakes

Placing a cargo requirement beside general vessel information does not prove that the relationship has been reviewed. Retain the responsible party's scoped decision.

Another mistake is to replace an exact technical question with a vague request for assurance. Preserve the information needed for a useful answer.

Finally, avoid treating technical review and commercial responsibility as the same decision. Record each within its authority and reconcile them before commitment.

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