Inspections and checklists with photo evidence
Checklists completed on a phone at the site, with photos attached to the check they prove and results the office can read the same day.
The evidence and the record live apart.
A checklist is filled in on paper and photographed later, if at all. The photos land in a camera roll with nothing saying which site they belong to. Results get typed up on Friday, by which time the failed item has been open for four days. When somebody asks to see the evidence for one specific check, finding it is an archaeology exercise.
Attach the proof to the check.
The checklist becomes rows against a site and a date. The inspector works through it on a phone, marks each item pass or fail, and takes the photo from inside the item so it is stored against that check and no other. If the site has no coverage it saves anyway and syncs later. The office opens the inspection and the evidence is already there, on the row it belongs to.
What gets built
Questions
Can we change the checklist ourselves?
Yes. Ask for the item, the wording, or the order you want and publish it. Every change is a version you can preview first and restore if the checklist you had was better.
What happens at a site with no coverage?
The answers and the photos are held on the device and go up when a connection returns. The inspector works straight through the checklist and nothing waits on a signal.
Who can close a failed item?
Whoever you decide. The usual shape is an inspector who records the result and a supervisor who closes it, set as roles and checked on the server every time. Sign-off is the account that saved the inspection and the time it happened.
