01
PPM at the plant
The board by the asset only shows a code when the check is due. The form that opens is the one you attached to that job.
Facilities
Proof the engineer was at the asset.
Planned maintenance, reactive callouts, and plant-room checks — recorded where the work is, not from a van in the car park.
A job ticket is not proof of attendance.
A closed work order can be closed from anywhere. A photo of a sticker can be taken last week. Facilities teams need the visit itself to be the record: who stood in front of the boiler, when, and what they logged before they left.
Same boards. Same scan. Facilities work.
Stationed is not a facilities product. It is one physical-operations platform. These are the jobs it already records.
02
Reactive callouts
A contractor or in-house engineer scans on arrival. The visit is named, timestamped, and ready for the next instruction.
03
Readings that can't be backfilled
Temperatures, run-hours, yes/no checks — submitted from the room, with ranges and incidents if a value is off.
- A named engineer at a signed board bound to one location
- The right portal or task opens from the scan, not from a menu
- One platform with Security, Property, and Contractors — not a facilities SKU
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.