1. What Is Hydraulic Fracturing Integrity and Containment (API RP 100-1)?
API RP 100-1 is an engineering recommended practice, not a conventional management framework. Its formal title is Hydraulic Fracturing—Well Integrity and Fracture Containment. API stands for American Petroleum Institute; RP means Recommended Practice. It addresses onshore well construction and hydraulic-fracture design and execution, with two objectives: maintaining well integrity and containing fractures within a prescribed geological interval.
For leaders in upstream exploration and production, the management question is straightforward: what evidence supports releasing a particular well for its planned stimulation treatment? Consultants can organize that evidence, clarify responsibilities, and improve decision processes. Qualified engineers must establish the technical design, acceptance criteria, and operating limits.
2. Origin and Background
The American Petroleum Institute published the first edition in October 2015, and its publications catalog records reaffirmation in August 2020. It was developed through API’s consensus-based standards process, rather than attributed to an individual framework creator.
The practice brings well construction and stimulation design together around groundwater protection, well barriers, and controlled fracture execution. Its original purpose remains technical. Applying it to executive assurance, contractor governance, or completion-readiness reviews is a management adaptation—not a replacement for the engineering document.
3. How Hydraulic Fracturing Integrity and Containment (API RP 100-1) Works
The practice distinguishes two questions. Well integrity concerns whether the constructed well can isolate protected groundwater, deliver the treatment, and contain produced fluids. Fracture containment concerns whether the treatment remains within its intended geological interval. Neither question substitutes for the other.
API organizes fracture-containment parameters into three categories. The table translates that distinction into questions for a completion-readiness review.
| Category | Technical meaning | Management question |
|---|---|---|
| Existing | Formation characteristics and their uncertainties. | Which geological assumptions materially affect the decision? |
| Established | Well barriers and integrity created during construction. | What was actually installed, and what verifies its performance? |
| Controllable | Fracture-design and execution parameters. | Which treatment settings and responses keep execution within the approved design? |
Evidence matters more than labels. A pressure-test record should be assessed against the loads the treatment will impose; a test below the eventual treating pressure does not establish containment at that higher pressure. Treating-pressure and annular-pressure monitoring provide additional information during execution.
For management purposes, connect these inputs in an assurance record covering each well, its relevant stages, and exposed offset wells. Record evidence, uncertainties, unresolved exceptions, accountable owners, and release decisions. This is a proposed governance artifact, not an API-prescribed scoring model.
4. When to Use Hydraulic Fracturing Integrity and Containment (API RP 100-1)
Use the practice to structure pre-stimulation reviews for new wells, completion-program changes, and acquired wells awaiting treatment. It is especially useful when drilling, cementing, subsurface, and completion teams hold different parts of the evidence. Reviews near existing wells also need explicit attention to interwellbore communication and offset-well response planning.
It is not a reservoir-valuation model, a detailed design manual, or a complete lifecycle integrity system. Its stated scope excludes continuous injection operations, including water disposal and waterflooding. Do not transfer its conclusions indiscriminately to those activities.
Prepare construction records, barrier-verification evidence, geological interpretations, treatment assumptions, and applicable requirements before convening decision-makers. Ask oilfield services providers to participate where their equipment, procedures, or measurements affect the proposed treatment.
The approach is useful only when uncertainties are visible and someone has authority to resolve them. Effort depends on evidence quality, additional diagnostics, and remediation—not workshop duration. A polished presentation cannot compensate for missing well records.
5. How to Apply Hydraulic Fracturing Integrity and Containment (API RP 100-1): Step-by-Step
The following workflow translates the practice into an executive-ready assurance process. It is not a substitute for reviewing the applicable standard and engineering program.
- Clarify the decision and scope.
Specify whether the team is releasing a well, approving a changed treatment, or resolving an integrity exception. Define the pad, wells, stages, treatment period, and relevant offset-well interfaces.
- Gather the required inputs.
Assemble as-built schematics, casing and cement records, pressure tests, subsurface interpretations, treatment designs, and offset-well information. Separate documented observations from assumptions. Construction and monitoring information are central to understanding potential subsurface fluid pathways.
- Define the units of analysis.
Evaluate individual wells and relevant treatment intervals. Add offset wells where communication could matter. Use pad-level summaries for coordination, but retain well-specific evidence and decisions underneath them.
- Construct the assurance artifact.
Create a register connecting each containment concern to its barrier or control, supporting evidence, uncertainty, owner, and required action. Keep the engineering basis accessible rather than compressing everything into a traffic-light score.
- Analyze discrepancies and evidence gaps.
Ask engineers to reconcile planned treatment loads with verified equipment and barrier capability. Identify missing evidence separately from confirmed deficiencies. Do not interpret the absence of a recorded failure as proof of satisfactory performance.
- Translate findings into actions.
Document release, hold, redesign, additional evaluation, or remediation decisions. Establish responsibilities for monitoring, escalation, suspension, investigation, and restart. Avoid approvals that depend on unspecified future checks.
- Test sensitivities.
Challenge uncertain geological interpretations, fracture-growth assumptions, and offset-well exposure. Ask which plausible changes would reverse the release decision. Where the answer is sensitive, seek stronger evidence or an engineer-approved alternative.
- Align stakeholders and iterate.
Review the decision with drilling, completions, subsurface, field supervision, and contractors. Record technical approval and change-control responsibilities. Revisit the assessment when construction findings, diagnostics, or treatment behavior invalidate assumptions.
Where reviews expose inconsistent field execution, consider targeted safety operations support to strengthen evidence handovers, contractor responsibilities, escalation procedures, and operational discipline. Technical acceptance must remain with competent engineering authorities.
6. Example: Hydraulic Fracturing Integrity and Containment (API RP 100-1) in Action
Fictional example: Red Mesa Energy plans to stimulate three horizontal tight-oil wells on one pad. The completion team wants a single pad-release decision before the fracture fleet arrives. The drilling superintendent flags incomplete cement-placement documentation on one well; the subsurface team identifies a legacy well near part of another lateral.
The operator selects API RP 100-1 to organize the review because the uncertainties involve both constructed barriers and fracture containment. The units of analysis are the three wells, treatment intervals near the legacy well, and the legacy well itself.
The team compares construction reports, pressure-test records, geological interpretations, treatment simulations, and available legacy-well records. It identifies two separate problems: incomplete evidence of zonal isolation on the first well and unresolved communication exposure around selected stages on the second.
Red Mesa holds the first well for engineering evaluation and any necessary remedial work. It defers the exposed stages on the second until the offset assessment and response arrangements are resolved. The third well proceeds only after its own review is complete.
The result is a differentiated release plan, not a blanket approval. Management accepts a scheduling change rather than treating fleet availability as evidence of readiness.
7. Strengths and Limitations
Strengths
- Connects disciplines: It gives executives a way to connect subsurface assumptions, well-construction evidence, and treatment execution rather than reviewing them independently.
- Clarifies accountability: An assurance register distinguishes who supplies evidence, who interprets it, and who authorizes the operation.
- Improves resource decisions: Teams can distinguish a need for better documentation from a need for diagnostics, remediation, or treatment redesign.
Limitations
- Subsurface uncertainty remains: Fracture growth and potential migration pathways depend on geological conditions. A model cannot eliminate uncertainty about the formation or nearby penetrations.
- Measurements require interpretation: Microseismic event locations contain uncertainty; borehole-survey uncertainty can affect the interpreted geometry. Monitoring should inform the assessment, not be presented as an exact containment boundary.
- Scope is bounded: Technical guidance does not establish universal legal compliance. Review applicable requirements, the relevant edition, and site-specific engineering conditions before relying on an assessment.
Above all, do not allow attractive production economics to compensate for unresolved technical acceptance criteria.
8. Common Pitfalls and How to Avoid Them
- Approving the pad instead of the well: A consolidated status can conceal exceptions. Retain individual release decisions and identify which treatment intervals each decision covers.
- Equating “tested” with “adequately tested”: A pressure test may not cover the treatment’s eventual loads. Have engineers assess its relevance, not merely its presence in the file.
- Overinterpreting cement logs: Cement-evaluation tools provide evidence about conditions behind casing, but their interpretation has limitations. Combine appropriate diagnostics with construction records and engineering judgment.
- Ignoring offset communication: Pressure communication can create an offset-well control problem. Identify exposed wells, establish communications, and prepare responses rather than focusing exclusively on the treatment well.
- Monitoring without decision authority: An alarm has little value if nobody knows who can suspend operations. Define the response chain, investigation responsibilities, and restart approval before execution.
- Closing actions administratively: “Completed” should mean that the required evidence has been reviewed and accepted—not simply that a task owner updated a spreadsheet.
Across multiple pads, program management support can coordinate evidence delivery, dependencies, unresolved actions, and decision logs. Its purpose is to make technical assurance executable, not to override engineering judgment.
9. How Hydraulic Fracturing Integrity and Containment (API RP 100-1) Relates to Other Frameworks
Bow-tie analysis: clarify threats and controls
Bow-tie analysis maps threats, preventive barriers, consequences, and mitigating controls around a loss-of-control event. Use it before or alongside the integrity review when stakeholders need to understand how controls connect. API RP 100-1 supplies the more specific well-construction and stimulation context.
Failure Mode and Effects Analysis: examine component failures
Failure Mode and Effects Analysis, or FMEA, systematically identifies potential failures and their effects. Use it alongside the review to examine equipment or procedural vulnerabilities. Prefer FMEA for detailed failure analysis; prefer the RP 100-1 assurance approach for integrating evidence into a treatment-readiness decision.
Companion technical practices: deepen the engineering assessment
API Standard 65-2 addresses isolation of potential flow zones during well construction. API RP 100-2 addresses environmental aspects of exploration and production, including hydraulic fracturing. These are complementary technical practices, not competing management frameworks; use them where the integrity review reveals related questions.
10. Key Takeaways
- Separate well integrity from geological fracture containment; assess both.
- Organize evidence around individual wells, relevant stages, and exposed offsets.
- Make assumptions, exceptions, and technical approval responsibilities explicit.
- Connect monitoring to predefined actions and restart authority.
- Use management tools to support engineering assurance—not replace it.
11. FAQs About Hydraulic Fracturing Integrity and Containment (API RP 100-1)
Is API RP 100-1 a management framework?
No. It is a technical recommended practice. Managers can use its distinctions to structure assurance reviews, but that governance process is an adaptation of the engineering guidance.
Does a successful pressure test prove fracture containment?
No. A pressure test addresses specified well-component conditions; it does not establish where fractures will propagate. Treat well integrity and geological containment as separate assessments.
Can smaller operators use this approach?
Yes. Start with a well-specific evidence register, clearly assigned technical reviewers, and documented release criteria. Keep administration proportionate, but do not reduce engineering scrutiny merely because the team is small.
How long does an integrity and containment review take?
Timing depends on the completeness of construction records, subsurface uncertainty, offset-well information, and any additional testing or remediation. Plan backward from evidence availability rather than promising a fixed workshop-based turnaround.
