Inspection and patrol rounds
A security guard's patrol, a cleaning round, a daily fridge check in a kitchen, a machine inspection. A QR code hangs at each checkpoint; scanning it proves someone was there, and a short form records what they found.
How it works#
- Put a QR label at each checkpoint: fridge 1, back door, boiler room.
- The worker scans the label and picks the result in a form: OK, Needs attention, Out of order.
- Your API logs the checkpoint, the time, the result and the device.
What your API checks#
- The checkpoint belongs to the route of this device (or this shift).
- Optionally, the order and the timing ("the back door was last checked 3 hours ago").
- A result other than OK can trigger your own follow-up, such as an email to maintenance.
Example answers#
{ "status": "ok", "title": "Fridge 1 logged", "message": "Next: fridge 2, freezer" }{ "status": "failed", "title": "Not on your route", "message": "Boiler room belongs to route B" }Settings#
{ "app": "scan2check.com", "settings": { "apiUrl": "https://api.example.com/rounds/checkpoint", "symbols": [ "qr" ], "formData": { "schema": { "result": { "title": "What did you find?", "type": "string", "enum": [ "OK", "Needs attention", "Out of order" ] } }, "showOnce": false } }}Open in configurator โ loads these settings so you can put in your own API URL and generate the QR code.
Watch out for#
- It records a judgement, not a measurement. "Too warm" is what the worker chose, not a thermometer reading. If an audit needs exact temperatures, photos or signatures, you need a different tool, or keep them alongside.
- Who did the check. The app has no user login. Either give each worker their own phone (
deviceId), or have them scan their own badge at the start of the round and let your API remember it for that device. - A photo of the QR is not a visit. Someone could scan a picture of the label. If that matters, compare times between checkpoints in your API, or replace the labels now and then.