Manage Checkpoints
:::info Download PDF LiteLog Proof of Location — Verifying Presence with NFC & QR :::
On this screen, you see all checkpoints of the current property. You can edit existing checkpoints, create new ones, assign NFC tags, and print QR codes. You can access this view via More → Settings → Tasks → "Manage checkpoints".
:::info In the App This feature is exclusively available in the mobile app. In the web portal, you manage checkpoints through Property Details → "Tasks" tab → "Setup" view. :::
Features at a Glance
Checkpoint List
All checkpoints of the selected property are displayed in a searchable list. Each entry shows the name, type, and the NFC status. There are two point types:
- Checkpoint — for routes as well as for tasks and forms at the point: in a running route that includes the point, a scan counts as route evidence and additionally opens the due tasks and forms; if no route is running, the scan only shows the tasks and forms at the point and does not start a route.
- Time tracking — for time recording; a scan checks in or out.
Points that were previously created as a “task point” remain usable and behave like any other checkpoint — including in routes. You link them to an NFC chip just like a checkpoint.
Create Checkpoint
Using the create button, you can add a new checkpoint:
- Name — Unique name for the checkpoint
- Instruction — Text shown to employees when they scan
- Internal note — visible to management only
- Photo — image of the checkpoint (e.g. where the tag hangs)
- Location — position on the map ("My location" or move the map)
- Task — an existing task that appears when scanning (see Binding tasks to checkpoints)
Edit Checkpoint
Tap on a checkpoint to edit its details. The editing options depend on whether the checkpoint is assigned to an active route:
- Checkpoints in a route template whose series start is still in the future: only notes can be edited, no archiving
- All other checkpoints: all fields can be edited, archiving is possible (archiving also detaches the NFC chip from the point)
Write an NFC Chip
The linking wizard guides you through the chip assignment in four steps: choose the type (checkpoint, login card, or time-tracking point — the point of type "Work time"), choose the target (with the "Only without chip" filter; via “+” you create a new checkpoint directly), write the chip, done. When writing:
- The app verifies what was written by reading it back and then, where possible, locks the chip against overwriting (read-only). If only the locking fails, the assignment remains valid nonetheless.
- If you remove the chip too early, the process deliberately aborts — nothing is half-assigned. Simply hold the chip steady again and retry.
- A chip that is already assigned triggers the dialog "Chip already linked — overwrite?".
- After success, "Link another" offers to write the next chip with the same type right away — handy when equipping an entire property.
Replacing a chip (lost or defective)
If a checkpoint's chip is lost or defective, simply give the point a new one: open the linking wizard, choose the type “Checkpoint”, pick the affected point as the target (switch off the “Only without chip” filter for this) and write the new chip. The old chip ID is detached from the point in the process; until then, the point's QR code keeps working. A chip cannot be assigned or detached in the portal — there, the checkpoint card only shows the NFC state. Archiving the point also detaches the chip.
What is on the chip?
There is no patrol information on the chip. The app writes only a short LiteLog marker, verifies it by reading it back and locks the chip against overwriting. The chip ID is assigned to the checkpoint in LiteLog, not the other way round. What has to be done at the point is maintained at the checkpoint or the patrol; the chip is not affected. That is why you can give a chip to another point at any time, and a point keeps its tasks when the chip changes.
Third-party, locked and unformatted chips
You do not have to buy chips from LiteLog. When binding, the app distinguishes four cases:
| Chip | What the app does |
|---|---|
| Unformatted (factory-fresh) | Android formats it, writes the marker and locks it in one step. iOS cannot write unformatted chips; use an Android device for those. |
| Writable | Write the marker, read it back, lock. |
| Locked, with LiteLog marker | Linked without a prompt, for example a chip from a previous property. |
| Locked or third-party, without LiteLog marker | The app asks "Chip might cause problems – This chip cannot be written reliably. Reading it later may cause problems. Continue anyway?". With Continue it binds the chip ID to the point. |
A third-party chip bound this way works when scanning in the open app. On Android it does not open the app by itself from the background because it lacks the LiteLog marker; the guard opens the app and holds the phone to the chip. Chips from another system can be reused this way as long as they can be read via NFC.
Chips on metal
On metal surfaces the base shields the radio field. Use on-metal chips with a ferrite layer there, or stick the chip onto a non-metallic surface next to it. Check that a chip reads reliably with a scan right after mounting it.
Print QR Codes
Using the QR print wizard, you select multiple checkpoints (the selection persists while searching and paging) and then share the QR codes as a PDF — e.g. for printing and laminating. In the portal, the same download is available from the checkpoints table.
Good to Know
:::tip Note The name of a checkpoint must be unique per property. The app automatically detects already used names. NFC tags can only be assigned to one checkpoint at a time — if a tag is assigned to a new checkpoint, the previous assignment is automatically removed. :::
Permissions
| Action | Permission |
|---|---|
| View checkpoints | View control points |
| Create checkpoint | Create control points |
| Edit checkpoint | Edit control points |
Link a Beacon
In addition to NFC and QR, you can link a Bluetooth beacon. Open the wizard via More → Settings using the "Link beacons" card (alternatively under Settings → Tasks → "Manage beacons").
- Choose type — Checkpoint or Time tracking.
- Find beacon — the app scans for nearby beacons and shows them with their distance.
- Set distance — you define how close the employee has to be to the beacon for it to trigger: by measurement ("Right where you are standing") or as a preset.
- Done — the beacon is programmed and linked to the target. "Disconnect beacon" removes the link again.
How a linked beacon behaves afterwards:
- Starting a route / checking in: beacon proximity produces a suggestion ("Start round?" or "Check in?") that the employee confirms — here the app never starts anything on its own.
- During a running route: once the route is started, the app records the linked checkpoint automatically on approach — no tapping needed. Brief signal spikes do not trigger it, and the same point is recorded again automatically only after 5 minutes at the earliest.
You maintain your beacons' namespace in the portal under Settings → Devices → Beacons.
:::info Permission To link a beacon, you need Edit control points or Edit employees. :::