The punch list is the workflow that determines whether your project actually closes out cleanly — or sits in punch limbo for months while the GC and subs argue about who owns which incomplete item. The list itself isn't complicated. The management of it, across the sub-GC-owner-architect chain, is where projects either ship on time or grind to a halt three weeks before substantial completion. This is a working guide on construction punch list management: what goes on the list, who owns each item, how to assemble photo evidence, the architect / owner sign-off chain, and how to keep the list from sprawling.
If you're a GC PM walking through a 100K-square-foot building with a yellow legal pad and a flashlight, you've probably wondered why this workflow hasn't been modernized. Most punch lists are still PDFs annotated with comments, sometimes printed and hand-marked, with sub responsibilities allocated by email. There's a better way.
What punch list management actually is
The "punch list" (also called a snag list or deficiency list) is the catalog of incomplete or defective work items identified at substantial completion. The list captures what must be remedied before the project can transition from active construction to occupancy / warranty / closeout. The GC owns the master list; each sub owns the items on the list that fall within their scope; the architect and owner sign off as items are closed.
The lifecycle:
- Pre-substantial-completion walks. The GC's superintendent and PM walk the building, often with the owner's rep and the architect, identifying incomplete or defective items. Sometimes there's a separate "pre-punch" walk by the GC to catch obvious issues before the formal walk.
- Formal substantial-completion walk. The architect (and sometimes owner and lender) walks the building with the GC. The architect signs the Certificate of Substantial Completion (AIA G704 or equivalent) with the attached punch list. This is the formal trigger for warranty start, retention release timing, and certificate-of-occupancy submission.
- Punch list distribution. The GC distributes the list to the relevant subs, with each item assigned to whoever's responsible for the scope.
- Remediation. Subs perform the punch work. Some items are quick (touch-up paint, missing escutcheon, broken sprinkler head). Others are substantial (replace a damaged door, redo improperly graded concrete, recommission a balancing issue).
- Sub sign-off per item. Sub marks each item complete, ideally with photo evidence.
- GC verification. GC PM or super verifies the sub's claim of completion. Approves or rejects per item.
- Architect verification (selective). For items that require design judgment (finish matches, code compliance, aesthetic issues), the architect re-walks and signs off.
- Owner acceptance. Once the list is at or near zero open items, the owner formally accepts the work. Final retention release follows.
Total cycle from substantial completion to fully-closed punch list typically runs 30-90 days on commercial projects. Cases where it runs 6+ months are almost always traced to broken handoff between subs and the GC, not to genuinely complex remaining work.
What goes on the list
The punch list captures three categories of items:
- Incomplete work. Scope items in the contract that simply aren't done yet. The sub still owes the work; this is just a list of "finish what was contracted."
- Defective work. Work that was done but doesn't meet the spec, the drawings, code, or industry standard. The sub has to remedy without additional payment.
- Damage caused during construction. Things damaged by one trade during the work of another (e.g., the carpet got cut while electricians ran new conduit). Often a separate negotiation over who pays.
What does NOT go on the punch list:
- Owner-directed scope changes. These are change orders, not punch items.
- Issues caused by tenant or post-occupancy use. These belong to the warranty period or maintenance, not punch.
- Items the architect or owner is unhappy about but were built per the approved drawings and specs. These are CO conversations.
Subs often try to push back on punch items they consider out-of-scope; GCs sometimes try to add items that should be COs. Discipline at list creation time prevents disputes later.
The recurring punch list failure modes
1. The list lives as a PDF that someone hand-annotates. The master PDF gets distributed; subs annotate their copies; the GC tries to reconcile from multiple annotated PDFs. Items get lost. Status updates don't propagate.
2. No photo evidence per item. Sub claims completion; GC re-walks to verify; finds the item still open. Rework cycle adds days. Photo evidence at completion-claim time eliminates most of these round-trips.
3. Items reopen quietly. Sub completes a touch-up; another trade damages it during their punch work; nobody updates the list. Owner walks at the end, finds the original item still defective, the list shows it as closed, and the GC has no audit trail.
4. Sub assignment is ambiguous. An item gets logged ("door doesn't latch properly") but it's not clear whether the door is the carpenter's, the hardware sub's, or the doorframe installer's responsibility. The item bounces between subs while the GC tries to assign ownership.
5. Punch list keeps growing post-walk. The formal walk produces a list of 180 items. Two weeks later the GC's PM is still adding "we noticed this too" items. Subs get frustrated; the boundary between "what we agreed to fix" and "what you keep adding" becomes contentious.
6. Architect or owner sign-off bottlenecked on one person. The architect's contract admin is on vacation; sign-offs queue; punch closure stalls; substantial completion paperwork delays. Single-point-of-failure scheduling.
7. Punch items not tied to corresponding warranties. A sub remediates a punch item with a different product than originally installed. The warranty registration doesn't get updated. Months later, the owner has a warranty claim and the records don't match what's actually in the building.
What good punch list management looks like
The principles:
One central punch list per project, with structured items. Every item has a unique ID, a description, a location (room number, drawing reference, GPS coordinate), the responsible sub, the type (incomplete / defective / damage), the priority, the photo evidence at logging, and the state (open / in-progress / sub-claimed / GC-verified / architect-verified / owner-accepted / closed).
Mobile-first capture. The PM walking the building should be able to log a new item with a photo, location, and sub assignment in under 30 seconds, from a phone. Anything slower kills adoption and pushes the workflow back to the legal pad.
Photo evidence at every state change. Logging captures a photo. Sub-claims-complete captures a photo. GC-verifies captures a photo (or annotates the existing one). The audit trail is visual.
Sub assignment by scope, not by guess. The platform should know which sub is responsible for which scope (concrete, drywall, mechanical, hardware, etc.) and propose the assignment automatically based on item type and location. The GC PM confirms or overrides.
List freeze at a defined point. The formal substantial-completion walk produces the master list. New items added after the freeze date are flagged as "post-freeze additions" so the boundary is clear. This isn't about preventing additions — sometimes you genuinely find new things — but about preventing the list from sprawling silently.
Multiple architect / owner sign-off paths. Avoid single-person bottlenecks by allowing the contract admin to delegate sign-off authority for routine items, with the senior architect reserved for items requiring design judgment.
Closeout binder coupling. Punch items that resulted in product or installation changes update the closeout binder automatically — warranty registrations, as-built drawings, O&M manuals. (See our closeout binder continuous-assembly post for the upstream workflow.)
How AOS handles punch list management
In AOS, the punch list is a project-level structured object with state, photo evidence, sub assignment, and cross-tenant workflow. Specifically:
- Mobile-first capture from any role. GC PM, sub PM, foreman, architect — all can log items from a phone with photo, location, and assignment in seconds.
- Sub assignment by scope. The platform knows which sub holds which scope (from the project's subcontract registry) and proposes assignments automatically. GC PM confirms or overrides.
- Photo evidence at every state change. Logging, sub-claims-complete, GC-verification, architect-sign-off — each transition captures (or references) a photo.
- Multi-tier verification workflow. Sub claims complete → GC verifies → architect verifies (selective) → owner accepts. Each tier configurable per project; delegation paths supported to avoid bottlenecks.
- List freeze with post-freeze tracking. The formal substantial-completion walk produces the master list; post-freeze additions are flagged distinctly with timestamps.
- Cross-tenant when both sides are on AOS. Items assigned to a sub appear in their punch queue cross-tenant; completion claims with photos flow back to the GC without document upload.
- Closeout binder coupling. Punch resolutions that change product or installation update the closeout binder records (warranty, as-built, O&M) automatically.
- Punch progress dashboard. GC, owner, and architect see real-time progress: items by state, items by sub, items by priority, aging. The owner doesn't need to ask "how's punch going" — they can see.
The GC PM role page walks through the project workflow from the GC's seat. The GC superintendent role page covers the field perspective. The sub PM role page covers the sub-side punch workflow. For the connected closeout workflow, see the closeout binder continuous-assembly post.
The punch list readiness checklist
- Is there one central punch list per project with structured items, or do PDFs and email threads do the work?
- Can a PM log a new item with photo evidence in under 30 seconds from the field?
- Are sub assignments proposed automatically based on the project's subcontract scope structure?
- Is photo evidence captured at every state change, not just at item creation?
- Is there a defined list-freeze date, with post-freeze additions flagged?
- Are architect and owner sign-off paths multi-person to avoid single-point bottlenecks?
- When a punch resolution changes product or installation, does the closeout binder update automatically?
If most answers are "we do it informally with PDFs and email," that's the workflow a connected platform closes.
If you'd like to see it
We're in private-beta design-partner mode for commercial subs and GCs. If you'd like to walk through how AOS handles punch list management on a real project — particularly one approaching or in punch — apply to the beta. The GC overview covers the platform broadly.