The complete workflow
One list. Three states. Zero group-chat archaeology.
SitePunch is a phone-first punch list app for general contractors, owners, and trades. Each issue keeps its photo, conversation, status, and review in one record. The crew reports the work; the owner decides whether to accept it. That small separation keeps “done” from meaning five different things.
- 01Active: somebody still needs to act
- 02Review: the trade reported the correction
- 03Complete: the owner verified it
Step 01
Create one project for one job
From Projects, choose New project. Use the name people already call the job—an owner name or familiar site label—and add a short description of the handoff. “Project Alpha” may sound official, but three months from now it mostly sounds like a riddle.
SitePunch gives the project one persistent link. That URL is the front door for the owner and every approved participant, so you do not need a fresh spreadsheet, PDF, or text thread every time the list changes.
Step 02
Add one observable issue at a time
Open the project and choose New item. Add the reference photo, write the correction as a plain-language task, and select the trades that should see it. SitePunch also lets you paste a copied image and mark up the detail in red before saving it.
Keep each item to one condition that can be independently finished and reviewed. “Patch the wall, swap the outlet, touch up the trim, and maybe look at that hinge” is not one punch item. It is a small committee meeting wearing a task title.
Step 03
Give the right people the right access
Choose Add contractors, then add the participant's U.S. phone number, a nickname you will recognize, and a role. Contractors work through existing tasks. Collaborators can add tasks too. Viewers can read the project without changing it. You can also limit someone to Painter, Electrician, Flooring, or another task type instead of handing them the whole list.
The current product allows up to three active access numbers on a project and five across an account. After you save access, share the project link yourself. On first entry, SitePunch verifies that approved phone number with a one-time SMS code—no reusable password for somebody to forget on the dashboard of a truck.
Step 04
Run the job from three honest states
Every participant opens the same live project. Active holds work that still needs action. Review holds work a contractor has reported finished. Complete holds items the owner has accepted. The task-type filter trims the view for a trade without creating a second version of the list.
When a contractor chooses Mark done, they can attach an optional completion photo. Their item moves to Review rather than quietly vanishing. When the owner marks an item done themselves, it completes immediately because the person doing the work and the person approving it are the same account.
Step 05
Verify the correction—or send it back with a reason
The owner opens Review and compares the original condition with the completion evidence. Verify item accepts the correction and moves it to Complete. Reject item requires a note and sends the task back to the active workflow, so the contractor knows what still misses the mark.
This separation matters: “done” is the contractor's progress report; “verified” is the owner's acceptance decision. Combining those two clicks makes a punch list look faster right up until somebody asks who actually approved the fix.
Step 06
Close the item without losing the record
Verified work remains available under Complete with its photo, comments, created date, completion date, and the people attached to those actions. The active list gets shorter without erasing the trail that explains how it got shorter.
That is the whole SitePunch loop: capture the condition, route it to the right people, collect the fix, review the evidence, and preserve the decision. It is not glamorous. Neither is searching 146 photos for the one baseboard gap you swear you documented on Tuesday.
▸Comments
No comments yet.