By Bryan Cook, QBC LLC. Published September 29, 2026. This is the long-form version of a BUILD newsletter issue written for fellow subcontractors.
The short answer: When the people responsible for fixing punch items can't or won't use the GC's software, print the punch list. Print one item per page, in color, and sort the packet by scope. Hand the packets to the people doing the work. As they fix a punch item, they photograph the fix with their punch sheet in frame. They then upload the photos to a drive. A foreman or PM closes the items out in the GC's system during their admin time. Before printing, sort the list into "ours" and "needs a conversation," because damage from other trades is a change order, not a punch item.
Because the software was built for tech savvy users, and the punch list gets closed in the field, usually by someone who's not a keyboard warrior.
Every subcontractor reading this has dealt with this. The punch list gets issued, it's in whatever system the GC runs (Procore, ConDoc, a spreadsheet, etc.), and the person who handles the punch on your crew is a carpenter who can barely access their own email. Maybe English isn't their first language. Maybe they've been a carpenter longer than you've been alive and they see technology as a blocker. Whatever the situation, the punch list has to get handled.
In this day and age everyone acts like paper is a terrible thing. Sometimes the old ways are the most efficient ways.
We've been closing out multifamily projects for years, and we've tried every technology there is. We've tried teaching crews to use the technologies, and they can learn, but then turnover happens and there we are again, teaching someone how to use an iPad and log into Procore. Then we get a subcontractor who does amazing work, but English isn't their first language, it's Albanian. After a long and winding road we figured out the punch process that actually works for the people doing the work. It requires no cell signal, no WiFi, and no translation. It's paper.
One item, one page, one packet per scope.
When the punch list comes in, we print every item, in color, one (1) item per page. Photo, unit number, description, who submitted it, all of it. Then we assemble one packet per scope, per project, and hand that packet to the person responsible for punch on that project. Could be one of our PMs, could be one of our foremen, could be one of our subs. They work the packet one page at a time, and after every fix they take a photo of the fix with their punch sheet in the foreground.
Those photos get uploaded from a phone into a Google Drive folder for that project. The foreman or PM then goes into the GC's system and closes the items out with the photo attached. The GC sees exactly what they need to see, a completed punch item with photo proof.
The photo step is not optional. Industry guidance on punch lists now recommends that GCs require photo evidence of every correction from their subs, because it speeds up verification and cuts down on repeat inspections (Smartsheet, construction punch list guide). A sub that shows up with the photos already attached is doing the GC's verification for them.
It costs more to print forty (40) pages than to print one list, but it has paid for itself more than once by preventing a trip back to Milwaukee for an item somebody overlooked because it was line item 23 of 40 on a sheet printed in a size 10 font.
This applies to every scope we run, from finish carpentry (base, case, doors) to countertops to cabinetry. The packet is the same.
Any item that is damage caused after your install, by a trade that isn't you, is a change order and not a punch item. Sort those out before anything gets printed.
This is the part we'd tell every sub to do, whether you use paper or not.
Before anything gets printed, our PM sorts the list into two (2) piles: "ours" and "needs a conversation." Ours is clearly ours and gets printed. The needs a conversation list requires the QBC PM for the project to call the GC directly and talk through who really owns each and every item.
What does "needs a conversation" mean? Scratches in LVP after the appliances are installed. Carpet stains from dirty boots or spilt paint. A dinged door face from another trade. If you were awarded the flooring scope, you're not responsible for babysitting the material after it's installed. That's on the GC for not controlling their jobsite.
As an example, on a recent project, 25% of the forty (40) items on a punch list were damages caused by other trades after install.
The reason to sort at the point of listing, not after the work is done, is that accepting an out-of-scope item onto the punch list quietly converts it into an obligation you're expected to absorb for free (Nomic, punch list reference). Once your crew fixes it without a change order, the conversation is over.
So you call the Site Sup and you say it plainly. "We will gladly replace the scratched LVP, but that will be a change order as I'm sure you can understand." Nine times out of ten the Sup will agree.
The GC is doing their job by adding items that need to be fixed before turnover to the list, you're doing your job by standing up for your company. It's not meant to be adversarial, it's just good business. The GCs worth working for respect a sub who has the backbone to firmly but politely call something out.
We covered the money side of this in The Real Cost of Subcontractor Coordination. Unbilled punch work is one of the coordination costs that never shows up on a bid sheet.
Pay for it before anyone asks. That's the only way change order conversations stay credible.
Let's look at the other end of the punch scenario. We had a hydraulic hose burst on a Manitou, and the fluid stained the asphalt on a bike path next to the site. Nobody had to ask. We paid for the remediation without question.
If you're going to write change orders for other people's damage, you'd better own yours without being told to.
The party that failed to hold the building within the manufacturer's spec, which is almost always the GC. But you only get to make that case if you documented the conditions before the material failed.
Every finish material we install has a spec sheet with a temperature and humidity range on it. As an example, one common LVP manufacturer's guideline calls for HVAC to be fully operational at 65 to 85 degrees F and 35% to 55% relative humidity before the flooring is delivered or installed, and maintained through installation and after (Provenza MaxCore LVP installation guidelines). Wood trim, doors, and cabinetry carry similar ranges.
If the building isn't being held in that range, here's what we do. Take readings and snap a picture. Send the readings and the product sheet in an email to the GC's Site Sup, the same day.
You're doing two (2) things at once. You're being a good partner by flagging a problem before it costs anybody money. And you're protecting yourself, because when that material peels or gaps, you've got a dated email showing you told them.
This isn't theoretical. In one documented case, a manufacturer denied a flooring warranty claim over low humidity in the building, and the GC, the installer, and the owner ended up splitting the tear-out and replacement three ways. The GC in that case was then advised to start requiring installers to hold the GC harmless for jobsite conditions (LBM Journal, "Who is responsible when humidity damages flooring products?"). Don't be the installer in that story.
If you're also supplying the material, you already have the spec sheets on hand. That's one of the quiet advantages of a sub that handles both materials and labor.
Walk your own work before the GC does, and ask the Site Sup to send items as they find them instead of saving them for the big walk.
The easiest punch list to close is the one that never gets long. That takes two habits.
First, our PMs walk the scopes they own every time they're on site. Anything they see gets texted to the project Foreman right then, with the unit number and a photo. Not written down for later, texted right then. Then every item gets a follow-up on the following day's daily call. A base scuff you fix on Tuesday is a fifteen (15) minute job. The same base scuff on the GC's final list is a line item in Procore, a potential trip back, a photo, etc. You get it.
Second, ask the Site Sup to text you items as they find them. They still need to enter it in their tracking system, but the solution gets a head start. Most Sups will, because it reduces their stress as occupancy approaches. We treat their texts the same as the system messages: print it, distribute it, fix it, photo it.
Industry closeout guidance backs this up: the best practice is an internal pre-punch two to three weeks before the formal owner walk, and a rolling list throughout the job rather than one list at the end (OpenSpace, construction punch lists guide). Subs can run their own version of that without waiting for the GC to set it up.
Do those two (2) things and the forty (40) item list turns into a twelve (12) item list, and the twelve (12) item list is the one you close in a day.
A sub they don't have to think about. Photos on every item, one clean closeout package, and a PM who calls before the Site Sup has to.
For our GC customers who might be reading this: you're closing out an entire project. You've got a tough job, we get it. Our goal is to be the one sub you don't worry about. Photos of every completed punch item, one clean closeout package, and a PM who calls you before you have to call us.
There's a reason this matters more than it looks. A GC is closing out dozens of subs at once, and a sub who reads the closeout requirements ahead of time and sends everything in one polished package takes an entire closeout off the GC's plate (Billd, closeout guide for subcontractors). That's the sub who gets the next bid invite.
More on how we work with GCs on our general contractors page.
Because it's the last thing that happens, and it's the thing that was happening when they decided whether to call you again.
GCs have memories like elephants. They remember companies in two buckets, easy and hard. Punch is the last impression you leave on a GC, and it's the first thing that comes up when your name is on the next bid list. Treat the final punch list like an audition for the next job and you'll hopefully stay in the easy bucket.
If you've got a punch process that works better than ours, we'd like to hear it. Questions or comments to media@questbuildingcorp.com, or contact us.
Does a paper punch packet work if the GC requires everything in Procore?Yes. The crew works from the paper packet and photographs each fix. A foreman or PM who does have a login then closes the items in the GC's system with the photo attached. The GC's record is complete; the crew never touches the software.
What if the Site Sup refuses to approve a change order for damage caused by other trades?Fix it anyway and keep the relationship, but document it: your dated photos showing the damage occurred after your install, your email raising it, and the Sup's response. Then decide with your PM whether the dollar amount is worth escalating to the GC's PM. Most of the time it is not, and the documentation is what protects you on the next one.
How do you handle punch when your crew speaks a language other than English or Spanish?The packet is mostly photos and unit numbers, which is why it works across languages. The written description matters less than the picture of the problem. We have run this with an Albanian-speaking sub with no changes to the process.
Should a subcontractor buy its own temperature and humidity loggers?A handheld meter and a phone camera are enough. Take the reading, photograph the display with the room visible, and email it with the product spec sheet the same day. The point is a dated record, not laboratory precision.
What happens if the GC never sends items during the project and dumps a 300-item list at the end?You still sort it into ours and needs a conversation before printing anything, and you still packet it. A big list is more reason to sort carefully, because the share of other-trade damage on a late list is usually higher, not lower.
Is one item per page really worth the printing cost?For us, yes. A 40-page packet costs a few dollars. One return trip to a Milwaukee jobsite for a skipped item costs a crew's morning plus fuel. The packet has paid for itself more than once.