Construction documents
on a residential job.

Construction documents are the full set of records that describe, authorise, price and evidence a building job. On a residential build that means the drawings and specification that say what to build, the engineering and certification that prove it is compliant, the contract that sets the commercial rules, the approvals that permit the work, and the running trail of quotes, orders, invoices, variations, diaries, photos and correspondence generated as the job proceeds. Together they are the job written down.

Defined precisely, a construction document is any record of a decision, an obligation or a fact about the job, and its value depends entirely on being current and findable when someone needs it. That framing is the whole point of this node. It sits inside the wider construction intelligence reference, which is about turning a business’s information into understanding; documents are the raw material that understanding is built from, and a document nobody can find in time is information the business does not really have.

Why it matters

Documents decide money and risk long after they are filed. A superseded drawing that reaches the field becomes built work that has to be pulled apart. A variation with no paper behind it becomes a discount at the end of the job. A condition of consent that nobody tracked becomes a hold at occupation. And in any dispute, warranty claim or insurance question, the builder with the organised, dated, complete record is usually in a winning position before the argument even starts, while the builder reconstructing the history from memory and scattered inboxes is already losing. The document set is not filing; it is the job’s memory, and memory is an asset or a liability depending on how it was kept.

The most useful way to think about a construction document is not as a file but as evidence. A quote is evidence of a price offered and its scope. An invoice is evidence of a supply and an amount owed. An email is evidence of an instruction or an approval. A site photo is evidence of a condition on a date. An inspection result is evidence that a stage was genuinely complete rather than merely reported complete. Seen this way, the question about any document stops being where do I put it and becomes what does this prove, and can I produce it when it matters.

That shift changes how a document is filed. Evidence is only useful attached to the thing it supports, so the quote belongs with the order it justified, the docket with the delivery it confirms, the approval email with the variation it authorised. A document filed as a loose PDF, disconnected from the decision it evidences, keeps the fact but loses the meaning. The record that a builder can actually use is the one where every important number, commitment and decision can be traced back to the document that stands behind it, a principle that becomes far more powerful once software can read the documents rather than merely store them, which is the subject of document intelligence.

The single most valuable discipline in the whole document set is making sure everyone works from one current version of anything that revises. On a residential job that is not only the drawings; the specification revises as selections are made, the contract revises as variations are signed, the selections list revises as the client decides. Each of those has a live version and a history of superseded ones, and the job’s health depends on the live version being obvious and the superseded ones being hard to use by accident.

The classic failure is quiet. A revised sheet arrives and stays in one person’s inbox because there was no enforced path from received to live. The office holds the current information; the field holds the old set; and the gap is only discovered when built work has to be corrected. It is worth being precise about the diagnosis, because it is almost always a process gap rather than a tool failure. The revision existed and someone had it; what was missing was the defined route from a revision arriving to it reaching every person who acts on it, with the old version visibly withdrawn. That route is the whole subject of the drawing revision control guide, and the cost it prevents lands directly on quantities measured in takeoff and on every trade priced from the set.

Where software fits the workflow

Traditionally the document set lives across a shared drive, several inboxes and the supervisor’s ute, and keeping the field on the current version depends on someone remembering to send it. In VIABUILD the current set lives in one place and the field app ViaSite puts it in the supervisor’s and the trades’ hands, so the version people build from is the version the office published, not whichever printout happened to survive. The office decides what is current; the system makes sure that is what reaches the site, and the superseded set stops being something anyone can pick up by mistake.

No single rule governs how a builder keeps its documents, but several Australian obligations reach into the set and give it a minimum life. The points below are labelled by evidence class; requirements differ by state and change over time, so confirm the current source before relying on any of them.

• Legislation. Each state and territory regulates residential building work, and the approvals, certificates and mandatory inspection records a job produces are documents the builder is obliged to hold and, at points, to produce. The specific requirements differ by jurisdiction and should be confirmed with your state building regulator.
• Government guidance. Tax records, including the invoices and records behind GST credits and income, carry their own retention obligations set by the ATO. Treat these as a confirm-with-your-accountant question, since the period and the records covered are specific and can change.
• Common practice. Statutory warranty and defects periods run for years from completion, and a document set is the evidence a builder relies on if work is questioned within that window. The practical convention is to retain the complete set for a finished home well beyond handover, because the obligations it might have to answer outlast the job by years. How those completion and warranty clocks work is covered under practical completion and the defects liability period.
• Common practice. The contemporaneous site record, diaries, photos and dated correspondence, is the evidence that decides delay and variation questions. A record written on the day carries weight that a reconstruction produced months later does not, which is why it matters for extensions of time and delay.

Illustrative only. A structural engineer issues a revised beam detail three weeks before the frame goes up. The revision lands in the contract administrator’s inbox, is glanced at, and is never published to the platform the supervisor and carpenter work from. There was no protocol that said a new revision must be logged, made live and pushed to the field, so it simply stayed where it arrived. The frame is built to the superseded detail, and the mismatch surfaces at the frame inspection, when correcting it means propping, partial demolition and a fortnight of programme.

Nothing here was a technology failure. The drawing existed, the right person received it, and everyone acted in good faith. What was missing was the enforced path from a revision arriving to that revision being the only set anyone could build from, with the old detail withdrawn the moment the new one went live. A document set is not a pile of files to be stored; it is a flow to be controlled, and the difference between the two is measured in reworked frames. The written-quality version of the same lesson, where a vague specification quietly produces the same kind of surprise, is covered next in specifications.

Revision (a superseding version of a document, dated and numbered), superseded set (a version withdrawn from use once a newer one is live), single source of truth (one authoritative current version everyone works from), order of precedence (the contract clause that ranks documents when two conflict), contemporaneous record (a document made at the time of the event it records), retention period (how long a record must be kept). Definitions for the wider vocabulary live in the construction glossary. From here, the natural next article is specifications, the written half of the document set that decides most of what the drawings leave unsaid.

• Your state or territory building regulator, for the approval, certification and record-keeping obligations that apply to residential work in your jurisdiction.
• Australian Taxation Office, for the retention obligations that apply to the tax records inside your document set.
• National Construction Code (ABCB), the technical requirements the drawings and engineering documents must satisfy.