Estimating Assemblies Setup: A Trade Sub's Step-by-Step Guide

An estimating assembly is a saved package of materials, labor and equipment priced for one unit of work, like a square foot of CMU wall or a linear foot of 4-inch drain line. To set one up, you define the unit, list every line item that unit needs, attach a quantity formula to each line, and connect the whole thing to your takeoff measurement. Do that for your 5 to 10 most common scopes and you stop rebuilding the workbook on every bid.

This guide walks through the setup in order. The examples are written for masonry, electrical, drywall and mechanical estimators, because that is who builds these things day to day.

Subascent

Build Estimates Without Rebuilding Workbooks

Subascent serves specialty trade businesses, including masonry, electrical, drywall and mechanical firms managing estimates and job workflows.

Visit Subascent

TL;DR

Pick one unit of measure per assembly (SF, LF or EA) and build every line item off that unit.
Write down what the assembly includes and excludes before you use it. Most assembly errors are scope gaps, not math.
Keep waste, productivity and burden as separate, visible inputs so you can adjust them per job.
Measure at the assembly level in your takeoff, then let the formulas drive the component quantities.
After each job closes, compare actual hours to the assembly and fix the assembly.

What an assembly is and why subs use them
Before you build: what to gather
Step 1: Define the unit of work
Step 2: List line items, and write the inclusions and exclusions
Step 3: Set labor, burden and productivity as visible inputs
Step 4: Add waste, allowances and purchase rounding
Step 5: Connect the assembly to your takeoff
Step 6: Code the assemblies so estimates match job costs
Step 7: Check the estimate before you submit
Step 8: Update assemblies after every job
Our perspective
Where Subascent fits
FAQ
Sources

What an assembly is and why subs use them

An assembly is a reusable unit-cost package. It holds the labor and materials for one defined unit of work, and you apply it to a takeoff quantity to get total cost, material requirements and labor hours. That is the whole idea.

Without assemblies, an estimator counts every stud, every box, every fitting, every time. That is slow, and it is where inconsistency creeps in. Two estimators in the same shop price the same wall differently because one remembered the bond beam blocks and the other did not.

With assemblies, the shop's knowledge sits in one place. The junior estimator gets the same wall price as the owner would. If you want the short version of how many to build first, we cover that in starting with 5 to 10 assemblies.

Before you build: what to gather

An assembly is only as good as the information behind it. Before setting one up, pull together the current drawings and specs, the scope narrative, addenda and revisions, schedules and details. The Marine Corps estimating manual also lists assumptions, site and logistics conditions, available equipment, labor availability and weather among the inputs. Sub estimators know the same list in plainer words: what is in your scope, what the GC is furnishing, what the spec says about product, and how hard the site is to work in.

For each scope you plan to turn into an assembly, write down:

The spec section and the typical product (for example, 8-inch CMU, Type S mortar, grouted cells at 32 inches on center).
Who furnishes what. Does the GC supply the rebar? Is scaffolding yours or theirs?
The drawing reference that supports the quantity you measure.
Your last three jobs of this type, with actual hours and material cost.

That last item matters most. Your own history is better than any published number, and it is what keeps the assembly honest.

Step 1: Define the unit of work

Pick one unit and stick to it. Good units are the ones you can read straight off a plan:

Masonry: SF of wall face, by wall type
Drywall: SF of board, by type and finish level
Electrical: EA for devices and fixtures, LF for conduit runs
Plumbing and HVAC: LF of pipe or duct by size, EA for fixtures and diffusers
Concrete: SF of slab by thickness, CY for footings
Painting and flooring: SF

The Marine Corps manual says to break the work into separately estimable elements and record a clearly definable quantity for each. If you cannot say what one unit of the assembly is in a sentence, the assembly is too big. Split it.

Name it so the next person finds it. "CMU 8in grouted 32oc, SF" beats "Block wall 2."

Step 2: List line items, and write the inclusions and exclusions

A line item is one thing you buy or one kind of labor you pay for. Each gets a description, a unit, a unit cost, and a quantity relationship to the assembly unit.

Here is a masonry example. The block count comes from geometry: a standard 8 x 16 CMU with a 3/8-inch joint covers about 0.889 SF of wall face, so you need about 1.125 blocks per square foot. For a 40 ft by 10 ft wall, that is 400 SF and 450 blocks before waste.

Line item	Unit	Quantity per 1 SF of wall	Notes
8x8x16 CMU	EA	1.125	Before waste
Waste	%	7%	Your own number, shown as a separate input
Mortar	bag or CF	From your history	Per block laid
Grout	CF	From your history	Only cells that are filled
Vertical rebar	LF	Spacing-driven	Skip if GC furnishes
Mason and laborer hours	HR	Your labor unit	See labor units guide
Scaffold	SF or day	Per your setup	Exclude if GC provides

The figures marked "from your history" are deliberately blank. They depend on your crew, your mortar mix and your jobs. Fill them from closed jobs, not from a book.

Then write the exclusions. Penn State's estimating text gives a clean example: a foundation-wall assembly includes formwork, reinforcing, concrete and finishing but excludes excavation and backfill, which must be estimated on their own. Every assembly needs that kind of note. For our CMU wall: excludes lintels over openings, control joints, flashing, cavity insulation, cleaning and sealing, unless you add them as separate assemblies.

Step 3: Set labor, burden and productivity as visible inputs

Do not bury labor inside a lump unit price. Break it into hours per unit, an hourly rate, and burden. Then you can see which one moved when a bid comes in high or low.

A few rules we use:

Hours per unit comes from your records. For electrical devices and conduit, see our three worked labor unit examples. For block and brick, see labor units for masonry estimators.
The rate is a loaded rate. Base wage plus payroll taxes, workers' comp, insurance and benefits. A national wage benchmark is not your rate. For context only, the Bureau of Labor Statistics reports private construction wages and salaries at $35.54 per hour in 2026 Q1, which excludes your burden and varies a lot by trade and city.
Productivity is a factor, not a rewrite. Keep a base labor unit and apply a multiplier for conditions: height, access, small footprint, overtime, winter. Our field guide to labor productivity factors shows how to keep that multiplier separate.

If you rework the unit every time a job feels hard, you lose the ability to learn from it.

Step 4: Add waste, allowances and purchase rounding

Waste belongs in its own column. A U.S. takeoff guide recommends separating measured work, assembly conversion, material allowance and purchase quantity, so drawing scope is not confused with waste or package rounding. The practical benefit: when the GC issues a revision and the wall gets 30 feet shorter, you change one number and the waste, mortar and labor follow.

CMU quantity conversion, waste, and pallet rounding

In the CMU example, 400 SF at 1.125 blocks and 7% waste gives about 482 blocks. If you buy by the pallet, round up at the purchase step, not inside the assembly. The assembly says what the wall needs. The purchase step says what you will buy.

Waste varies. A long straight wall wastes less than one with many corners and openings. Set two or three versions of the factor, or keep one assembly and change the input per job.

Step 5: Connect the assembly to your takeoff

This is the step most tutorials rush. The connection is simple in principle: the takeoff produces one quantity in the assembly's unit, and the assembly multiplies that quantity through every line item.

The order that works:

Measure in the assembly's unit. On a PDF plan, trace the wall length, multiply by height, and deduct openings to get SF. Set the scale first and verify it against a known dimension. Our seven-step PDF plan takeoff guide covers scale errors, which wreck every downstream number.
Assign the assembly to the measurement. In most takeoff tools, you tag the measured object with the assembly. The tool then reads the quantity.
Let formulas generate component quantities. Blocks, mortar, grout and hours all come from the one SF number.
Handle counts separately. Doors, outlets, sprinkler heads and diffusers are EA assemblies. Use count takeoff with audit-ready counts so each count traces back to a plan sheet.
Roll up. Sum the assemblies, then add general conditions, overhead, bond, tax and margin.

Two habits keep this honest. First, measure net quantities, and show the deductions. Second, keep the raw measurement unchanged. One takeoff guide points out that retaining raw, unadjusted measurements makes later changes auditable, because you can tell whether a difference came from geometry, conversion, waste or purchasing. That matches how a bid actually gets argued over after addenda.

A simple worked total for the CMU wall at 400 SF:

Piece	Calculation	Result
Net wall area	40 ft x 10 ft	400 SF
Blocks with waste	400 x 1.125 x 1.07	about 482 EA
Labor hours	400 x your hours per SF	From your history
Labor cost	Hours x loaded rate	From your rate
Material and sub-items	Per line item	From quotes

Swap in your own hours and prices and the total updates when the quantity changes. That is the payoff.

Step 6: Code the assemblies so estimates match job costs

Give each assembly a cost code that matches the codes you use in the field and in accounting. When estimate lines, timecards and invoices share the same code, you can compare budget and actual without translating. This is also where QuickBooks sync pays off, since the job cost categories already line up.

Keep the code list short. Twenty to forty codes cover most trade subs. If your foremen cannot remember the code, they will pick the wrong one and your data goes bad.

Step 7: Check the estimate before you submit

An assembly estimate can be wrong in three ways: a missing item, a wrong quantity, or a wrong price. A 20-minute review catches most of it.

Missing items. Read each assembly's exclusions against the spec and the scope letter. Did anything fall between two assemblies?
Quantities. Spot-check two or three big numbers by a second method. Colorado DOT's guidance, written for bridge design, recommends calculating quantities independently from the plans and resolving differences. The same discipline works for a tenant improvement.
Addenda. Compare the current set to the one you measured. Our plan overlay comparison takes about 20 minutes.
Prices. Confirm quotes are current and valid through the bid date.

Keep expectations realistic, too. AACE International says estimate accuracy depends on how mature the project definition is, the quality of reference cost data, assumptions, estimator skill, time available, market conditions and complexity. Its classification system gives typical ranges for building work: a Class 4 estimate runs about -10% to -20% on the low side and +20% to +30% on the high side, at 80% confidence. A rushed assembly bid on incomplete drawings sits wider than that. Know where yours sits and set margin on purpose.

Step 8: Update assemblies after every job

The setup is not finished when the library is built. After each job closes, compare actual hours and costs to what the assembly predicted. AACE's recommended practice on lost labor productivity calls for contemporaneous, uniform field records and routine comparison of actual productivity with the as-bid basis, so a decline shows up early rather than at closeout.

That means daily reports and timecards coded to the same assemblies. If the foreman logs 62 hours against a wall you bid at 48, you want to know in week one. Equipment cost belongs in the same comparison, and this piece on putting equipment costs on every job shows how to keep it in the job cost picture. For the field side, see our crew productivity tracking guide.

A simple rule: if three jobs in a row miss the same way, change the assembly. If one job misses, check the conditions first.

Our perspective

We have seen the same pattern in trade shops for years. The estimator builds a great spreadsheet, it works for one trade and one person, and then it breaks the first time someone else touches it or a GC sends a revision.

We think assemblies should be small, boring and traceable. Start with the five scopes that make up most of your bids. Write down what each includes and excludes. Keep waste and labor as separate inputs. Tie every assembly to a cost code the field also uses. Then let closed jobs correct the numbers.

General-contractor software is built around the owner's budget and the master schedule. A sub's assembly lives somewhere else: in a takeoff trace, a labor unit and a foreman's timecard. That is why we build around the sub's workflow, from the bid invite to the final invoice, and why we think the seven-step estimating workflow matters more than any single tool.

— Dave

Where Subascent fits

Subascent is job and bid management software built for specialty trade subcontractors, including masonry, electrical, plumbing, HVAC, drywall and more. It brings bid tracking, estimating, PDF takeoff (a paid add-on), submittals and RFIs, change orders, daily field reporting, crew tracking with the free CrewTrack mobile app, QuickBooks sync and profit analytics into one place. That means the assembly you set up for a bid can be the same one you compare against field hours later.

Subascent

If you want to see how that fits your trade, start with Subascent and try it on a real bid.

FAQ

How many assemblies should I build first?

Start with 5 to 10, covering the scopes that make up most of your bids. Add more only when you catch yourself rebuilding the same item by hand. A small library that the whole team trusts beats a big one nobody checks.

Should an assembly include labor?

Yes, but as its own visible line with hours per unit and a loaded rate. Do not fold labor into one lump price. Separate inputs let you adjust for site conditions and compare actual hours later.

What unit should I use for an assembly?

Use the unit you measure on the plan: SF for walls, board, slabs and finishes, LF for pipe, conduit and duct, and EA for devices, fixtures and heads. One unit per assembly keeps the takeoff and the math simple.

How do I handle waste?

Keep it as a separate percentage on each material line, not buried in the unit quantity. Set it by scope and crew experience, then round to purchase units (pallets, boxes, sticks) at the buying step. Check it against closed jobs.

How often should I update my assemblies?

After every closed job, compare actual hours and material cost to the assembly. Change the assembly when several jobs miss in the same direction. Refresh material prices at each bid, since they move faster than labor units.