The GC’s punch list arrives with 40 items for the electrical sub. Twelve of them are legitimate — a cover plate missing on Floor 2, a circuit breaker that needs labeling, a light fixture with a loose connection. Eighteen are finish damage in the corridors the sub didn’t cause — paint scuffs on outlet covers that went in weeks before the painters came through, a cracked plate that happened after the sub’s crew left the floor. Ten are items the sub completed in month three of a six-month job, logged complete in the field, but the GC’s inspector walked those floors after the concrete crew came through and didn’t note which work was already done.
The sub who can separate those 40 items closes the job with twelve items to address and eighteen back-charges to submit. The sub who can’t prove which items belong to him works through all 40 and absorbs the damage.
What separates them isn’t luck. It’s the field record built before the punch list arrived.
Why Punch List Disputes Happen
The GC’s punch list is based on what the GC’s inspector observed during the punch walk — typically one or two walkthroughs toward the end of the project. What the inspector sees is the end state. He doesn’t know when the outlet cover was installed. He doesn’t know whether the paint scuff was there before or after the painters came through. He doesn’t know that Floor 3 East was completed and signed off four weeks before the punch walk.
The GC’s inspector documents what he sees. The sub’s PM knows what actually happened and when. When those two records describe the same floor differently, the sub who has a dated field record is in a different position than the sub who has a memory.
Three types of punch list items generate disputes:
Items the sub completed before the punch walk. The GC’s inspector walks Floor 3 at week 22. The sub’s foreman marked Floor 3 East complete at week 14. Between week 14 and week 22, the concrete crew repaired a section of slab, the drywall crew patched a wall, and two other trades worked in that corridor. The inspector sees an incomplete floor — but the incompleteness happened after the sub left. Without a zone-level completion record from week 14, the sub’s PM is arguing from memory against an inspector’s written report.
Finish damage caused by other trades. Paint scuffs, cracked cover plates, bent conduit — finish damage that happens after the sub’s crew leaves the floor gets attributed to whoever put the hardware in. The sub’s entry-condition photo taken when the crew accessed the floor establishes what was there when they arrived. The zone completion record establishes when they left. The condition that appeared between those two timestamps isn’t the sub’s.
Items that belong to other trades. A light fixture with a connection issue goes on the electrical punch list because it’s an electrical fixture. If the connection issue is at the fixture’s supply circuit — and that circuit is the electrician’s work — it belongs there. If the connection issue is at the fixture’s mounting bracket — installed by a different sub — it’s a wrong-list item. The sub who can show from the field record that his work on that circuit was complete and inspected before the punch walk has a basis to redirect the item.
The Record That Determines Who Owns Each Item
Zone-Level Completion with Timestamps
The foreman who marks zones complete in the field tool at the time the work finishes — not at the end of the week, not from memory on Friday — creates a record that establishes exactly when the sub’s crew was in each space and when they left.
“Floor 3 East rough-in complete, logged Tuesday the 14th at 10:15 AM” is a record. When the GC’s punch list attributes a damaged outlet cover on Floor 3 East to the electrical sub, the PM pulls up the completion record, confirms the date, and asks what other trades were on that floor between the 14th and the punch walk. The answer is usually two or three trades, any of which could have caused the damage.
Without that timestamp, the sub is arguing about what he remembers. The GC’s inspector has a written report. Memory loses.
Entry-Condition Photos
The photo taken when the crew enters a zone at the start of work documents the condition before the sub touched anything. If the floor was in poor condition when the crew arrived — debris, damage from prior trades, work left by others — that’s in the photo. If the floor was clean when the crew arrived, that’s also in the photo.
The entry-condition photo taken at the start of work on Floor 4 West establishes a before state. The zone completion record establishes when the sub left. Any damage that appears between those two points didn’t come from the sub’s crew. The photo is the evidence. The absence of a photo is an absence of evidence, which resolves in the GC’s favor.
Entry-condition photos don’t require a separate documentation workflow. The foreman with his phone at the start of each zone access takes a photo before the crew starts work — the same phone he uses to log the task, track his hours, and mark the zone complete when the work is done. The photo is timestamped, tied to the zone in the project record, and available when the punch list arrives.
Inspection Records at the Zone Level
A passed inspection is the strongest punch list defense a sub has. When an independent authority — a building inspector, a commissioning engineer, the GC’s quality control rep — signs off on a zone, that sign-off establishes that the work was complete and code-compliant at the time of inspection.
The inspection record that ties to the zone — zone name, inspection type, inspector’s name, date and time, result — is the document that says: this work was done, it was inspected, it passed. If an item on the punch list relates to work that passed inspection at week 14, the sub has a dated record showing the work was acceptable at that time. Whatever condition the GC’s inspector observed at week 22 developed after the inspection.
For specialty subcontractors, inspection records belong in the same project tool as zone completions and daily logs — not in a separate email chain or a folder of PDFs. The record the sub needs at punch list time is the record built during the job, not assembled in response to the dispute.
How to Respond to a Punch List Dispute
When the GC’s punch list includes items the sub disputes, the response process is straightforward if the record exists:
For items completed before the punch walk: Pull the zone completion record with timestamp. If the zone was marked complete before the punch walk date, ask for specificity on the item — when was the deficiency observed, and has the GC confirmed no other trades accessed the space between the completion date and the punch walk?
For finish damage: Pull the entry-condition photo for the zone and the zone completion timestamp. Present the before state (photo) and the departure date (completion record). If the damage isn’t visible in the entry photo and appeared after the completion date, it’s attributable to work that happened after the sub left.
For wrong-list items: Compare the punch list item description to the sub’s scope of work. If the item is work performed by another trade, redirect it in writing — “Item 23 relates to fixture mounting, which is outside our scope per Section [X] of the contract. Redirecting to [other sub].”
The sub who can do all three without reconstruction — because the record was built during the job, not assembled in response to the punch list — closes punch list in days, not weeks.
The Punch List Starts in Month One
The field record that protects the sub at punch list isn’t built at punch list time. It’s built every day the foreman is in the field.
Zone-level completions logged at the time of completion. Entry-condition photos taken when the crew accesses each space. Inspection results recorded at the time of inspection. Daily reports generated from field entries that go to the GC’s inbox and establish a contemporaneous record of what happened and when.
At punch list, all of that is already there. The sub doesn’t need to reconstruct anything. He opens the project record and looks up the date the work was done, the photo taken when the crew entered, and the inspection result that confirmed it was complete. Those are the documents that determine which punch list items the sub owns.
For how the same field record protects the sub in payment disputes and change order negotiations, see subcontractor progress payment and construction change order documentation.
See how LogLoon’s task management and daily reporting work for specialty sub punch list defense, or check the pricing — it’s on the website.