Checklists that know they’re done.
Build your own recurring checklists, for one department, several or everyone. Staff do them on the phone, with the photo, the note or the number each item asks for. A check that is not done becomes overdue, then missed, and raises an alert.
30 minutes, on your own rooms and departments.
- Daily, chosen weekdays or a one-off period
- A photo or a note required per item
- One grouped alert per missed checklist
Three things to try
Each page has a small demonstration you can use.
Also in Checklists
Part of the module today, without a page of its own yet.
- Checklists in Automations: a checklist that is overdue or missed, or a critical item that fails, can start an automation.
Works with
Questions
Who can a checklist be assigned to?
To one or more departments, or to everyone. A checklist is Shared, or Per person.
How do we know a check was really done?
An item can require a photo or a note. “Complete checklist” stays disabled until the required evidence is there.
What happens when a checklist is not done?
After its due time it is overdue. If it stays open it is marked missed, and each checklist raises one grouped alert.
Bring one paper checklist to the demo.
We build it in Livion with you, and you see what the same check looks like on a phone.