Drilling contract day rate management, a field guide

A drilling contract is one of the few commercial agreements where the price changes several times a day. The same rig earns an operating rate while making hole, a reduced standby rate while waiting on the operator, a repair rate or nothing at all during contractor equipment failure, and a separately negotiated rate while moving. Over a multi-well program the difference between careful and careless administration of those transitions is frequently the largest single controllable variance in the well cost.

The contract itself is rarely the problem. Rates are negotiated with attention, and the definitions are usually workable. What fails is the connection between the definition and the daily record. The clause says repair time beyond a cumulative threshold is zero-rated. The daily drilling report records a non-productive time code. Nobody has established which code maps to which contractual state, so the mapping is reconstructed at invoice time by whoever is available.

This guide covers how to structure day rate administration so the evidence exists when it is needed: rate state definitions, evidence artifacts, recharge control and dispute handling. It complements the broader contract structure material in joa-epc-contract-automation-guide.html.

The rate states that need definitions

Every drilling contract defines a set of states and a rate for each. The states below appear in most agreements, and each needs an unambiguous trigger and an agreed evidence artifact.

• Operating rate, the full rate applying when the unit is working under the operator instruction, usually the default state against which all others are exceptions
• Standby rate, the reduced rate applying when the unit is available but not working because of operator decision, weather or third-party delay
• Repair or breakdown rate, the reduced or zero rate applying during contractor equipment failure, typically with a cumulative free allowance before zero rating begins
• Moving and mobilization rate, the rate applying during rig move, with separate treatment for mobilization and demobilization lump sums and their amortization
• Force majeure and suspension, the rate applying when neither party can perform, often the most loosely drafted state and the most frequently disputed

The cumulative repair allowance deserves particular attention. Contracts commonly grant a number of hours of paid repair time per month or per well, after which the rate drops to zero. Tracking the running total against the allowance requires a daily record that both parties accept. When that total is only reconciled at month end, the operator and contractor arrive with different numbers, and the difference is settled by negotiation rather than by evidence.

Five leakage points in day rate administration

Value leaks in predictable places. None of these require bad faith from either party, and all of them are addressable with better record structure.

• Unmapped time codes. When report codes do not map cleanly to contract states, the mapping is made at invoice time by interpretation. Publish the map and apply it daily.
• Untracked repair allowances. Cumulative free repair hours are a running balance. If neither side maintains the balance daily, month-end reconciliation becomes a negotiation.
• Uncontrolled third-party recharges. Services procured through the contractor and recharged at cost plus a handling percentage need supporting invoices and markup verification. Absent that, the markup is taken on trust.
• Mobilization amortization drift. Mobilization lump sums amortized across a program need recalculation when well count changes. Program scope shifts frequently and the amortization schedule rarely follows.
• Rate escalation clauses. Index-linked or periodic escalation provisions apply automatically under the contract but are frequently missed in the invoice check, in both directions.

A five-step roadmap to controlled day rate administration

Step 1, Extract the rate matrix into fields

Pull every rate, trigger condition, allowance and escalation provision out of the contract and into structured fields. A drilling contract typically yields between twenty and forty distinct commercial parameters, and holding them as fields rather than as clause text is what makes automated invoice checking possible.

Step 2, Publish the time code mapping

Agree with operations and with the contractor which report codes correspond to which contract states, document the mapping and attach it to the contract record. Where a code is ambiguous, resolve the ambiguity in writing before the state occurs rather than after.

Step 3, Maintain running balances daily

Track cumulative repair hours, weather standby days and any capped allowances as running balances updated from the daily report. Both parties should see the same balance, because a shared balance prevents a dispute and a private balance merely prepares for one.

Step 4, Automate the first-pass invoice check

Compare the invoice against the rate matrix and the daily state record automatically, and route only the exceptions to a human. Most invoice lines on a drilling contract are arithmetically verifiable, and human review is better spent on the small number of genuinely contested transitions.

Step 5, Close disputes against contract evidence

When a line is contested, resolve it by reference to the clause, the daily record and the agreed mapping, and record the outcome against the contract. A decided interpretation that is not written down will be re-litigated on the next well.

Why this is a contract data problem

Drilling contract administration sits awkwardly between functions. The contract is owned by supply chain or legal, the daily record is produced by the drilling team, and the invoice is processed by accounts payable. Each function holds part of the evidence and none holds all of it, which is why reconciliation tends to happen late and under pressure. The structural fix is to make the contract record the anchor. The rate matrix, the time code mapping, the running allowances and the invoice history should all attach to the same contract object, so that any of the three functions can see the full picture without requesting it from the others. That also changes what happens at audit. Joint venture audits and internal audits of drilling spend both ask the same question: show me the basis for this charge. When the answer is a link from the invoice line to the daily state to the contract clause, the audit closes quickly. When the answer requires assembling three systems and interviewing people who have since moved to another asset, the finding usually stands regardless of whether the charge was correct. Industry cost control practice has converged on this pattern for a reason, and the same approach extends naturally to service contracts, marine spreads and integrated services agreements where the rate structure is comparable.

Rate states, triggers and evidence

The table sets out a workable evidence standard for each state. Specific contracts will vary, and the value lies in agreeing the standard in advance rather than in the particular convention chosen.

Day rate contracts reward administrative discipline more than negotiating skill, because the rates are usually market-determined while the transitions are entirely within the parties control. Extract the rate matrix into fields, agree the time code mapping before operations begin, maintain the running balances daily and automate the arithmetic so that human attention goes to the transitions that are genuinely contested. Done that way, the audit trail is a by-product of normal operations rather than a reconstruction exercise.

For related guidance, see Why oilfield service rate schedules leak margin, Rate card drift: when the SOW stops matching the MSA and Contractor prequalification and MSA control for operators.

Aavenir Oil, Gas & Mining PracticeContract administration and cost control guidance for upstream and mining operations.