Conceptual construction estimating: make assumptions visible before the price hardens

Build a conceptual estimate around explicit design assumptions, scope boundaries and decision dates, so a benchmark budget does not become a false commitment.

Guide3 min read

Published

Tower crane above steel reinforcement

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Define the decision and the design basis
  2. Build quantities and comparable costs that can be challenged
  3. Work a range from explicit cases
  4. Keep an assumption register beside the number
  5. Reconcile the next milestone

A conceptual estimate is a decision tool built from incomplete project information. For a commercial GC or CM, the defensible output is a range tied to a defined scope and a short list of assumptions that could move it. The total alone cannot tell an owner whether the proposed program fits the budget or merely omits an expensive system.

Use the range for the decision it was built to support, such as comparing program options. Do not treat it as a subcontract commitment or a guaranteed price. A range is only as useful as the assumptions and scenarios behind it; there is no universal accuracy percentage for all conceptual estimates.

Define the decision and the design basis

Record the estimate date, design documents and revisions, intended occupancy or use, gross area, project location for pricing purposes, schedule, procurement strategy and the decision the estimate will inform. Identify what the owner has confirmed and what the team has inferred. List excluded work such as land, financing or owner equipment when applicable, rather than letting a reader assume it is included.

For a public-building program, GSA's cost-management requirements identify parametric and historical benchmark bases at early stages and require documentation of key design and cost data. That is GSA guidance for its program, not a mandatory method for every project.

Build quantities and comparable costs that can be challenged

Start with documented areas or capacities. Where details are missing, select a proxy that relates to the system, such as perimeter for exterior wall area or equipment capacity for a central plant, and state its derivation. A single building-area rate may conceal major differences in envelope, floor loading, utilities and site conditions.

Choose comparable projects with known scope, date, size, delivery and location. Remove noncomparable scope before adjusting for changes in scale, market timing, location, complexity and procurement. Record each adjustment and its basis; do not describe an old total divided by area as a current quote. If the comparable lacks a usable breakdown, state that limitation and seek another basis. For incomplete assemblies, price incomplete design intent by identifying the implied work and what remains unconfirmed.

Work a range from explicit cases

Illustrative example: a team is testing a 40,000-square-foot light industrial building. A normalized comparable supports a base building assumption of $200 per square foot, or $8.0 million. Site and utility work is a separate $1.0 million provisional allowance; it is not included in the building rate. The base before uncertainty is $9.0 million. Land and owner equipment are excluded. All figures are invented for arithmetic, not benchmarks.

CaseBuilding basisSite and utility assumptionTotal before excluded items
Low40,000 SF at $190 per SF = $7.6M$0.8M$8.4M
Base40,000 SF at $200 per SF = $8.0M$1.0M$9.0M
High40,000 SF at $215 per SF = $8.6M$1.5M$10.1M

The $8.4 million to $10.1 million range reflects only these stated cases. The high case assumes a more expensive building and utility outcome together; it is not a statistical confidence interval or a guaranteed ceiling. Confirm whether escalation through the assumed construction period, general conditions, fee and taxes are included in the comparable. Add any omitted costs explicitly rather than silently treating the building rate as all-in. A separate risk allowance should cover identified uncertainty not already represented in the scenarios or other allowances.

Keep an assumption register beside the number

AssumptionBasis and ownerPrice treatmentNext evidence
40,000 SF gross areaProgram revision A and ownerMultiplies building rateConfirm space program
Utility capacity and routePreliminary site sketch and design team$1.0M base allowanceObtain utility feedback and concept routing
Building systemComparable adjusted by estimatorIncluded in building rateConfirm structural and envelope concept
Schedule and escalationProposed start and estimatorConfirm inclusion in each rateUpdate procurement dates and pricing
Excluded owner equipmentOwner scope listOutside rangeConfirm purchase and installation interface

The register distinguishes an allowance for an identified scope from uncertainty about that allowance. Give each open item an owner and date, and note which cost lines change when an assumption changes. If a site route affects pavement restoration as well as utilities, update both, without adding the same risk twice.

Reconcile the next milestone

At schematic design or another agreed milestone, freeze the new document list, replace proxies with measured quantities where available, refresh pricing and explain the movement from the previous basis. Separate scope and design changes from market or schedule changes. A constructability review in preconstruction can expose access, sequencing or installation assumptions that deserve new cost or schedule treatment before the next estimate is presented.

A useful estimate handoff names the decision, the range and its limits, unresolved high-impact assumptions, exclusions and the next confirmation date. If the owner chooses a single planning number, retain the range and assumptions alongside it.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.