A drilling contract is one of the few agreements where the commercial terms are executed daily. Every twenty-four hours a rig sits in one or more states, each state carries a rate, and the sum of those rates becomes an invoice. In theory this is straightforward arithmetic. In practice it is where a substantial amount of value quietly moves between the parties.
The complexity is not in the headline operating rate. It is in the boundaries. When does moving become operating. How long can a repair run before the rate drops to zero, and does that clock reset between events or accumulate across the well. Whether a weather day is standby or force majeure. Each of these is defined somewhere in the agreement and each is answered, day by day, by a supervisor filling in a report.
Operators that reconcile rig invoices carefully tend to find the same things. Rate states applied inconsistently, zero-rate clocks that were never tracked cumulatively, escalation applied from the wrong index date, and deductions the contract allows that nobody claimed. None of it is fraud. It is what happens when the rate schedule sits in a contract file and the invoice is approved by someone working from the daily report alone.
The rate states and where they get confused
Most drilling contracts define five or six rate states. The definitions are usually clear enough on paper; the ambiguity appears at the transitions between them.
- Operating rate, applies when the rig is working under the contract, and the question that matters is what specific event starts and stops the clock at the beginning and end of a well.
- Standby rate, the rig is available but not working, which covers waiting on the operator, on weather or on materials, and each cause may carry a different rate or a different duration limit.
- Moving rate, applies during rig move or mobilization, frequently with a fixed lump sum for the move itself and a separate rate once movement stops but operations have not started.
- Repair rate, reduced or zero during contractor equipment failure, subject to a free-repair allowance that is usually cumulative rather than per event, which is the detail most often missed.
- Force majeure rate, typically a low rate for defined events outside either party's control, where the argument is almost always about whether the event qualifies rather than about the rate itself.
The practical control is to make the daily report capture the contractual state directly rather than a free-text description of activity. When the report fields and the rate tiers are designed together, reconciliation becomes a comparison instead of an interpretation exercise.
Many drilling contracts allow a fixed number of repair hours at full rate before the rate drops, measured cumulatively across a period rather than per incident. Tracking those hours requires a running total that is maintained continuously. Operators who reconstruct it at invoice time almost always reconstruct it in the contractor's favor, because the earlier events are the ones that get forgotten.
The contract data to extract before the rig spuds
Everything needed to verify an invoice exists in the agreement at signature. Pulling it into structured fields before operations begin is what makes daily verification possible rather than aspirational.
- The full rate schedule. Every rate state with its numeric rate, the event that triggers entry and exit, and any duration cap or tapering that applies after a defined period in that state.
- Allowance clocks. Free repair hours, permitted standby days and any other allowance, recorded with its measurement basis and whether it resets per well, per month or not at all.
- Escalation mechanics. The index or formula, the base date, the review frequency, any cap or collar, and the notice the contractor must give before an adjusted rate can be invoiced.
- Reimbursable and pass-through items. Fuel, catering, third party services and consumables, with the markup permitted on each and the documentation required to support the charge.
- Deduction and set-off rights. Performance deductions, damage recovery and any agreed liquidated amounts, which are entitlements that lapse if not applied within a stated period.
A five-step roadmap to reliable rig invoice verification
Step 1, structure the rate schedule at award
Convert the rate exhibit into fields at contract award rather than at first invoice. This is a short exercise that, done once, removes the need for anyone to reread the contract each month and makes the terms visible to the people in the field.
Step 2, align the daily report to the contract
Change the daily drilling report so the activity classification maps directly onto the contractual rate states. This single change eliminates most reconciliation disputes because it removes the translation step where interpretation enters.
Step 3, maintain allowance clocks continuously
Keep running totals for repair hours and any other cumulative allowance, updated daily rather than assembled at invoice time. A clock that is current is a fact; a clock reconstructed later is a negotiating position.
Step 4, verify the invoice against the register
Check each invoice line against the structured rate schedule and the day-state record before approval, with variances raised inside the contractual dispute window rather than after payment has gone out.
Step 5, review escalation on its own cycle
Apply the index formula on the contractual review date rather than when the contractor raises it, and hold the source data. Escalation applied from the wrong base date compounds quietly across a long campaign.
Turn the rate schedule into verifiable data
Aavenir extracts rate tiers, allowances and escalation terms from drilling contracts into structured fields the field and finance teams can both use.
Why rig contract administration is different from services procurement
Procurement functions are generally good at services contracts where the deliverable is discrete and the invoice reflects a purchase order. Drilling contracts break that model in three ways. The commercial terms execute continuously rather than at defined milestones, so there is no natural checkpoint at which someone reviews the agreement. The person who determines which rate applies is a rig supervisor focused on operations rather than on contract terms. And the contract runs for a campaign long enough that the people who negotiated it are rarely the people administering it. The organizations that handle this well do not add approval layers, which slow the operation without improving accuracy. They push the contract terms out to the point of capture, so the daily report itself carries the contractual classification and the invoice becomes a summation of decisions already made correctly. That is the same principle behind the rate discipline described in oilfield service rate schedule compliance.
Rate states, triggers and verification sources
The table below sets out the states found in most drilling contracts, what typically starts the clock, and the record an operator should hold to verify the classification independently.
| Rate state | Typical trigger | Verification source | Common dispute |
|---|---|---|---|
| Operating | Spud or defined well event | Daily report and well log | Start and end of well boundaries |
| Standby | Rig ready, work suspended | Daily report cause code | Cause attribution between parties |
| Moving | Rig release to next location | Move plan and timestamps | Where the move formally ends |
| Repair | Contractor equipment failure | Maintenance log | Cumulative allowance already used |
| Force majeure | Defined qualifying event | Notice correspondence | Whether the event qualifies |
Rig contract administration is not a legal discipline and it is not really a procurement one either. It is a data problem that sits between the contract file and the daily report, and it responds to structure rather than scrutiny. Extract the rate schedule into fields at award, make the daily report speak the contract's language, keep the allowance clocks current, and verify invoices against the register instead of against memory. Campaigns run with that discipline produce fewer disputes and a cleaner audit trail, and they surface the deductions and allowances that were negotiated and then forgotten. For the services side of the same supply base, see oilfield master service agreements.
For related guidance, see Rate card drift: when the SOW stops matching the MSA, Payer fee schedule audits, finding the loaded rate errors and API terms: fair use, rate limits and deprecation notice.
