Voice + photo capture during the walkthrough. Trueleveler transcribes, clusters items by room, tags trade and severity, attaches the photo with location metadata, and auto-routes each item to the responsible subcontractor with a deadline. The punch list writes itself between the walk and the next coffee break.
Three steps on the mobile app. Total field time on a 200-unit residential floor: ~30 minutes. The desk work that used to take a full afternoon — transcribing notes, organizing by room, assigning to subs, sending the punch list email — happens automatically while you walk to the parking lot.
Take a photo. Hold the mic. "Unit 4B kitchen — cabinet door misaligned upper left corner, also baseboard caulk gap at the dishwasher." Geotag + EXIF lock the location. Two items captured in 6 seconds.
The engine clusters captures by inferred location (voice cue + GPS + previously-walked rooms). One walk produces 80–200 individual items, grouped into 30–50 room-level cards for review.
Each item gets tagged with trade (cabinetry, paint, drywall, HVAC), severity (cosmetic / functional / blocking), and the assigned sub based on the project's vendor directory. Routed to Tasks with a deadline (default: 7 days for cosmetic, 3 days for functional, 24 hours for blocking).
One captured walk produces a structured punch list per floor, sorted by location, with photo evidence and trade-routing already done.
A punch list grouped by sub, by floor, by severity — with photo evidence and deadline per item. The sub gets the email automatically (or PDF, their preference). The PM gets a project-wide dashboard showing punch density by floor, by trade, and by sub-completion-rate.
Before this engine, the punch-list workflow was three jobs that one person had to do:
Walk every unit, every common area. Scribble on a clipboard or type into a tablet. Phone photos in the camera roll, hopefully captioned. Mental note: which trade owns each item.
Transcribe handwritten notes. Match photos to items. Type into a spreadsheet. Group by sub. Set deadlines. Forget half of what you saw because you didn't write it down clearly.
Email each sub their list. Copy the PM. Set follow-ups. Track completion in a separate system. Send reminders before the walk-back.
Jobs 2 and 3 disappear. The engine clusters, routes, sets deadlines, and emails the subs while you finish walking. The PM reviews the list when they get back to the trailer — not the next afternoon.
Times above are typical for a residential mid-rise (200-300 units). Smaller jobs scale down proportionally; healthcare and lab work scales up because of code-driven items per room.
Punch items live as Tasks in the project's tracker. Each sub gets a per-sub view (their items only). Each item gets:
Punch List is a closeout-phase engine. Its output feeds two downstream chains: the closeout package and the sub-vendor scorecard.
Capture works fully offline. Photos and voice notes save locally; sync happens when connectivity returns. Most walkthroughs in concrete/steel structures lose cell deep inside — this is the expected case, not the edge case.
~85% on first-day deployment, ~93% after the engine learns your project's specific vendor mix and naming conventions. The PM can override trade assignment with one tap on any item. Wrong assignments don't email the wrong sub — the engine flags items it's unsure about for PM review before routing.
Both. Same engine, different routing rules. The owner-rep mode tags items but routes to the GC PM rather than directly to subs. The GC reviews and dispatches. Useful for owner-side reps who want their walk to be authoritative without bypassing the GC's command structure.
Export-only for v1. Routes punch lists as PDF + structured CSV that you can drop into Procore's Inspections module or Autodesk Build's Issues. Direct API integration with both is on the v4.2 roadmap.
Bring an actual walkthrough to a 15-minute call. We'll capture it live on screen and generate the routed punch list. You keep the output and the routing data.
Start free — 14 days, no card →