Getting control of the oilfield master service agreement portfolio

For contracts managers at operators and service companies, the MSA carries the risk allocation, and almost nobody can query it across the whole portfolio.

What makes oilfield master service agreements hard to manage?

The master service agreement carries the risk allocation for work that has not been scoped yet. It sets a knock-for-knock indemnity structure, the insurance that supports it, audit and HSE duties, and the terms that every later work order inherits. Because the commercial detail sits in call-offs while the risk sits in the MSA, most operators cannot answer portfolio questions about indemnity posture, insurance limits, jurisdiction or certificate expiry without opening files one at a time.

Last updated: September 9, 2026 · Reviewed by the Aavenir Oil, Gas & Mining practice

Key takeaways

  • ✓The master service agreement allocates risk before scope exists, and every work order issued under it inherits those terms
  • ✓Knock-for-knock indemnity trades fault-based argument for predictability, and it only works when the supporting insurance holds
  • ✓Enforceability of indemnity turns on state law and insurance backing, so jurisdiction belongs on the record as a field
  • ✓A lapsed certificate of insurance before a work order is executed is the failure mode a register is built to catch

The master service agreement is the most consequential document an upstream operator signs and the least examined. It is negotiated once, often years before the work it governs, and it allocates risk for activities nobody has scoped yet. The commercial conversation happens later, in work orders and call-offs, which is where attention goes. The risk stays in the MSA.

Ask a contracts manager a portfolio question and the difficulty becomes visible. Which active service agreements carry mutual indemnity supported by insurance at the limits we require. Which are governed by a state with an anti-indemnity statute. Which have a certificate of insurance expiring inside ninety days with live work orders running underneath.

Those are not exotic questions. They are the ordinary content of a risk review, and most operators answer them by opening files one at a time. This guide sets out the structure that makes them answerable, from why the indemnity model looks the way it does to the register fields that carry it.

Why knock-for-knock became the industry default

Under a knock-for-knock structure, each party takes responsibility for injury to its own people and damage to its own property, regardless of who was negligent. The operator covers its group, the contractor covers its group, and the argument about fault does not happen. On a well site with a dozen contractors in overlapping space, the alternative is a fault inquiry after every incident, priced into every bid.

  • Mutual indemnity between defined groups, with each side’s group described carefully to include affiliates, subcontractors, employees and invitees, because the definition of the group determines what the indemnity actually reaches.
  • Insurance that supports the indemnity, at agreed limits and lines of cover, since an indemnity promise from a counterparty without the balance sheet or the policy behind it is a drafting exercise.
  • Additional insured and waiver of subrogation, so the indemnified party has a direct route to the policy and the insurer cannot recover against the party the indemnity was meant to protect.
  • Consequential loss and pollution carve-outs, which sit outside the mutual scheme and are usually allocated separately, often by reference to the source of the pollution and its position relative to the wellhead.
  • Audit and HSE obligations, including inspection rights over contractor records, training and competency requirements, incident reporting duties and site access conditions that flow through to every call-off.

Each of those is a field, not a paragraph. Portfolio questions go unanswered because the answers were written as prose inside a signed document and never transcribed anywhere a query can reach. A contracts team maintains a partial spreadsheet, usually of the twenty agreements somebody remembers, while the rest of the portfolio sits unmeasured until something goes wrong.

The MSA register is the missing asset

Most operators have a contract repository and no register. A repository stores documents. A register holds the attributes that decisions depend on, jurisdiction, indemnity posture, insurance limits, certificate expiry and the work orders running underneath. Built once and maintained through the normal contracting workflow, it turns a week of file review into a filtered list.

Where the work order relationship breaks down

An MSA governs, a work order executes. That division is efficient until the link between them stops being tracked. Work orders get issued against agreements that have expired, lost their insurance backing, or been superseded by a version nobody circulated. The MSA terms are inherited either way, including the ones that no longer function.

  • Work orders outlive the agreement they hang from. A multi-year campaign issued under an MSA that lapsed in month eight is common. Link every call-off to a parent agreement record and the mismatch shows up as an exception rather than a finding.
  • Certificates of insurance expire quietly. Cover renews annually, the certificate is filed once, and nobody checks. Track expiry as a date field with an owner, and block work order execution when the supporting certificate has lapsed.
  • Amendments change the indemnity and nobody reindexes. A negotiated carve-out in a side letter can change the risk posture materially. If the register reads only the original document, the posture recorded against that counterparty is wrong.
  • Jurisdiction is assumed rather than recorded. Teams carry a general belief about how indemnity is treated in the states they operate in. Governing law and place of performance belong on the record, because the treatment differs by state.
  • HSE and audit duties never reach an owner. Inspection rights and reporting obligations are negotiated and then left in the document. Extract them as dated obligations with named owners or they will not be exercised or evidenced.

A five-step path to a working MSA register

Step 1, Agree The Field Set First

Decide what the register holds before you populate anything. A workable starting set is counterparty, agreement dates, governing law, place of performance, indemnity posture, insurance lines and limits, additional insured status, certificate expiry, and linked work orders. Keep it small enough that operations will maintain it and specific enough to filter on.

Step 2, Extract From Executed Agreements

Populate the register from signed documents rather than from memory. Clause extraction returns indemnity structure, insurance requirements and audit provisions with a pointer back to the source text. Record confidence, and route anything ambiguous to a reviewer rather than guessing, because a wrong field is worse than an empty one.

Step 3, Link Work Orders To Parent Agreements

Every call-off references a parent MSA. Make that reference a relationship in the system rather than a line of text in a header. Once the link exists you can see live work under expired agreements, work under counterparties with lapsed cover, and dormant agreements to retire at renewal.

Step 4, Automate The Certificate Watch

Certificate of insurance expiry is the highest-value alert in the whole register because it is unambiguous and time-bound. Set notice at ninety, thirty and seven days to the contract owner and the counterparty, and add a hard check at work order execution so a lapse cannot pass unnoticed into the field.

Step 5, Push Obligations To Owners

Audit rights, HSE reporting, training records and insurance renewals become scheduled tasks with named owners and expected artifacts, which is what obligation management is for. This step converts negotiated protection into exercised protection, and it is the one most often skipped once the agreement is filed.

See an MSA register built from your own agreements

Walk through clause extraction, jurisdiction and indemnity fields, certificate expiry alerts and work order linkage using a sample of your executed service agreements.

Book a demo

Jurisdiction, insurance and the limits of indemnity

Indemnity provisions are not enforced identically everywhere. Several US states restrict indemnity in certain oilfield and construction agreements through anti-indemnity statutes, and Texas and Louisiana are the two most often discussed in this industry. The detail is state specific. Whether a particular mutual indemnity holds can turn on how the statute is drafted, how the agreement is characterized, and in some states on whether the indemnity is supported by insurance obtained in a particular way. None of that is a judgment a contract register should make. What the register should do is record governing law and place of performance as fields, so legal review is targeted at the agreements where the question is live.

The MSA register, field by field

The table sets out the fields that carry the most decision weight, where each one comes from, and the condition that should raise an alert. Operators running the same discipline across joint operating and construction agreements will find the approach familiar from a JOA and EPC contract automation guide, and the HSE duties flowing from an MSA sit naturally in an HSE compliance audit checklist.

Register fieldSource in the agreementWhy it carries weightAlert condition
Governing law and place of performanceChoice of law and site clausesIndemnity treatment varies by stateState changes or new operating area
Indemnity postureMutual indemnity and carve-outsDefines who bears which lossAmendment alters the agreed structure
Insurance lines and limitsInsurance schedule or exhibitIndemnity without cover is thinLimit falls below the required floor
Certificate of insurance expiryCertificate filed by counterpartyCover lapses silently between renewalsExpiry within ninety days or passed
Linked work ordersCall-off and work order recordsLive work inherits MSA termsActive call-off under an expired MSA

The master service agreement was designed to make risk predictable. It does that only while somebody can see what it says across the whole portfolio. Operators holding indemnity posture, insurance limits, jurisdiction, certificate expiry and work order linkage as structured fields answer risk questions in an afternoon. Everyone else answers them after an incident, reading the agreement for the first time in years, in the least useful conditions available.

For related guidance, see The operator’s guide to oilfield master service agreements, Contractor prequalification and MSA control for operators and Why oilfield service rate schedules leak margin.

FAQ

Oilfield MSA questions, answered

What is knock-for-knock indemnity in an oilfield MSA? +
It is a mutual arrangement in which each party accepts responsibility for injury to its own personnel and damage to its own property, regardless of fault. The structure is used because multiple contractors work in shared space, and resolving fault after every incident is slow and expensive. Predictable allocation lets each party insure its own exposure.
Why does insurance matter so much to the indemnity structure? +
An indemnity is only as good as the ability to pay behind it. Agreements normally require specified lines and limits of cover, additional insured status for the indemnified party, and a waiver of subrogation so the insurer cannot pursue the party the indemnity protects. If cover lapses, the commercial protection weakens even though the wording is unchanged.
Are oilfield indemnity provisions enforceable in every US state? +
No. Several states restrict indemnity in certain oilfield or construction agreements through anti-indemnity statutes, and Texas and Louisiana are the jurisdictions most often discussed in this industry. Enforceability turns on the specific state law, how the agreement is characterized, and in some cases on how the indemnity is supported by insurance.
How do work orders relate to the master service agreement? +
Work orders and call-offs sit under an MSA and inherit its terms, including indemnity, insurance and HSE obligations. The commercial scope and pricing live in the call-off while the risk allocation lives in the parent agreement. Linking each work order to its parent record is what lets you see live work running under an expired or unsupported agreement.
What should an MSA register actually contain? +
Counterparty, agreement dates, governing law, place of performance, indemnity posture, insurance lines and limits, additional insured status, certificate of insurance expiry, audit and HSE obligations, and linked work orders. Keep the field set small enough that operations will maintain it. The value comes from being able to filter the portfolio, not from capturing everything.
Is this guide legal advice on indemnity enforceability? +
No. It describes contract management practice for supply chain and contracts teams, and it deliberately describes indemnity enforceability in general terms without asserting outcomes in any jurisdiction. Anti-indemnity statutes and their application are state specific and fact specific. Confirm the position for your agreements with qualified legal counsel before relying on any indemnity structure.

Turn your service agreements into a register

See how a CLM platform extracts indemnity posture, insurance limits and jurisdiction from executed service agreements, links every work order to its parent, and alerts before a certificate of insurance lapses.

  • ✓Indemnity and insurance fields extracted from agreements
  • ✓Certificate expiry alerts linked to work orders
  • ✓Standalone or native on ServiceNow