Free Construction Punch List Template (Fillable + Example)

Introduction: what needs to happen before handover?

A room can look finished while a door closer still fails, a ceiling tile is missing, a commissioning record has not been delivered, or a paint defect remains hidden behind furniture. If those observations live in scattered emails and phone photos, the owner, general contractor, and trades may disagree about what was found, where it is, who must act, and whether the correction has actually passed inspection. A construction punch list turns the final walk into a traceable closeout process.

This guide explains how to create and run a useful punch list, gives you a fillable structure and worked log, and shows how to classify findings, capture evidence, manage contractual boundaries, retest corrections, and report closeout performance. Adapt it to the contract, specifications, approved submittals, applicable codes, and project procedures; it is an operational aid, not legal advice.

What is a construction punch list?

A construction punch list is a numbered register of specific work that remains incomplete or does not meet an agreed requirement at inspection. Each entry describes a condition that someone can locate, understand, correct, and verify. The list may be called a snag list, deficiency list, or outstanding work list depending on the project and region.

The term is used differently across contracts and organizations. Some teams reserve “punch list” for minor items discovered near substantial completion; others include broader incomplete work. Do not assume the label itself decides whether work is accepted, whether payment is due, or whether a deadline changes. The contract’s defined terms, notice requirements, acceptance procedure, and governing law control. The list supports those processes; it does not amend them.

A good entry is factual rather than argumentative. “Three west-corridor door closers do not latch the doors from 30 degrees” is more useful than “bad doors.” The first statement identifies a count, location, observable result, and a test that can be repeated. It does not speculate about fault or prescribe an unapproved repair.

What should a construction punch list template include?

A usable template captures enough context to manage the item from discovery through verified closeout. Keep a stable unique ID, and make the record readable on a phone as well as in a spreadsheet or project platform.

Do not turn the spreadsheet into a contract encyclopedia. Include the applicable reference when it can be identified, but flag uncertain references for the architect, engineer, owner’s representative, or contract administrator to confirm. A blank field should mean “not applicable” or “to be confirmed,” not silently imply agreement.

How do you create a punch list from a walkthrough?

1. Set the rules before inspection

Confirm who may add findings, who can classify them, how disagreements are recorded, what “ready for inspection” means, and who can close an item. Agree whether the team uses one shared register or a controlled master with distributed views. Establish an ID convention, status values, photo naming approach, and a method for recording revisions. State whether trades can propose a due date and who confirms it.

Ask the project team to identify access, safety, and operational constraints before the walk. The relevant trade should not be asked to enter an unsafe area or operate equipment without authorization. Do not test live systems casually; use approved commissioning and lockout procedures and qualified personnel.

2. Inspect systematically and describe what is observable

Walk by building, floor, room, elevation, or system rather than following whichever participant spots something next. Check the scope against the current drawings and specifications, approved samples, commissioning plan, and agreed inspection criteria. Record unfinished work as unfinished; do not disguise it as a defect or assume a defect is merely cosmetic.

Write one independently actionable issue per row. If a corridor has five separate damaged wall sections that different trades or repair steps may address, give them separate entries or clearly itemize them under a parent only if the workflow can assign and close them independently. Avoid combining unrelated concerns in “miscellaneous.”

Use language that separates observation from proposed remedy. For example: “Room 204, north wall: two tile corners are chipped; see photo P-204-07; compare with approved finish sample.” A suggested repair can be recorded after coordination, but the responsible design authority may need to approve a method that affects appearance, performance, or warranty.

3. Locate every issue so it can be found again

A floor number alone is rarely enough. Use room number, grid line, elevation, ceiling zone, equipment tag, or a marked-up plan. For a long corridor, specify a direction and landmark; for repeated units, state the unit range and count. If a room label has changed, record the current label and a stable reference where possible.

For example, “Level 2” could describe dozens of doors. “Building A, Level 2, Room 214, hinge side, Door D-214” narrows the search. If the item affects several identical locations, list each location or attach a clear schedule and count. Confirm that the reference is legible to someone who did not attend the walk.

4. Assign both a trade and one accountable owner

The responsible trade identifies the organization expected to coordinate the correction; the owner field identifies the person who will acknowledge it, arrange access, and report progress. One named lead prevents the diffusion of responsibility that comes with assigning an item to “all trades.” Other contributors can be listed as collaborators.

Assignment is not automatically a legal determination of liability. If trades disagree about scope, record the disagreement and route it to the contractually designated decision-maker. Keep the item visible while the dispute is resolved. Do not erase the original observation or present an unconfirmed assignment as a final finding about responsibility.

5. Classify severity consistently

Severity describes risk and sequence, not blame. Agree category definitions in advance. A practical starting point is:

These examples are not universal classifications. A cosmetic-looking issue may conceal a performance problem, and a visible safety concern may require immediate action outside the punch-list workflow. Escalate uncertain risks instead of downgrading them to protect a completion metric. Track operational urgency separately from contract status where needed.

6. Capture evidence that answers “what and where?”

Take a contextual image showing the room or asset and a close-up showing the condition. Add a scale or reference point when size matters, and mark the exact location on a plan for hidden, overhead, or repeated conditions. Use consistent file names that include item ID and date, such as `A-014_2026-11-13_before_01.jpg`. Follow site rules on privacy, security, and photography.

Record evidence as a link or attachment in the item, not as an unexplained camera-roll file. Preserve original evidence and label later images “after correction” or “retest.” Do not alter a photo in a way that obscures the condition; annotations should clarify location and be distinguishable from the original. Some issues need more than a photograph: attach a test report, commissioning result, inspection certificate, delivery record, or signed approval where that is the appropriate evidence.

How do you set due dates and manage severity?

Set a due date after considering risk, access, cure method, material availability, interfaces, testing, and the contractual schedule. The contractor or trade can propose a realistic date; the designated project representative should confirm the commitment under the project’s process. A date is not credible if the work requires a long-lead part or an outage that has not been approved.

Prioritize immediate hazards and acceptance-critical systems first, then work that blocks other trades, access, testing, or occupancy. Group nearby cosmetic work to reduce remobilization, but do not let efficient batching delay a high-risk item. If an item cannot be completed by the agreed date, record the reason, revised date, decision-maker, and any interim control. A changed date should not overwrite the original commitment; retain both for an honest audit trail.

Status labels should be few and unambiguous. For example: Open, Assigned, In progress, Ready for retest, Rejected/reopened, and Closed. Define whether “complete” means the trade says the repair is done or the verifier has accepted it. Avoid vague labels such as “almost done.” A workflow can add “Disputed” or “On hold” if each state has an owner, next action, and review date.

How do you retest and close an item?

A trade’s completion notice is not proof of acceptance. The assigned verifier should compare the corrected condition with the stated requirement and repeat the relevant inspection or test. The test may be visual, dimensional, operational, documentary, or a combination. Use an appropriately qualified person and approved procedure, especially for regulated systems.

For a door that failed a latch test, the record might state: “Closer adjusted by Trade X on Nov 15; verifier Y tested three cycles on Nov 16; latches from full opening; accepted.” For a leak, a photo of a dry surface may be insufficient if the specified test requires pressure or observation over time. Record the method, result, verifier, date, and evidence reference. If it fails, reopen the same item with a concise reason and next action; do not create a fresh row that hides the history.

Closeout should distinguish at least three ideas: the trade reports correction complete; the designated inspector or representative verifies the correction; and the party authorized by the contract records acceptance or sign-off. These can be different people and decisions. A closed punch item does not by itself waive latent defects, warranties, claims, or other contractual rights unless the governing documents say so. Likewise, an unresolved minor item may have a defined contractual treatment, but teams should not invent one in the log.

What does a filled construction punch list look like?

The examples below illustrate useful records, not universal acceptance standards. Substitute the actual project references, people, dates, and test criteria. Keep the original discovery details intact when the status changes.

Notice how A-016 is a documentation gap rather than an assumed physical defect. The person assigned can obtain the required record, but the verifier must confirm that it corresponds to the correct equipment and approved procedure. A placeholder entry such as “pump paperwork” would not be enough to identify the needed document or acceptance check.

Example 1: sequencing by risk

A 60-room hotel has 18 punch items: 2 potential safety concerns, 6 functional items, and 10 cosmetic items. The team first routes the 2 safety concerns through the site’s immediate escalation process and keeps them out of ordinary batching. The 6 functional issues are then sorted by whether they prevent inspection or operation. The 10 cosmetic items are grouped by floor for efficient access, but retain separate IDs and acceptance evidence. The arithmetic does not determine completion; it simply makes the queue visible.

Example 2: calculate aging and overdue work

Suppose an item was raised on November 10 and has an agreed due date of November 14. On November 16 it remains open. Its age is 6 calendar days if the project counts from the discovery date through the reporting date as elapsed days (November 16 minus November 10); it is 2 calendar days overdue (November 16 minus November 14). State the counting convention, since inclusive day counts and working-day calculations differ. Do not silently mix calendar and business days in one report.

Example 3: make first-pass acceptance meaningful

A team retests 20 items during a reporting period. Sixteen pass on the first retest; four fail and are reopened. First-pass acceptance is 16 ÷ 20 = 0.80, or 80%. This is a diagnostic measure, not a trade ranking by itself. Review the failed items for unclear criteria, incomplete repairs, wrong materials, access issues, or test setup problems before assigning blame.

How does the punch list relate to contractual handover?

A punch list is one part of closeout, alongside inspections, commissioning, record drawings, operation and maintenance information, training, warranties, keys, certificates, and other deliverables specified by the contract. The required package depends on the project and jurisdiction. Build a separate handover matrix that identifies each deliverable, responsible party, required format, reviewer, and acceptance state; link punch items to it when useful.

Before substantial completion or handover, review the contract’s definitions and procedures: who determines completion, which notices are required, what remains permissible, whether a certificate or formal letter is needed, and what deadlines apply. Do not assume that a walkthrough alone creates substantial completion or that a punch-list signature is unconditional acceptance. Obtain advice from the project’s contract administrator or qualified counsel when interpretation has consequences.

Keep the list versioned and distribute it through an agreed channel. Date inspection records, retain meeting decisions, and record any agreed exceptions or deferred items with the authority and basis for the decision. If an item is excluded as out of scope or disputed, preserve the observation and document the disposition rather than deleting it. This lets all parties see both the condition and the decision history.

A practical handover check asks: Are all safety and required system tests resolved? Are remaining items clearly assigned and permitted under the contract? Are required documents complete and traceable to equipment and spaces? Are outstanding conditions disclosed to the receiving party? Are keys, access, training, and operating responsibilities transferred through the required process? A punch-list status alone cannot answer every handover question.

Which closeout metrics are worth tracking?

Use a small set of metrics that trigger a useful decision. Define the denominator and reporting period, and segment by phase, severity, or trade only when the sample is large enough to be meaningful.

For example, if 45 items are open and 9 are overdue, overdue rate is 9 ÷ 45 = 20%. If 12 of 60 items marked complete are reopened, reopen rate is 20%. Present the count beside the percentage so a small denominator is not misleading. A high count can reflect thorough inspection, while a low count can reflect missed inspection; neither proves quality alone.

Review trends weekly during closeout. Ask what is blocked, what decision is needed, which dates are at risk, and whether a recurring pattern suggests a root cause. Metrics should prompt action—such as coordinating access, clarifying acceptance criteria, or escalating a material delay—not reward teams for suppressing legitimate findings.

What are the common punch-list mistakes?

The first common mistake is using subjective wording. “Looks bad” creates debate; a specific location, observed condition, reference, and evidence create a shared starting point. Second, assigning work to a company without a named contact leaves follow-up unclear. Third, setting a due date without checking access or procurement creates a commitment that was never achievable.

Another frequent failure is treating a photo as a complete record. A close-up without room context may be impossible to locate; a “fixed” photo without a retest can show appearance but not performance. Teams also lose control when they overwrite old details, merge unrelated items, or maintain multiple conflicting spreadsheets. Use one controlled source, preserve history, and identify the current revision.

Finally, do not conflate “punch list complete” with “project accepted.” Handover involves contract-defined criteria and other deliverables. Do not use a cosmetic list to hide safety issues, use a criticality label as a legal conclusion, or close work because the schedule is tight. Escalate material disagreements and uncertain requirements through the agreed process.

When does software help manage punch-list work?

A spreadsheet can be a practical choice for a small, stable project with one coordinator, few users, and simple evidence needs. It is easy to start and familiar to most trades. Its trade-off is that version conflicts, mobile photo handling, permissions, notifications, and audit history can become difficult as the number of users and items grows. A shared drive plus naming rules may help, but it still depends on disciplined administration.

A project management platform can help when teams need assigned owners, due dates, comments, attachments, notifications, and status reporting in one place. Doitify is our product, so we know its project and team management features directly; it can organize tasks, subtasks, checklists, owners, schedules, documents, and progress in a unified workspace. It is not a substitute for construction inspection expertise, contract administration, a dedicated field inspection workflow, or required commissioning software. Confirm that any platform’s permissions, export, mobile access, and record-retention fit the project before adopting it.

Whatever tool you choose, agree the record structure first. A digital board cannot repair vague acceptance criteria or resolve a disputed scope automatically. The essential controls are stable item IDs, one accountable owner, a current status, evidence linked to the location, and an authorized verifier.

How can you start with this fillable template?

Copy the fields in the table above into a controlled spreadsheet or your project system. Add project-specific columns only when someone will use them and the meaning is defined. Create a blank master, duplicate it for the inspection, and protect the master from accidental edits. Set dropdown values for severity and status so different people do not create “done,” “fixed,” and “complete” as interchangeable states.

Before the first walk, fill in project name, phase, date, version, attendees, inspection scope, and the agreed status definitions. During the walk, enter one item at a time and attach the evidence while the location is known. At the end of each inspection block, read the items back with the responsible leads. Resolve unclear locations, owners, severity, and target dates while the team is together; record disagreements without pretending they are settled.

After the walk, issue the controlled log through the agreed channel, keep a dated copy, and schedule a short review cadence. Update status without deleting history, request retests explicitly, and use a verifier who has authority and competence for the relevant check. At handover, reconcile open items against the contract and document register, then retain the final list and evidence according to project requirements.

Conclusion

A construction punch list works when each finding can be located, understood, assigned, corrected, and independently verified. Start with one observable issue per item; capture location, owner, severity, due date, and evidence; then preserve the full correction and retest trail. Keep urgent risks on the right escalation path and use the contract—not assumptions about the word “punch”—to govern handover and acceptance.

The most useful template is not the one with the most columns. It is the controlled log the team can keep current, use to make decisions, and reconcile with the project’s closeout requirements. Pilot the fields on one inspection area, clarify what caused confusion, then use the improved format for the remaining walkthroughs.

If this post on construction punch list was helpful, you might also enjoy How to Estimate a Project: Costs, Time and Effort and How to Plan a Project From Start to Finish.