Construction Punch List Template
Table of Contents
Introduction
Keep a defect open until the agreed correction has been checked. This punch list gives each item a location, responsible trade, due date and acceptance condition. It separates a contractor’s completion claim from the reviewer’s decision to close or reopen the item.
Confirm who can raise, assign and accept punch items on this project. Have the applicable drawings, specifications and approved changes available. Use one record per distinct defect; combine related evidence under that item rather than creating duplicates.
If parties disagree about the required correction, reference the governing project documents and send the issue to the authorized reviewer. Record access constraints and dependencies early. Unresolved items must remain visible in the handover record.
Save one checklist per project, then add one task per defect. The saved-app Table keeps correction claims, reinspection evidence and acceptance separate.
The starter row includes concrete naming examples, while all defect fields start blank. Capture the date raised and the trade’s acknowledgment to distinguish an assigned item from work someone has agreed to correct.
| Task name | Defect ID | Date raised | Exact location | Observed defect | Requirement reference | Acceptance condition | Before evidence reference | Responsible trade/owner | Defect status | Trade acknowledgment | Access or dependency | Correction claim and evidence | Authorized reviewer | Reinspection date | Reinspection result | Acceptance or failure evidence |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Starter defect: [exact location] — [observable issue] | ||||||||||||||||
Show noteRename this starter row for one real defect, and add one separate row for each further defect. Examples of suitably specific names: “Room 203 door — latch does not engage”; “Lobby wall — finish differs from approved sample”; “Plant-room label — asset ID missing”. These are examples, not reported project defects. Fill the defect ID, exact location, observation, requirement/revision and acceptance condition. Record the trade’s acknowledgment, then use the native assignee for the internal coordinator and native due date for the agreed correction date. Capture the correction claim and reviewer/date/result separately. Keep this task incomplete until the authorized reviewer accepts it; a trade’s completion claim only requests reinspection. | ||||||||||||||||
Download or Print this Construction Punch List Template
Get a printable version of this checklist in your preferred format: PDF, Word, Excel, or print directly from your browser.
Presented by:
Checklist.com
Stats
Views
20
Views: 20
Uses
0
Uses: 0
Tasks
1
Tasks: 1
Details
Before you begin
Confirm who can raise, assign and accept punch items on this project. Have the applicable drawings, specifications and approved changes available. Use one record per distinct defect; combine related evidence under that item rather than creating duplicates.
Exceptions and handoffs
If parties disagree about the required correction, reference the governing project documents and send the issue to the authorized reviewer. Record access constraints and dependencies early. Unresolved items must remain visible in the handover record.
Worked example
P-018, Room 203 door: latch fails to engage; assigned to joinery; corrected photo received; reviewer tests against agreed door schedule and reopens because latch still misses.
Review and improve
Review items with acceptance criteria, median time from completion claim to review, reopened items, overdue items by trade. Use recurring failures and staff feedback to revise the approved process; record the reviewer and revision date.
Use the defect register
Create one row for each defect with its unique item ID. Required operational fields are location, observed defect, requirement/acceptance reference, responsible trade, due date and current status. Add before evidence, reported-correction evidence, reviewer/date and reinspection result. Use statuses such as Open, Assigned, Ready for reinspection, Reopened and Accepted; the project defines who may make each transition. Do not assume the app enforces those permissions.
How to run the punch-list register
1. Identify the project, inspection scope and who may accept corrections. Agree who will accept corrections and which project requirement applies. Number items consistently. Named reviewer and approved drawing/specification reference are recorded. 2. Create one item per distinct defect. Use room, floor, grid or asset identifiers that another trade can find. Include one clear defect per item. Unique item ID, exact location, concise observation and permitted evidence make it findable. 3. Define the acceptance condition before assignment. Describe the expected corrected state and its requirement reference. Route disputed scope to the authorized reviewer. Expected corrected state points to the agreed requirement; disputes are routed rather than guessed. 4. Assign responsible trade, target date and access constraints. Ask the assigned trade to confirm access and sequence. An owner name without acknowledgment may leave work unclaimed. The responsible party acknowledges the item and unresolved dependencies have owners. 5. Record completion claim and evidence. Record when the trade says the fix is ready for inspection. This is a review request, not closure. Completion date/photo/reference is distinct from acceptance. 6. Reinspect against the acceptance condition. Record pass or failed criterion. If reopened, retain the earlier evidence and assign the next correction. Reviewer closes passed items or records failed criterion and reopens work; remaining exceptions are carried to handover.
Who it's for
How to use
- Save this as a checklist for one project. In the saved checklist, use Table to review the defect fields or List to open individual items. The public preview is not an editable Table register.
- Add the project, inspection scope and authorized acceptance reviewer to the checklist notes. Rename the starter row and add one task for each distinct defect. Keep a stable unique defect ID when an item is reopened.
- Record exact location, observed defect, permitted before-evidence, approved requirement revision and the acceptance condition before assignment. Refer disputes to the authorized reviewer rather than inventing a requirement.
- Record the responsible trade, its acknowledgment and access or dependency constraints. Set the agreed correction date with the native task due date, and assign the internal coordinator with the native task assignee.
- Record the contractor’s correction claim and dated evidence. Set Ready for reinspection only when it is ready for review; do not mark the task complete at this point.
- Have the authorized reviewer check the correction against its acceptance condition. Record the reviewer, actual date, result and evidence. Use qualified personnel for technical tests.
- Set Accepted and complete the task only after a passing authorized reinspection. For a failure, retain the evidence, set Reopened and assign the next correction. Carry outstanding items and agreed exceptions into the project handover.
Status fields do not enforce project permissions. A closed punch list does not replace occupancy approval, statutory inspection, commissioning or contractual acceptance.