Log it on the walk. Clear it before the sub gets paid.
PieceWrk builds the daily walk list from what actually got worked, not just what is on the schedule, so you are inspecting jobs with real activity on them. Log a punch item on the spot, attach a photo, and it sits open until a manager verifies it. On a shared project, one open item holds every subcontractor’s payout until the list is clear.
How it works
Walk it, log it, verify it, release it.
- 01
Walk it
The daily queue is built from what got scheduled and what actually got logged as production, not a static site list, so the walk lands on jobs with real recent activity on them.
- 02
Log the item
A punch item is a task with its own priority and, when there is one, a photo attached directly to it: the same record a crew already works from, not a separate app.
- 03
Disposition it
Once it is dealt with, it gets marked redo, make aware, or accept. The call is on the record, not just remembered by whoever caught it.
- 04
Verify and release
A crew member marking something done does not close it. It stays open until a manager verifies it, and on a shared project no payout releases for any subcontractor on it while those items still are.
The daily walk
Production outranks the schedule, on purpose.
A project scheduled for today has nothing built on it yet, so it should not float to the top of the walk list ahead of a job finished yesterday. PieceWrk ranks the queue by what was actually produced first and falls back to the schedule only when nothing has been logged at all.
Projects sitting at the same address group into one stop, so a site with three projects on it gets walked once, not three times. A job with crew on site today carries its own flag, so a defect can get fixed the same day instead of costing a return trip.
Where a punch list usually lives
- A notebook in the truck, a text thread, or a spreadsheet nobody opens between walks.
- A defect gets caught, then forgotten before the next visit to the same site.
- Nobody can tell you which of the last ten jobs still have something open.
In PieceWrk the walk list, the punch item, and the sign-off live in the same record the crew already works from.
Documentation
The video goes in the project, not the camera roll.
The job-walk recorder is built into the app: choose Pre-Job Walk or Post-Job Walk before you hit record. Resolution is capped at 1080p on both iOS and Android, since an uncapped Android camera defaults to 4K and roughly triples the file size for footage nobody watches at that resolution. Narration is optional, though a silent walk misses the point of one. A hard twenty-minute cap keeps a phone left recording in a truck from filling the device, and long files upload resumable, checkpointed as they go, so a dropped connection on a jobsite does not send a long walk back to zero.
A photo attaches to the task or punch item itself, taken on the spot or pulled from the library right on the completion screen. Duplicate uploads get caught by a file hash before they reach storage, a bad-signal upload retries with backoff, and if a later step still fails, whatever already made it to storage gets removed rather than left behind as an orphaned file.
The payout gate
A punch item is a hard block, not a warning.
Releasing a subcontractor’s payout on a project checks two things before a bill can be created: the project has to be marked work complete, and it has to carry zero open tasks, warranty and exclusion items aside. Either gap and the release is refused outright, not surfaced as a note someone can click past.
The check runs against the whole project, so one open item holds up every subcontractor working that job, not only the one who caused it, until the list is clear. That is a project-scoped payout gate for subcontractors, not a per-worker piece-rate deduction.
Common questions
- What is the difference between an Assignment and a Punch Item?
- They are the same task record, split by a kind field. An Assignment is planned work a crew is scheduled to do. A Punch Item is a defect caught on a walk, carrying its own priority, and once it is dealt with, a disposition: redo, make aware, or accept.
- Does an open punch item actually stop anyone from getting paid?
- For subcontractors, yes. Releasing payout for a subcontractor on a project checks that the project is marked work complete and has zero open tasks, warranty and exclusion items aside. Either one missing and the release is refused outright, not flagged with a note someone can dismiss. Because the check runs on the whole project, one open item holds up every subcontractor working that job until the list clears.
- Where does the job-walk video go?
- It records straight into the project through a dedicated in-app recorder, not the camera roll on the phone. You choose Pre-Job Walk or Post-Job Walk before you hit record, and it uploads resumable, so a dropped connection on a jobsite does not send a long walk back to zero.
- Who sees the QC Dashboard?
- Managers and above. It rolls up every open punch item across every project: counts by severity, by project, and by who is responsible, plus how many are sitting in the awaiting-verification state because a worker marked something done and nobody has confirmed it yet.
Bring us a job with an ugly punch list.
That is the one where the difference between a notebook and a record shows up fastest.