One shared list
Everyone works from the same list instead of splitting notes across multiple channels.
QR reporting
Anyone can report a problem with a photo, and every report waits for your review.
Sign-off before closing
Work marked done stays visible until someone responsible reviews it.
The basics
What does SitePunch do?
SitePunch carries every fix from start to finish: someone reports a problem, the right person gets a link, fixes it and shows proof, and nothing closes until you sign off. Each issue, photo, message, and status update lives in one record.
Who is it built for?
General contractors and remodelers running punch lists and subs, and property and maintenance managers who take repair requests and coordinate vendors.
What problem is it solving?
It solves the handoff problem where the list lives in one place, photos live somewhere else, and updates are buried in messages. Each issue lives in a single record so everyone can see what's still open, what's been done, and what still needs review.
Is it only for the very end of a project?
No. It fits final punch work, active renovations, warranty callbacks after handover, and the day-to-day maintenance of a building.
How it works
How is a project created and shared?
You create a project for a job or a building, add issues, and give people access with their phone number. Then you share the project link and everyone opens the same list on their phone.
What does a sub or vendor see when they open it?
They see the open items that are theirs, with descriptions, photos, messages, and status. If you tag items by trade, each person sees only their own work.
How do photos and messages work?
Each item can hold marked-up photos and messages inside the same record. That makes it easier to show the location or the expected fix without separating the image from the explanation.
What happens when someone finishes an item?
The work can be marked done, but it doesn't disappear right away. You review and verify it, or send it back with a note, before it comes off the active list.
Ask AI
What is Ask AI?
A second opinion on an item. In the item's Internal tab, type a question and tap the AI button. It looks at the item, its photos, and its messages, and suggests the likely fix, whether the discussion is on track, whether a price looks reasonable, and the next step.
Who can use it and see the answers?
The project owner and collaborators. Answers stay in the Internal tab, which contractors and vendors never see, unless you choose to share an answer with everyone.
What does the AI see?
Your question and the item's context: the project name and description (plus its city, state, building type, and year built, if you added them), the item, up to 8 photos, and recent messages. People are identified only by role, never by name, phone number, or email. AI runs only when someone taps the button.
Is our data used to train AI?
No. Ask AI runs on Anthropic's Claude. Under Anthropic's commercial terms, our requests aren't used to train its models and are deleted within 30 days unless they're flagged for a possible policy violation. The privacy policy has the details.
Can I rely on its prices?
Treat them as estimates. Prices vary by region and change over time, and the AI can be wrong. Use it to decide when to ask questions or get a second quote, and confirm prices, permits, and code requirements with licensed pros.
QR code reporting
How does the QR code work?
Turn on a project's QR code and print it. Anyone who scans it can send a report with a photo, a circle around the problem, and a note. The report lands in the project's Incoming tab.
Who can report? Do they need an account?
Anyone who scans the code: tenants, staff, visitors, or the owner of a finished build. They don't need an account or an app, and their name is optional.
Do reports turn into work automatically?
No. Each report waits in Incoming until the owner or a collaborator accepts it as an item or dismisses it. Nothing reaches a sub or vendor without that review.
Does it work for warranty callbacks?
Yes. A general contractor can leave the QR code with the owner at handover, so warranty issues land in the same project instead of arriving by phone and text.
What if someone misuses the code?
Generate a new one and the old one stops working right away. Every report also passes an automated bot check.
Access and daily use
Do subs and vendors need usernames and passwords?
No. SitePunch uses phone-based sign-in with one-time codes, so opening a project is quick and nobody has to create or remember a password.
Is SitePunch meant to replace spreadsheets and text threads?
Yes. The goal is to stop forwarding photos, copying notes, and maintaining a separate running list. SitePunch keeps the history of each issue in one place.
Can it be used from a phone?
Yes. It's designed around phone use, so you can add items, review reports, upload photos, and send messages from the job site or the building.
Where does SMS fit in?
SMS is used for user-requested one-time login codes. It isn't a promotional texting or marketing platform.
Still have questions?
Use the contact page if you need help with account access, project workflow, or a product-specific question.