Checkpoints
A checkpoint is a marked location in a property where something needs to be checked or done on a regular basis — a machine that needs servicing, a meter that needs reading, or a sanitary area that needs inspecting. The point is captured via NFC tag, QR code, Bluetooth beacon, or — outdoors — automatically via GPS. People scan it during a route and thereby create a complete record of what was checked, when and where — this also works without an internet connection; the scans are synchronized automatically later (see Offline mode).
You manage checkpoints in the portal in the "Setup" view of a property's Tasks tab (Master data → Properties → select property → "Tasks" → "Setup"). Linking a checkpoint to a physical NFC chip or beacon happens afterwards in the mobile app.
Besides the checkpoint there is the task point: a physical point whose scan does not record a route, but only opens the tasks and forms due there — for example for stations that are only worked through when needed. Task points appear in the same table with their own type.
Table and status
The table lists all points of the property with the columns Name, Type (checkpoint or task point), Internal note, Note and Detection. The Detection column shows as icons which capture methods are set up for the point: QR code (always available — every point has a downloadable QR code), NFC (once a chip is linked and active), Beacon (once a Bluetooth beacon is bound) and GPS (once a location is set and "Capturable via GPS" is enabled). Via the multi-select, the bulk actions Download PDF, Archive and (for archived points) Restore are available — there is no delete; points are archived and can be restored.
Create and edit
The editor opens full-page — the list of all checkpoints with a search field on the left, the form on the right — and edits one point at a time; after saving a new point, the form is cleared so you can create the next one right away. The only required field is the checkpoint name (max. 100 characters). Optionally you add:
- Task — a linked task from the task library, shown to the employee when scanning during a route
- Internal notes — visible only in the portal
- Photo — JPG or PNG, automatically compressed
- Location — a pin on the map. Without any further option, display only (no geofencing; the GPS requirement is the property-wide location lock). With a location set, you can additionally enable GPS capture (see below)
If you switch to another point with unsaved changes or close the editor, a confirmation dialog appears — changes are never lost silently.
Details on the statistics cards (scans 30D, last scan), QR download, templates and configuration can be found under Setting up routes (property). The Active/Inactive status shown there maintains itself automatically: a photo fallback booking ("No checkpoint present") sets the point to Inactive; the next successful scan sets it back to Active.
Capturable via GPS
Checkpoints outdoors can be captured automatically via GPS — without the employee scanning anything. Prerequisites: the point has a location on the map, and the "Capturable via GPS" switch is enabled. You also define the radius within which the point counts as reached (default: 50 m, minimum: 20 m, maximum: 1000 m).
How the capture behaves in the app:
- It only works during an active round — outside of rounds, there is no continuous tracking.
- When the employee enters the radius, the app books the point automatically and shows a short confirmation. The phone can stay in the pocket; the app must be running.
- In the round protocol and in the PDF, the scan appears with the capture method "GPS".
- Points with GPS capture show a corresponding hint in the app's checkpoint list.
:::tip Recommendations for the radius
- Choose the radius generously — GPS is only accurate to a few meters with a clear view of the sky.
- For vehicle patrols (approach by car), choose a larger radius.
- GPS capture is unsuitable indoors — use NFC, QR code, or beacon there. :::
Tasks bound to a checkpoint or route
A task from the task library can be bound to a checkpoint or to a route. The employee then sees the task in the app when scanning or during the route and completes it per occurrence — each run creates its own completion to check off individually.
Bound tasks inherit the rhythm of the route or template and have no series schedule of their own: a custom recurrence rule and the binding are mutually exclusive (see Create Task).
Permissions
:::info Permission To view checkpoints you need the View control points permission. Contact your administrator if you do not have access. :::
| Action | Permission |
|---|---|
| View checkpoints | View control points |
| Create checkpoint | Create control points |
| Edit checkpoint | Edit control points |
| Archive / restore checkpoint | Delete control points |