SitePunch Guides
You walk the job, spot the miss, and text the right sub. Then the photo, the reply, and the final sign-off land in three different places. Nobody gets paid extra for hunting down IMG_4821 among 146 photos. These guides show how to keep punch work moving without turning the GC into the project's full-time reminder system.
Start here
Follow a sample project from the first photo through final approval. No feature parade. Just the work, in the order it happens.
Open the product guideThe series
If you manage buildings through winter
Frozen pipes, ice dams, and quiet leaks in empty units are some of the most expensive problems a building can have. The good news: most of them send a warning first. The bad news: it usually goes to someone who assumes you already know.
If you're preparing a home for market
In a market where buyers can negotiate, unfinished details can become repair requests, price objections, or reasons to move on. A disciplined pre-listing punch list helps you deal with them before the first showing.
If the list keeps growing
The walkthrough is the easy part. The hard part is getting every miss to the right trade, getting proof back, and knowing the fix was actually accepted.
If the crew won't use the software
The best field tool isn't the one with the longest feature list. It's the one your subs can open, understand, and update before they leave the room.
If every update lives somewhere else
A sheet can track a list. It starts to fail when the photos, trade replies, rejected fixes, and final approvals all live somewhere else.
The goal
SitePunch keeps the description, photos, correction, and final review in one record everyone can open from a phone. Less digital archaeology. More finished work.
Start a punch list