What is a pre-completion inspection, and who attends it?
A pre-completion inspection is the walk through a finished unit or building in the last weeks before practical completion, room by room against a checklist, to find everything that is not finished or not to standard so it can be fixed before the client walks the same rooms. The builder’s own team walks first, the client’s representative second, and the certifier last; on residential jobs the purchaser often gets a walk of their own. In IssuesId the checklist is a reusable template with hold points, every Fail raises a defect linked to the question, and the client’s walk prints from the register as a Door Sheet.
The last walk before someone else’s walk
Every pre-completion inspection is really a rehearsal for the next one. The site team walks so the client’s rep finds less; the client’s rep walks so the certifier finds less; the certifier walks so the owner, in month three, finds less. The list gets shorter at each stage only if what the earlier walk found was actually raised, issued and fixed, which is where the paper version fails: thirty-one crosses on a PDF that somebody has to type into a register that night. The inspection is the easy part. The job is making every Fail a defect with a photo, a trade and a date before the next person opens the door.
Four walks, in order
One checklist, every unit, no typing up
- 1Build the checklist once, run it per unitThe checks live in a checklist template at organisation level: one observable thing per question, phrased so Yes passes. Allocate it across every unit on a level from the Locations page in one step, so forty units get the same fifty-five checks and the same reference numbers.
- 2Mark the hold pointsThe waterproofing certificate, falls to waste, the balustrade and the smoke alarm are hold points. A checklist with a hold point still open shows a marker on its row, and the organisation-wide checklists list flags every open hold point across every job until it is released.
- 3Let the Fail raise the defectA No on a question raises a defect linked to that question, with the photo, at the moment it is answered. There is nothing to type up that night. When the defect is verified and closed, the question flips back to Yes on its own, so the inspection and the register never disagree.
- 4Send the trade’s stretch to the tradeWhere a subcontractor answers their own section, a share link scoped to the questions between hold points goes to them with a due date; their No raises a defect exactly as an inspector’s would.
- 5Walk the client’s rep with the Door SheetThe Door Sheet prints one page per room from the register, so the second walk is ticking rooms against what the first walk found. The Purchaser Report does the same for the buyer, one page per defect with photos.
Asked alongside this one
Where this answer comes from
The docs behind this answer are inspections (templates, allocation, hold points, share links) and reports (Door Sheet, Purchaser Report). The fifty-five checks are the pre-completion inspection checklist, free in Excel and CSV. What practical completion itself means, and what it triggers, is in the glossary under practical completion; the register the certifier’s walk is granted against is the register you hand over.