Specifications in residential construction,
the words the drawings cannot carry.

A specification is the written half of the design. It describes the quality of the building, the materials, products and workmanship, the things the drawings cannot carry. A drawing can show where a wall sits and how large a window is; it cannot say which brick, what paint system, which window frame and glazing, or what standard the tiling is laid to. On a residential job the specification holds all of that, which makes it the document that decides what the finished house is actually like to own.

Together the drawings and the specification form the technical description of the works the contract promises, and the specification is one of the core construction documents on any residential job. This page is part of the construction intelligence cluster because the spec is a working example of that cluster's central problem. The answers a builder needs mid-job usually exist in a document; whether anyone can find the current version of that document, at the moment the question is asked, is a separate matter entirely.

Why the specification matters

The specification is where money and expectation meet. Every line of it is a price, and every silence in it is a price somebody guesses. An item the spec pins down gets priced once, consistently, by everyone who quotes it. An item the spec leaves vague gets priced three different ways by three different subbies, each assuming a different quality, and the gap between those assumptions surfaces later as a variation, a dispute or an absorbed cost. The spec is also where the client's expectations are either managed in writing or left to memory, and memory on a twelve-month build favours nobody.

Upstream, the specification is an estimating input. Every item it names can be priced from current rates; every decision it defers becomes an allowance, a prime cost item or provisional sum standing in for a selection the client has not made. Allowances are legitimate machinery, but each one is a price movement waiting to happen, and quotes that arrive over the allowance are among the most common margin decisions a builder faces (the quotes over allowance guide covers that decision in detail). The fewer unmade decisions the spec carries into contract, the fewer of those conversations the job books in advance.

Downstream, the specification is what the trades are actually buying and building. Every trade package quotes the spec, directly or by assumption, so the spec's precision sets the ceiling on how comparable the quotes can be. And at contract, the specification becomes a contract document in its own right, listed and ranked alongside the drawings in the written building contract. A spec is a description until it is signed; afterwards it is a promise with a price attached.

On a real job the drawings and the specification will sometimes say different things. A finish shown on an elevation that the spec never mentions, a product named in the spec that the drawing details differently, a note on one document that contradicts a schedule on another. This is normal, because the two documents are usually produced by different people at different times and revised at different speeds. What matters is not preventing every conflict but knowing, in advance, how a conflict gets resolved.

The mechanism is the contract's order-of-precedence clause. Building contracts conventionally list the contract documents and rank them, so that when two documents disagree, the higher-ranked one governs. Which document ranks higher differs between contract forms, and some contracts instead require conflicts to be referred for a direction, so there is no general rule worth memorising. The answer lives in your contract, and the time to read that clause is before the job starts, not during the argument. This is general information, not legal advice.

The practical discipline sits alongside the legal one. A conflict noticed at tender is a question that costs an email; the same conflict noticed at frame stage is a variation, a delay or a dispute. Many builders find it worth a deliberate pass over the documents before signing, drawings against spec, schedule by schedule, precisely because whoever notices the gap first gets to decide what it costs.

Most variations on a residential job are traced back to a change; a fair share should be traced back to a sentence. A spec line that reads quality equal to or similar to a named brand, or worse, names only a category, has not made a decision, it has delegated one. The person it delegates to is whoever prices the line, and their incentive is to price the cheapest thing the words permit. The client, meanwhile, read the same words and pictured something better. Both parties are holding the same document and expecting different houses.

The mechanics are predictable. An underspecified item gets priced three different ways by three different subbies, so the quotes cannot be levelled and the cheapest assumption usually wins. The gap between what was priced and what the client expected then surfaces at installation, the worst possible time, and becomes a variation if the builder is disciplined or an absorbed cost if not. In its slowest form it is scope creep by vocabulary, the scope drifting upward one generous interpretation at a time while the price stands still. None of this required anyone to behave badly. The sentence did all the work.

Spec levels and the display home

A related gap opens between spec levels. The display home is built to sell, and it is conventionally dressed with upgrades well beyond the standard inclusions the base price carries. The contract spec describes the base. Both are legitimate, and the gap between them is not the problem; the silence about the gap is. Managed honestly, the selections process walks the client through what the display showed against what the contract includes, prices the difference, and lets the client decide with the numbers in front of them. Left unmanaged, the client discovers the gap item by item during the build, and every discovery reads as something being taken away.

Ask an operator who has run enough jobs for the most expensive sentence in a residential specification and the answer is two words, or equivalent. Experienced builders write the product, the model and the finish into the spec at selection time, and they treat every item the spec leaves unnamed as a pricing risk they are personally carrying, because that is what it is. The client remembers the display home; the contract remembers nothing that was never written into it. Between those two memories sits the builder, and the only instrument that protects both parties is a spec precise enough to settle the question before it is asked.

The same operators hold the spec the way they hold the drawings, as a controlled document with one current version. Selections and approved variations revise the spec, and the site needs the revision, not the original. The near-misses in this area have a common shape, two versions of a document in circulation and the mismatch caught by chance, and the defence is structural rather than heroic. One authoritative current set, superseded versions withdrawn, and a system that makes building from the old version hard to do by accident. The same discipline applied to drawings is covered in the drawing revision control guide, and it applies to the specification without modification.

Where software fits the workflow

Traditionally the spec is a word-processor document, selections are an email thread, and reconciling the two is a Friday job that slips. In VIABUILD, client selections are tracked against the allowances the estimate carried, each confirmed selection records the actual product and price against its allowance, and the job's record of what was chosen moves with the decision instead of waiting to be retyped. The judgement calls, what to allow, what to name, what to walk the client through, remain the builder's; the software's contribution is that the current answer is findable when the site asks.

The specification sits inside a regulated documentary framework in Australia. The points below are labelled by evidence class. Requirements differ by state and territory and change over time, so confirm the current source before relying on any of them.

• Legislation. Domestic building contract legislation in the states and territories commonly requires residential building contracts to be in writing and to include the plans and specifications that describe the work, and regulates how allowances such as prime cost items and provisional sums are disclosed. The specific requirements differ by jurisdiction and this page asserts none of the clause-level detail; confirm the current requirements with your state or territory regulator.
• Government guidance. The National Construction Code (ABCB) sets the minimum technical requirements the specified design must meet. A specification cannot lawfully go below the code, and a spec that names non-compliant products or omits required performance has failed before pricing begins.
• Professional recommendation. Code compliance is a floor, not a quality target, and the specification is the instrument a builder uses to exceed it. A view shared bluntly among performance-focused builders is that the code describes the minimum house you are legally allowed to build, and that a merely compliant home can still be cold, damp and costly to run. Builders who specify above minimum, on insulation, glazing and ventilation performance, are making a deliberate promise the spec is the only place to record.
• Industry best practice. Standard-form residential contracts published by HIA and Master Builders are designed to carry the specification and inclusions schedules as listed contract documents, with precedence machinery maintained against each jurisdiction's legislation. Using a current edition inherits that machinery; using an old template inherits its gaps.
• Common practice. Residential specifications conventionally call up Australian Standards and manufacturer installation requirements for trade workmanship. The reference only does its job if the cited standard and edition are current, so specs reused from job to job need their references checked, not assumed.

Illustrative only, not a benchmark. A contract spec for a custom home carries the line engineered timber-look flooring to living areas, quality equal to or similar to the display. Three flooring subbies quote the package. One prices a budget hybrid plank at $45 per square metre supplied and installed, one a mid-range product at $70, one the wide-board engineered oak actually used in the display at $95. The quotes cannot be levelled because they are not pricing the same floor, and the $45 quote wins the package because on paper it satisfies the words.

The client walks the slab at lock-up, recognises nothing underfoot, and points to the display home. The builder is now choosing between a variation conversation the client believes should not exist, an absorbed upgrade worth thousands, or a dispute about what similar meant. The alternative cost nothing at the time it was available. At selection, the line becomes a named product, brand, range, board width and finish, priced against its allowance with the client's signature next to the number, and all three subbies quote the same floor. The most expensive sentence in the spec was never the price of the oak; it was the sentence that declined to choose.

Specification or spec (the written description of quality, materials, products and workmanship), inclusions (the items the contract price supplies and installs), product schedule (the named products with brand, model and finish), finish level (the specified grade of a surface or fitting), order of precedence (the contract's ranking of documents for resolving conflicts), or equivalent (a substitution clause that needs a defined judge to be safe), PC and PS items (allowances standing in for unmade decisions), as-built spec (the specification as revised by every selection and variation). Definitions for the wider vocabulary live in the construction glossary.

A precise, current spec is only useful if the answer inside it can be found when the site asks; how a builder's documents become answerable rather than merely stored is the subject of the next reference, document intelligence.

• National Construction Code (ABCB) , the minimum technical requirements a residential specification must meet and may exceed.
• Housing Industry Association , publisher of standard-form residential building contracts that carry the specification and inclusions schedules as contract documents.
• Master Builders Australia , publisher (through its state and territory associations) of standard-form residential building contracts.
• Your state or territory's building regulator and fair trading body, for the current rules on what a residential building contract and its specification must contain in your jurisdiction.