Who is responsible for defects after practical completion?
Under most building contracts the builder stays responsible for rectifying defects in their work that are notified during the defects liability period, usually twelve months from practical completion, and the owner’s side is responsible for noticing them, notifying them in time and giving access. Once the period ends, anything still wrong is a warranty or statutory matter rather than a contract item, and the record of what was notified and when decides which it is. In IssuesId the handover record keeps running after completion: residents report on a QR card, each item is typed Warranty or Maintenance, the builder is still the party it is issued to, closing stays with the owner’s side, and the post-completion list comes out as a report.
Responsibility moves. The record should not.
Practical completion changes who is in the building, not who built it. The builder demobilises and the owners move in, and for the next year defects arrive one at a time into a process that, at most builders, has nobody on it. The owner emails the office; the office forwards it; somebody writes “I think that was Dave” from a car park. The question of who is responsible is usually clear enough in the contract. The thing that is actually missing is a record that survives the change of occupants: what was reported, by whom, on what date, what the builder said, and whether it was fixed. That record is what the retention conversation at month twelve is about.
Three parties and a contract
The same register, with the owners in it
The builder’s handover record and the building’s post-completion register are the same product. Handover is a change of role, not a change of system: the committee or the facilities manager takes the client seat, residents get cards, and the builder’s trades keep receiving work the way they did during the build.
- 1Residents report on a card, not a phone callAt handover each resident gets a printed QR card. Scanning it logs them into their own portal with no password. They raise the item with a photo and it lands in the register already filed against their lot. A stranger scanning a lobby code gets a short form and a pending request; nothing is live until a manager approves it.
- 2Every item is typed before anyone argues about itThe record carries a Type: Defect, Warranty, Maintenance, Incomplete Works and so on. A dripping mixer filed as Warranty is a different conversation from a blocked drain filed as Maintenance, and the register separates them from the first minute rather than in a dispute six months on.
- 3The builder stays the party it is issued toThe item is issued to the builder or their trade, who gets an email with a link that opens the job without a login, attaches a photo of the fix, and can dispute it on the record if they think it is wear and not workmanship. The dispute and the ruling both stay on the file.
- 4Closing stays with the owner’s sideThe trade cannot close anything. A building manager or manager verifies the fix and closes it, with their name and time on the transition. The resident watches the status move in their portal, with cost and contractor identity stripped out.
- 5The post-completion list is a report, not a reconstructionThe report catalogue includes a Post PC Issues report, items raised after practical completion grouped by category, and a Purchaser Report, one page per defect with photos written for the owner. Filter to the DLP window, read the count, and the month-eleven inspection pack is already written.
Asked alongside this one
Where this answer comes from
The docs behind this answer are defects (Type, the reporter directory, disputes), trades, tenants and clients (the QR card and the pending request), roles and dashboards (who can close) and reports. For running the whole period as a job, read tracking DLP defects after the trades have gone; for the owners corporation’s side, strata and owners corporations; for the resident’s, how do tenants report maintenance without calling the office?