1. What a category is actually for
A punch item is a recorded deficiency. The category answers a single question: does this stop the next milestone? Everything else about the item — description, photo, owner, discipline — describes the defect. Only the category connects it to the schedule.
That is why category integrity matters more than punch volume. A project with 4,000 correctly categorised items is in better shape than one with 900 where everything is Category A.
2. The three categories
| Category | Meaning | Effect on milestone |
|---|---|---|
| A | Affects safety, function, or the ability to proceed to the next phase. | Blocks. Must be cleared before the certificate is issued. |
| B | Does not prevent progression but must be corrected before final handover. | Carried forward with visibility; blocks final acceptance. |
| C | Cosmetic or minor — paint, labelling, tidiness. | Tracked and closed on a best-efforts basis. |
Exact definitions are set by project procedure and differ between operators. Some projects run only A and B. Some split A into A1 and A2 by phase. The important thing is that the definitions are written down, agreed with the client, and applied by the same rule by everyone raising items.
Put a number on it
What is this costing your project right now?
Estimate the hours and cost lost to transcription, register consolidation and dossier assembly — with editable assumptions and the maths shown.
3. Category inflation, and how to stop it
The default failure mode is that everything becomes Category A. It happens for a rational reason: nobody wants to be the person who downgraded the item that later caused an incident. The result is a blocking list so long that the gate becomes negotiable, which defeats the purpose.
Four things reduce it:
- Write test-style definitions, not adjectives. 'Prevents the system being energised safely' is testable. 'Serious' is not.
- Name the person who assigns the category. Usually a discipline lead or the commissioning engineer, not whoever spotted it.
- Review categories in batch, weekly. A short recategorisation review keeps the list honest and spreads the judgement across people.
- Report category mix over time. If the A share climbs steadily, that is a categorisation problem rather than a quality problem.
4. What a usable punch item contains
- The tag. Not the area or the room — the tag it affects, so it can gate the right subsystem.
- A photo. One image removes most of the follow-up questions and most of the disputes at close-out.
- A defect description in plain terms. What is wrong, not what should be done about it.
- The category, and why. A one-line justification makes review possible later.
- An owner. A discipline, contractor or individual responsible for the correction.
Items raised without a tag are the most common cause of punch that cannot be actioned. Raising them on tablet at the defect — as in punch list software — is largely a way of making the tag mandatory at the moment it is obvious.
5. Close-out and verification
Closing a punch item is a second assertion, and it deserves the same rigour as raising one. A close-out should carry evidence of the correction and an acceptance signature from someone with the authority to accept it — normally not the same person who did the work.
Where this is skipped, the same defects reappear during the client's own walkdown, and the punch list has to be re-run against a delivery date that has not moved.
Check your own process
Score your handover readiness in eight questions
A structured self-assessment of register control, evidence capture, sign-off and gate logic — with a specific recommendation for every gap.
