Unit Prices & Assemblies

Definition — what it is

A unit price is the fully loaded cost to install one unit of a defined item of work -- one cubic yard of concrete, one linear foot of pipe, one square foot of drywall -- built from its labor, material, equipment, and sometimes subcontract components. An assembly is a bundle of unit prices that together produce a complete element of construction, such as a wall assembly combining studs, board, insulation, taping, and finish. Together they are the reusable building blocks of estimating: rather than pricing every project from raw components, an estimator applies calibrated unit prices and assemblies to measured quantities. They are not fixed market prices and not quotes; they are the firm's own calibrated cost model, only as good as the discipline with which they are maintained and back-tested against what work actually cost.

Also known as: Unit Costs, Assemblies, Cost Assemblies, Composite Rates, Recipe Costs, Unit Rate Library

Why it matters — what it protects

Unit prices and assemblies are how estimating knowledge is stored, reused, and improved. Without them, every estimate is built from raw components by whoever happens to be estimating, and the firm's hard-won knowledge of what work actually costs lives only in individual estimators' heads. With a maintained library, that knowledge is captured, applied consistently, and -- when back-tested against as-built cost -- systematically improved. The library is the firm's institutional cost memory.

They are the speed that lets a firm bid enough work to win some. Bid windows are short and estimating capacity is finite; pricing from calibrated assemblies rather than raw components is often the difference between bidding a package thoroughly and bidding it thinly or not at all. A firm that can price a wall type in one line rather than six can cover more scope in the same window, and coverage is what wins work over time.

They enforce consistency, which is what makes estimates comparable and defensible. When the same wall assembly is priced identically across estimates and estimators, a variance between two estimates means a real difference in scope or market, not a difference in who did the arithmetic. This consistency is also what makes an estimate defensible in a change negotiation -- the unit price is a known, documented rate, not a number invented for the occasion.

Their calibration is where a firm's competitive edge quietly lives. Two firms bidding the same scope with the same quantities differ mainly in their production rates and unit prices, and the firm whose library is calibrated to its own actual field performance bids tighter with less risk. Stale, generic, or optimistic unit prices are how a firm either loses bids it should win or wins bids it should lose -- which makes the maintenance of the library a strategic activity, not a clerical one.

Lifecycle — how it moves

1. Definition and scope

   Each unit price is defined precisely -- what it includes, its unit of measure, and its exclusions. An ambiguously defined unit price is applied inconsistently, and the inconsistency is invisible until estimates that should agree do not.

2. Component buildup

   The unit price is built from its labor, material, equipment, and subcontract components, each with its own rate and quantity per unit. Building it from components rather than a single blended number is what lets it be updated intelligently when one input moves.

3. Assembly composition

   Related unit prices are bundled into assemblies that produce complete construction elements, with the quantity of each component per unit of assembly fixed. A well-composed assembly prices a wall type in one line while remaining traceable to its parts.

4. Calibration to the firm

   Generic or published rates are adjusted to the firm's actual crews, wage rates, and productivity. This is the step that turns a bought library into a competitive one; an uncalibrated library prices someone else's business.

5. Application in estimates

   Unit prices and assemblies are applied to measured quantities to build the estimate quickly and consistently. Application is where a poorly defined unit price does its damage, because it is used many times before anyone notices the definition was wrong.

6. Market and wage updating

   Material prices, wage rates, and burdens are refreshed as the market moves, especially on volatile commodities. A library that is not updated is a slow, silent source of mispriced bids that looks complete on the page.

7. Back-testing against actuals

   Unit prices are compared against as-built cost from completed jobs and adjusted where they consistently miss. This feedback loop is what makes the library get better over time rather than drift, and it is the step most often neglected.

8. Governance and versioning

   Changes to the library are controlled and versioned so estimates are traceable to the rates in force when they were made. Uncontrolled edits mean an estimate can never be reproduced or defended after the fact.

Anatomy — the data it carries

Item definition and unit of measure

Precisely what the unit price covers and the unit it is priced per. Ambiguity here causes inconsistent application that is invisible until estimates disagree.

Labor component

Crew-hours per unit times crew wage plus burden. The most volatile component and the one most in need of calibration to the firm's own productivity.

Material component

Material quantity per unit, its price, and waste factor. The component most exposed to market movement and stale pricing.

Equipment component

Equipment time per unit and its rate. Easy to omit, and its omission systematically under-prices equipment-intensive work.

Subcontract component

Where the unit includes subcontracted work, its cost. Blurs the self-perform boundary if not clearly flagged.

Assembly recipe

For assemblies, the fixed quantity of each component unit price per unit of assembly. The recipe that makes a wall type one line while staying traceable to its parts.

Inclusions and exclusions

What the unit price does and does not cover. The field that prevents the same scope being double-counted or dropped between unit prices.

Region and wage basis

The location and wage regime -- open shop, union, prevailing wage -- the rate is calibrated to. A rate applied outside its wage basis is simply wrong for the jurisdiction.

Source and calibration basis

Whether the rate is published, quoted, or back-tested from actuals, and when. Establishes how much to trust the number and when it was last validated.

Effective date and version

When the rate took effect and its version. What makes an estimate reproducible and traceable to the rates in force at the time.

Productivity assumption

The production rate embedded in the labor component. The single assumption most responsible for whether the unit price wins or loses money.

Last back-test variance

How the unit price compared to actual cost the last time it was checked. The health indicator that tells an estimator whether to trust or adjust it.

Failure modes — how it breaks

Blended rates that cannot be updated

A unit price is stored as a single all-in number with no component breakdown, so when wages rise or a commodity spikes there is no way to update the affected input. The whole rate is either left stale or re-guessed, and the calibrated knowledge inside it is lost.

Uncalibrated library pricing someone else's business

Published or purchased rates are used without adjustment to the firm's own crews, wages, and productivity. The estimate is internally consistent but priced to a business that is not this one, and it either loses winnable bids or wins losing ones.

Ambiguous inclusions causing double-counts and gaps

Two unit prices both claim -- or both omit -- the same scope item because their inclusions are loosely defined. The overlap inflates the estimate or the gap under-prices it, and because each unit price looks correct alone, the error is nearly impossible to find.

Stale library never back-tested

The library is applied for years without comparing its rates to actual as-built cost. It drifts silently from reality, and the firm's bids slowly decouple from what work actually costs it, with no signal until margins erode across many jobs.

Wage basis mismatch

An open-shop rate is applied to prevailing-wage work, or a union rate to a non-union market, without adjustment. Labor is priced to the wrong regime, and on prevailing-wage jobs the error is compounded by certified-payroll obligations the rate never anticipated.

Uncontrolled edits break reproducibility

Estimators edit shared unit prices without versioning, so a completed estimate can no longer be reproduced from the library as it stood when the estimate was made. In a change negotiation or a dispute there is no defensible basis for the numbers that were used.

Metrics — how it is measured

Back-test variance

Unit price against actual as-built cost, by item. The core health metric of the library and the trigger for recalibration.

Library currency

Share of unit prices refreshed within a target window, weighted toward volatile inputs. Measures whether the library is a living model or a stale archive.

Calibration coverage

Share of rates back-tested against actuals rather than left at their generic or purchased value. Distinguishes a competitive library from a bought one.

Application consistency

Variance in how the same assembly is priced across estimates and estimators. High variance signals ambiguous definitions or uncontrolled edits.

Productivity accuracy

Embedded production rates against achieved field productivity, by trade. Isolates the assumption most responsible for win-or-lose outcomes.

Estimate speed gain

Time to price a scope from assemblies versus from raw components. Quantifies the coverage advantage the library provides in a bid window.

The AI shift — what actually changes

Conversational

The library stops being a static table and becomes something you can question. You can ask which unit prices have not been back-tested this year, which have drifted most from recent actuals, whether a wall assembly's components still add up correctly, or which rates are priced to the wrong wage basis for a given job -- with the component breakdown surfaced rather than opened line by line.

Generative

Building and refreshing the library shifts to a reviewed draft. From a scope definition, a system drafts a unit price with its labor, material, and equipment components and a productivity assumption, or composes an assembly recipe from existing unit prices -- which an estimator calibrates and approves rather than assembling from scratch.

Orchestrated

The library stops being an island. Material components are checked against current quotes, wage components against the jurisdiction's prevailing or union rates, and assembly recipes against their constituent unit prices so a change in one propagates correctly, while back-test variance from completed jobs is matched to the specific rates it should recalibrate.

Autonomous

The routine motion runs without a person driving it: volatile-commodity components flagged and re-priced against current quotes, wage bases checked against the job's jurisdiction, back-test variance from closed jobs surfaced against the rates that missed, and library versions maintained so every estimate stays reproducible -- while humans own every rate change, every productivity assumption, and the decision to trust or recalibrate any unit price.

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 — Auditing the rate library before a heavy bidding season.

Audit our unit-price library for reliability before we go into a heavy bid season. Tell me which unit prices have not been back-tested against actual cost in the last twelve months, which have a back-test variance greater than ten percent from the most recent completed jobs, and which volatile-commodity lines -- steel, copper, fuel, lumber -- are priced from data older than sixty days. For our composite assemblies, confirm the component recipes still sum correctly and flag any assembly whose components have been individually edited since the assembly was last validated. Present the highest-risk rates first, with the component that is driving the risk named for each.

What good output looks like: A risk-ranked audit of the library -- stale rates, high back-test variance, out-of-date commodities, and broken assemblies -- with the driving component named for each, not a list of every rate.

Follow-ups:

• Which of these rates do we apply most often, so I can prioritize the recalibration?
• Show me the labor components whose productivity assumption looks optimistic against recent actuals.
• Which rates are calibrated to the wrong wage basis for our upcoming prevailing-wage jobs?

Generative — Creating a new assembly for a wall type the firm has started building often.

Draft a composite unit-price assembly for an interior one-hour rated partition we are now building frequently: metal studs at sixteen inches on center, gypsum board each face, batt insulation, taping and finishing to a standard level, priced per linear foot at a stated wall height. Build it from our existing unit prices where they exist, and where a component is missing, draft the missing unit price from its labor, material, and equipment parts with an explicit productivity assumption. Show the recipe -- the quantity of each component per linear foot -- keep the labor, material, and equipment components separate, and state the inclusions and exclusions so this does not overlap with adjacent assemblies. Do not finalize the rates; mark each component with its source so I can calibrate it.

What good output looks like: A traceable assembly recipe with separated components, explicit productivity assumptions, stated inclusions and exclusions, and source-marked rates -- an estimator's draft to calibrate, not a finished library entry.

Follow-ups:

• Produce a variant of this assembly for a two-hour rating and show the cost delta.
• Which components in this recipe are most sensitive to the productivity assumption?
• Flag any scope this assembly might double-count against our existing finishes assembly.

Orchestrated — Propagating a market and wage change through the library correctly.

Two things changed: the regional carpenter wage plus fringe went up under the new agreement, and structural steel pricing has moved. Propagate both through our library correctly. For the wage change, update the labor component of every affected unit price and recompute every assembly that contains them, showing me the before and after and which estimates in progress are affected. For the steel change, update the material component of the affected unit prices and flag any active estimate priced from the old number. Confirm that assembly recipes still sum correctly after the propagation, and version the library so estimates made before today remain reproducible against the old rates. Flag anything that does not propagate cleanly rather than forcing it.

What good output looks like: A controlled propagation of wage and material changes through unit prices and assemblies with before-and-after values, affected estimates flagged, recipes re-verified, and versioning preserved -- not a blind global edit.

Follow-ups:

• Which in-progress estimates need to be re-priced and re-issued because of these changes?
• Show the margin impact on our current backlog if these rates had applied all along.
• Which assemblies did not sum correctly after propagation, and why?

Autonomous — Standing policy for keeping the rate library calibrated and reproducible.

Maintain our unit-price library continuously under these rules. Monitor volatile-commodity components -- steel, copper, fuel, lumber -- against current quotes and flag any that has moved beyond a threshold I set since it was last priced. When a completed job closes, compare its as-built cost by item against the unit prices used and surface every rate whose back-test variance exceeds ten percent, matched to the specific rate that missed. Check that every rate's wage basis matches the jurisdiction of the jobs it is being applied to, and flag mismatches. Keep assembly recipes internally consistent and flag any assembly whose components have drifted. Version every change so estimates stay reproducible. Never change a rate, never adjust a productivity assumption, and never approve a recalibration -- surface each with the evidence and route it to me.

What good output looks like: A continuously monitored, versioned library where drift, staleness, and wage-basis mismatches surface as a short exception queue with evidence -- while every rate change and productivity judgment stays a human decision.

Follow-ups:

• Show me every rate flagged for recalibration this month and the actuals behind it.
• Which commodity components have moved past threshold and need re-pricing?
• Which rates are being applied outside the wage basis they were calibrated to?

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

Maturity — locate yourself honestly

0. Level 0 — Estimator's head

   Unit prices live in individual estimators' memory and personal spreadsheets. There is no shared library, no calibration, and no reproducibility from one estimate to the next.

1. Level 1 — Shared blended rates

   A shared list of all-in unit prices exists but they are blended, rarely updated, and uncalibrated to the firm's own performance. Assemblies, if any, are informal.

2. Level 2 — Component-built and versioned

   Unit prices are built from labor, material, and equipment components, composed into assemblies, calibrated to the firm's crews and wages, and versioned so estimates are reproducible.

3. Level 3 — Assisted

   New rates and assemblies are drafted from scope for review, market and wage changes are propagated with before-and-after, and back-test variance from actuals is surfaced against the specific rates that missed.

4. Level 4 — Operated

   Commodity monitoring, wage-basis checking, back-test surfacing, recipe consistency, and versioning run unattended inside guardrails, while every rate change, productivity assumption, and recalibration remains a human decision.

Common questions

What is the difference between a unit price and an assembly?

A unit price is the fully loaded cost of one unit of a single item of work -- one cubic yard of concrete in place, one linear foot of a specific pipe. An assembly bundles several unit prices into a complete construction element, such as a wall type combining framing, board, insulation, and finish, with a fixed recipe of how much of each goes into one unit of the assembly. Assemblies let an estimator price a whole element in one line while remaining traceable down to the component unit prices behind it.

Should a firm buy a published cost database or build its own?

Most firms do both: a published database is a reasonable starting point and a useful cross-check, but rates applied without calibration to the firm's own crews, wage rates, and productivity price someone else's business, not yours. The competitive value is in the calibration -- adjusting the generic rates to what work actually costs your crews and back-testing them against your completed jobs. A purchased library that is never calibrated is a convenience; a calibrated one is an edge.

How often should unit prices be updated?

It depends on the component. Volatile material components -- steel, copper, fuel, lumber -- need refreshing whenever the market moves materially, sometimes within weeks, while labor components move with wage agreements and productivity trends and should be recalibrated against as-built cost as jobs close out. The discipline that matters most is back-testing: comparing the library's rates to what the work actually cost and adjusting the ones that consistently miss. A library that is applied but never back-tested drifts silently from reality.