Knowledge · Business and operations
Defects management,
running the tail of the job.
Practical completion ends the build; it does not end the job. What follows is a workflow: a register of items, a triage discipline, trades to bring back, costs to attribute, a period to close out formally, and claims that can arrive years later. Builders who run that workflow spend weeks on the tail of a job. Builders who improvise it spend seasons. This is the reference for the workflow itself.
01 / Overview
What defects management is
Defects management is the operational workflow that runs from the handover walk-through to the last warranty claim: receiving reported items, deciding what each one actually is, getting the right people back to fix the genuine ones, attributing the cost to whoever caused it, closing the period out formally, and answering the claims that arrive long after. It is a workflow in exactly the sense that claiming or procurement are workflows, with a register, a cadence and an evidence trail, and it rewards being run like one.
This node deliberately does not own the boundary events around it. The practical completion milestone, the handover day and the three clocks that start at it (the contractual defects period, the statutory warranties and the insurance periods) are the territory of the practical completion and defects liability reference. The warranties themselves, what they promise and how long they run per state, live in statutory warranties. And preventing defects during the build, hold points and inspections while rectification is cheap, is the quality assurance discipline. What none of those pages carries, and this one does, is the running of the rectification machine itself.
Why it matters
Three things ride on the defects workflow. Cash: the final payment, and the subcontract retention releases covered in retention and payment terms, all key off how cleanly the period runs and ends. Reputation: for the client, the defects period is the product; the house was expected to be good, and how the builder handles the eleven items that were not is the story that gets retold. And margin: the defects tail is real cost, borne by the builder wherever attribution fails, and it is the difference between a job's reported profit and its true one.
02 / Process workflow
The defects workflow, end to end
Eight steps from handover to the long tail. The register in step one is the load-bearing element; every later step either reads from it or writes to it.
- 01
Open one register at handover
The agreed handover list starts the register: every item dated, described, photographed and acknowledged. From this moment there is exactly one list, and every later item joins it. Two lists (the builder’s and the client’s) is the failure state, and it is where most defects periods go bad.
- 02
Triage every incoming item
Each new report gets classified before it gets promised: a genuine defect (work not conforming to the contract, plans or workmanship standards), a maintenance item (the client’s to do), fair wear and tear, damage caused after handover, or a wishlist change. The classification is communicated with reasons, in writing, item by item.
- 03
Attribute each defect to its cause
Behind most defects is a subcontractor’s work, a supplier’s product or the builder’s own coordination. Attribution decides who returns to fix it and who ultimately wears the cost, so it is recorded on the item at triage, while the trade records and site diary can still settle the question cheaply.
- 04
Batch the call-backs
Rectification visits are scheduled in batches per trade, not one trip per phone call. The painter comes once for nine items, not nine times for one. Batching is what keeps the defects period from consuming supervision time the business already spent, and clients accept scheduled visits far better than silence.
- 05
Rectify, evidence, close each item
Each item gets fixed, photographed after, and closed on the register with a date. The evidence matters twice: it answers the client who remembers the item as unresolved, and it answers a tribunal years later if the same defect is alleged again. An item fixed without a record was, for practical purposes, never fixed.
- 06
Run the end-of-period inspection
Before the defects liability period expires, a final inspection with the client walks the register to zero. Open items are resolved or formally scheduled, the closing state is documented and acknowledged, and the subcontract retention releases that key off the period’s end can proceed on a clean record.
- 07
Handle the long tail deliberately
Claims arriving after the defects period fall under the statutory warranties, which run for years and cannot be contracted away. Each one gets the same triage and the same register treatment, plus a judgement call: inspect early, assess honestly, and take advice where the claim is large or the classification is contested.
- 08
Feed the pattern back into method
The register is a dataset. The same defect appearing on three jobs is not three bad luck events, it is a method, detail or trade problem, and the fix belongs in the quality system and the next job’s checklists, which is the loop covered in the quality assurance reference.
03 / Cost attribution
Who pays for the fix
Every defect costs somebody money, and the builder’s job is to make sure it is the right somebody. Four cases cover the territory.
The subcontractor’s defect
Where the defect sits in a trade’s work, the subcontract’s defects obligations bring the trade back at its own cost, and the retention held under the subcontract is the lever if it will not come. A builder who has released retention early, or never held it, is negotiating with goodwill instead.
The back-charge that sticks
When the trade will not return and someone else fixes its work, the cost comes back to the trade as a back-charge. Back-charges stick when the defect was documented, the trade was notified and given the chance to rectify, and the cost is evidenced. Back-charges imposed by surprise, without notice, poison the relationship and frequently fail.
The builder’s own cost
Coordination defects, damage between trades, and items nobody can fairly pin on one contractor land on the builder. These belong in the job’s costs, attributed to the job that generated them, not absorbed invisibly in overhead, because the true profit on a job is not known until its defects tail is costed.
The warranty-period claim
Rectification under statutory warranties, years after handover, is real money spent on a job that closed long ago. Costing it back to the original job keeps the business honest about which jobs, clients, designs and trades actually made money, and which are still quietly paying out.
The uncomfortable operator's truth in this section: attribution is a use-it-or-lose-it discipline. The evidence that settles who caused a defect, the site diary, the inspection photos, the trade's scope in the package, exists in abundance in the week the work was done and decays from there. A builder who attributes at triage recovers call-backs and back-charges as routine; a builder who attributes at year's end donates the defects tail to overhead and calls it bad luck.
04 / Common mistakes
Where the defects period actually goes wrong
Rarely on the tools. The failures are administrative: lists that fork, items that drift, retention released early, and evidence never taken.
Two lists
The builder tracks defects in a spreadsheet, the client tracks them in emails and memory, and the two never reconcile. Every conversation becomes an argument about what the list is instead of progress against it. One register, shared and acknowledged, is the whole game.
Accepting every item as a defect
Agreeing to fix maintenance items, wear, and post-handover damage to keep the peace teaches the client that everything is claimable, and the list grows to meet the generosity. Classify honestly with reasons instead; clients respect a documented no far better than a resented yes.
The call-back that never gets scheduled
Items acknowledged but never booked drift for months, the client’s goodwill drains, and the final payment or retention conversation sours. An item on the register either has a scheduled visit or a documented reason it does not. Drift is a choice.
Releasing subbie retention before close-out
The retention held under a subcontract exists substantially for this period, and releasing it before the defects inspection clears the trade’s work removes the only commercial lever for the call-back. Release against the record, not against the invoice date.
No after-evidence
Work rectified without a photo and a closure date is undefended: against the client who remembers it as open, and against the warranty claim years later that alleges it was never fixed. The thirty seconds of evidence at closure is the cheapest insurance in the whole workflow.
Treating warranty claims as ambushes
Claims after the defects period are a statutory reality, not an outrage. Builders who triage them like any other item, inspect early and answer with the job’s records resolve most of them cheaply. Builders who go silent or defensive convert small claims into tribunal matters.
05 / Best practice
How experienced builders run the tail
The operator's observation is that the defects period is won by response time, not rectification time. Clients do not actually expect a cracked tile to be fixed tomorrow; they expect to be answered tomorrow. The builders whose defects periods stay calm acknowledge every item within days, classify it with reasons, and give it a scheduled visit, even one weeks away. The builders whose defects periods turn into withheld payments and tribunal letters are rarely the ones with the most defects; they are the ones who went quiet. Silence is read as refusal, and refusal recruits helpers, the relative with opinions, the building inspector hired for a second walk, the regulator's complaint line.
The second habit is treating the register as a permanent record rather than a temporary to-do list. The job's warranty exposure runs for years past the last call-back, and the register, with its dates, photos, classifications and closures, is the file that answers a claim in year four. It is also the dataset the business learns from: recurring defects by trade and by detail feed the quality assurance loop, and a trade's call-back record feeds the next engagement decision.
Where software fits the workflow
Traditionally the register is a spreadsheet that lives on one laptop, photos are in three camera rolls, and the close-out evidence is nowhere. In VIABUILD the site record runs through ViaSite, so defect items carry their dates, photos, status and closure evidence in one place, per job, for as long as the exposure lasts. The builder still makes every judgement, what is a defect, who caused it, what gets back-charged; what changes is that the judgement is made once and recorded, instead of re-argued from memory each time the item resurfaces.
06 / FAQ
Common questions.
A defect is work that does not conform to the contract, the plans and specifications, or the standard of workmanship the law and the contract require: the leaking shower, the door that never closed, the cracked render outside tolerance. A maintenance item is the ordinary upkeep the home needs regardless of build quality: caulking that shrinks over years, filters, adjustments that follow normal settlement within tolerance. The boundary is defined by the contract, the specifications and the applicable standards and tolerances rather than by either party’s feelings, and classifying honestly, in writing, with reasons, is the core triage discipline of the whole defects period. Contested classifications on significant items are worth professional advice rather than a standoff.
The client does not, for a genuine defect, and behind the builder the answer follows attribution. Where the defect sits in a subcontractor’s work, the subcontract’s defects obligations generally require the trade to return and rectify at its own cost, with the retention held under the subcontract as the commercial lever, and a documented back-charge as the fallback if someone else has to fix its work. Defects of coordination, damage between trades, and unattributable items land on the builder. The discipline that makes any of this workable is recording attribution at triage, while the site diary and trade records can still settle who caused what; attribution attempted a year later is guesswork with invoices attached.
The contractual rectification window has closed, but the builder’s obligations have not. Statutory warranties implied by each state and territory’s domestic building legislation run for years from completion, cannot be contracted out of, and are the basis on which later defect claims arrive, with several jurisdictions distinguishing longer periods for structural matters. The operational answer is to treat the claim like any register item: triage it, inspect early, assess honestly against the warranty obligations, and answer with the job’s records. The legal detail, the periods, definitions and processes, differs by state and lives in the statutory warranties reference; a large or contested claim is a matter for advice. What decides how these go, more than anything, is whether the original register and rectification evidence still exist.
With the register and the triage discipline rather than with resistance. Every reported item goes onto the one register and gets classified with reasons: genuine defects get scheduled, maintenance items and post-handover damage get explained in writing, and wishlist changes get quoted as variations if the client wants them done. What escalates these relationships is not the number of items; it is silence, drift and inconsistency. A client who sees items acknowledged within days, classified with reasons, and rectified in scheduled batches almost always settles into the process. A client who hears nothing compiles a bigger list with help. The handover itself sets most of this trajectory, which is why the practical completion reference treats the slow walk-through as the cheapest insurance on the job.
Yes, and most builders do not, which is why their job profitability is overstated in exactly the way that repeats. Rectification during the defects period, back-charges recovered and not recovered, and warranty-period work years later are all real costs generated by the job, and costing them back to it tells the business what each job, client, design and trade actually returned. The pattern is the second payoff: cost attributed by trade and by defect type turns the register into evidence of which subcontractors and which details keep paying out, which is what the quality feedback loop and the next procurement decision should run on. A defects tail nobody costs is a lesson nobody learns.
07 / Terms
Glossary for this topic
Defects register (the single dated, evidenced list of reported items and their status), triage (classifying each reported item as defect, maintenance, wear, damage or change), call-back (a subcontractor returning to rectify its own work), back-charge (recovering the cost of fixing a trade's work from that trade), close-out (the end-of-period inspection and the documented zeroing of the register), defects liability period (the contractual rectification window after practical completion), statutory warranties (the legislated obligations that continue for years after it), maintenance item (upkeep that is the owner's responsibility). The wider vocabulary lives in the construction glossary.
The natural next reads are the practical completion reference for the milestone this workflow hangs off, and statutory warranties for the legal tail it feeds into.
08 / Keep reading
Related knowledge, guides and features
09 / Further reading
Primary sources
- The signed contract on each job, for the defects liability period, its notice mechanisms and the rectification obligations that actually apply.
- Your state or territory's domestic building legislation and building regulator guidance, for the statutory warranties and any published standards and tolerances guides used to classify defects in your jurisdiction.
- The subcontract terms for each trade, for the defects obligations, retention and back-charge mechanics available down the chain.
One register, run to zero.
VIABUILD keeps the defects register with its photos, dates and closures in one place for the life of the exposure, so the tail of the job runs on a record instead of a memory.