A defects or punch-list register should help a team move from an observation to a verified outcome. It should not force every observation into an immediate technical judgement. A clear record separates what was seen, what action was agreed, who is responsible and who has authority to confirm closure.
Give each observation a durable identity
Assign a unique item number and retain it through updates. Include the work package, precise location, asset or drawing reference, observation date, description and relevant photograph reference. Write descriptions that another person can locate and understand without attending the original walk-through.
For instance, “Label unreadable at panel DB-02, north service room” is more actionable than “labelling issue”. If the observation is disputed or requires interpretation, record that status and route it to the responsible reviewer rather than rewriting it as an agreed defect.
Separate action from verification
Useful fields include the action owner, agreed action, target date, completion evidence, verification owner, verification date and closure status. A contractor’s message saying an item is complete is evidence of a response; it is not automatically the client’s acceptance.
A short status vocabulary can distinguish:
- Open: action or clarification required.
- Ready for review: completion evidence supplied.
- Returned: reviewer requests further action.
- Closed: designated reviewer confirms the outcome.
- Withdrawn or duplicate: reason recorded and cross-reference retained.
Use labels that fit the project’s agreed procedure and define who may change them.
Keep the evidence trail intact
Attach the original observation photo and link later photographs separately. Preserve dates and source filenames. If work is concealed or access changes, record that fact so the verifier understands the limits of a later photograph. Do not treat a cropped image as proof of matters outside its visible frame.
When an item is split into several actions, retain the parent item number and link the children. When two lists overlap, cross-reference them instead of silently deleting one history.
Review exceptions, not every row
A useful weekly meeting focuses on overdue actions, repeated returns, missing evidence and decisions needed from others. Record one next action and owner for each blocker. Contractual obligations, technical classifications and acceptance authority depend on the actual project; the register is a coordination tool supporting those decisions, not the decision-maker itself.



