Detailed Estimate

Definition — what it is

A detailed estimate is a bottom-up cost buildup derived from measured quantities, in which each item of work is priced for labor, material, equipment, and subcontract cost, then aggregated with indirect costs, markup, and contingency into a total. It is the most rigorous form of estimate, produced when the design is complete enough to measure, and it becomes the basis for the bid and, once awarded, the working budget. Unlike a conceptual estimate, which projects cost from parameters, a detailed estimate prices actual quantities against actual production rates and current prices. It is not a bid until markup and strategy are applied, and it is not the budget until it is awarded and reconciled; it is the disciplined engine that turns a measured scope into a defensible number.

Also known as: Definitive Estimate, Hard-Dollar Estimate, Bottom-Up Estimate, Bid Estimate, Cost Estimate

Why it matters — what it protects

The detailed estimate is where a job's margin is won or lost before a shovel moves. Labor production rates, crew compositions, and the quantities they are applied to determine most of the cost and most of the risk, and an optimistic production assumption compounded across thousands of hours is how estimators bankrupt otherwise well-run companies. The estimate is the single document where the entire economic bet of the project is made explicit and either sound or fatally optimistic.

It becomes the budget the whole job is measured against. Once awarded, the detailed estimate is converted into the cost-code budget, and every job-cost report, cost-to-complete, and profit-fade analysis measures actual performance against it. An estimate structured to match the cost codes lets the field see overruns as they happen; one that does not leaves the project flying blind until the money is already spent.

It is the evidentiary basis for pricing every change. When scope changes, the estimate's unit prices, production rates, and buildup logic are what the change is priced against, and a well-documented estimate makes a change-order negotiation a matter of applying known rates to a measured delta. A thin, undocumented estimate turns every change into a fresh argument with no agreed basis.

Its structure encodes the company's cost intelligence. The production rates, crew mixes, waste factors, and indirect-cost logic in a detailed estimate are the accumulated, calibrated knowledge of what work actually costs the firm. This is why estimators guard their rate libraries and why back-testing estimates against as-built cost is the mechanism by which a company gets systematically better at bidding rather than relying on luck.

Lifecycle — how it moves

1. Quantity takeoff intake

   Measured quantities are received from the takeoff, organized by assembly and cost code. The estimate inherits every error and every stated convention from the takeoff, so a takeoff on the wrong revision or the wrong basis corrupts the estimate before pricing begins.

2. Pricing strategy and rate selection

   The estimator decides what is self-performed versus subcontracted, and selects labor production rates, crew compositions, and material and equipment prices. Rate selection is where experience matters most; the same quantity priced at two production rates yields two very different bets.

3. Direct cost buildup

   Each work item is priced for labor, material, equipment, and subcontract cost. Labor is quantity times production rate times wage plus burden -- the most volatile and most consequential part of the buildup and the place errors do the most damage.

4. Subcontractor and quote integration

   Subcontractor bids and vendor quotes are leveled and folded in for scope the firm does not self-perform. Un-leveled subcontract numbers imported directly are a major source of scope gaps carried into the estimate.

5. Indirect and general conditions

   Project overhead -- supervision, temporary facilities, equipment, insurance, and general conditions -- is added, typically as time-dependent costs tied to the schedule duration. A schedule slip inflates these directly, which is why estimate and schedule must be built together.

6. Markup, contingency, and escalation

   Overhead and profit markup, an estimating contingency sized to the design completeness, and escalation to the construction period are applied. This is where the cost estimate becomes a price, and where competitive and risk strategy enter.

7. Review, reconciliation, and validation

   The estimate is reviewed for completeness and reasonableness, reconciled against a conceptual estimate or benchmark, and stress-tested on the riskiest assumptions. Cross-checking cost per square foot against comparables catches gross errors a line-by-line review can miss.

8. Bid finalization and budget conversion

   Final strategy adjustments are made, the bid is submitted, and on award the estimate is converted into the working budget by cost code. The fidelity of that conversion determines whether the field can actually track performance against the bet the estimate made.

Anatomy — the data it carries

Cost code / work breakdown

The structure the estimate is organized to, aligned with the job-cost system. Misalignment here means estimated and actual cost can never be compared during the job.

Quantity and unit of measure

The measured quantity from the takeoff and its unit. The multiplicand of every line; an error here scales through labor, material, and equipment simultaneously.

Labor production rate

Units of work per crew-hour, from the rate library. The most consequential and most volatile assumption in the estimate and the usual source of a losing bid.

Crew composition and wage rates

The trades and headcount in each crew and their wage plus burden, including any prevailing-wage or union-fringe obligation. Determines labor cost per hour and must match the jurisdiction's wage requirements.

Material price and waste factor

Current unit price and the waste allowance. Prices must be current and quoted; stale material pricing is a slow, silent margin leak on volatile commodities.

Equipment cost

Owned or rented equipment cost, by hour, day, or duration. Often underestimated for long-duration or specialty equipment tied to the schedule.

Subcontract cost

Leveled subcontractor pricing for scope not self-performed. Must be leveled before inclusion or scope gaps in the sub bid become scope gaps in the estimate.

Indirect / general conditions

Time-dependent project overhead -- supervision, temp facilities, insurance, fees. Tied to schedule duration, so it moves with any schedule change.

Markup — overhead and profit

The applied margin for home-office overhead and profit. Where cost becomes price and where competitive strategy is expressed.

Contingency

The estimating reserve sized to design completeness and risk. Distinct from markup and from owner allowances; squeezing it to win is a self-inflicted loss.

Escalation

Adjustment of material and labor prices to the construction period. A one-directional error when omitted on projects that build far in the future.

Basis of estimate and assumptions

Documented inclusions, exclusions, quotes used, and assumptions. The record that makes the estimate defensible and that turns change pricing into arithmetic instead of argument.

Failure modes — how it breaks

Optimistic labor production rates

Production rates are set to what a good crew achieves on a good day and applied across the whole quantity. The optimism is invisible per line and catastrophic in aggregate -- a ten percent production miss across thousands of labor hours is the difference between profit and loss on many jobs.

Estimate structure divorced from cost codes

The estimate is built in a structure that does not map to the job-cost system, so on award the budget conversion is a manual reinterpretation. Actual cost can never be cleanly compared to the estimate, and overruns stay hidden until the money is spent.

Un-leveled subcontractor numbers imported directly

A subcontractor's bid is dropped into the estimate without leveling, carrying that sub's scope gaps and exclusions into the estimate unnoticed. The gap becomes the general contractor's cost after award, discovered as a change or a backcharge fight.

General conditions not tied to the schedule

Time-dependent overhead is estimated as a lump rather than derived from the schedule duration, so when the schedule stretches, the general conditions do not stretch with it in anyone's model. The overrun on supervision and temp facilities is real but was never budgeted.

Stale material pricing on volatile commodities

Steel, copper, fuel, or lumber are priced from a rate library that has not tracked a fast-moving market. The estimate looks complete and is quietly under-priced on the exact items whose prices moved, and the margin evaporates at buyout.

Contingency and escalation dropped to win

Under competitive pressure the estimating contingency and escalation are trimmed until the bid is low enough to win. The bid wins and the job loses, because the risks those reserves covered did not disappear -- only the money set aside for them did.

Metrics — how it is measured

Estimate-to-actual variance

Difference between estimated and actual cost by cost code, back-tested at closeout. The definitive calibration of the estimate and the production-rate library.

Labor productivity factor achieved

Actual production rates against estimated ones, by trade. Isolates the single most consequential estimating assumption for correction on future bids.

Bid spread against competitors

The gap between the firm's bid and the next bidder. A consistently large low spread signals a systematic estimating error, not a competitive edge.

Buyout variance

Difference between estimated subcontract and material cost and the bought-out cost. Reveals whether the estimate's pricing and leveling held up against the real market.

Contingency consumption

How much estimating contingency the job consumed. Calibrates whether contingency was sized honestly or trimmed to win.

Estimate cycle time and coverage

Time to produce the estimate and how much of scope was priced versus allowanced. Balances thoroughness against the bid window and flags scope carried on assumption.

The AI shift — what actually changes

Conversational

The estimate stops being a spreadsheet you scroll and becomes something you interrogate. You can ask which cost codes carry the most labor risk, which material lines are priced from stale quotes, how the total moves if a key production rate is off by ten percent, or where this estimate diverges from a comparable completed job -- with the underlying lines cited.

Generative

The buildup shifts from manual line entry to a reviewed draft. From the takeoff and a rate library, a system prices each item for labor, material, equipment, and subcontract, applies waste and crew logic, and drafts the direct-cost buildup with assumptions recorded -- which the estimator adjusts for strategy and risk rather than typing every line.

Orchestrated

The estimate stops being an island. Quantities are pulled from the current takeoff, subcontractor bids are leveled before integration, general conditions are tied to the schedule so a duration change flows through, material lines are checked against current quotes, and the whole estimate is mapped to the cost-code structure so award-day budget conversion is automatic rather than a manual reinterpretation.

Autonomous

The routine motion runs without a person driving it: estimates re-priced when the takeoff or a material quote changes, stale prices flagged, un-leveled sub numbers blocked from import, general conditions kept synchronized with the schedule, and estimate-to-actual variance from completed jobs fed back to flag production rates that keep missing -- while humans own every production rate, every markup and contingency decision, and every number submitted as a bid.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Stress-testing a completed estimate before it is submitted as a bid.

Stress-test the attached detailed estimate before we submit. Identify the cost codes that carry the most labor risk by showing labor as a share of each code and the production rate assumed, and flag any rate that looks optimistic against typical field performance for that work. List every material line priced from a quote older than thirty days, especially steel, copper, fuel, and lumber. Confirm that general conditions are derived from the schedule duration rather than a lump, and tell me what happens to the total if the schedule slips by a month. Finally, compute the cost per square foot and compare it to comparable completed projects, flagging any divergence large enough to suggest a missed or double-counted scope.

What good output looks like: A risk-ranked read of the estimate -- labor exposure, stale prices, schedule-linked general conditions, and a cost-per-square-foot benchmark -- each tied to specific lines, not a restatement of the total.

Follow-ups:

• If our concrete production rate is ten percent worse than assumed, what does that do to the total?
• Which subcontract lines went in without leveling, and what scope gaps might they carry?
• Where is the contingency relative to the design completeness -- is it enough?

Generative — Building the direct-cost buildup from a takeoff for a self-perform scope.

Build the direct-cost buildup for our self-perform sitework scope from the attached takeoff and our rate library. For each item price labor as quantity times production rate times crew wage plus burden, add material with the appropriate waste factor, and add equipment cost by duration. Use the crew compositions from our library and apply the prevailing-wage rates for this jurisdiction to the labor. Organize the buildup by our cost-code structure, keep labor, material, and equipment as separate columns, and record for every line the production rate and price source you used so I can verify them. Do not apply markup, contingency, or escalation -- I will set those. Flag any quantity you priced against an assumption because the takeoff carried one.

What good output looks like: A cost-code-structured direct-cost buildup with separated labor, material, and equipment, documented rates and price sources, and assumptions flagged -- ready for the estimator to apply strategy, not a finished bid.

Follow-ups:

• Reprice the earthwork with the alternate crew composition and show the delta.
• Which lines are most sensitive to the production rate, and by how much?
• Add a column mapping each line to the job-cost code it will convert to on award.

Orchestrated — Integrating leveled subcontractor bids and keeping the estimate synchronized.

We have subcontractor bids in for four trades on this estimate. For each trade, level the bids against the bid-package scope, identify each bidder's exclusions and scope gaps, and tell me the true leveled cost including anything a low bidder excluded that we would have to carry. Fold the leveled numbers into the estimate against the correct cost codes, and reconcile the result against the allowances we had been carrying for those trades. Then check the whole estimate: are general conditions still consistent with the current schedule duration, are any self-perform material lines now priced from quotes older than thirty days, and does every line map cleanly to a job-cost code for award conversion. Flag anything you cannot reconcile rather than forcing it.

What good output looks like: Leveled subcontract pricing integrated against the right cost codes with carried-gap costs made explicit, reconciled against allowances, plus a synchronization check on general conditions, pricing currency, and cost-code mapping.

Follow-ups:

• Draft the scope clarifications we need from the low mechanical bidder before we carry them.
• How does folding in the leveled subs change our total against the conceptual budget?
• Which allowances can we now release because real pricing has replaced them?

Autonomous — Standing policy for keeping estimates current and feeding actuals back.

Maintain our estimates continuously under these rules. When a takeoff is revised, re-price the affected lines using the current rate library and flag the net change. Keep material pricing current: flag any line priced from a quote older than thirty days and any volatile commodity that has moved beyond a threshold I set since it was priced. Block any subcontractor number from being imported into an estimate unless it has been leveled, and hold it for me if it has not. Keep general conditions synchronized with the current schedule duration and flag the delta when the schedule changes. As jobs close out, compare estimate to actual by cost code and flag any production rate or unit price that has missed consistently across multiple jobs so we can recalibrate the library. Never set or change a production rate, markup, or contingency, and never submit or finalize a bid -- route every one of those to me.

What good output looks like: Estimates that stay re-priced, current, and schedule-synchronized with a feedback loop from actuals, presented as a short exception queue -- while production rates, markup, contingency, and bid submission stay human decisions.

Follow-ups:

• Show me every estimate line priced from a stale or moved quote right now.
• Which production rates have missed across the last several completed jobs?
• Which pending sub numbers are held because they have not been leveled?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Lump-sum spreadsheet

   The estimate is a handful of lump numbers with no unit rates, no labor breakdown, and no cost-code structure. It cannot be interrogated, reconciled, or converted cleanly into a budget.

1. Level 1 — Unit-priced buildup

   Work is priced from unit rates with separated labor, material, and equipment, but the rate library is informal, pricing currency is manual, and cost-code alignment is loose.

2. Level 2 — Coded and reconciled

   The estimate is structured to the job-cost codes, general conditions are tied to the schedule, subcontract numbers are leveled before inclusion, and estimates are reconciled against conceptual budgets and benchmarks.

3. Level 3 — Assisted

   Direct-cost buildups are drafted from the takeoff and rate library for review, stale prices and un-leveled subs are flagged, sensitivity to production rates is computed, and estimate-to-actual variance is fed back for calibration.

4. Level 4 — Operated

   Re-pricing on takeoff change, price-currency monitoring, sub-leveling gates, schedule-synchronized general conditions, and the actuals feedback loop run unattended inside guardrails, while production rates, markup, contingency, and bid submission remain human decisions.

Common questions

What separates a detailed estimate from a conceptual estimate?

Information and method. A conceptual estimate projects cost from parameters -- dollars per square foot, per key -- before the design can be measured, and carries a wide range. A detailed estimate prices measured quantities line by line against production rates and current prices once the design is complete enough to take off, and carries a much tighter range. The detailed estimate is bottom-up and defensible line by line; the conceptual estimate is top-down and defensible only as a range.

Why are labor production rates the riskiest part of an estimate?

Because labor is often the largest and most variable cost, and a production-rate error compounds across the entire quantity. A rate set to a good crew's best day, applied to thousands of hours, produces an aggregate optimism that no single line reveals and that only surfaces once the work is underway and the hours are being burned. Material and subcontract prices are largely fixed at buyout, but labor productivity is exposed for the whole job, which is why calibrating rates against as-built performance is the highest-value estimating discipline.

How does the detailed estimate become the project budget?

On award, the estimate is converted into a budget organized by cost code, and that budget is what job-cost reporting, cost-to-complete, and profit-fade analysis measure actual performance against. The conversion is clean only if the estimate was built in the same cost-code structure the job-cost system uses; if it was not, the conversion is a manual reinterpretation that loses fidelity and blinds the field to overruns. This is why aligning the estimate structure to the cost codes from the start is not a formality but a control.