Offshore logistics sits in an awkward place in most operators' contract portfolios. The agreements are large, long-running and operationally critical, but the day-to-day management is distributed across marine operations, aviation, supply chain and finance, each holding part of the record and none holding all of it.
The result is a familiar pattern. The contract is in the repository. The rate table lives in a spreadsheet maintained by logistics. Daily vessel reports arrive in an operations system. Certificates are chased by a compliance coordinator. Invoices are checked against whichever of these the accounts payable team can reach. Each part works; the joins do not. Nobody owns the question of whether a day invoiced as standby was recorded as standby in the operations system and priced as standby in the contract, because answering it requires all three.
Most of the recoverable value in these contracts sits precisely at those joins. The same structural problem appears in contractor engagement generally, and the remedy described in contractor prequalification and MSA control applies here: put the contractual parameters where the operational data can be tested against them.
The five control areas
A logistics support agreement concentrates its commercial risk in five areas. Each maps to data that has to be held as fields rather than read from the document, because the test that matters happens daily against operational data and cannot be run against prose.
- Availability commitment, with a measurement window, a defined numerator and denominator, an exclusion list and a remedy for shortfall.
- Operating state rate table, naming every state the asset can be in and the rate, minimum charge and evidence requirement for each.
- Cost adjustment mechanics, covering fuel, crew cost escalation and currency, with named indices and settlement cycles.
- Indemnity and insurance, setting the knock-for-knock structure, its carve-outs, required limits and the evidence refresh cycle.
- Certification and compliance, listing the certificates each asset and crew must hold current, with the consequence of a lapse during the term.
The rate table deserves the most attention because it is where money moves every day. A supply vessel can be on hire working, on hire standby, waiting on weather, in port, bunkering, under repair or off hire, and a contract that names four of those states will see the other three priced by convention. Convention favours whoever writes the invoice. The amounts are individually small, which is why they are rarely challenged, and collectively large over a multi-year charter, which is why they are worth fixing once at mobilisation rather than arguing monthly.
The highest-return hour in a logistics contract review is spent mapping the vessel daily report categories to the contract rate states, in writing, agreed with the contractor. Do it at mobilisation and most invoice queries for the term disappear.
What belongs on the asset record
Certificates and qualifications attach to a vessel, an aircraft or an individual rather than to the contract, and treating them as contract attachments is why they lapse unnoticed. An asset can move between contracts, a contract can cover several assets, and crew rotate across both, so filing certification against the agreement guarantees that some of it will be looked for in the wrong place. Five items belong on the asset record with their own expiry tracking.
- Class and statutory certification. Held per vessel, with survey windows that do not align to the contract term.
- Safety management documentation. Tied to the operating company as well as the asset, so a change of manager resets it.
- Insurance certificates. Showing limits, named interests and waivers, refreshed at every policy renewal rather than annually by habit.
- Crew certification and currency. Individual-level records that change constantly and are the hardest to keep accurate.
- Inspection and audit outcomes. Vetting results and operator audits with their findings and closure status.
A five-step control roadmap
Step 1, Extract the rate table as data
Load every operating state, rate, minimum charge and evidence requirement into structured fields. The document stays authoritative, but the fields are what invoices are tested against, and they can be compared to a daily report automatically.
Step 2, Agree the state mapping at mobilisation
Sit with the contractor and map each daily report category to a contract state in writing. Append the mapping to the contract. Doing this before the first invoice costs an hour and avoids a recurring monthly discussion for the life of the agreement.
Step 3, Define availability precisely
Write the measurement window, the formula and the exclusion list into the agreement, and build the same definition as a calculation over the operational data. Where the two disagree, the difference is almost always an exclusion that was understood but not written down.
Step 4, Move certificates to asset records
Create records for each vessel, aircraft and, where practical, each certificated crew position, and attach the certificates with their expiry dates. Alert the asset owner before expiry rather than discovering the lapse in a pre-mobilisation check.
Step 5, Settle cost adjustments on a fixed cycle
Run fuel and escalation settlements on the stated cycle whether or not either party raises them. Adjustments left to accumulate are settled eventually as a negotiated lump rather than as the arithmetic the clause specifies.
Test every invoice against the contract
Operating states, availability formulas and certificate status, held as data on one record.
Why certificate lapses are a contract problem
A lapsed certificate is usually treated as an operational failure, and it is. It is also a contractual one, because the agreement almost always makes current certification a condition of the asset being on hire. An asset operating with an expired certificate may be off hire by the terms of the contract for the whole period of the lapse, which can be commercially significant, and neither party usually notices until an audit. By then the lapse has typically been remedied, the operational risk has passed, and what remains is a retrospective commercial argument that neither side has much appetite for. The discipline that prevents this is the same one applied to long-dated restoration duties in decommissioning obligation tracking, which is that expiry dates belong in a system that alerts, not in a folder that is reviewed when someone remembers.
Operating states and evidence requirements
The table shows a representative state set for a marine support contract. State names and treatment vary by agreement and should be taken from the governing rate schedule.
| Operating state | Typical rate basis | Evidence | Common dispute |
|---|---|---|---|
| On hire, working | Full day rate | Daily report signed by operator representative | Partial days at change of state |
| On hire, standby | Full or reduced day rate | Daily report with standby reason | Standby attributed to the wrong party |
| Waiting on weather | Reduced rate, often capped | Weather record and master's log | Threshold for weather criteria |
| In port or bunkering | Reduced rate or no charge | Port log and bunker receipt | Time counted either side of the call |
| Off hire, breakdown | No charge after grace period | Technical report and repair record | Start of the grace period |
Logistics support contracts reward attention because the volume is high and the margin of error on each transaction is small. A one per cent misclassification on a vessel on long-term charter is a meaningful annual number, and it is invisible unless the contract parameters are close enough to the operational data that the comparison can actually be run. Operators that make the comparison routine tend to find the value in the first quarter and then spend the rest of the term with a materially quieter invoice queue.
For related guidance, see The operator’s guide to oilfield master service agreements, Why oilfield service rate schedules leak margin and The land manager’s guide to mining royalty obligations.
