Integrated Estimate Plan and Basis of Estimate: Improving Cost Estimate Accuracy in FEL
Updated: 1 day ago
Estimate Plan and Basis of Estimate in Capital Projects | ROMAN Consulting Group
Why Projects Go Over Budget Despite Complete Estimate Documentation
The estimate looked complete. The Basis of Estimate was attached. The Estimate Plan had been prepared. Every gate requirement appeared to be satisfied, and the project moved forward with approved funding.
Then execution began.
Scope gaps surfaced that had not been visible in the estimate. Disciplines had made different assumptions about what was in and what was out. Quantities had been built on inputs that the responsible engineers had never formally validated. The Basis described a different methodology than what the estimator had actually used.
Nothing in the review process flagged the issue, because both documents had been prepared independently, by different contributors, at different points in time, with no shared reference connecting them.
In the estimate reviews I've done, this is one of the most common structural failure patterns in Class 4 and Class 3 cost estimating.
The estimating technique is usually sound. What fails is the integration between the estimate plan and basis of estimate.
Why This Problem Lives in FEL Estimating
This pattern is a natural outcome of how front-end estimates are typically developed.
Front-end estimates are developed under conditions that naturally drive fragmentation.
Scope is evolving. Engineering is incomplete. Multiple disciplines contribute inputs at different levels of maturity. Decisions move faster than information can be fully validated.
In this environment, the estimate plan and basis of estimate are often treated as separate administrative deliverables rather than as a single, coordinated system. The usual sequence:
The Estimate Plan is prepared early, then set aside
The Basis of Estimate is written late, often describing what happened rather than guiding how the estimate was built
By the time both documents exist, the estimate is already complete. The opportunity to detect misalignment has passed.
Estimate Quality Depends on Alignment
Estimate quality at this stage depends on alignment across:
Scope
Quantities
Assumptions
Cost methodology
When the plan and basis are not integrated, consistency breaks down and the estimate loses traceability.
For decision-makers, this creates a visibility gap. Confidence in the estimate depends on the number itself and on understanding how it was built, what assumptions were made, and where uncertainty remains.
Where Integration Breaks Down in Practice
The disconnect between estimate planning and basis documentation shows up in predictable, structural patterns across projects and organizations.
Common Failure Patterns
Parallel but unaligned development: different contributors develop the Estimate Plan and the Basis of Estimate independently.
Timing mismatch: the plan is created at kickoff. The basis is written near completion.
Assumption drift across disciplines: engineering, estimating, and project controls interpret scope differently.
Quantity and method disconnects: quantities evolve, while the Basis reflects earlier assumptions.
Risk and contingency misalignment: contingency is not clearly tied to defined uncertainties.
These issues are rarely visible in isolation. They emerge during execution, when scope, cost, and schedule begin to diverge from expectations.
This is fundamentally an integration issue.
The Foundation: Two Recommended Practices, One Integrated Purpose
AACE International provides clear guidance on both documents. Each serves a distinct purpose, and they are most effective when applied together.
A cost estimate plan defines how an estimate will be built before the work starts.
A basis of estimate documents what the finished estimate represents and what it depends on.
Estimate Plan | Basis of Estimate | |
AACE guidance | RP 36R-08 | RP 34R-05 |
Question it answers | How will the estimate be built? | What does the estimate represent? |
Typical timing | At estimate kickoff | Developed alongside the estimate, finalized with it |
Main audience | Estimate team and contributing disciplines | Reviewers, approvers, and decision-makers |
Risk if prepared alone | Set aside once work starts | Written after the fact to describe what happened |
RP 36R-08: Cost Estimate Plan
Defines how the estimate will be built:
Purpose and classification
Scope boundaries
Methodology and approach
Inputs and responsibilities
Alignment with execution strategy
RP 34R-05: Basis of Estimate
Explains what the estimate represents:
Scope and design maturity
Assumptions and exclusions
Quantity sources
Pricing logic
Risk and contingency
Individually, both are necessary. Together, they form the foundation of an integrated estimate plan and basis of estimate.
The Integrated Estimating Workflow
The solution is to integrate the two documents into a single workflow that produces one controlling reference from kickoff through decision, rather than improving either one in isolation.
In an integrated estimate plan and basis of estimate, planning and documentation evolve together as the estimate is built.
Key Workflow Elements
Estimate Kickoff: align scope, classification, and roles
Integrated Plan and Basis: one controlling document
Receivables and Deliverables: gaps made visible
Planning Structure: WBS aligned with execution
Quantity Basis: traceable, discipline-owned quantities
Cost Basis: consistent pricing logic
Risk, Contingency, and Accuracy: tied to uncertainty drivers
Review and Validation: alignment confirmed
The result is an estimate that is complete, consistent, traceable, and defensible.
Why This Is a Governance Problem, Not a Documentation Problem
The implication extends beyond estimating discipline into capital allocation and decision quality.
It is tempting to view this issue as one of documentation quality. In reality, it is a governance issue.
Estimate Plans and Basis of Estimate documents are the mechanism through which scope, assumptions, cost methodology, and uncertainty are communicated and understood.
The Core Risk
Confidence advances faster than definition maturity.
When that happens:
Estimates appear more reliable than they are
Capital is approved based on incomplete alignment
Cost growth is misattributed to execution
This is how cost risk becomes embedded at approval.
What Good Looks Like in Practice
An integrated approach shows up in how disciplined teams structure their work, from how the estimate is developed to how it is documented.
Characteristics of Strong Integration
Single controlling reference throughout development
Continuous integration during development, not end-of-process reconciliation
Clear linkage between scope, quantities, and cost
Visible uncertainty, tied to real drivers
Reviews focused on internal consistency, not checklist completion
In this environment, the estimate works as one transparent system instead of a stack of separate documents.
What Changes When You Integrate
Integration changes how estimates are interpreted and used in decision-making.
When estimate planning and basis documentation are integrated:
Assumptions are clarified early
Scope, quantities, and cost remain connected
Risk becomes visible and structured
Reviews confirm consistency instead of uncovering gaps
Most importantly, decision-makers gain clarity into:
How the estimate was built
What drives the number
Where uncertainty remains
How confident they should be
This is what turns an estimate into a decision tool.
How an Integrated Estimate Plan and Basis Improves Investment Decisions
The value of integration ultimately shows up at the point of investment decision, where clarity, traceability, and confidence must come together.
Most estimate failures are caused by a lack of structure connecting how the estimate was planned to how it was built, more often than by poor estimating technique.
Integrating the estimate plan and the basis of estimate into a single workflow creates one controlling reference that connects scope, assumptions, and methodology into a traceable system.
In that context, the estimate becomes a defensible foundation for investment decisions, with assumptions, risks, and uncertainties clearly understood before capital is committed.
At ROMAN Consulting Group, this is the structure we bring to the front end of capital projects through early-phase estimating and independent estimate reviews, helping teams reduce project cost uncertainty and make stronger investment decisions.
Key Takeaways
A cost estimate plan (AACE RP 36R-08) defines how an estimate will be built; a basis of estimate (AACE RP 34R-05) explains what the finished estimate represents.
When the two are prepared separately, by different people at different times, they drift apart and the gaps surface during execution.
Five patterns drive most breakdowns: unaligned development, timing mismatch, assumption drift, quantity and method disconnects, and contingency not tied to defined uncertainties.
Integrating both documents into one controlling reference keeps scope, quantities, assumptions, cost methodology, and contingency traceable from kickoff through decision.
This is a governance issue: confidence in the estimate should never advance faster than definition maturity.
Frequently Asked Questions
What is a cost estimate plan?
A cost estimate plan defines how an estimate will be built before work starts: its purpose and class, scope boundaries, methodology, inputs, responsibilities, and alignment with the execution strategy. AACE International Recommended Practice 36R-08 provides guidance for developing one.
What is the difference between an estimate plan and a basis of estimate?
The estimate plan is written at kickoff and defines how the estimate will be built. The basis of estimate documents what the finished estimate represents, including scope maturity, assumptions, quantity sources, pricing logic, and risk. The plan sets the intent, and the basis records the result.
Why should the estimate plan and basis of estimate be integrated?
When they are prepared separately, nothing checks that the estimate was built the way it was planned. Integrating them into one controlling reference keeps scope, quantities, assumptions, and cost methodology consistent and traceable.
When should the basis of estimate be written?
In parallel with the estimate, starting from the estimate plan. A basis written after the estimate is complete tends to describe what happened instead of guiding how the estimate was built.
Who should review the estimate plan and basis of estimate?
A reviewer independent of the estimate team, before the gate or funding decision. An independent estimate review checks that scope, quantities, cost, and assumptions are consistent across both documents and with the stated estimate class.
Author Acknowledgment
This article reflects work developed collaboratively by Roger Farish and Christopher Kinney, drawing on shared technical research and practitioner experience in front-end capital project estimating.
The concepts presented are based on work developed for AACE International conference presentations and reflect ongoing contributions to industry practice in estimate planning and Basis of Estimate development.
The work is aligned with the technical presentation: "Integrating Estimate Plans and Basis Documents for Higher-Quality Cost Estimates."
References
AACE International Recommended Practice 36R-08, Development of Cost Estimate Plans
AACE International Recommended Practice 34R-05, Basis of Estimate
Farish, R. and Kinney, C., "Integrating Estimate Plans and Basis Documents for Higher-Quality Cost Estimates," AACE International technical presentation 2026
Reducing project cost uncertainty for stronger investment decisions.
Comments