Feature · Checklists & proof of work
Prove what happened, without the paper.
Checklists that behave like real forms, reusable templates so every technician follows the same routine, before-and-after photo galleries, and an on-screen signature captured at the door.
What you get from checklists & proof of work
A checklist is a form, not a to-do list
Each item is a checkbox, a yes/no question, or a free-text or number answer — a serial number, a meter reading, a pressure figure. Mixing types on one checklist is normal.
Save it once, reuse it forever
Build a standard inspection or install routine once, save it as a template, and drop it onto any future job in a click. Recurring jobs carry the structure forward with answers cleared.
Photos and signatures as evidence
Before/after photos land in a grouped, captioned gallery with a lightbox — not a flat attachment list — and "Collect Signature" opens a real signature pad the customer signs on screen.
Three steps, start to finish
Build the checklist on a job, or add one from a saved template.
The technician works through it on the mobile app, attaching photos as they go.
Collect the customer's signature on the device before leaving; it's saved to the job as an attachment.
Straight answer
What this doesn't do
Every limit below was checked against the code. We'd rather you find them here than three weeks after migrating.
- There's no general form builder — checklists attach to jobs, not to standalone forms you can send out.
- Checklist completion isn't enforced before a job can be closed.
- No conditional logic: an item can't appear based on the answer to another.
Common questions
No — completion isn't enforced. The checklist records what was answered and what wasn't, but nothing blocks a job from being closed with items outstanding.
Ready to run your business on it?
Start a 14-day trial today. No credit card, no sales call, no implementation project.
14 days free · No credit card required · Cancel anytime