# Punch List

> The itemized list of incomplete or deficient work that must be corrected before a project reaches substantial completion and final acceptance — the last gate between construction and closeout.

- Source: https://briq.ai/acu/object/punch-list
- Department: Field Operations & Project Controls (https://briq.ai/acu/department/field)
- Catalog code: FLD 106 · Level: Foundation · Track: Operations · 10 min read
- Also known as: Snag List, Deficiency List, Pick-Up List, Completion List

## Definition

A punch list is an itemized record of work that is incomplete, defective, or not in conformance with the contract documents, identified during inspection as a project approaches completion, that the contractor must correct before final acceptance. It is generated when work is far enough along that substantial completion is in view, and it becomes the checklist that governs the transition from active construction to closeout. The punch list is tightly bound to substantial completion and final payment: retainage release and final payment are typically conditioned on punch-list completion, which is why it carries direct financial consequence. A punch list is not a mechanism for adding scope or catching design changes; items that represent new or changed work are not punch items but changes, and mixing the two is a frequent source of disputes about what final payment is actually contingent upon.

## Why it matters

The punch list controls the release of money. Substantial completion generally triggers the reduction or release of retainage and starts warranty periods, and final payment is typically withheld until punch items are complete and verified. A punch list that drags is retainage that stays trapped, so the list is not a courtesy exercise; it is the gate on the last and often most profitable portion of the contract balance.

It is where quality reputation is made or lost. The owner experiences the punch process as the visible proof of how the building was built; a short, well-managed list signals a controlled project, while a sprawling list of avoidable defects signals the opposite and colors the owner's willingness to award future work. The punch list is a contractor's final and most durable quality impression.

It exposes the true cost of deferred quality. Defects that could have been caught and corrected during production at low cost become punch items that must be fixed after finishes are in, furniture is arriving, and access is restricted, at multiples of the in-progress cost. A large punch list is usually evidence that in-process quality control failed, not that the punch walk was thorough.

It carries schedule and occupancy consequences. When punch completion is a condition of occupancy or of a tenant's move-in date, unresolved items become the critical path in the final weeks, and a single unresolved life-safety or systems item can hold up a certificate of occupancy for an entire building regardless of how minor the cosmetic remainder is.

## Lifecycle

1. **Pre-punch self-inspection** — Before inviting the owner and architect, a disciplined contractor punches its own work and corrects what it finds. Skipping this produces a bloated formal list of items the contractor could have caught itself and damages credibility.
2. **Formal punch walk** — The owner, architect, and contractor walk the work and record deficiencies by location and trade. Ambiguous items — 'touch up paint' with no location — cause endless re-walks because no one can tell if they are done.
3. **Item logging and assignment** — Each item is logged with a location, description, and responsible subcontractor, and assigned for correction. Items with no clear owner sit uncorrected while everyone assumes someone else has them.
4. **Correction** — Subcontractors return to correct their items, ideally in a coordinated sequence so trades do not damage each other's completed work. Uncoordinated correction creates new punch items as one trade's fix scuffs another's finish.
5. **Verification / back-check** — Corrected items are re-inspected and signed off. The back-check is where an item marked complete but not actually fixed is caught; skipping it lets 'complete' diverge from reality.
6. **Substantial completion determination** — When the work is usable for its intended purpose with only minor items remaining, substantial completion is certified, often triggering retainage reduction and the start of warranties. Disputes about whether remaining items are truly minor arise here.
7. **Final completion and acceptance** — The last items are closed, final inspection passes, and the owner accepts the work, releasing final payment and remaining retainage. Lingering trivial items can hold the whole release hostage if the list is not closed cleanly.
8. **Warranty transition** — Accepted work moves into the warranty period. Items that surface after acceptance become warranty claims rather than punch items, a distinction that determines who pays and under what obligation.

## Anatomy

- **Item number** — Unique identifier for tracking, closure, and back-check reference across what can be hundreds or thousands of items.
- **Location** — Room, grid, floor, or area, precise enough that anyone can find the item. Vague locations are the top cause of re-walks and disputed closure.
- **Trade / responsible subcontractor** — Who must correct it. Unassigned items are the ones that never get done because no one owns them.
- **Description of deficiency** — What is wrong, specifically. 'Damaged' is useless; 'gouge in door frame, 6 inches above handle, north face' is actionable.
- **Photograph** — Image of the deficiency, ideally geolocated, so the item is unambiguous and closure can be verified visually.
- **Severity / category** — Life-safety, functional, or cosmetic. Determines priority and whether the item bears on occupancy versus final acceptance.
- **Contract reference** — The specification or drawing requirement the work fails to meet, which distinguishes a genuine deficiency from a change.
- **Assigned date and due date** — When correction was assigned and is due, driving the schedule to substantial and final completion.
- **Correction status** — Open, corrected, verified, closed, disputed. The field that reveals whether 'done' has actually been back-checked.
- **Back-check / verifier** — Who re-inspected the corrected item and when. The control that keeps claimed completion honest.
- **Change-vs-punch flag** — Whether the item is genuine punch work or actually new or changed scope, which must be handled as a change rather than withheld from payment.
- **Linked records** — Quality inspection checklists, non-conformance reports, and warranty items the punch item connects to.

## Failure modes

- **No pre-punch self-inspection** — The contractor invites the owner to walk before punching its own work. The formal list balloons with obvious items the contractor should have caught, the walk takes days, and the owner's confidence in the project's quality control drops before final payment is even in sight.
- **Vague items nobody can close** — Items are recorded as 'paint touch-up' or 'clean up' with no location or acceptance criterion. No one can tell whether they are done, back-checks fail, and the same items linger through multiple walks purely because they were never defined.
- **Change work smuggled onto the punch list** — The owner or architect adds items that are actually new or changed scope. Final payment is then held hostage to work the contract never included, and the argument about what is punch versus change delays retainage release for everyone.
- **Marked complete without back-check** — Subcontractors mark their items corrected, the status shows complete, but no one re-inspects. At final walk the owner finds items still deficient, credibility collapses, and the closeout timeline resets.
- **Trades undo each other's corrections** — Corrections run uncoordinated, so the flooring crew scuffs the freshly touched-up base and the ceiling crew damages the painted wall. Every correction generates new items, and the list grows even as work is being done.
- **Life-safety item lost in the cosmetic noise** — A fire-rated penetration or an exit-signage deficiency is logged as one item among hundreds of paint dings, unprioritized. The certificate of occupancy is held for a critical item that was never triaged out of the cosmetic backlog.
- **Substantial-completion dispute over 'minor'** — The contractor believes remaining items are minor and substantial completion is due; the owner disagrees. Because severity was never categorized on the list, there is no objective basis to resolve whether the work is usable, and retainage sits frozen during the argument.

## Metrics

- **Item count and density** — Total items and items per unit area. High density is evidence that in-process quality control failed, not that the walk was thorough.
- **Closure rate and velocity** — Items closed per week and time to close by trade. Reveals which subcontractors are gating the path to final completion.
- **Back-check pass rate** — Share of corrected items that pass re-inspection on the first back-check. Measures whether 'complete' actually means complete.
- **Aging by severity** — Days open, segmented by life-safety, functional, and cosmetic. Keeps critical items from hiding inside the cosmetic backlog.
- **Change-vs-punch ratio** — Share of listed items that are actually changes. High values mean final payment is being held against out-of-scope work.
- **Re-walk count** — Number of formal walks required before acceptance. Each re-walk is schedule and relationship cost, usually driven by vague items or missing back-checks.
- **Retainage held against open items** — Dollars of retainage frozen by the open list. Ties the punch process directly to the trapped contract balance.

## The AI shift

- **Conversational** — The punch list becomes something you interrogate rather than scroll through hundreds of rows. You ask which open items are life-safety and bear on the certificate of occupancy, which subcontractor is gating closure, which items have been marked complete but not back-checked, and how much retainage is frozen against what remains, cited to the items.
- **Generative** — Capture shifts from typing during the walk to reviewing a drafted list: from photos and voice notes taken on the walk, a model produces punch items with location, a specific description, a candidate trade, and a severity category, tied to the photo, which the inspector confirms, raising the specificity that makes items closable.
- **Orchestrated** — The punch list stops being a standalone spreadsheet. Items are assigned to responsible subcontractors and routed to them, each item is checked against the contract requirement to separate genuine deficiencies from changes, life-safety items are surfaced against occupancy requirements, back-checks are tracked so claimed completion is verified, and retainage exposure is tied to what remains open.
- **Autonomous** — The routine motion runs continuously: items are logged with location, severity, and trade from field capture, routed to the responsible subcontractor with due dates, aging monitored by severity and escalated, back-check reminders issued and completion held until verified, and change-versus-punch flags raised, while severity judgment, substantial-completion determination, and any final acceptance remain human.

## Prompts

### Conversational — Driving the last two weeks to substantial completion.

```text
Review our open punch list against the target substantial-completion date. Tell me which open items are life-safety or functional and could hold the certificate of occupancy, which subcontractors have the most open items and are gating closure, and which items are marked corrected but have not passed a back-check. Give me the count and dollar value of retainage frozen against the open list, and identify any item that looks like changed scope rather than genuine punch work. Rank everything by its impact on reaching substantial completion, not by item number.
```

**Expected output:** A ranked view that surfaces life-safety items, the gating subcontractors, unverified completions, frozen retainage, and suspected change items, oriented to the substantial-completion date rather than to the raw list order.

**Follow-ups:**

- Draft a sequenced correction plan so trades do not damage each other's work.
- Which items, if not closed this week, will hold occupancy?
- Separate the genuine deficiencies from the change items so we can resolve payment cleanly.

### Generative — Turning a walk-through of photos and notes into a real punch list.

```text
Assemble a punch list from the photos and voice notes I captured on today's walk of level 4. For each deficiency produce an item with a precise location, a specific description that states exactly what is wrong and where, a candidate responsible trade, and a severity category of life-safety, functional, or cosmetic. Tie each item to its photo. Where a note is too vague to close later, tell me what detail I need to add. Flag any item that appears to be new or changed scope rather than a contract deficiency so we handle it as a change, not a punch item.
```

**Expected output:** A specific, closable punch list with locations, severity, and candidate trades tied to photos, with vague items and suspected changes flagged rather than silently logged.

**Follow-ups:**

- Group the list by responsible subcontractor for assignment.
- Which of these should I re-shoot because the photo does not show the deficiency clearly?
- Add acceptance criteria to the cosmetic items so back-checks are objective.

### Orchestrated — Keeping the punch process honest across quality and payment.

```text
Reconcile our punch list against the surrounding records and surface problems. For each open item, check it against the contract requirement it supposedly fails to separate genuine deficiencies from changed scope; cross-reference against our non-conformance reports so nothing already documented as an NCR is being re-litigated as a minor punch item; check that every item marked corrected has a recorded back-check; and connect the open items to the retainage being withheld. Return the reconciliation tied to each item and the record it relates to, and flag any item where completion is claimed but not verified.
```

**Expected output:** A reconciliation that separates deficiencies from changes, exposes unverified completions, links to NCRs, and ties the open list to frozen retainage, each finding cited to the item and record.

**Follow-ups:**

- Draft change events for the items that are actually changed scope.
- Which corrected-but-unverified items should be re-inspected before the final walk?
- Quantify how much retainage we could release if the verified items were formally closed.

### Autonomous — Standing policy for running the punch process.

```text
Operate our punch process continuously under these rules. Log every item from field capture with a location, a specific description, a candidate severity, and a responsible trade, and route it to the responsible subcontractor with a due date. Monitor aging by severity, escalating life-safety and functional items to the superintendent immediately and cosmetic items as they approach the target date. Hold any item in 'corrected' status until a back-check is recorded, and remind for the back-check. Flag any item that appears to be changed scope rather than a deficiency. Keep the retainage-exposure view current. Never assign a severity of life-safety or downgrade one, never certify substantial completion, never accept final work, and never reclassify a change as punch or the reverse on your own; route all of those to a human with your reasoning and the supporting photos and references.
```

**Expected output:** A continuously routed and back-checked punch process with a short human exception queue, where severity judgment, substantial completion, final acceptance, and change classification always stay human, fully audited.

**Follow-ups:**

- Show me this week's life-safety items, unverified completions, and suspected changes.
- Which subcontractors are consistently missing back-check due dates?

## Maturity ladder

- **Level 0 — Level 0 — Handwritten walk** — Punch items are scribbled on a clipboard, transcribed inconsistently, and tracked in memory. Vague items linger and back-checks are informal.
- **Level 1 — Level 1 — Logged spreadsheet** — Items are logged with location, trade, and status in a shared list, assigned to subs, but severity and back-check discipline are inconsistent.
- **Level 2 — Level 2 — Categorized and verified** — Items carry severity, link to contract requirements and NCRs, are back-checked before closure, and retainage exposure is visible.
- **Level 3 — Level 3 — Assisted** — Items are drafted from field photos and notes with location, description, and severity, changes are flagged versus punch, and aging by severity is surfaced.
- **Level 4 — Level 4 — Operated** — Logging, routing, back-check tracking, and aging escalation run within guardrails, while severity, substantial completion, acceptance, and change classification stay human.

## FAQ

### What is the difference between substantial and final completion?

Substantial completion is the point at which the work is sufficiently complete that the owner can use it for its intended purpose, typically with only minor punch items remaining; it usually triggers retainage reduction, the start of warranty periods, and the transfer of certain responsibilities. Final completion is when every remaining item is corrected and verified and the owner formally accepts the work, releasing final payment and any remaining retainage. The punch list spans both, and disputes often center on whether remaining items are minor enough to justify substantial completion.

### Can an owner add new scope through the punch list?

They should not, and a well-run project resists it. A punch item is work that is incomplete or does not conform to the existing contract documents; new or changed requirements are changes, handled through a change order, not items withheld from final payment. When changed scope is smuggled onto the punch list, the contractor's final payment gets held against work it never agreed to perform, which is why flagging change-versus-punch on each item matters financially.

### Why does the same punch item keep coming back after being marked done?

Usually one of two reasons. Either the item was too vague to have an objective completion criterion, so 'done' is a matter of opinion and fails the next walk, or it was marked complete without an actual back-check and was never really corrected. Both are solved the same way: write items specifically enough that closure is unambiguous, and require a recorded back-check before an item can move to closed.

### How do you keep a punch list short?

By not relying on the punch walk to find defects. A short punch list is the product of quality control during production — inspection checklists at each phase, correcting deficiencies while access is easy and finishes are not yet in, and a rigorous pre-punch self-inspection before the owner ever walks. A large punch list is almost always evidence that in-process quality control was weak, and no amount of thoroughness at the end can substitute for it cheaply.

## Related objects

- [Quality Inspection Checklist](https://briq.ai/acu/object/quality-inspection-checklist)
- [Non-Conformance Report (NCR)](https://briq.ai/acu/object/non-conformance-report)
- [Closeout Package](https://briq.ai/acu/object/closeout-package)
- [Retainage](https://briq.ai/acu/object/retainage)
- [Warranty](https://briq.ai/acu/object/warranty)
- [Site Photo Documentation](https://briq.ai/acu/object/site-photo-documentation)