An upstream operator's contracts department had 62 active MSAs with field service contractors. Most had been executed using the company's standard form with a standard insurance exhibit. But standard form is not the same as identical - many MSAs had been negotiated with modifications, site-specific addenda had been attached for specific well programs, and several legacy MSAs predated the current standard form by five to eight years. The insurance requirements across those 62 MSAs were not uniform.
When the risk manager ran a project to build a compliance baseline, the team discovered that the internal understanding of "our standard MSA requirements" did not match what was actually written in many of the MSAs. Fourteen of the 62 MSAs had site-specific addenda that increased pollution liability requirements beyond the standard exhibit. Eight legacy MSAs had lower umbrella requirements than the current standard. Two MSAs for offshore work had USL&H and maritime coverage requirements that the standard onshore form did not include.
Nobody had been reading the actual MSAs. They had been checking contractors against a remembered standard. The result was a compliance program that was systematically miscalibrated for 37% of the active MSA relationships.
Anatomy of an Oil & Gas MSA Insurance Exhibit
An oil and gas MSA insurance exhibit is typically structured in layers, and the complete insurance requirement for any given contractor relationship requires reading all of them:
Layer 1: Base insurance requirements. The standard exhibit attached to the MSA body specifies coverage types, minimum limits, endorsement requirements, and additional insured designations that apply to all work under the MSA. This is where most compliance reviewers focus, and it is only part of the picture.
Layer 2: Work category appendices. Many operator MSA forms include appendices that modify the base requirements based on the type of work being performed. A drilling services appendix may require control of well coverage that the base form does not specify. A well services appendix may increase CPL requirements for contractors who handle hazardous materials. These appendices are binding but frequently overlooked.
Layer 3: Site-specific addenda. For specific well programs or locations, additional insurance requirements may be attached by the operator's land or contracts team. These addenda commonly reflect state-specific requirements, lender requirements on financed assets, or operator risk policy updates that postdate the original MSA execution.
Layer 4: Minimum financial assurance provisions. Some MSAs include financial assurance requirements - specific carrier ratings, policy form restrictions, or requirements that coverage be placed with admitted carriers - that constrain how contractors may satisfy the insurance requirements.
Understanding which of these layers apply to a specific contractor relationship requires reading the full MSA package, not just the base insurance exhibit.
Standard vs. Site-Specific Requirements: How They Differ
The base MSA insurance exhibit typically specifies requirements that the operator has determined are appropriate for their standard contractor relationships. These standard requirements are calibrated to a general risk profile and may not account for:
- Elevated pollution exposure at specific well locations
- Increased control of well requirements for high-pressure or sour gas wells
- Lender-imposed minimums on financed well programs
- State-specific regulatory requirements (Louisiana offshore minimum requirements differ from Texas inland requirements)
- Work-scope-specific risks (acid jobs, high-rate frac programs, NORM-containing produced fluids)
When a contractor is engaged for work that involves any of these elevated risk factors, the standard exhibit requirements may be insufficient, and a site-specific addendum should be (or should have been) attached.
The compliance review for contractors working under MSAs with site-specific addenda must verify compliance against both the base exhibit and the addendum. A contractor who meets the base requirements but not the addendum requirements is non-compliant for that specific engagement.
How to Extract Requirements From Complex MSA Language
The challenge in reading MSA insurance exhibits is that the language is written by lawyers for contracts, not by insurance professionals for compliance verification. The same coverage concept may be described differently across different MSA versions, and the threshold question of "what is actually required" often requires interpretation.
A structured extraction approach:
Step 1: Read every section of the insurance exhibit. Do not skim. Read the definitions section (if present), the coverage requirements section, the additional insured language, the endorsement requirements, and any exceptions or carve-outs.
Step 2: Build a coverage-by-coverage requirement table. For each required coverage type, extract: minimum per-occurrence or per-claim limit, minimum aggregate limit, required endorsements, and AI/waiver requirements.
Step 3: Note ambiguous language for escalation. Some MSA provisions are genuinely ambiguous - "commercially reasonable limits" without further specification, references to regulatory minimums without identifying which regulation, or AI requirements that do not specify which endorsement form. Flag these for legal or risk management review rather than making a compliance determination on ambiguous language.
Step 4: Check all appendices and addenda. Identify every document attached to the MSA and check each one for insurance-related provisions that modify the base exhibit.
Step 5: Confirm the final requirement set applies to the specific contractor. Not all appendices apply to all contractors. A wellbore services appendix applies to contractors doing wellbore work; it may not apply to a location services contractor whose scope does not include wellbore activities.
Translating MSA Language Into a Verification Checklist
Once requirements are extracted, the output should be a contractor-specific verification checklist that maps every requirement to a specific data point on the submitted COI or supporting documentation.
Example translation from MSA language to verification checklist:
| MSA Language | Verification Point |
|---|---|
| "CGL with per-occurrence limits not less than $5,000,000" | COI shows CGL per-occurrence ≥ $5M |
| "Contractor's pollution liability with limits of $10,000,000 per claim" | COI shows CPL; per-claim limit ≥ $10M |
| "Operator named as additional insured on primary and excess coverage" | AI designation on CGL and umbrella; P&NC confirmed |
| "Waiver of subrogation in favor of Operator on all lines" | WOS endorsement on CGL, auto, WC, umbrella confirmed |
| "Notice of cancellation not less than 30 days" | 30-day cancellation notice confirmed |
| "Coverage with carriers rated A- or better by AM Best" | AM Best rating for each carrier confirmed |
This translation step is where the compliance value is created. Without it, a reviewer reading a COI has no clear standard to check against. With it, every data point on the COI has a corresponding requirement, and the compliance determination is objective.
Why Manual MSA Reading Fails
For an operator managing 50 active MSAs with varying exhibits and addenda, manual requirement extraction for each contractor is not operationally sustainable. The reasons it fails:
Time. Reading and extracting requirements from a complex MSA insurance exhibit takes 45-90 minutes per contract. At 50 contracts, that is 37-75 hours of work - before any COI verification begins.
Consistency. Different reviewers extract requirements differently, especially for ambiguous language. Without a structured extraction process, the same MSA will produce different verification standards depending on who reads it.
Version control. MSA amendments and addenda must be tracked and applied. A reviewer working from an old version of an MSA - or from memory of what the "standard" form says - will apply the wrong requirements to the contractor's COI.
Scale. Contractor pools in upstream operations are dynamic. Contracts are added, amended, and terminated. An extraction process that requires manual reading every time something changes cannot keep pace with the contract lifecycle.
Automated contract-intelligence platforms address all four failure modes by reading the full MSA package (body, exhibits, addenda) automatically, extracting requirements consistently, and maintaining a current requirement set that updates when the underlying contract is amended.
For E&P operators who want a defensible, consistently-applied MSA compliance program, automated extraction is the foundation - not a convenience, but an operational necessity at any significant contractor pool size.
Bramble's oil and gas MSA compliance capabilities include automated requirement extraction from complex MSA insurance exhibits and addenda, with contract-to-COI comparison built for upstream contractor programs. Book a demo at getbramble.com/demo to see how the platform handles O&G MSA complexity.