Unit Rate Build-Up: How to Price Quantity Take-Off on Capital Projects
How to build a defensible unit rate from a quantity take-off on capital projects — measurement conventions, labor constants, allowances and rate staleness.
In the twelve months to April 2026, US producer prices for aluminum mill shapes rose 37.7% and for steel mill products 12.3%, while cement fell 0.1% and plastics pipe fell 4.6%. Statistics Canada shows the same shape at lower amplitude: non-residential building construction costs up 3.5% year over year in the second quarter of 2026, but structural steel framing and metal fabrications moving 2.2% and 2.0% in that single quarter against 0.5% for finishes. An estimator who escalated last year’s rate library by a headline index is now wrong on nearly every line — light on the metals, heavy on the concrete — and the total may still benchmark acceptably, because the errors run in opposite directions. That is what makes take-off and unit rate build-up a discipline rather than a data-entry task: the errors are structural, they hide inside a plausible total, and they are invisible at summary level.
This article covers where measured quantities diverge from what a project actually buys and installs, the anatomy of a composite unit rate, why the all-in labor rate carries most of the error, how take-off maturity is bridged with allowances rather than contingency, and how rate libraries go stale without anyone noticing. The aim is a rate that can be defended line by line under challenge — not a rate that merely reconciles to a total.
The Measured Quantity Is Not the Quantity the Project Buys
Every take-off is measured against a rule set, and on most North American work that rule set is undocumented. MasterFormat and UniFormat organize the estimate — by specification section and by building system respectively — but neither is a method of measurement. Neither tells you whether reinforcement laps are measured, whether formwork is the contact face or the material consumed, whether pipe is centerline or cut length. The CIQS Method of Measurement of Construction Works fills part of that gap in Canada, but it is a voluntary professional standard rather than a contractual requirement, and outside formal quantity-surveyed procurement it is rarely invoked.
The practical consequence is that measurement conventions are house rules, and house rules travel badly. When a rate developed under one set of assumptions is applied to a quantity measured under another, the mismatch is silent — no error is thrown, no reconciliation fails, the estimate simply comes out light. The measured quantity of reinforcement typically excludes laps, tie wire, chairs and spacers; the purchase order does not. The measured area of formwork is the contact face; the field consumes plywood, bearers, ties and a stripping cycle. If the rate build-up does not explicitly restore what the measurement stripped out, the estimate is short by a margin that scales linearly with the quantity. The fix is unglamorous: state the measurement basis in the estimate documentation, item by item, so that “is this included?” has a written answer rather than a remembered one.
Model-based take-off has sharpened this problem rather than solved it. Quantities extracted from a design model are fast, repeatable and auditable, which makes them feel authoritative. But a model reports what has been drawn, and at Class 3 maturity a great deal of the eventual scope has not been drawn — secondary steel, pipe supports, small-bore, cable tray, penetrations, temporary works. Model quantities also inherit the modeler’s conventions on arraying, nominal versus actual dimensions, and which disciplines were modeled at all. Treating a model export as a completed take-off is the single most common way a bottom-up estimate acquires a systematic downward bias while appearing more rigorous than its predecessor.
The measured quantity answers what the design contains; the unit rate has to answer what the field consumes.
Anatomy of a Composite Unit Rate
A composite rate is five layers, and each layer fails differently. Building it as five explicit lines rather than a single number is what makes it reviewable.
- Labor. An output constant — hours per unit — multiplied by the all-in hourly rate for the crew that performs the work. This layer carries the productivity assumption and is dealt with in the next section.
- Materials. Net measured quantity, grossed up for waste and for the items the measurement excluded, priced at a delivered rate including freight, offloading and duty. Waste is not one number: a 5% allowance on structural steel and a 5% allowance on drywall describe entirely different physical processes, and copying a single default across a rate library is how a build-up becomes decorative.
- Equipment. Either a rate per unit of output where the equipment is dedicated (a piling rig priced per foot), or a time-related cost in general conditions where it is shared (a tower crane). Double-counting between the two is common; so is omitting shared equipment entirely because everyone assumed it sat in the other column.
- Subcontract. Where the work is sublet the rate is a quoted price, not a build-up — but it still needs analysis. A subcontract quotation carries its own qualifications, its own attendances assumed to be provided free, and its own markup, and it was not priced against your measurement conventions.
- Overhead and profit. Field overhead, home office overhead and fee, applied consistently and stated separately. Published cost data presents bare costs and costs with overhead and profit as distinct figures for exactly this reason; a library that blends the two without saying so will not survive a benchmark comparison.
Separating the layers is not tidiness. A rate expressed as a single number can only be challenged as a whole, which in practice means it is not challenged at all. A rate expressed as 0.85 hours per linear foot at $62.40 an hour, plus $31 of material at 7% waste, plus $4 of equipment, plus 12% overhead and profit, can be challenged in four places by four different specialists — and the specialist who knows the productivity constant is rarely the one who knows the steel price.
The All-In Labor Rate Carries Most of the Error
On labor-intensive capital scope, the labor layer is where the estimate is genuinely won or lost, because it multiplies two uncertain numbers together. Both are routinely treated as constants.
The output constant is drawn from published cost data or an internal library, and both describe base productivity under defined conditions — reasonable access, a normal work week, a competent crew, temperate weather. Capital projects rarely provide those conditions. Congested brownfield tie-ins, permit-controlled hot work, elevated work, PPE-restricted duration, night shift, turnaround windows, winter conditions and learning-curve effects on an unfamiliar system all degrade output, and the degradation is multiplicative rather than additive. A base constant adjusted by a single round factor — the ubiquitous 1.15 — is not an adjustment; it is an admission that nobody measured. The defensible version is a small number of named factors, each traceable to a project condition described in the basis of estimate, so a reviewer can test the reasoning rather than the number.
The all-in rate is more tractable but is frequently built short. It should assemble from the base wage, statutory and fringe burden (payroll taxes, workers’ compensation, health and welfare, pension, training funds), non-productive overtime built into the planned schedule, shift and premium time, travel, per diem or camp where the workforce is not local, small tools and consumables, and supervision at the ratio actually planned. Where the work is covered by a collective agreement or a prevailing wage determination, the rate is not an estimate at all — it is a published obligation, and using a market average instead is a straightforward error. Two builds that produce $62 and $81 an hour for the same trade are usually not disagreeing about wages; they are disagreeing about the work week, the burden schedule and whether the workforce sleeps at home. On a project running a 60-hour rostered week out of a camp, an all-in rate built on a 40-hour local assumption is wrong by an amount that will show up in every single labor line simultaneously.
The practical test is to invert the build-up. Divide total labor cost by the total measured quantity of the principal commodity and compare against outturn from completed work — hours per ton of erected steel, hours per linear foot of pipe, hours per square foot of formwork. If that ratio sits outside the historical band, one of the two multiplicands is wrong, and the rate agreeing on a dollars-per-ton basis proves nothing. Two metrics agreeing is evidence; one metric agreeing is a coincidence that has not been investigated yet.
Take-Off Maturity and the Allowances That Bridge It
A take-off is only as complete as the deliverables it was measured from, and the gap between what is drawn and what will eventually be built is a known, quantifiable quantity — not a risk. AACE’s estimate classification framework ties each class to a level of deliverable maturity, and the correct response to immature deliverables is an explicit material take-off allowance on the bulk quantities: steel, concrete, piping, small-bore, cable and fittings. This is a design development allowance — an above-the-line addition to the base estimate reflecting quantity growth that experience says is coming.
It is not contingency, and conflating the two causes real damage. Contingency covers uncertain events that may or may not occur; a design development allowance covers growth that will almost certainly occur, because it always has. Booking known growth as contingency understates the base estimate, overstates the reserve, and produces a project that appears to be drawing down reserve heavily in its first year when it is simply completing its design.
The allowance percentage should be an empirical number, not a convention. The organizations that get this right measure the ratio of final installed quantity to the quantity measured at each estimate class, by commodity, across completed projects. The organizations that do not apply a round 10% to everything, because 10% is defensible in a meeting and nobody has the data to argue. Where an internal history exists, normalize it for scope boundary and measurement convention first — a take-off measured under different house rules produces a growth factor that means nothing.
Rate Libraries Go Stale Quietly
A unit rate is a snapshot with a base date, and the base date is the part most often lost in transmission. A rate carried forward without one cannot be escalated correctly, benchmarked, or reconciled to a previous estimate — because nobody can establish what it was ever true of.
The 2026 index data makes the second failure mode concrete. Escalating a whole library by a single aggregate assumes the commodities inside it move together, and they do not — the spread between aluminum mill shapes and plastics pipe over the twelve months to April 2026 was more than forty points inside one materials basket. A steel rate and a concrete rate escalated by the same factor are both wrong, and the errors partially cancel at the total, which is precisely why the problem survives review. Commodity-weighted escalation, applied by resource rather than by rate, is more work and is the only version that holds up when the estimate is disaggregated. The same logic applies to escalating forward across a long spend curve, where a single blended rate compounds the same distortion over five years instead of one.
Three further failures recur often enough to name. Rates carried across scope boundaries — a greenfield rate reused on a brownfield tie-in, where the physical work is identical and the access is not. Quoted procurement entered as a rate without the quotation’s validity period, quantity break or exclusions traveling with it, so a price valid for a 400-ton order is applied to 90 tons. Library rates with no owner, inherited through three estimates until nobody can say which project they came from or what they included. Each is a documentation failure rather than a technical one, which is why the fix is a discipline rather than a tool: every rate in a live library carries a base date, a source, a scope note and a named owner, or it is not in the library.
Key Takeaways
- North American practice has no contractually mandated method of measurement, so inclusion rules are house rules and must be written into the estimate basis rather than assumed.
- Model-based take-off is fast and auditable but reports only what has been drawn, which at early estimate classes gives a systematically light quantity dressed up as a rigorous one.
- A composite rate should be built and presented as five separate layers — labor, materials, equipment, subcontract, and overhead and profit — because a single-number rate cannot be meaningfully challenged.
- Most rate error lives in the labor layer, where an unadjusted output constant multiplies an all-in rate built on the wrong work week or the wrong burden schedule; test it by inverting to hours per ton or per foot against outturn data.
- Quantity growth between the current deliverables and the as-built scope is a design development allowance in the base estimate, not contingency, and the percentage should come from measured take-off-to-outturn history.
- Every rate needs a base date, a source and a scope note, and escalation must be applied by commodity — US producer prices spread more than forty points between aluminum mill shapes and plastics pipe in the twelve months to April 2026.