The Short Version
I've done JobTread implementations for 312+ builders and the pattern is consistent: builders spend their first few weeks learning to estimate in JobTread line by line, build their first four or five projects from scratch, and then hit a wall where estimating feels slower in JobTread than it did in Excel. That's the assembly gap. The builders who build a proper assembly library in their first 60 days never hit that wall. The ones who don't are still rebuilding the same framing and plumbing line items from scratch two years later.
Sound Familiar?
Signs you're missing an assembly library in JobTread:
- Every estimate still takes 8–12 hours regardless of how familiar the scope is
- You copy line items from old jobs instead of using a structured, current-priced library
- Your pricing on similar project types varies by 10–15% between estimates with no clear reason
- You can't delegate estimating because all the pricing knowledge is in your head
- You have JobTread but still default to Excel for rough numbers before entering anything formal
What We Found
What JobTread Assemblies Are and Why They Change Everything
An assembly in JobTread is a saved group of estimate items — a pre-built set of labor, materials, and subcontractor costs that represents a common unit of work. Instead of adding framing to an estimate line by line, you drop in your "Exterior Wall Framing" assembly, enter the linear footage, and every line item calculates automatically.
Here's what that looks like in practice. A well-built framing assembly might contain:
- 2x6 studs at 16" OC (quantity driver: linear feet of wall)
- OSB sheathing (quantity driver: wall square footage, auto-calculated from height × LF)
- Framing labor (per LF, at your current burdened rate)
- Hardware and fasteners (allowance per LF)
- Framing inspection allowance (flat)
You add the assembly to an estimate, enter 240 linear feet of exterior wall, and every number populates. The assembly knows your lumber cost, your labor rate, your sheathing coverage. You review the output, adjust for any site-specific conditions, and you're done with framing in 10 minutes instead of 45.
The Consistency Problem Assemblies Solve
Most builders who estimate manually have pricing variation of 8–15% on similar scope items between jobs — not because costs fluctuate that much, but because they're rebuilding from memory each time. An assembly library forces you to make a deliberate pricing decision once, test it against real job costs, and then apply it consistently. That consistency is what makes job cost variance analysis meaningful.
The second thing assemblies do is make your estimates transferable. If your pricing logic lives in your head, you can't delegate estimating. If it lives in a tested assembly library, a PM or project coordinator can run estimates using your methodology without you in the room. For a builder trying to scale past the point where the owner is personally involved in every bid, that capability is essential.
How to Build Your First Assembly in JobTread (Step by Step)
Building assemblies takes about 30–60 minutes per assembly the first time. The investment compounds: each assembly you build gets applied to every future estimate forever. Here's the process.
Step 1: Navigate to your Item Library. In JobTread, go to Settings and then Item Library. This is where all your individual line items and assemblies live. If you've been estimating in JobTread already, you likely have individual items in here. Assemblies will sit alongside them.
Step 2: Create a new Assembly. Click "New Item" and select "Assembly" as the item type. Name it clearly and specifically. "Framing" is too vague. "Exterior Wall Framing per LF" tells you exactly what scope the assembly covers and what quantity driver it uses. Good naming matters because you'll be searching for assemblies during live estimates.
Step 3: Add component items with quantity formulas. This is where you build the logic. For each component:
- Add the item (lumber, labor, etc.) from your existing item library or create it
- Set the unit type (LF, SF, EA, HR)
- Set the cost per unit from your current supplier pricing or labor rates
- Set the quantity formula — how many units of this item are needed per unit of the assembly
The quantity formula is the key. For exterior wall framing, one linear foot of wall requires approximately 0.8 board feet of framing lumber at 16" OC with standard stud height. That's the formula. You build it once, test it, and then it runs automatically.
Step 4: Test it against a closed job you know the actual costs for. Pull up a completed project where you know the real framing costs. Apply the assembly to that job's dimensions and compare the assembly output to what the job actually cost. If you're within 5%, the assembly is solid. If you're off, adjust the quantity formulas or unit costs and run the test again.
Step 5: Update pricing quarterly. Assemblies go stale when material costs shift. Schedule a quarterly review — 30 minutes, compare your assembly unit costs to your current supplier invoices, update anything that's drifted more than 5%. This keeps your estimates accurate without requiring you to think about pricing from scratch on every bid.
The 10 Assemblies Residential Builders Should Build First
You don't need 50 assemblies to see results. You need 10 well-built assemblies that cover the scope you price most often. Here's the list I build with residential builders in the $500K–$3M range during their Go First implementation:
1. Site Prep (per mobilization + SF of disturbed area) — demo, excavation, grading, erosion control. Most residential builders price site prep inconsistently. One assembly per project type (slab-on-grade vs. crawl vs. basement) standardizes it.
2. Foundation (per SF of footprint) — forms, concrete, waterproofing, backfill. Separate assemblies for slab, crawl, and full basement are worth the setup time because the cost structures are completely different.
3. Exterior Wall Framing (per LF of wall) — lumber, sheathing, hardware, labor. Your highest-volume framing assembly. Get this one right first.
4. Roof Framing and Sheathing (per SF of roof area) — rafters or engineered trusses, ridge board, sheathing, felt, ice and water. Complex enough that assembly consistency matters significantly.
5. Rough Electrical (per circuit or per SF) — wire, boxes, rough labor. Many builders use a per-SF rough number for early estimates and a per-circuit assembly for detailed bids. Both are worth building.
6. Rough Plumbing (per fixture) — separate assemblies per fixture type (toilet, shower, tub, sink, exterior hose bib). Plumbing cost varies significantly by fixture, so per-fixture assemblies give better accuracy than a per-SF number.
7. Drywall (per SF of wall area) — board, screws, tape, mud, labor. Your single highest-volume finish assembly. If you do any kind of interior work, this one pays for itself in the first week.
8. Tile Installation (per SF) — tile allowance (or specific material), setting materials, labor, grout, sealer. Separate assemblies for floor tile vs. shower tile vs. backsplash are worth the extra 20 minutes because labor rates differ meaningfully.
9. Interior Doors (per unit) — door, frame, hardware, installation labor. Pre-hung vs. slab vs. pocket door each warrant their own assembly.
10. Exterior Window (per unit by size tier) — window allowance by size (small, medium, large), flashing, trim, installation. Most builders use allowances here; assemblies formalize the allowance amount and installation cost.
From Assemblies to Estimate Templates
Once you have 8–10 solid assemblies, you build project templates: a "Master Bath Remodel" template that includes the bathroom framing assembly, drywall assembly, tile floor and shower assemblies, rough plumbing by fixture, and an allowance assembly for cabinetry. When a new master bath bid comes in, you open the template, enter the room dimensions and fixture count, review the generated estimate, and adjust for site-specific conditions. A 90-minute estimate instead of an 8-hour one — every time.
The total setup time to build all 10 assemblies and two to three project templates is roughly 8–12 hours. Most builders recoup that in the first two estimates they run through the new system. After that, every estimate runs faster and every number is more defensible because it's built on tested data rather than memory.
Keeping Your Assembly Library Current
An assembly library you built two years ago and never updated is worse than no library at all — it creates confident inaccuracy. Builders who price concrete at $185/yard when current supply is running $210 are not estimating. They're generating numbers that feel rigorous but are systematically wrong.
The maintenance protocol I recommend is simple:
Monthly: When you receive final invoices on a closed job, compare the actual material unit costs against your assembly pricing. If any line item is off by more than 8%, update the assembly. This takes 20 minutes and keeps your pricing current without requiring a formal review calendar.
Quarterly: Pull supplier price lists for your top 10 materials and do a deliberate update pass. Update labor rates if your crew costs have shifted. Run a test estimate on a recently closed project to verify the assemblies still produce accurate outputs.
Annually: Review the full assembly library. Retire assemblies for scope you no longer take on. Add assemblies for scope you're adding. Evaluate whether your project templates still reflect your current service mix.
The builders who get the most from their assembly library are the ones who treat it as a living pricing database rather than a one-time setup task. Your assembly library is, in effect, your intellectual property as an estimating operation. It encodes 5–10 years of real cost data into a system anyone on your team can use correctly.
See Where Your JobTread Setup Has Gaps
The JobTread Pathfinder quiz identifies exactly which features you're underusing — including whether your estimate library and assembly structure are costing you hours on every bid.
Take the JobTread Pathfinder Quiz →Frequently Asked Questions
Assemblies in JobTread are saved groups of estimate items — labor, materials, and subcontractor costs — organized as reusable units of work. When you add an assembly to an estimate, you enter a single quantity driver (like linear feet of wall or square feet of floor) and the assembly calculates every line item automatically based on pre-built quantity formulas. Assemblies eliminate the need to rebuild common scope items from scratch on every estimate.
Go to Settings, then Item Library, then create a New Item and select Assembly as the type. Name the assembly specifically (e.g., "Exterior Wall Framing per LF"), then add component items with unit costs and quantity formulas. Test the assembly against a closed job with known actual costs before using it on live estimates. Update unit costs quarterly or whenever material prices shift significantly.
Most residential builders need 10–15 assemblies to cover 70–80% of their common scope. Start with the assemblies for your highest-volume work — typically framing, drywall, rough plumbing, and tile. Add assemblies for specialty scope as you win that work. More assemblies isn't better; accurate, well-tested assemblies are better. Fifty poorly-tested assemblies are worse than ten tested ones.
Yes. Assemblies stored in your JobTread Item Library are available to anyone on your team with estimating access. This is one of the primary reasons to build an assembly library — it allows you to delegate estimating work without requiring the estimator to carry all the pricing knowledge in their head. Your assembly library becomes the methodology that any team member can apply correctly.
Update assembly unit costs at least quarterly, or immediately when a material price shifts more than 8% from your current assembly pricing. The most reliable approach is to compare assembly unit costs against your most recent supplier invoices whenever you close a job. A 20-minute monthly pass catching any significant drift keeps your estimates accurate without requiring a dedicated review session.
