This guide covers everything you need to know about the basis of estimates in PMBOK 8. The basis of estimates is the document that turns numbers into defensible commitments — it explains how every cost and schedule estimate was derived, what assumptions were made, and what level of confidence the team has in each figure.
What Is the Basis of Estimates?
The basis of estimates (BoE) is a supporting document that records the methodologies, assumptions, data sources, and confidence levels behind all project estimates. It answers the fundamental question: “How did you arrive at that number?” Without a BoE, estimates are arbitrary; with one, they become traceable, auditable, and defensible to sponsors, stakeholders, and auditors.
A strong basis of estimates documents not only what the estimate is but also what would cause it to change. It identifies the estimating technique used for each work package — whether analogous, parametric, bottom-up, or three-point — and explains why that technique was chosen given available information.
The basis of estimates is also a risk management tool: by stating confidence ranges and underlying assumptions, it surfaces where the greatest uncertainties lie. High-uncertainty line items become the focus of contingency reserve planning.
Basis of Estimates in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, the basis of estimates belongs to the Finance and Schedule Performance Domains and is produced during the Estimate Costs and Develop Schedule processes. PMBOK 8 treats the BoE as essential to both cost and schedule planning, reinforcing that estimates without documented rationale are unreliable.
The basis of estimates feeds directly into the cost baseline, schedule baseline, and risk register. When scope changes occur, the BoE is updated to reflect revised assumptions and new estimating rationale, ensuring the audit trail remains complete throughout the project.
Key Elements of the Basis of Estimates
A well-structured basis of estimates typically includes:
- WBS Reference — the work package or activity each estimate applies to
- Estimating Technique — analogous, parametric, bottom-up, or three-point estimation method used
- Data Sources and References — historical data, vendor quotes, industry benchmarks, or expert judgment consulted
- Assumptions and Constraints — conditions treated as true for the estimate to hold
- Confidence Range — the uncertainty band (e.g., -10%/+20%) and the basis for that range
- Exclusions — items explicitly not included in the estimate to prevent scope creep confusion
Basis of Estimates Example — Project Phoenix
For Project Phoenix, Alex Morgan prepared a basis of estimates covering all six WBS packages: Project Management, Requirements and Design, Development, Infrastructure, Testing and QA, and Launch and Transition. The Development package used parametric estimating — 240 combined labor hours for Sam Lee and John Tran at a blended rate of $65/hour — while the Design package was anchored by BrightFrame’s fixed-price quote of $12,900, making it a vendor-quoted estimate with a confidence range of just +-5%.
The Infrastructure package used bottom-up estimating aggregated from CloudHost Pro’s hosting contract, SSL certificate cost, and CDN configuration fees. When sponsor Riley Park reviewed the $72,250 budget request, the basis of estimates was the document that made approval straightforward — every number was traceable to a methodology and a data source.
You can download the complete filled-in example below — it shows exactly how the basis of estimates was applied in a real project context.
Download Free Basis of Estimates Template and Example
We have prepared two free resources to help you apply the basis of estimates on your own projects:
- Download the Basis of Estimates Template — PMBOK 8 (blank, ready to fill in)
- Download the Basis of Estimates Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Basis of Estimates — Best Practices and Common Mistakes
Document the estimating technique at the time estimates are made, not retroactively. Retrospective documentation invites rationalization rather than honest recording of the reasoning used. Require a confidence range for every estimate — a range forces the estimator to think about uncertainty, which is more valuable than a false-precision single number. Link each line item explicitly to a WBS element so the BoE can be updated cleanly when scope changes.
The basis of estimates is most effective when it is created collaboratively with the team members doing the work, not by the project manager alone. Teams that skip or rush this document often face budget disputes mid-project when sponsors ask “why does this cost so much?” and no one can answer with evidence.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Free Template & Filled-In Example
Apply what you’ve learned with these two free resources:
- Download the Free Basis of Estimates Template (PMBOK 8) — Ready-to-use blank template for your next project.
- Download the Filled-In Example — Project Phoenix — See exactly how this document was completed for a real $72K website launch project.
Project Management