Checklist 101: The simple way to standardise work (and actually get it done)

A digital list of steps your team completes on a phone or tablet, with instant results available in your web console (PC Control) for oversight, reporting, and audits.

Supported inputs include: photos, text/comments, barcode scans, yes/no, customised checkboxes, dropdowns, on-screen signatures, image overlay, and voice notes—kept paperless and centralised.

1) Standalone checklist

You open the Checklist module and complete it whenever you need it. This is ideal for routine tasks that are time-based or team-driven rather than triggered by an event.

Use it for: daily opening/closing checks, end-of-shift handovers, weekly equipment spot checks, hygiene and housekeeping routines, ad-hoc quality inspections.
Why it works: simple to find, simple to complete, and simple to review.

2) Attached checklist

This fires automatically because something else happened—for example, when an incident is logged, when a guard tags a patrol point, or during an access-control action such as scanning a driver’s licence or vehicle licence disc. The right steps appear at the exact moment they are needed.

Use it for:
- Incidents: trigger the correct first actions per incident category.
- Patrols: show location-specific checks at each tagged point.
- Access: prompt the right process while scanning IDs or vehicle licence discs at gates.

Combine them when it helps

You can also configure a checklist to be both Standalone and Attached—available on demand and fired by a trigger—so teams can run it ad-hoc while still getting the automatic prompt at critical moments.

- Pick Standalone when timing is routine (daily, weekly, end-of-shift) or you need to complete ad-hoc checklists.
- Pick Attached when timing depends on an event (incident created, patrol point tagged, access scan performed) and you want the checklist to appear automatically within that workflow.

If in doubt: pilot it as Standalone to get the wording right, then attach it to the live workflow once proven.

- Security patrols: attached micro-checks at each NFC tag; standalone end-of-shift handover.
- Facilities and campuses: attached safety steps when logging a maintenance incident; standalone daily opening checks.
- Access control: attached verification steps when scanning driver’s licences or vehicle discs at entry.

- How fast do results show in PC Control? Instantly, subject to connectivity quality.
- How long are records kept? Up to 5 years (with options to archive).
- Can we build our own checklists? Yes—create and tailor them yourself.
- Who can see the reports? You decide the users and their access levels.
- Do you support photos, signatures, barcodes, and voice notes? Yes—all supported.