01
Due-window checks
Schedule fire, HACCP, or opening procedures against the board. The code only exists when the work is due.
Compliance
Proof the statutory check was done.
Audits fail on backfilled logs. If a check can be completed from the office, it isn't evidence. Compliance on Stationed is the same scan as every other job: place, time, person, then the form.
A completed form is not a completed check.
Most compliance software captures the answers. It does not capture whether the person was in front of the thing they were answering about. Stationed treats the visit as the first field of the record, then opens the checklist you already designed.
Same boards. Same scan. Compliance work.
Stationed is not a compliance product. It is one physical-operations platform. These are the jobs it already records.
02
Forms with consequences
Numbers, temperatures, yes/no, photos. A reading outside range can raise an incident without a supervisor noticing first.
03
A log you can hand over
Every entry carries who submitted it, where, and exactly when. Administrative changes sit in a separate audit log.
- The check cannot start until the board in that location is scanned
- One product — not a 'compliance edition' with a different price list
- Operations is the usual plan: five sites, fifteen boards, unlimited users
The workflow changes. The evidence standard doesn't.
A patrol, a kitchen check, a contractor callout, a care visit. The job on the phone changes. The record does not: the right place, the right time, the right person.
We start with one site and one check. The rest of the platform is there when you need it.
Kitchen first
Start with one kitchen.
We set up the walk-in check with you. A browser tab on a screen you already own is enough for the first log.
Other kinds of physical work.
Put a board where the work happens.
Register a site, enrol a board, and the next person who scans it becomes a record you can stand behind.