Final Walkthrough Best Practices

A final walkthrough performed badly creates more problems than it solves. Done at night on wet surfaces, it generates false findings and misses real ones. Done without written criteria, it becomes a negotiation between two impressions. Done a week late, it cannot distinguish what the crew left from what has happened since.

Done well it is a short, structured comparison against something agreed in advance, and it ends with a signed record that closes the engagement.

Timing

• In daylight. Non-negotiable. Overnight work should be walked the following morning, not at 4 AM when the crew wants to leave.
• On dry surfaces. Wet pavement conceals remaining soiling and darkens uniformly, which produces both false passes and false failures.
• Promptly. Within a day or two of completion. Beyond that, new soiling, weather, and traffic make attribution impossible.
• Before final payment, which is the practical leverage that makes punch items get addressed.

The Route

1. Start at the approved test area on each substrate. It is the reference and it should be the first thing looked at, so the eye is calibrated.
2. Walk the scope boundary first, confirming what was in and out. Most disputes start at the edges.
3. Follow the visitor route — approach, parking, walkway, entry — because that is where the work will be judged.
4. Then the areas nobody sees: service corridors, rear elevations, enclosures. These absorb the most cost cutting.
5. Check under and around obstructions deliberately. Coverage failures concentrate where something had to be worked around.
6. Finish with site condition — debris collected, drains uncovered, equipment cleared, controls removed, access resecured.

What to Check

Separating Punch Items From Scope Disputes

This is the distinction that determines whether a walkthrough resolves or escalates. A punch item is work within the agreed scope that was not completed to the agreed standard. A scope dispute is disagreement about whether something was in the scope at all.

They need different handling. Punch items go on a list with a completion date and get done. Scope disputes cannot be resolved by the crew standing on site, and attempting to resolve them there generally produces either unpaid work or an unresolved grievance. They go back to the written scope — and if the scope does not answer it, that is a lesson for the next scope rather than an argument to win now.

Categorizing each finding as one or the other, at the point of observation, is what keeps the walkthrough short.

Recording Findings

1. Photograph every finding with enough context to locate it again.
2. Note the location precisely — row, bay, storefront number, elevation.
3. State what is expected, not just what is wrong. "Recleaning required to match test area" is actionable; "not clean enough" is not.
4. Assign a completion date to each punch item.
5. Record the items that passed, not only the ones that did not. A walkthrough record showing what was accepted is what closes the engagement.
6. Sign and date it, both parties, and keep it with the work documentation.

Reinspection

Punch items need a verification pass, and it should be a short targeted walk rather than a repeat of the full route. Where a contractor reports completion, verifying before releasing final payment is the practical control — and where items recur across multiple engagements with the same contractor, that pattern is more informative than any single walkthrough.

See the site acceptance checklist for a printable version of this route.