Day rates get attention. They are large, recurring and comparable, so they are benchmarked, audited and renegotiated. Mobilization and demobilization charges get far less, despite being substantial on a per-event basis, because they appear once per job, arrive at the point when operational pressure is highest, and are approved by people whose priority is getting equipment to location.
That asymmetry is where the leakage lives. A lump-sum mobilization charge carries a set of embedded assumptions, about origin, route, load count, crew and rig-up time, that are invisible in the invoice and therefore never tested. A demobilization charge is frequently billed whether or not the return journey it prices actually occurred. And when a job is suspended and restarted, the same move is often charged twice because the contract never addressed partial deployment.
None of this requires bad faith on the contractor’s side. It is the predictable result of pricing an event as a single figure and reviewing it under time pressure. The controls that fix it are contractual and administrative, and they are inexpensive relative to what they recover.
Where the variance actually sits
Reviewing mob and demob charges across a campaign tends to surface the same five patterns, in roughly this order of frequency.
- Origin substitution, where equipment mobilizes from a nearer yard than the one the lump sum was priced against, with no reduction applied.
- Phantom demob, where equipment moves directly to another operator’s site and the return journey priced into the demob charge never happens.
- Double mobilization, where a suspension and restart produces two full charges because the contract is silent on partial moves.
- Rig-up overrun billed as standby, where rig-up exceeds the allowance and the excess is recharacterized at standby rates rather than absorbed.
- Pass-through markup, where permits, escorts and third-party transport are billed with a markup the contract did not authorize.
The first two account for most of the recoverable value, and both are detectable with information the operator already has. Origin substitution shows up when the transport documentation is compared against the yard named in the pricing basis. Phantom demob shows up when the demob charge is checked against any evidence of arrival at the contractual return point, which in a well-drafted agreement is a condition of payment rather than an afterthought.
Quoting mobilization as a single figure does not remove the assumptions behind it, it only removes your ability to see them. Requiring the pricing basis, the origin, the load count and the rig-up allowance to be stated in the schedule costs nothing and makes every subsequent charge checkable.
Five contract terms worth getting right
These terms are usually available at negotiation and rarely requested, largely because mob and demob are treated as administrative detail rather than as a commercial category.
- State the pricing basis explicitly. Record origin yard, distance, load count, crew size and rig-up allowance in the rate schedule, so a deviation is identifiable rather than invisible.
- Condition demob on return evidence. Make arrival at the stated return point, or a defined alternative, a condition of the demob charge, with a reduction where equipment transfers directly to another location.
- Write a suspension and restart term. Specify what is payable when a job is suspended, whether standby is an alternative to demobilizing, and how a remobilization is priced.
- Set an intra-field and campaign rate. Agree a reduced or waived charge for moves within a defined radius or within a single campaign, since repeated full charges across one field are rarely justified.
- Cap and evidence pass-throughs. Require third-party documentation for permits, escorts and transport, and state whether any markup applies and at what rate.
A five-step verification approach
Step 1, Extract the charge terms into a schedule
Pull mobilization, demobilization, standby, rig-up allowance and pass-through terms out of each master agreement into a structured rate schedule. In a supply base of any size the variance between suppliers is substantial, and it is not visible while the terms sit in document text.
Step 2, Make the pricing basis a required field
Require the contractor to state origin, distance, loads and allowance on the mobilization notice or the first invoice. This single change converts an unverifiable lump sum into a comparable one, and it is the precondition for every other control. The broader MSA context is covered in our operator’s guide to oilfield master service agreements.
Step 3, Add an evidence gate at approval
Hold mob and demob invoices until transport documentation, timestamps and for demob the return evidence are attached. An evidence gate is more effective than a post-payment audit, because the documentation is still available and the contractor has an incentive to supply it.
Step 4, Reconcile the campaign, not the invoice
At campaign close, total the mob and demob events against the number of actual moves and the agreed intra-field treatment. Double charges and phantom demob are far easier to see across a campaign than on any individual invoice, which is the same effect described in our note on the margin case for oilfield services contract compliance.
Step 5, Close the terms at the next renewal
Feed the findings into the next tender or renewal as specific clause changes rather than as a general request for better rates. Suppliers will typically accept an evidence condition and an intra-field rate more readily than a headline reduction.
See rate schedules enforced at approval
Walk through how contract allowances and evidence requirements gate an event-based invoice.
Why this is a contract data problem
Every control above depends on the rate schedule being available to the person approving the invoice, in structured form, at the moment of approval. Where charge terms live only in a signed PDF in a document repository, the approver works from memory or from the purchase order, and neither contains the allowance, the origin basis or the pass-through rule. Extracting charge terms into fields attached to the supplier and the agreement is what makes verification routine rather than exceptional, and the same structure supports the dated commitments described in our obligation management datasheet for energy and mining.
The organizational dimension matters as much as the data. Mob and demob invoices are typically approved by a field or drilling supervisor whose accountability is schedule, not cost recovery, and who has neither the rate schedule nor the time to interrogate a lump sum while equipment is waiting. Moving the verification step to a commercial or contract administration function, with a service level short enough not to delay payment terms, changes the outcome without changing anyone’s priorities. Operators that have done this generally report that the first campaign reviewed produces the largest findings, and that supplier invoicing behavior adjusts quickly once an evidence condition is actually enforced.
Charge categories and the evidence each requires
The table below sets out the recurring categories and the document that substantiates each. Allowances shown are placeholders to be replaced with the negotiated values in each schedule.
| Charge | Basis | Required evidence | Common issue | Control |
|---|---|---|---|---|
| Mobilization | Lump sum or distance rate | Origin, loads, transport documents | Nearer yard, no reduction | Stated pricing basis |
| Rig-up | Hours against allowance | Timestamped field tickets | Overrun billed as standby | Written allowance and overrun rule |
| Demobilization | Lump sum or distance rate | Arrival at return point | Direct transfer to next job | Return evidence condition |
| Suspension remob | Per event | Suspension notice and cause | Full second charge | Suspension and restart term |
| Permits and escorts | Pass-through | Third-party invoices | Unauthorized markup | Stated markup or none |
Mob and demob will remain a legitimate and significant cost of field operations. The question is narrower than whether the charges are fair: it is whether the operator can tell what it agreed to pay, whether the event billed actually occurred as priced, and whether the evidence was available at the moment someone had both the authority and the information to say no.
For related guidance, see Decommissioning and abandonment obligation tracking, The land manager’s guide to mining royalty obligations and Crude quality bank adjustments in supply contracts.
