# Conceptual Estimate

> The early, parametric cost projection made before design is complete, used to test feasibility and set the budget the project will be held to.

- Source: https://briq.ai/acu/object/conceptual-estimate
- Department: Preconstruction & Estimating (https://briq.ai/acu/department/preconstruction)
- Catalog code: PRE 203 · Level: Practitioner · Track: Foundations · 10 min read
- Also known as: ROM Estimate, Order-of-Magnitude Estimate, Parametric Estimate, Programming Estimate, Budget Estimate

## Definition

A conceptual estimate is an early-stage cost projection produced before the design is detailed enough to measure, using parametric methods -- cost per square foot, cost per key, cost per bed, or historical cost models -- rather than measured quantities. It exists to answer the feasibility question: can this program be built for a budget the owner can fund, and where are the cost drivers before anyone has spent design fees resolving details. It carries a wide, deliberately stated accuracy range because it is built on assumptions, not measurements. A conceptual estimate is not a bid, not a guaranteed price, and not a detailed estimate; treating an order-of-magnitude number as a hard commitment is one of the most common and damaging mistakes in preconstruction.

## Why it matters

The conceptual estimate is where the budget is born, and the budget outlives the estimate. The number produced here often becomes the figure the owner funds, the board approves, and the team is measured against for the life of the project -- long after everyone has forgotten it was an order-of-magnitude projection with a wide range. Getting the framing right, and stating the range honestly, is what prevents a defensible early estimate from becoming an indefensible broken promise.

It is the cheapest point to change the project. Decisions made at concept -- building height, structural system, envelope type, site strategy -- move cost by percentages that later value engineering can only nibble at. The conceptual estimate is the tool that makes those trade-offs visible while they can still be made cheaply, which is its highest-value use and the reason it is worth producing before the design can be measured.

It sets expectations about uncertainty, or fails to. A conceptual estimate presented as a single number invites the reader to treat it as precise; the same estimate presented as a range with named assumptions and an escalation basis invites the right conversation about risk and contingency. The discipline of expressing and defending the uncertainty is as important as the point number, because the point number will be wrong and the range is what protects everyone when it is.

It is the baseline design development is measured against. As the design matures and the estimate is redone with more information, the movement between conceptual and later estimates is itself information -- it shows whether the design is tracking the budget or drifting away from it. Without a documented conceptual basis, there is nothing to measure that drift against, and budget erosion becomes invisible until a detailed estimate delivers the bad news all at once.

## Lifecycle

1. **Program and basis capture** — The program -- areas by use, key counts, capacity -- and the project's location, timing, and quality level are captured. This basis is the foundation of every parametric calculation; an unstated or wrong basis produces a number that looks precise and means nothing.
2. **Selecting comparables and cost models** — Historical costs from comparable completed projects, or published parametric models, are selected and adjusted for the project. Comparable selection is the whole exercise -- a wrong comparable, or one not adjusted for region and time, poisons the estimate at the source.
3. **Parametric calculation** — Costs are computed by applying rates to program units -- dollars per square foot by system, per key, per bed. Breaking the parametric rate down by system rather than a single blended rate is what lets the estimate be interrogated and adjusted intelligently.
4. **Adjustments for location, time, and complexity** — Rates are adjusted for regional cost differences, escalated to the midpoint of construction, and modified for site, complexity, and market conditions. Escalation to the right point in time is routinely underdone, and it is a large, systematic error when construction is years away.
5. **Allowances, contingency, and soft costs** — Design and construction contingencies appropriate to the low information level are added, along with allowances for undefined scope and the soft costs the parametric rate excludes. Contingency at concept is large by design, and shrinking it to make the budget work is a self-inflicted wound.
6. **Range and confidence statement** — The estimate is expressed as a range with a stated confidence level and the key assumptions listed. This is the step most often skipped under pressure to give a single number, and its absence is what turns an honest estimate into a broken promise.
7. **Review, reconciliation, and issue** — The estimate is reviewed for reasonableness, benchmarked against comparables, and issued with its assumptions and exclusions documented. The documented basis is what lets the estimate be defended and updated rather than merely argued about later.
8. **Progressive refinement** — As design develops, the conceptual estimate is superseded by increasingly detailed estimates, and the movement between them is tracked. The conceptual estimate's real end state is to be measured against, not merely replaced.

## Anatomy

- **Program summary** — Areas by use, key or bed counts, and capacity metrics. The denominator of every parametric calculation; an error here scales through the entire estimate.
- **Basis of estimate** — The documented assumptions -- quality level, systems assumed, exclusions, and information available. The single most important field, because it is what makes the number interpretable and defensible.
- **Parametric rates by system** — Cost per unit broken down by building system rather than a single blended figure. What lets the estimate be interrogated and adjusted rather than taken on faith.
- **Comparable projects** — The completed projects the rates are drawn from, with their type, size, location, and date. The provenance of the numbers; undocumented comparables are unfalsifiable.
- **Location adjustment factor** — The regional cost multiplier applied to the base rates. A large and often-mishandled adjustment when comparables are from a different market.
- **Escalation basis** — The rate and the target date -- typically the midpoint of construction -- used to escalate to future dollars. Systematically underdone, and material when construction is years out.
- **Allowances** — Dollar amounts for scope known to exist but not yet defined. Distinct from contingency and essential where the program implies scope the parametric rate does not cover.
- **Design and construction contingency** — The reserve appropriate to the low information level, larger at concept than at any later stage. Shrinking it to make the budget close is the classic self-inflicted overrun.
- **Soft costs** — Design fees, permits, financing, and other non-construction costs the parametric rate excludes. Owners routinely conflate construction cost with project cost, and this field is where that confusion is prevented.
- **Confidence range** — The stated accuracy band -- often plus or minus twenty to thirty percent at concept. The field that communicates that this is a projection, not a price.
- **Exclusions** — What the estimate explicitly does not cover -- land, FF&E, utility upgrades, hazardous material abatement. Unstated exclusions are the source of the worst budget surprises.
- **Estimate date and information level** — When it was made and what design information existed. Anchors the estimate to a point in the design's maturity so drift can be measured against it.

## Failure modes

- **Range dropped, point number promised** — The estimate is produced with an honest plus-or-minus band, but only the single number survives into the budget memo and the board presentation. The project is then held to a precise figure that was never meant to be precise, and the eventual overrun looks like failure rather than the expected settling within a stated range.
- **Wrong or unadjusted comparables** — Rates are drawn from a project of a different type, era, or region and applied without adjustment. A number that appears grounded in real experience is actually anchored to the wrong experience, and the error is baked in at the source where it is hardest to detect.
- **Escalation to today instead of construction midpoint** — Costs are stated in current dollars for a project that will not break ground for two years and will build over three. The systematic shortfall from omitted escalation is large, predictable, and entirely avoidable, yet it is one of the most common conceptual-estimate errors.
- **Contingency shrunk to make the budget work** — The parametric number comes in over the owner's target, so contingency is quietly reduced until the total fits. The uncertainty did not go away -- it was simply removed from the paper -- and it reappears as the overrun the contingency existed to absorb.
- **Soft costs and exclusions blurred into construction cost** — The owner reads the parametric construction number as the total project cost, and no one distinguishes land, design fees, FF&E, and permits. The funding is set against the wrong scope, and the gap surfaces when the real bills arrive.
- **Blended rate that cannot be interrogated** — The estimate is a single dollars-per-square-foot number with no breakdown by system. When someone questions it or the program changes, there is no way to see which system drives the cost or to adjust intelligently -- the number is a black box that can only be accepted or rejected.

## Metrics

- **Conceptual-to-final variance** — Difference between the conceptual estimate and the final cost, back-tested after the job. The core calibration metric for the estimating team's parametric models.
- **Estimate range at issue** — The stated plus-or-minus band. Should be wide at concept and narrow as design matures; a suspiciously tight early range is a warning, not a strength.
- **Escalation adequacy** — Whether the escalation basis matched actual cost movement to the construction midpoint. Tracks a systematic and recurring source of early-estimate error.
- **Contingency consumption** — How much of the conceptual contingency the project actually consumed. Calibrates whether contingency was set honestly or squeezed to fit the budget.
- **Comparable relevance** — How closely the chosen comparables matched the actual project by type, size, region, and era. A leading indicator of estimate reliability set at the source.
- **Design-development drift** — Movement between successive estimates as design matures. Reveals whether the design is tracking the conceptual budget or drifting away from it.

## The AI shift

- **Conversational** — The estimate stops being a single defended number and becomes something you can pull apart. You can ask which system drives the cost per square foot, how the number changes if the structural system or the envelope changes, or how this project's rate compares to your comparable set -- and get an answer tied to the rates and comparables behind it rather than re-deriving the estimate by hand.
- **Generative** — First-pass parametric estimating shifts to a reviewed draft. Given the program, location, timing, and quality level, a system produces a system-by-system parametric estimate with comparables cited, location and escalation adjustments applied, and a stated range -- which the estimator interrogates and corrects rather than building every line from a blank model.
- **Orchestrated** — The estimate stops being an isolated snapshot. It is reconciled against the historical comparable database, escalated consistently to the construction midpoint, checked for the exclusions and soft costs owners routinely forget, and carried forward so that each later, more detailed estimate is automatically compared to the conceptual basis and the drift made visible.
- **Autonomous** — The routine motion runs without a person driving it: comparable projects surfaced and adjusted for region and era, escalation recalculated as timelines move, ranges and contingencies kept sized to the information level, and drift between the conceptual basis and later estimates tracked and flagged -- while humans own comparable selection, contingency sizing, and every number that leaves the door as a budget.

## Prompts

### Conversational — Pressure-testing an early estimate before it becomes the budget.

```text
Interrogate the attached conceptual estimate for a four-story, one-hundred-forty-thousand-square-foot outpatient medical office building in this region, with construction expected to start in eighteen months and run two years. Break down the cost per square foot by system and tell me which systems drive the number. Confirm whether the escalation is calculated to the midpoint of construction rather than today, whether the contingency is appropriate for a concept-level information level, and whether soft costs and common exclusions -- land, FF&E, utility upgrades, abatement -- are clearly separated from construction cost. Then tell me the stated confidence range and whether it is honest for this stage. Cite the comparables the rates come from.
```

**Expected output:** A system-by-system interrogation with the cost drivers named, escalation and contingency checked, exclusions confirmed separate, and the honesty of the range assessed -- not a restatement of the single number.

**Follow-ups:**

- How does the cost per square foot change if we drop from a structural steel frame to concrete?
- Are the comparables genuinely medical office, or are some general office adjusted upward?
- What is the risk if the owner funds only the point number and not the top of the range?

### Generative — Producing a first-pass conceptual estimate from a program.

```text
Produce a first-pass conceptual estimate for a two-hundred-key limited-service hotel in this metropolitan market, wood-framed, with construction starting in about a year. Build it parametrically by building system -- substructure, structure, envelope, interiors, MEP, sitework -- rather than a single blended rate, and state the cost per key and per square foot for each. Draw your rates from comparable recently completed hotels of this class, adjust explicitly for region and escalate to the midpoint of construction, and add design and construction contingency appropriate to the concept level. List soft costs separately, state your exclusions clearly, express the total as a range with a confidence level, and document the basis of estimate and every assumption you made.
```

**Expected output:** A system-by-system parametric estimate with cost per key and per square foot, cited comparables, explicit region and escalation adjustments, contingency, separated soft costs, a stated range, and a documented basis -- a defensible draft, not a bare number.

**Follow-ups:**

- Show the same estimate if the building is podium concrete over two levels of parking instead of wood-framed.
- Which of your assumptions, if wrong, would move the total the most?
- Produce a one-page budget memo for the owner that keeps the range and exclusions front and center.

### Orchestrated — Keeping the budget honest as design develops.

```text
The design-development set for this project is now available and we have a new, more detailed estimate. Compare it against the original conceptual estimate we issued at programming. Reconcile the two by building system, showing where cost has moved and by how much, and attribute each movement to a cause where you can -- design change, scope added, escalation catching up, or an assumption that resolved differently than assumed. Tell me whether the design is tracking the conceptual budget or drifting away from it, whether the movement is inside the conceptual estimate's stated range, and whether the remaining contingency is still adequate for the reduced uncertainty. Flag anything you cannot attribute rather than guessing.
```

**Expected output:** A system-by-system reconciliation of conceptual versus developed estimate with movements attributed to causes, a clear call on whether the project is tracking or drifting, and a contingency-adequacy check -- the drift made visible, not hidden.

**Follow-ups:**

- Which drifting systems are the best candidates for value engineering to pull back to budget?
- Update the running budget-versus-estimate trend so leadership can see the trajectory.
- Is the contingency being consumed faster than the design is de-risking?

### Autonomous — Standing policy for maintaining conceptual estimates and comparable models.

```text
Maintain our conceptual estimating basis continuously under these rules. Keep the historical comparable database current as projects complete, tagging each with type, size, region, era, and final actual cost by system. When a new conceptual estimate is requested, surface the most relevant comparables and their adjustment factors for the estimator, never selecting the final set yourself. As market escalation data updates, recompute the escalation adjustment for active early-stage projects to their construction midpoint and flag any estimate whose escalation basis is now stale. As each project's design matures and new estimates are produced, compare them to the conceptual basis and flag drift beyond a threshold I set and contingency consumed faster than uncertainty is retiring. Never select comparables, never set or shrink a contingency, and never issue a number as a budget -- route every one of those to me with the supporting data.
```

**Expected output:** A living comparable database and a set of early-stage estimates that stay escalated and monitored for drift, with a short exception queue -- while comparable selection, contingency sizing, and issuing any budget number stay human decisions.

**Follow-ups:**

- Show me every active project whose escalation basis is now stale.
- Which projects are drifting beyond threshold from their conceptual budget?
- Which recently completed projects should update our per-square-foot models, and by how much?

## Maturity ladder

- **Level 0 — Level 0 — Gut and last job** — The early number is a blended rate from the last similar project, applied from memory with no documented basis, no escalation, and no range. It becomes the budget and no one can say why.
- **Level 1 — Level 1 — Parametric spreadsheet** — Estimates are built from a per-unit rate in a spreadsheet with some adjustment for region and time. The basis and range may be stated but comparables are ad hoc and reconciliation is manual.
- **Level 2 — Level 2 — Comparable database and ranges** — A maintained comparable database drives system-by-system parametric rates, escalation is calculated to the construction midpoint, and estimates are issued with documented ranges, assumptions, and exclusions.
- **Level 3 — Level 3 — Assisted** — Relevant comparables are surfaced and adjusted for review, first-pass estimates are drafted by system with basis and range, and drift between conceptual and later estimates is computed and attributed for the estimator.
- **Level 4 — Level 4 — Operated** — The comparable database, escalation, and drift monitoring run unattended inside guardrails, with a short exception queue, while comparable selection, contingency sizing, and issuing any budget number remain human decisions.

## FAQ

### How accurate is a conceptual estimate supposed to be?

Deliberately imprecise. At the programming stage a conceptual estimate typically carries a range on the order of plus or minus twenty to thirty percent, narrowing as design matures and more information replaces assumption. The accuracy is a function of the information available, not the estimator's skill, which is why the honest expression of the range matters as much as the point number. A conceptual estimate presented with a suspiciously tight range is a warning sign, not a sign of quality.

### Why does escalation matter so much in an early estimate?

Because a conceptual estimate is made years before the money is spent, and construction cost moves continuously in the interim. Costs must be escalated from today to the midpoint of the construction period, not to the estimate date, and for a project that breaks ground in two years and builds over three that adjustment can be large. Omitting or under-applying escalation is a systematic, one-directional error that makes the budget look achievable and then breaks it -- and it is entirely avoidable with a stated escalation basis.

### Should the conceptual estimate include contingency, and how much?

Yes, and more than a later estimate will. Contingency at concept exists to cover the scope that is not yet defined and the assumptions that will resolve differently than assumed, so it is largest when information is scarcest and shrinks as the design de-risks. The dangerous move is reducing contingency to make the total fit the owner's target -- the uncertainty is still there whether or not it is on the paper, and squeezing the reserve simply converts a visible risk into an invisible overrun.

## Related objects

- [Detailed Estimate](https://briq.ai/acu/object/detailed-estimate)
- [Quantity Takeoff](https://briq.ai/acu/object/quantity-takeoff)
- [Value Engineering Log](https://briq.ai/acu/object/value-engineering-log)
- [Project Budget](https://briq.ai/acu/object/budget)
- [Contingency](https://briq.ai/acu/object/contingency)
- [Allowance](https://briq.ai/acu/object/allowance)