Quality checks
Written By Ignacio
Last updated 2 days ago
Quality checks are the manager's review queue. Completed jobs land here for a look before they're signed off, so problems get caught by you rather than reported by the customer.
It's Reports > Quality checks.

1. Needs review
The default view and the working queue: completed jobs nobody has looked at yet.
The point is to review the evidence, not the job. Photos attached, checklist ticked, notes making sense. A job with no photos and a blank checklist is the one to ask about.

2. Approved
Jobs already signed off. Your record that someone actually looked, which matters when a complaint arrives a month later.

3. All
Everything regardless of state, for when you're looking for a specific job rather than working the queue.

Making it work
Quality checks are only as good as what technicians attach, which means the two upstream habits matter more than this page does:
- Checklists on every job, attached automatically from Settings > Price Book so nobody has to remember.
- Photos before leaving site, on anything that could be questioned.
With those two in place this page takes a few minutes a day. Without them there's nothing here to review and the queue is theatre.
A realistic routine
Work Needs review once a day, at the end of the day. For each job: photos there, checklist complete, anything odd in the notes. Approve the good ones, follow up the rest with the technician while they still remember the visit.
Waiting a week means asking someone about a house they can't picture.
Tips and gotchas
- Review daily, not weekly. Memory fades fast.
- You're reviewing evidence, not work. No photos means you can't check anything.
- Automate checklist attachment, otherwise this queue slowly empties out for the wrong reason.
- Approved is your defence when a customer complains a month on.
Next up: Estimates