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 via the "Checkpoints" section in the property menu (Master data → Properties → select property → "Checkpoints"). Create at the top of the list and Create checkpoint in the section's "+" menu open the form directly; the same menu holds Create area and Create with AI. Linking a checkpoint to a physical NFC chip or beacon happens afterwards in the mobile app.
Every checkpoint can be part of a route and carry tasks or forms — there is no separate point type for tasks. What a scan does depends solely on whether a route is currently running: in a running route that includes the point, the scan records the point and additionally opens the tasks and forms due there; if no route is running, the scan only shows the tasks and forms at the point — no route is started. Points that were previously created as a “task point” remain usable and behave like any other checkpoint. In the app you create checkpoints via the NFC wizard or the beacon wizard.
Table and status
The table lists all points of the property with the columns Name, 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 — via “Add task” you pick an existing task of your account, or you create a new one directly in the task side panel via “Create task”. When editing, the editor lists all open tasks bound to the point, each with an edit button
- Detection — shown on the right under the properties already when creating: the QR code is active, NFC, beacon and GPS sit next to it as chips. Clicking GPS opens the location section; NFC chip and beacon are paired in the app once the point is saved
- Internal notes — visible only in the portal; the field shows "+ add" until the first entry
- Photo — JPG or PNG, automatically compressed
- Location — a pin on the map. Without any further option, display only (no location check; the GPS requirement is the property-wide location check). With a location set, you can additionally enable GPS capture (see below)
Enter in the name field creates or saves the point. If you click "Create task" on a point that is not saved yet, the portal saves the point silently, reports "Checkpoint saved" and switches the address to the new point; the task is then created at this point.
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 (NFC, QR, beacon or GPS) sets it back to Active. The status only affects the NFC indicator in the Detection column — neither the coverage nor the linked tasks.
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. :::
:::tip Existing or third-party NFC chips A GPS point needs no hardware: no chip, no sticker. Conversely, an NFC chip has no GPS; the position always comes from the phone. You can reuse chips you already have, including locked ones or chips from another system. How the app binds them is described under Third-party, locked and unformatted chips. :::
Binding tasks to checkpoints
A task can be bound to one or more checkpoints — from the checkpoint (field “Task”, see above) or from the task itself (property “Checkpoints” in the task side panel). A point can carry several tasks; the checkpoint editor shows all open bound tasks. There is no binding to a whole route in the portal — the “Task” field in the route wizard is a free-text instruction for the people performing the route, not a link.
This is how a bound task behaves:
- Scan in a scheduled route: scanning the point marks the task as completed for this run — unless it requires photo or form evidence; in that case the employee completes it in the “Due at this checkpoint” overview with a photo or form.
- Scan in a free round or without a running route: the scan opens the task; it is completed by checking it off, counted for the day of the scan.
- Not completed: the task stays open. There is no “missed” status for tasks, and the route does not become incomplete because of it; the gap shows up in the “Done (30d)” rate of the task list.
- Without a scan: the task can also be completed without a scan — in the portal and in the app. If that should not be possible, enable “Complete only at checkpoint” on the task: the app then blocks completion until a linked point is scanned; in the portal a completion is saved with the note “completed without scan”.
- Series: bound tasks have no series schedule of their own; a recurrence rule and the binding are mutually exclusive.
- Archiving the point: the binding remains in the task. Remove the checkpoint from the task beforehand so that no orphaned link is left behind.
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 |