The punch walk: how to run one, and what to capture

By Adam Chandler, founder of Pangea · August 27, 2026

A punch walk is the joint walkthrough — contractor, owner, and architect together — held when a project is close enough to finished that the work left over can be listed instead of scheduled. It happens after the contractor submits a written list of items to be completed or corrected, and it produces the agreed punch list that has to be cleared before final payment. The walk is the event; the punch list is the document it generates.

That distinction matters more than it sounds. Most of the pain people blame on punch lists is really a badly run walk: three people writing three versions of the same observation, a hallway conversation that decided something and never got written down, and a second walk two weeks later to settle what the first one meant.

What is a punch walk?

It is the inspection where the parties who can bind the project agree, room by room, on what is still wrong. The contractor points at what they have already caught. The owner and architect look at the same work with fresh eyes and add what got missed. Everyone leaves with one list.

The term is jobsite shorthand rather than contract language — you will not find "punch walk" in AIA A201. What the contract describes is an inspection triggered by the contractor's list, and the walk is how that inspection actually gets done. Some teams call it the pre-final, the substantial completion walk, or just "the walk." Same event.

When does a punch walk happen?

When the contractor believes the work has reached substantial completion — not when the schedule says it should have. Substantial completion, under AIA A201-2017 § 9.8.1, is the point at which the work is complete enough that the owner can occupy or use it for its intended purpose. Not perfect. Usable.

Calling the walk too early is the single most common way to guarantee a second one. If a trade is still working in the space, the walk records conditions that will change before anyone reads the list. The list then contains items that fixed themselves, misses items created after you left, and loses credibility with the people expected to act on it.

The fix is an internal walk first. A contractor-only pre-punch, two or three weeks ahead, catches the obvious defects while the trades are still mobilized and there is no owner in the room asking what that is. Everything closed out during the pre-punch is an item that never has to be argued about, tracked, or re-inspected. The formal walk should be about judgment calls, not about missing outlet covers.

Who attends a punch walk?

Four roles, minimum:

• The general contractor — leads the walk, carries their submitted list, and owns the record of what gets added. Usually staffed by a superintendent who knows the building and a project engineer or coordinator who writes.
• The architect — judges the work against the drawings and specifications. On AIA-form commercial projects the architect performs the inspection that determines whether the work is substantially complete, so their presence is not optional.
• The owner, or an owner's representative — the person who will live with the building, and who decides what is acceptable when the specification is silent.
• Relevant subcontractors — not all of them, at all times. Bring the trades whose work dominates the area you are walking, or schedule them by zone so a mechanical foreman is not standing around during a millwork review.

Engineers, commissioning agents, and the facilities staff who will maintain the building are worth adding when the project warrants it. Facilities in particular catch things nobody else does — access panels that open into ductwork, valves you cannot reach with a ladder.

What does the contract actually require?

More than most teams realize, and the sequence is specific. Under A201-2017:

• § 9.8.2 — the contractor prepares and submits to the architect a comprehensive list of items to be completed or corrected before final payment. Critically, the same section states that leaving an item off that list does not reduce the contractor's obligation to complete all work per the contract documents. The list is not a scope limit.
• § 9.8.3 — the architect inspects to determine whether the work is substantially complete. If the inspection turns up anything not sufficiently complete — whether or not it was on the contractor's list — the contractor corrects it before the Certificate of Substantial Completion issues, and then requests another inspection.
• § 9.8.4 — once substantially complete, the architect issues the Certificate of Substantial Completion. That certificate establishes the date, assigns responsibility for security, maintenance, utilities, damage, and insurance, and fixes the time within which the contractor must finish the items on the attached list.
• § 9.8.5 — after the owner and contractor accept the certificate in writing, the owner releases retainage, adjusted for work still incomplete.
• § 9.10.1 — separately, when the contractor gives notice that the work is ready for final inspection, the architect inspects again and, if satisfied, issues the final Certificate for Payment.

Two consequences worth internalizing. First, the contractor writes the list — the architect and owner review and add to it. Second, there are two inspections in the contract, not one, and the punch walk is the first. Teams that treat the punch walk as the last event of the job are surprised by the second inspection every time.

Punch walk, pre-punch, or final inspection — which walk is this?

How do you run a punch walk that doesn't need a sequel?

Preparation does most of the work. Before the walk:

1. Finish the pre-punch and close what you can. Every item you fix now is one that never enters the tracking system.
2. Submit the contractor's list in advance — a day or two ahead, not on the tailgate. The architect walking in having already read it is a different walk than one spent reading.
3. Split the building into zones and sequence them by floor, wing, or room number. Announce the sequence so subs know when to be there.
4. Confirm the space is ready: powered, lit, cleaned, unlocked, with final finishes installed and protection removed. Walking a space under temp lighting produces a list of paint items that are not real.
5. Bring the documents you will argue from — current drawings, the finish schedule, approved submittals, and any approved substitutions. "That's not what was specified" is settled fastest with the submittal in hand.
6. Decide who writes before you start. One person records. Everyone else observes. Two recorders means two lists and a reconciliation meeting nobody scheduled.
7. Agree on the standard out loud — the tolerance, the viewing distance, the lighting condition for finish work. Do it at the start rather than at item 47.

What to capture for every item

Eight fields make an item actionable. Fewer, and someone has to come back and ask:

• Item number — sequential, never reused.
• Location — room number and grid or wall, not "the lobby."
• Trade or responsible sub — the company that owes the fix.
• Description of the defect — what is wrong, in plain words.
• Required correction — what "done" looks like. This is the field most often skipped and most often disputed.
• Reference — the drawing, spec section, or submittal that makes it a defect rather than a preference.
• Photo — one per item, taken at the item, before you walk away.
• Status and date closed — open, corrected, verified, or rejected on re-inspection.

A ninth field earns its place on larger jobs: disputed / not in contract. Owners add items during the walk that are genuinely new scope. Capturing them on the same sheet with a flag, rather than arguing on the spot, keeps the walk moving and gives you a clean list of change candidates afterward.

How long does the contractor have to finish the list?

Whatever the Certificate of Substantial Completion says. There is no industry-wide number, and rules of thumb you find online are somebody's typical project, not your contract. § 9.8.4 puts the deadline in the certificate, which means it is negotiated at the moment of substantial completion — read it before signing.

The financial pressure is real on both sides. Retention on commercial work commonly runs around five to ten percent of the original contract price, and it is released against the punch list closing out. That is also where punch list disputes concentrate: an owner holding back enough retention to cover the outstanding items, and a contractor arguing those items were never in scope. Both positions are easier to defend when the list says what was observed, where, and against which document.

The hard part is not the walk. It is what got said during it.

Walk any near-complete building with an owner and an architect and you will generate two records: the list, and everything else — the decision to accept a finish variation, the agreement that a door swing gets fixed but the hardware stays, the owner mentioning they want the mechanical room signage done before their board tours it. The list captures the first kind. The second kind lives in whoever's memory is best.

That gap is not a small tax. FMI and PlanGrid's Construction Disconnected research put the cost of bad data and poor communication in US construction at roughly $177 billion a year in labor, with the average person losing about five and a half hours a week just looking for project information. Closeout is where that compounds, because the people who were on the walk move to the next job.

Pangea is an AI notetaker built for project-based firms rather than for meetings in the abstract. It records in-person conversations — a phone on the table works for site walks, city counters, and conference rooms — with no bot joining anything, writes the notes in your firm's format, and files every meeting, decision, and document to the correct project automatically. Later, when someone asks what was agreed about the lobby finish, you can ask the project instead of the person, and get an answer with its source cited. It will not write your punch list; the item numbers and photos still belong in your field tool. It makes sure the conversation around the list does not evaporate on the drive back.

It is worth a look if your firm's project knowledge currently lives in the heads of three people. There is a 14-day free trial with no credit card, and it is aimed squarely at the coordinator role — the person who is expected to keep the logs, the minutes, and the PM software all telling the same story. If you already run a disciplined daily log and a current RFI log, this is the layer that keeps them fed without a second pass of typing.