Knowledge · Estimating

Assemblies and construction recipes,
the builder's method written down.

An assembly is a reusable build-up of materials, labour and plant per unit of finished work, a lineal metre of wall, a square metre of roof. Built once from first principles and refined after every job, it is how small builders price with first-principles accuracy at unit-rate speed.

01 / Overview

What an assembly is

An assembly, also called a construction recipe or a cost build-up, is a reusable combination of materials, labour and plant expressed per unit of finished work. One lineal metre of a particular external wall. One square metre of a particular roof system. The build-up lists everything that unit consumes (framing, insulation, cladding, fixings, the carpenter's hours, the waste on each material), so that when a takeoff says the job has 42 metres of that wall, the estimate prices all 42 metres in one step.

Defined against the other methods in the estimating reference, an assembly is first-principles detail captured once and reused. A first-principles estimate builds every item up from scratch each time, which is accurate and slow. A unit-rate estimate applies composite rates quickly, but the detail behind each rate is invisible. An assembly holds the first-principles detail permanently, so it prices at unit-rate speed while every component underneath stays visible and correctable.

Why it matters

An assembly is where a builder's construction method gets encoded. Two builders pricing the same wall will build it slightly differently (different framing habits, different waste, different crews), and a recipe captures how this business builds it, not how a cost guide assumes it is built. That makes the estimate a prediction of your job rather than an average of the industry's. It also makes accuracy a property of the system rather than of one person, which is the central argument of the construction estimating guide. When the estimator who wrote the recipe is on leave, the recipe still prices the wall the same way.

02 / The workflow

Where assemblies sit between takeoff and the cost database

An assembly is the middle layer of the estimating stack, and it only works because of what sits either side of it. Below it, the cost database supplies the current price of every component; the recipe holds quantities and method, never its own prices, so when the database moves, every estimate that uses the recipe moves with it. Above it, takeoff supplies the measured quantities that drive it; the recipe converts metres and square metres into cost, so a wrong quantity multiplies through everything the recipe got right.

Around it sit the costs assemblies deliberately do not carry. Job-wide running costs (supervision, site establishment, general scaffold) belong in preliminaries, priced once for the job rather than smeared per unit. The practical test is simple. If the cost scales with units of finished work, it can live in the recipe; if it scales with the job or with time, it belongs in preliminaries, and it must live in exactly one of the two.

03 / Process workflow

How an assembly is built and refined

Seven steps, from choosing the unit of work to correcting the recipe from finished jobs. The last two steps are where the compounding happens.

  1. 01

    Pick the repeated unit of work

    Choose work the business builds the same way job after job, expressed per unit of finished product. A lineal metre of external wall, a square metre of roof, a standard wet-area floor.

  2. 02

    Break it down from first principles

    List everything the unit actually consumes. Materials with waste allowed, labour hours at real productivity, plant and equipment, consumables and fixings. This is done once, carefully, not per estimate.

  3. 03

    Price the components from the cost database

    Each component draws its current rate from the maintained cost database rather than carrying its own number. The recipe holds quantities and method; the database holds prices.

  4. 04

    Record the assumptions

    Write down the specification the recipe assumes. Frame sizes, insulation level, cladding type, fixing centres, access conditions. An assembly without written assumptions is a number nobody can safely reuse.

  5. 05

    Apply it across estimates

    Takeoff produces the quantity (metres of wall, square metres of roof) and the assembly converts quantity to cost in one step. First-principles detail, unit-rate speed.

  6. 06

    Reconcile against actuals at close-out

    When the job finishes, compare what the assembly allowed against what the work actually consumed, by cost code, and find out where the recipe was optimistic.

  7. 07

    Refine and version the recipe

    Correct the quantities, waste and labour constants from the evidence, note what changed and why, and let the next estimate start from a recipe that has already learned from the last job.

04 / Key mechanics

What a recipe carries

Six things a complete assembly holds. The first four are the cost build-up; the last two are what makes it safely reusable by someone other than its author.

Materials, with waste

Every material the unit consumes, in purchase units, with a realistic waste allowance per material rather than one blanket percentage. Offcuts on framing behave differently from breakage on tiles.

Labour, as productivity

Hours of each trade per unit of finished work, based on how your crews actually perform, not a textbook constant. This is usually the largest and least examined number in the recipe.

Plant and equipment

Scaffold, cranage, compaction gear, mixers, anything the unit of work needs that is neither material nor labour. Small per-unit amounts here prevent a large surprise in preliminaries later.

Consumables and fixings

Nails, screws, adhesives, sealants, blades. Individually trivial, collectively real money across a whole house, and the classic category a hand-priced estimate silently omits.

The specification assumed

The spec level the build-up was written for. Change the insulation requirement, the cladding, the fixing detail or the site access and the recipe no longer describes the work.

Notes and provenance

Which jobs the recipe was corrected from and when it was last reviewed. A recipe with a history can be trusted; a recipe with no history is one estimator’s memory in disguise.

05 / Best practice

How experienced builders run their recipes

The operators who estimate well treat an assembly as the place where hard-won method gets written down once instead of re-derived per estimate. Every builder already knows how they build a wall; most re-price that knowledge from memory every time they tender, and the knowledge walks out the door with whoever holds it. Writing the build-up down turns a person's method into the business's method, which is the same principle as keeping construction knowledge anywhere else in the business. The recipe is estimating's version of it.

The refinement loop is where the payoff compounds. A builder pricing their first duplex builds the wall and roof recipes carefully and still gets some allowances wrong, because first times are like that. At close-out, the actuals show the framing waste was optimistic and the wet-area labour was light, and the recipes are corrected. The second duplex then prices faster and lands closer, not because anyone got smarter, but because the recipes did. In practice this loop, run job after job, is what the hard work behind accurate estimating actually looks like.

The judgement experienced operators apply is knowing when a recipe does not fit. The danger case is quiet, a recipe whose spec assumptions differ from the current job in ways nobody re-checked. The wall recipe assumed last year's insulation standard and this job specifies higher; the quantity is right, the method is right, and the price is wrong on every metre, with no single line that looks wrong. Good estimators read the recipe's written assumptions against the current specification before trusting it, and price genuinely one-off work from first principles rather than stretching the nearest recipe over it.

Where software fits the workflow

Traditionally, recipes live in a spreadsheet, and keeping their components connected to current rates is manual work that quietly stops happening. In VIABUILD the layers stay connected as one workflow. Oryn™-assisted takeoff measures quantities from uploaded plans, those quantities drive your assemblies, the assemblies price from your maintained database, and the estimator reviews and approves every number rather than re-keying it. The recipes remain yours, encoding your method; the system keeps them priced from current rates and applied consistently.

06 / Australian considerations

Standards, codes and cost data behind Australian recipes

Assemblies themselves are a working method, not a regulated artefact, but the things a recipe assumes are shaped by standards and codes that change over time. The points below are labelled by evidence class; confirm the current source before relying on any of them.

  • Industry standard. The Australian and New Zealand Standard Method of Measurement of Building Works (ANZSMM, published by AIQS with Master Builders Australia) is the recognised basis for measuring building work. Recipes priced per unit only stay comparable across jobs, and against subbie quotes, when the quantities driving them are measured consistently with a recognised method.
  • Government guidance. The National Construction Code (ABCB) sets the technical floor a compliant build-up must meet, and NCC updates can change what a compliant wall or roof assembly physically contains, insulation, sarking and sealing details among them. A recipe written under an earlier edition can describe a non-compliant build-up under the current one, so code changes should trigger a recipe review. Confirm requirements against the current NCC edition and your state's variations.
  • Common practice. Published cost data (Rawlinsons' construction cost guides, Cordell) offers reference build-ups and rates that are useful for seeding a first recipe or sanity-checking your own. Treat them as a reference class, not your numbers; a published assembly describes an average method, and your margin lives in the difference between the average and how your crews actually build.
  • Common practice. Requirements and standard inclusions differ between states and territories (energy efficiency provisions, bushfire and wind classifications, termite management), so a recipe that prices correctly in one jurisdiction may not describe compliant work in another. Builders working across borders commonly hold jurisdiction-specific variants of the affected recipes.

07 / Common mistakes

Where recipes actually go wrong

Each of these is mechanical and preventable, and most of them fail silently, which is exactly why they cost money.

Reusing a recipe across spec levels

The recipe was built for last year’s standard inclusion and the current job specifies higher. The quantity is right, the method is right, and the price is quietly wrong on every metre.

Never reconciling against actuals

An assembly that is never compared with what jobs actually consumed stops being evidence and becomes folklore. The feedback loop at close-out is what keeps a recipe honest.

Forcing custom work into a recipe

One-off structural work, unusual junctions and heritage details do not repeat, so a recipe has nothing to learn from. Price those items from first principles inside the estimate instead.

Recipes with unwritten assumptions

If the spec, access and inclusions the build-up assumes live only in the author’s head, every reuse by anyone else is a guess. The assumptions are part of the assembly.

Rates baked into the recipe

A recipe that carries its own prices goes stale the moment the market moves. Quantities and method belong in the assembly; prices belong in the cost database it draws from.

Double-counting with preliminaries

Scaffold, supervision or cranage priced inside an assembly and again in preliminaries pads the estimate twice. Decide once where each running cost lives and hold the line.

08 / Practical example

A worked recipe, one lineal metre of external wall

Illustrative only, not a benchmark; every figure below is invented to show the mechanics. A duplex builder holds a recipe for one lineal metre of their standard external wall. It lists the framing timber with 10% waste, wall wrap, insulation batts, cladding with 7.5% waste, fixings and sealants, and 1.4 carpenter hours at the current database rate. The components price from the database at, say, $185 of materials and $130 of labour, so the recipe returns $315 per metre. The takeoff for the next duplex measures 96 metres of that wall, and the estimate carries $30,240 for it in one step, with every assumption underneath still visible.

At close-out on the first duplex, the actuals showed cladding waste ran nearer 12% on the ground floor because of window penetrations, and the carpenter hours were closer to 1.55 per metre. The builder corrects the recipe and notes why. The second duplex prices in minutes instead of days and lands closer to actual, because the recipe now carries what the first job learned. The same builder wins a job specifying a premium cladding and a higher insulation requirement, and rather than reusing the recipe as-is, copies it to a new variant and reprices the changed components, because the written assumptions made the mismatch visible before it became a margin problem.

09 / FAQ

Common questions.

A unit rate is a single composite price per unit of work, often adopted from a cost guide or from history, with the build-up invisible. An assembly is the build-up itself, the materials, labour and plant behind the rate, held as live components that reprice from the cost database. When a material price moves, a unit rate has to be re-judged; an assembly recalculates. When a job goes wrong, a unit rate offers nothing to interrogate; an assembly shows which component was optimistic.

Fewer than most builders expect. The useful move is to start with the work that appears on every job and carries the most money, external walls, roof, wet areas, floor systems, and let coverage grow as jobs finish. A small library of well-maintained recipes beats a large library of unverified ones, because the value is in the refinement loop, not the count.

Job-wide running costs (site supervision, temporary services, general scaffold, site sheds) are usually kept out of assemblies and priced in preliminaries, because they scale with the job rather than with units of finished work. Work-specific plant that genuinely varies with the unit can live in the recipe. Whichever convention a business picks, the discipline is to pick it once and apply it everywhere, so nothing is priced twice and nothing falls between.

Two triggers matter more than any calendar. Every finished job that used the recipe should feed a comparison of allowed against actual, and any change in the specification environment (a code change, a new standard inclusion, a different cladding supplier) should force a review of the assumptions. Many builders also give each recipe a last-reviewed date so a stale one is visible before it prices a tender.

Both, at different coverage. A project-home or duplex builder can cover most of a job with recipes because the product repeats. A custom builder repeats less of the whole house but still repeats the parts, wall systems, wet areas, footings on comparable sites, and can run recipes for those while pricing the genuinely one-off work from first principles. The blend is normal; the mistake is stretching a recipe over work it has never seen.

10 / Terms

Glossary for this topic

Assembly or recipe (a reusable cost build-up per unit of finished work), first principles (building a price up from labour constants, material quantities and plant), unit rate (a composite price per unit of work), labour constant (hours of a trade per unit of finished work), waste allowance (the margin between material purchased and material in the finished work), cost database (your maintained rates), takeoff (measuring quantities from drawings), preliminaries (the cost of running the job). Definitions for the wider vocabulary live in the construction glossary.

One class of estimate line deliberately sits outside every recipe, the allowances for selections not yet made and work not yet definable, covered next in prime cost items and provisional sums.

12 / Further reading

Primary sources

Write the method down once, and let it keep pricing.

VIABUILD runs takeoff, assemblies and your cost database as one connected workflow, so every estimate prices from your method and every finished job makes the recipes better.