Key takeaways
- Define whether the engagement concerns a call or a programme.
- Compare recurring support against actual workload, not assumed scale.
- Recheck call-specific facts even when the route is familiar.
- Make continuity and replacement arrangements part of the selection.
Use local infrastructure as context, not acceptance
TNPA's Saldanha berth information identifies liquid-bulk crude oil handling by pipeline. TNPA: Saldanha berths
That local context can help frame an enquiry, but it does not establish acceptance of a particular tanker or parcel. The broker should coordinate the current particulars with the relevant authorised reviewers each time the proposed movement requires it.
For a current transaction, the authorised programme-service brief is not provided; obtain current verified information. Identify the intended calls, recurring coordination tasks, current exceptions and agreed review responsibilities. Do not turn a planning programme into a statement that future nominations are confirmed.
Ask candidates how their proposed service changes if the principal expects repeated movements rather than a single transaction. The answer should describe work and responsibility, not simply promise more attention because the account may grow.
Compare service models on the same workload
Give candidates a fictional repeat programme with familiar participants but occasional cargo and timing changes. Ask which tasks they include and which need a separate instruction.
| Selection area | Evidence to request | Comparison purpose |
|---|---|---|
| Core offer | Defined commercial and continuing coordination work | Distinguishes call support from programme management |
| Coverage and hours | Primary and replacement contacts across repeated calls | Tests continuity |
| Recap and operations | Reusable structure with call-specific confirmations | Avoids automatic carryover |
| Payment security | Consistent verification of new or changed instructions | Keeps familiarity from weakening controls |
| Procedures | Review triggers for changed cargo, vessel or recipient | Makes exceptions deliberate |
| Shared record | Programme history linked to individual call files | Supports learning without merging evidence |
| Suitable use case | Demonstrated fit for the principal's repetition and variability | Tests practical value |
A broader service is useful only if the principal needs and uses the additional work. A focused engagement can be appropriate where the principal's own operations team already manages continuity effectively.
Decide what should be standardised
A repeat programme can use a consistent information request, responsibility map and handover format. This reduces avoidable reinvention. It should not turn old acceptance responses into standing approval for new particulars.
Identify the elements that remain call-specific. The broker should ask which source confirms each one and record material differences from the prior movement. Familiarity is most useful when it helps spot a change, not when it discourages review.
Consider the principal's internal capability. If its team already consolidates nominations and manages local interfaces, a broker focused on market access may be sufficient. If the team struggles to maintain the programme history or cover absences, continuing coordination may be a more relevant selection criterion.
Agree how the service will be reviewed. Discuss whether enquiries are well qualified, exceptions are identified early and handovers are usable. Avoid evaluating a recurring relationship only by message volume or the absence of visible complaints.
A fictional programme outgrows a single-call arrangement
A fictional cargo principal initially appoints a broker for a South African tanker call. As further movements are planned, the same broker informally becomes the contact for programme questions, receiver changes and duty handovers. Neither side has clearly defined the expanded role.
One candidate proposes continuing on the same vague basis. Another separates commercial enquiry work from recurring coordination and asks the principal which tasks its own team will retain. The resulting service brief identifies the broker's continuing responsibilities and the call-specific reviews that remain necessary.
The principal can compare the proposal with a more limited service on equivalent terms. The case does not claim that a recurring arrangement is always better. It shows why the service model should reflect the actual work rather than grow through unrecorded expectations.
When a traditional broker may be the better choice
A traditional tanker broker may be attractive where continuity of personal market knowledge is especially valuable. An experienced relationship holder can understand the principal's preferences and help explain recurring commercial questions to established contacts.
Ask how that knowledge is preserved during absence or staff change. A shared programme record may support continuity, while personal judgment can remain valuable in negotiations. Choose a service whose scope and replacements match the programme's complexity rather than relying solely on the original relationship.
Common mistakes
Allowing a single-call engagement to become an undefined programme role creates mismatched expectations. Other mistakes include paying attention to broad availability claims while ignoring replacement arrangements, carrying old responses into new calls and assuming a wider service is valuable without identifying the work it performs. Compare explicit responsibilities before choosing the model.
Where Zeaclub fits
Zeaclub offers digitalised procedures across the voyage workflow.
Zeaclub provides 24/7 operating systems and worldwide coverage.
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 recurring broker arrangement always preferable?
No. It depends on the principal's workload, internal capability and need for continuity. A focused service can be suitable when other appointed teams already manage the programme effectively.
What can be reused between calls?
Formats, contact structures and relevant historical context can help. Current particulars and required confirmations should still be checked for the actual proposed movement.
How should the principal assess continuing support?
Look at the clarity of responsibilities, treatment of exceptions and quality of handovers. Ask whether the service solves a real coordination problem rather than merely generating more communication.
What if the programme changes substantially?
Review the service brief and authority boundaries. A change in participants, cargo pattern or internal staffing may alter which tasks the broker should perform and which remain elsewhere.