All guides

A guide for general contractors

The punch list doesn't close the job. The follow-through does.

The walkthrough is the easy part. The hard part is getting every miss to the right trade, getting proof back, and knowing the fix was actually accepted.

01

The list is where the handoff starts

Every GC knows the drill. You start the final walkthrough feeling organized. Forty-seven photos later, your notes say things like “paint thing by door,” and Future You is expected to know which door. A punch list becomes useful only when each observation turns into a clean handoff: what you saw, exactly where it is, who owns the correction, what good work looks like, and who gets the final say.

This isn't a fussy software opinion. The U.S. Army Corps of Engineers uses the same basic chain: the contractor corrects an item, reports it corrected, and sends it back for Government verification. The item stays open until the reviewer agrees the work is satisfactory. If even the Army Corps doesn't trust a single “done” checkbox, neither should your closeout.

02

Substantial completion is not the finish line

The owner may be moving in while you're still moving ladders out of the way. That's normal. GSA guidance says a project can be substantially complete enough for beneficial occupancy while punch items remain. It also separates a usable project with open items or final payments from a fully closed project where the work—and the money—are actually finished.

That is why the punch list is not the whole closeout package, tempting as it may be to call one PDF “closeout” and hope for the best. AIA's project-file classification separates punch lists from completion certificates, record drawings and specifications, submittals, and operations-and-maintenance material. The punch list manages corrections. The closeout file proves the larger handoff.

03

Write each item so nobody has to call you

A punch item should not read like a fortune cookie. If a sub has to call and ask which wall, which scratch, or what “finish trim” means, the item isn't ready to hand off. Keep it to one visible condition, but include enough context for someone who missed the walkthrough to act without consulting three people and a floor plan.

  • Exact location: building, floor, room, wall, elevation, or equipment tag. “Upstairs” is not a location.
  • Observed condition: the specific visible issue, written without guessing at its cause.
  • Expected correction: the result you plan to inspect. “Fix it” is an emotion, not a scope.
  • Responsible party: one trade or owner for the next action, even when several trades are involved.
  • Timing: the target date or sequence constraint that affects access and turnover.
  • Evidence: an orientation photo for location and a detail photo for the condition when both are needed.
  • Disposition: open, reported complete, verified, rejected, or formally deferred—with a date and reviewer.

04

“Done” is a claim. “Verified” is a decision.

Finding an item takes seconds. Closing it takes another loop—and usually at least one “hey, did you get that?” The trade needs the original photo, you need proof of the correction, and everyone needs to see why work was rejected or sent back. If tapping “done” makes the item disappear, you've lost the exact moment when the work is actually accepted.

A well-run list therefore preserves two verbs: the responsible party reports the work complete; the owner, general contractor, architect, or designated reviewer verifies it. That small state boundary is the difference between a progress report and an acceptance record.

On the job

This is how the work should move.

  1. 01

    Observe

    Record one condition with a location, plain-language description, and photo—before you walk ten feet and forget which door it was.

  2. 02

    Assign

    Give the next action to one responsible party. “Everyone” is not a trade.

  3. 03

    Correct

    Keep the completion note and after-photo on the original item, not wandering loose through your messages.

  4. 04

    Verify

    Accept it, reject it, or send it back—with the history still attached and nobody guessing why.

Bottom line

Could someone else run the follow-up?

Someone who missed the walkthrough should still be able to find the condition, understand the correction, see who owns the next action, and tell whether the work was merely reported complete or actually accepted. If only you can decode the list, you don't have a system. You have personal notes with an audience.

Sources

For further reading.

  1. 01

    RWA process ↗U.S. General Services AdministrationExplains the difference between substantial completion, beneficial occupancy, and closeout.

  2. 02

    Quality Control System Manual ↗U.S. Army Corps of EngineersDocuments the correct-report-verify-concur sequence for QA punch items.

  3. 03

    Keys to classifying project files ↗American Institute of ArchitectsPlaces punch lists in the broader record structure for completion and project closeout.

About SitePunch Guides

SitePunch Guides draw on documented construction closeout practices, primary industry sources, and research into how contractors coordinate punch work.

SitePunch

Keep the correction attached to the issue.

One link per project. Photos and comments per item. Verification before closeout.

Start a punch list