How to run a defect register that holds up

1. One register, not six

The single most common failure is fragmentation. The client keeps one list, the contractor another, each trade a third. Arguments become about whose list is right instead of what is actually fixed. Keep one register that everyone works from, so argument becomes evidence.

2. Locate every defect

Each item needs a precise location: level, unit, room, element. If a defect cannot be found again, it cannot be reinspected or closed. Photographs at capture save hours of dispute later.

3. Cost-code against the responsible trade

Every defect should carry an estimated cost and a cost code tied to the trade responsible. This turns the register from a to-do list into a commercial instrument: open exposure becomes a single number you can report, and you know what close-out will cost months before it can hurt you.

4. Track status honestly

Use clear states (open, in progress, awaiting reinspection, closed) and never mark an item closed on a say-so. Reinspection verifies rectification. A register full of items closed without a second look is worse than no register, because it creates false confidence.

5. Report what matters

The register should answer three questions at any time: how fast are we closing out, where is the open exposure by trade, and are we going to make practical completion. Close-out velocity and a readiness trend tell a project director more than a raw count of open items. See the live demo for a worked example on a sample project.

6. Keep the record

Every inspection, photo, price and sign-off should be retained. If the defect liability period ever turns adversarial, a complete, cost-coded register is a defensible file, not a folder of loose ends.

Short on time before PC? The Practical Completion Readiness Checklist is a one-page test you can run today.