A construction project can look complete while still having dozens of small issues that affect its quality, safety, or usability. A door may not latch, a tile may be chipped, a handrail may be loose, or a ventilation system may not work as specified. These unfinished or defective items are commonly recorded in a snag list—also called a punch list in some countries.
A well-organized snag list helps clients, contractors, and consultants agree on what needs attention before handover. It also makes responsibilities, deadlines, and close-out evidence easier to track. This guide explains what a snag list is, how to inspect a project, and how to use a sample snag list to manage defects through to completion.
Note: “Snagging” is a common term in the UK and other markets; “punch list” is often used in the United States. The exact process and legal significance vary by contract and jurisdiction.
What Is a Snag List?
A snag list is a written record of incomplete work, visible defects, damage, or items that do not appear to meet the agreed project requirements. It is usually prepared during inspections near the end of construction, although teams may also create lists at earlier stages.
Examples include:
- A window that does not open or lock properly
- Paintwork that is uneven or incomplete
- A cracked floor tile
- Missing sealant around a bath
- A light fitting that does not operate
- An incomplete test certificate or handover document
A snag list is not a substitute for the contract documents, inspection records, or formal quality-control procedures. It is a practical tool for identifying and tracking items that need to be resolved.
Why a Snag List Matters
A clear snag list can help project teams:
- Record issues consistently. Specific descriptions reduce the chance of misunderstandings.
- Assign responsibility. Each item can be allocated to the relevant contractor or trade.
- Set priorities. Safety-critical or operational issues can be addressed before cosmetic defects.
- Track progress. Statuses and due dates show what remains outstanding.
- Support handover. A documented close-out process gives the client and contractor a shared record of completion.
The list works best when it is prepared collaboratively and checked against the project’s drawings, specifications, approved samples, and contractual requirements.
When Should You Prepare a Snag List?
Snagging is often associated with the final stages of a project, but waiting until the end can make defects more difficult or costly to correct. Consider using inspections at several points:
- During construction: Check work before it is concealed, such as pipes, wiring, waterproofing, or insulation.
- At trade completion: Inspect each area after a trade finishes its work.
- Before practical completion or handover: Record remaining defects and incomplete items.
- After remedial work: Verify that the reported items have been resolved.
- During any agreed defects or warranty period: Record issues that arise after occupation, following the contract’s procedures.
The contract determines what formal inspections, completion milestones, and defect-correction procedures apply. A snag list should support those arrangements, not replace them.
How to Carry Out a Snagging Inspection
1. Prepare before the inspection
Bring the latest drawings, specifications, schedules, approved finish samples, and any relevant inspection or test records. If possible, confirm that areas are accessible, adequately lit, and safe to inspect.
2. Inspect systematically
Work through the property in a consistent order—for example, by floor, room, or building zone. Check each area from ceiling to floor and include:
- Finishes and surfaces
- Doors, windows, and hardware
- Electrical fittings and controls
- Plumbing fixtures and drainage
- Heating, ventilation, and air conditioning
- Joinery, cabinetry, and built-in equipment
- External areas and access routes
- Safety features and required signage
- Handover documents and operating information
Only carry out tests that are safe and appropriate for your role. Systems requiring specialist commissioning or certification should be checked by qualified personnel.
3. Describe each item clearly
A useful snag entry says what is wrong and where it is. “Bad paint” is vague; “Patchy paint finish on the north bedroom wall, beside the window” is more actionable.
Avoid assigning blame or guessing at the cause. Record the observable condition and, where relevant, refer to the drawing, specification, or agreed standard.
4. Add supporting evidence
Photos can help explain the location and condition of an item. Use a wide shot to show where the issue is and a close-up to show the defect. Label photos with a room, area, or item reference.
5. Agree priority and responsibility
Not every item has the same urgency. A blocked fire exit should be treated differently from a minor paint blemish. Agree priority categories with the project team and allocate each item to the responsible party.
6. Set a due date and verify the fix
Record a target date, then inspect the completed work. An item should not be marked closed solely because someone reports it as complete; confirm that the correction is satisfactory and record the verification date or evidence.
Sample Snag List in Construction
The example below is a general template. Adapt the fields and categories to suit the contract, project, and local requirements.
| ID | Location | Snag / Observation | Priority | Responsible Party | Target Date | Status | Close-Out Evidence |
|---|---|---|---|---|---|---|---|
| S-001 | Main entrance | Door closer does not bring the door fully into the closed position | High | Door contractor | 05 Nov | Open | Retest and photo |
| S-002 | Ground-floor hall | Two floor tiles have chipped edges near the stair opening | Medium | Tiling contractor | 07 Nov | Open | Photo after replacement |
| S-003 | Kitchen | Sealant is missing along the rear edge of the sink | Medium | Plumbing contractor | 06 Nov | In progress | Photo and visual check |
| S-004 | Bedroom 2 | Paint finish is uneven on the wall beside the window | Low | Decorating contractor | 10 Nov | Open | Photo after redecoration |
| S-005 | Bathroom | Extract fan did not operate during the agreed functional check | High | Electrical/mechanical contractor | 04 Nov | Open | Test result |
| S-006 | External path | Uneven paving creates a potential trip hazard at the side entrance | High | Groundworks contractor | 03 Nov | Open | Inspection and photo |
| S-007 | Living room | One socket faceplate is loose | Medium | Electrical contractor | 05 Nov | Open | Secure and verify |
| S-008 | Plant room | Equipment operating instructions are not present in the handover pack | Medium | Main contractor | 08 Nov | Open | Document register |
| S-009 | Staircase | Handrail fixing is loose at the upper landing | High | Joinery contractor | 03 Nov | Open | Physical check |
| S-010 | Utility room | Final sealant around pipe penetration is incomplete | Medium | Relevant trade | 06 Nov | Open | Photo and visual check |
Suggested status labels
Keep status terms simple and consistent. For example:
- Open: Identified but not yet corrected
- In progress: Work has started
- Ready for inspection: Contractor reports the item complete
- Closed: The correction has been checked and accepted
- On hold: Work cannot proceed until an identified dependency is resolved
If the item is disputed, add a separate “disputed” status or note rather than silently removing it from the register.
What Information Should a Snag List Include?
A useful snag list usually includes:
- A unique item number
- Project, building, floor, and room or area
- A precise description of the issue
- Date identified and inspector’s name
- Reference to a drawing, specification, or requirement, if relevant
- Priority or risk category
- Responsible contractor or trade
- Target completion date
- Current status
- Photographs or other supporting evidence
- Completion and verification details
- Notes about access, dependencies, or disagreements
For larger projects, teams may also track cost implications, repeat defects, warranty details, or links to inspection and test records.
Prioritizing Snag Items
A practical priority system can help teams focus on the most important work. One simple approach is:
- High: A safety concern, a critical system failure, a significant breach of requirements, or an issue that prevents intended use or handover.
- Medium: A functional or quality issue that should be resolved promptly but does not present an immediate serious risk.
- Low: A minor cosmetic or finishing issue that does not significantly affect safe use or operation.
These labels are only a coordination aid. They do not replace a formal risk assessment, statutory inspection, commissioning process, or the requirements of the contract. Where there is an immediate danger, follow the site’s safety and escalation procedures rather than relying on a routine snagging workflow.
Common Snagging Mistakes to Avoid
Writing vague descriptions
Entries such as “check door” are hard to action. State the location, observed problem, and expected result where known.
Listing opinions as defects
Record measurable or observable conditions. When a concern depends on an interpretation of the design or contract, identify the relevant requirement and raise it for review.
Failing to identify the location
A photo without a room or area reference can be difficult to use. Include both a location and an item number.
Treating every issue as equally urgent
Prioritize safety and essential functionality. Cosmetic issues should not obscure more serious items.
Closing items without verification
Use a consistent close-out check. If a repair is incomplete or has created another issue, keep the item open or create a linked follow-up item.
Using the list as the only quality-control record
A snag list is generally a close-out tool, not a replacement for quality plans, inspection and test plans, commissioning documents, statutory approvals, or required certificates.
Confusing incomplete work with defects
A missing item may be unfinished work rather than a defect in completed work. Record the condition accurately and follow the terminology and process used by the contract.
Digital Snag Lists and Record Keeping
A spreadsheet may be enough for a small project. Larger projects often benefit from a shared digital register or construction-management platform that supports:
- Photo and document attachments
- Filters by location, trade, priority, or status
- Notifications and due dates
- Change histories and audit trails
- Mobile access during inspections
- Reports for handover meetings
Whatever tool you use, agree who may edit the register, how changes are approved, and where the official project record is stored. Keep backups and retain records in line with the project’s document-control and contractual requirements.
Conclusion
A sample snag list is most useful when it becomes a clear, shared process—not just a final walk-through checklist. Inspect systematically, describe each item precisely, assign responsibility, set a realistic due date, and verify the correction before closing it. Prioritize safety and essential operation, keep supporting evidence, and make sure the list aligns with the project’s contract and quality procedures.
The result is a more transparent close-out process and a better chance that outstanding work is identified, resolved, and documented before handover.
Sources and Further Reading
- Royal Institution of Chartered Surveyors (RICS), New Rules of Measurement: Order of Cost Estimating and Cost Planning for Building Maintenance Works and related guidance. RICS publications: rics.org
- Chartered Institute of Building (CIOB), resources on construction quality management and project practice. ciob.org
- U.S. General Services Administration, Construction Quality Management resources and guidance. gsa.gov
- International Organization for Standardization, ISO 9001:2015—Quality management systems: Requirements, a framework for quality-management processes. iso.org
- U.S. Occupational Safety and Health Administration (OSHA), construction safety standards and guidance. osha.gov
These sources provide broader quality and safety context; they do not prescribe one universal snag-list format. Always check the project contract, applicable regulations, and local professional guidance.