Quick overview: construction basis of estimate
A basis of estimate, often shortened to BOE, is the narrative that travels with the estimate. The estimate shows quantities and money. The BOE explains the boundaries and decisions behind them.
It should let a qualified reviewer follow the logic without relying on the original estimator's memory. The document is useful at every design stage, but its detail should match the estimate. An early budget may depend on benchmark quantities and broad assumptions.
A bid estimate may depend on issued drawings, specifications, addenda, subcontractor quotes, and explicit scope qualifications. The BOE should say which condition applies.
A documented construction estimating process makes revisions safer. When a drawing changes or a quote expires, the team can identify the affected basis, revise the right cost lines, and preserve the history of the earlier decision.
Why the basis matters during estimate review
Most estimate disputes begin with a boundary that was understood by one person but never written down. One estimator priced night work while another assumed normal hours. A supplier quote excluded freight.
A budget carried a rough equipment allowance that later appeared to be a firm price. The arithmetic can be correct while the estimate still gives the wrong impression. A BOE brings those conditions into the review.
It tells the reviewer which documents were used, what was measured, which prices came from quotes or historical data, how labor was developed, and where uncertainty remains. The reviewer can then challenge the basis instead of guessing at it. The record also helps after award.
Operations can compare buyout and actual cost against the original scope and assumptions. That comparison is much less useful when the estimate total has no traceable explanation.
What a useful basis of estimate should contain
Start with identification: project name, estimate purpose, estimate date, pricing date, design stage, estimator, reviewer, and the document revision used. List drawings, specifications, addenda, reports, schedules, and owner instructions by revision when possible. A generic note such as 'per plans' is too vague for change control.
Describe the scope and the work breakdown used to organize it. State whether the estimate covers direct construction only or also includes general conditions, design, permits, testing, escalation, contingency, owner costs, taxes, bonds, and insurance. Name anything handled outside the estimate.
Then record the estimating methods. Explain where quantities came from, how crews or productivity were selected, what wage and equipment rates apply, how quotes were normalized, and which historical data was adjusted. The explanation does not need to repeat every line item.
It needs enough detail to show the governing logic. Close with assumptions, exclusions, allowances, alternates, risks, escalation treatment, contingency basis, reconciliation status, and approvals. Give each open item an owner or review trigger where the workflow supports it.
Separate ground rules from assumptions
Ground rules are the project conditions the estimate accepts as direction. Examples include the planned start date, working calendar, contracting strategy, location, currency, or required completion milestone. Assumptions fill gaps where firm direction is not available.
The distinction matters because an assumption should be tested and replaced when better information arrives. The AACE Recommended Practice 106R-19 treats the basis of estimate as a required part of an estimate package for the engineering, procurement, and construction projects within its scope. It provides a guideline for developing that record rather than treating it as an afterthought.
Write assumptions so another person can challenge them. 'Normal conditions assumed' is weak because it hides the actual condition. 'One daytime shift, Monday through Friday, with unrestricted site access' gives the scheduler, superintendent, and estimator something specific to confirm or revise. Avoid converting an unresolved scope question into a quiet assumption.
If the documents conflict, record the conflict, the temporary pricing treatment, and the clarification needed. The estimate can proceed, but the open decision remains visible.
Basis of estimate review checkpoints
A reviewer should be able to connect each major cost driver to a scope source and pricing method. The table below provides a compact review sequence. It is not a substitute for trade review, but it catches missing context before the estimate is approved or issued.
Review the BOE beside the estimate, not as a separate administrative exercise. If the narrative says the work excludes temporary power but the estimate contains a temporary-power allowance, resolve the conflict. The priced file and its explanation must describe the same scope.
| Review area | What to record | Reviewer question |
|---|---|---|
| Purpose and stage | Budget, bid, control estimate, or change estimate | What decision should this estimate support? |
| Scope sources | Drawings, specifications, addenda, reports, and revisions | Can every major scope area be traced? |
| Pricing basis | Quote, cost database, historical cost, or developed rate | Is the source current and suitable for this project? |
| Methods | Quantity, crew, productivity, waste, and markup logic | Can another estimator reproduce the approach? |
| Assumptions | Specific unresolved conditions and temporary treatment | What changes if the assumption is rejected? |
| Risk treatment | Allowances, escalation, contingency, and alternates | Is each provisional amount visible and explained? |
| Review status | Prepared by, checked by, approvals, and open actions | Who owns the remaining decisions? |
How to maintain the BOE through revisions
Keep a dated version with each formal estimate issue. Do not overwrite the earlier basis and leave the earlier estimate behind. A revision log should state what changed, why it changed, which source triggered the change, and which cost areas were affected.
When new drawings arrive, compare revisions before changing quantities. When a subcontractor quote replaces a budget rate, retain the quote date, inclusions, exclusions, alternates, and any leveling adjustment. When an assumption becomes confirmed direction, move it into the applicable ground rule or scope note.
Revisit escalation and contingency rather than carrying them forward automatically. Their basis can change as procurement dates, design maturity, and known risks change. The BOE should explain the new treatment and preserve the prior basis in the revision history.
A project cost analyst can maintain source registers, assumption logs, quote comparisons, and revision records. The estimating manager should still approve scope judgment, risk treatment, markups, and the final issued estimate.
A practical review tip
Pro tip: ask a reviewer who did not build the estimate to locate the source, method, and assumption behind three major cost lines. If the reviewer cannot do that from the estimate package, strengthen the BOE before issue. This small test exposes missing revision notes and undocumented judgment quickly.
Common basis of estimate mistakes
Do not write the BOE after the estimate is finished from memory. Capture sources and decisions while the work is being built. Retrospective notes tend to miss discarded options, temporary assumptions, and the reason a rate changed.
Do not copy the prior project's basis without checking every condition. Structure can be reused, but dates, location, labor rules, taxes, logistics, procurement strategy, design maturity, and scope sources belong to the current project. Do not bury exclusions in scattered estimate tabs.
Collect material exclusions and qualifications in the BOE, then confirm they match the proposal or budget presentation. An internal estimate note does not protect the team when issued language says something different. Do not treat approval as proof that every assumption is correct.
Approval records the decision made with the available information. Open assumptions still need owners, due dates, or replacement triggers.
Key takeaway
A construction basis of estimate should make the cost forecast understandable, reviewable, and updateable. Record the scope boundary, source revisions, methods, ground rules, assumptions, exclusions, allowances, risks, and approvals while the estimate is developed. If a reviewer can trace the important numbers and revise them without relying on memory, the BOE is doing its job.
