Punch list software
Punch list software where every fix comes back with photos
RTI is punch list software where the list is the work a reviewer sent back with a written reason, and each fix is a re-inspection that cannot be submitted without its photos. The sent-back original stays on the record beside the fix.
- Sent back with a written reason
- Fixes re-inspected through the Photo Gate
- NCRs close on an approved re-inspection
- Drywall ding at bath door Pass
- Cabinet door realigned Pass
Why punch items reopen after they’re marked done
Done, by a status change
An item is ticked closed on a list, and nobody can tell from the list whether the work was fixed.
Notes nobody can act on
“Touch up paint, second floor” reaches the crew with no wall, no photo and no reason.
Lists that disagree
Three versions of the list circulate by email, and the owner’s walk finds what each of them missed.
With RTI
- The reason travels with the item
- The fix is a photo-gated re-inspection
- Both kept in the tag’s history
A fix is not a status change in RTI: it is a new inspection of the same tag, and the Photo Gate checks it like any other.
From sent back to fixed, on the record
Send it back with a reason
On the review board, a reviewer sends the inspection back and has to write why. The reason reaches the crew word for word, by email and in the app.
Mark the photo
The reviewer can draw on the crew’s own photo to show exactly what to fix. The markup shows as Rework required on the tag’s page.
The crew sees it as theirs
Sent-back work lands in the submitter’s Sent back to you list with a Fix button, and stays there until a newer inspection of that tag is submitted.
Fix and re-inspect
The Photo GateThe fix is a new inspection of the same tag. It goes through the Photo Gate like any other, so it cannot be submitted without its required photos.
Track the serious ones as NCRs
A nonconformance gets an assignee, a due date and a severity, and it can be closed only with a linked, approved re-inspection of the same tag when the NCR names one.
What it doesn’t do
- It has no separate punch item. The list is the inspections sent back for rework; a defect that needs an assignee and a due date becomes an NCR.
- It does not pair before and after photos. The sent-back original and the re-inspection both stay in the tag’s history.
- It does not judge the fix. The gate counts the photos the checklist needs; whether they show the work is right is the reviewer’s call.
How to judge any punch list tool
Check what it takes to close an item
If a status dropdown is enough, your re-walk is the verification step and you will do it more than once.
Check how locations are recorded
Free-text locations are hard to walk and impossible to roll up. Structured locations, like site, building, floor, zone and inspection point, show where the open rework sits.
Ask what the owner sees
A read-only client portal keeps the owner informed without giving them your internal board or a weekly email you have to write.
Ask where the fixed work ends up
The passing re-inspections, with their photos, are part of the handover record. If they live in a separate tool, someone re-types them.
Three moments it answers
Use case 1
A ding at the bath door
When a reviewer sends back a unit’s punch walk, the crew gets the written reason and any marked-up photo, and the item waits in their list until the fix is submitted.
Use case 2
The owner’s walk
When the owner’s rep opens the client portal, they see approved inspections only, so a fix shows up there once a reviewer approves it.
Use case 3
A defect that needs an owner
When a defect needs someone named and a deadline, a reviewer raises an NCR, and it closes only on an approved re-inspection.
Questions about punch list software
6 answers
- What is punch list software?
- Punch list software tracks the work still to fix before a job is handed over, from the moment it is found until the fix is accepted. In RTI, the punch list is the inspections a reviewer sent back, each with a written reason, and each fix is a re-inspection that has to carry its photos.
- How does a punch item close in RTI?
- The crew submits a new inspection of the same tag, and the Photo Gate refuses it until the checklist’s required photos are attached. The sent-back item leaves the crew’s list once that inspection is submitted, and a reviewer approves the fix on the board.
- Can a punch item have an owner and a due date?
- A sent-back inspection goes back to the person who submitted it. For an assignee, a due date and a severity, raise an NCR: it moves through its own statuses, every move is written to the activity log, and it closes only on an approved re-inspection.
- Can I export the punch list?
- Yes. From the review board, members with the export permission download a punch list CSV of the sent-back inspections in view, with the tag, the checklist, who sent each one back and when, and the written reason.
- Does the owner see the punch list?
- Not item by item. On the Company plan, the client portal shows approved inspections only, with a count of inspections sent back for rework on each project, so the owner sees each fix once a reviewer approves it, along with the NCRs on their projects.
- Is the punch list in the turnover package?
- The package holds approved inspections, so it carries each passing re-inspection rather than the list itself. Packages built from Reports or the client portal also print the NCR register, showing which NCRs were closed by an approved re-inspection.
Close your next punch list with proof
The punch list is the last thing the owner sees you do. It is worth having the record show that every item was fixed, not just marked.
30-day trial · No card required