Perform Route
You see your upcoming routes in the task feed right on the dashboard — together with your other tasks. Via "Show all" you open the full daily agenda. Select a route to start it and work through the associated checkpoints.
:::info In the App Performing routes is only possible in the mobile app. You can plan and analyze routes both in the web portal and in the app (see Manage Routes (App)). :::
Two Kinds of Routes
LiteLog supports two kinds of routes — clarify with your site manager which kind applies to your shift:
| Type | Who plans it? | When do you start it? | How does it end? |
|---|---|---|---|
| Scheduled route (template) | Site manager or admin in the web portal or in the app | Tap it in the task feed on the dashboard — or simply scan the first checkpoint | Automatically once every checkpoint is scanned or marked as not present |
| Free route | You, ad-hoc | Via "Start ad hoc" (appears when nothing is scheduled for today) or manually from the route selection | Manually via the "Finish" button |
Scheduled routes have a predefined checkpoint list and are the standard shift format. Free routes are useful for additional inspections, special checks after alarms, or ad-hoc rounds.
If you forget to finish a free round manually, the system ends it automatically — once the time configured on the property has passed without further activity (default 60 minutes, adjustable from 30 to 1440 minutes under Set Up Rounds (Property)). The time of your last action is recorded as the end, not the moment of the automatic finish.
Automatic Start by Scanning
You do not necessarily have to start a route from the task feed: simply scan a checkpoint, and the app automatically starts the matching route.
- If the point belongs to a due scheduled route, that route is started.
- If there is no matching one but another scheduled route is due, that one starts.
- Otherwise, a free route begins with the scan as its first entry.
Nothing is lost after the fact either: every scan that falls into a scheduled route's time window and belongs to its checkpoints is automatically credited to the scheduled route — even if it was recorded as part of a free check.
Multiple Devices, One Route
A scheduled route can be completed by several people together: if colleague A scans points 1–3 and colleague B scans points 4–6, the server recognizes the complete coverage and finishes the route automatically. When you open a scheduled route, the app shows scans already recorded by other devices, so you only walk the remaining points.
Features at a Glance
Task Feed & Agenda
The task feed on the dashboard and the daily agenda ("Show all") show the status of each route:
| Status | Meaning |
|---|---|
| Pending | Route is still pending |
| Running | Route has been started |
| Completed | All required checkpoints have been scanned |
| Missed | Time window has expired without all checkpoints being scanned |
If you are near a beacon, the app can also actively suggest starting a round. If you decline the suggestion, it will not reappear for that route for 30 minutes. You set up a time-based reminder for upcoming routes in the portal via the automation rule "Round starting soon".
Scanning Checkpoints
During an active route, you scan the checkpoints via NFC tag or QR code. The app remembers your last used method and offers it as the primary button next time; in addition, swipe gestures work everywhere — swiping left starts the NFC reader (iOS), swiping right the QR camera. The QR scanner offers a flashlight and zoom levels for hard-to-reach codes.
If a checkpoint is linked to a Bluetooth beacon, the app records the point in the running route automatically as soon as you approach it — you don't have to tap anything. A brief signal flicker is not enough (the proximity has to last a few seconds), and the same point is recorded again automatically only after 5 minutes at the earliest.
If a checkpoint is set up as "Capturable via GPS", the app likewise records it in the running route automatically as soon as you enter the configured radius — the phone can stay in your pocket, but the app must be running. The app shows a short confirmation, and the protocol lists the capture method as "GPS". Such points carry a corresponding hint in the checkpoint list. Outside an active round, there is no GPS capture and no continuous tracking.
For each scanned point, the timestamp and optionally the GPS location are recorded. You can also take photos as evidence — these are saved together with the scan result. A successful scan confirms itself with a vibration and a green flash of the screen edge; rejected scans (e.g. wrong order) respond with a double vibration and a red edge.
Tasks and Forms at the Checkpoint
After every scan, the app checks what is due at that point and, if needed, opens the "Due at this point" overview:
- Linked tasks are completed as a checklist right in the checkpoint list — with a mandatory photo as evidence where required.
- Forms assigned to the route or the checkpoint type are filled in right after the scan.
- The floating camera button lets you create an incident at any time — with the last scanned checkpoint already preselected.
If nothing is due at a point, no overview appears and you continue the route right away.
Checkpoint List
Through the detail view, you can see all checkpoints of the current route with timestamps and scan status. Mandatory points carry their sequence number, completed points a "Completed" badge. This helps you keep track of which checkpoints have already been scanned.
Order
If order control is enabled for the route, it applies to the points marked as mandatory: a mandatory point can only be scanned once all earlier mandatory points are completed — otherwise the app reports "Wrong order". Unbound points may be scanned in between at any time. A rejected scan is not lost: it is stored as additional evidence and visible in the log, but does not count as completing the point.
Time Window
For scheduled routes, a countdown shows the remaining time of the window. When the time runs out, the route is not ended automatically — you can keep scanning; the evaluation then rates it as "missed" or "incomplete" afterwards.
Pause, Finish, Abort
- Pause: you can interrupt a running route and resume it later — pause and resumption appear as their own entries in the log.
- Finish early: if you finish a scheduled route before all points are completed, the app requires a reason (free text). The reason is stored in the log.
- App restart: a running route survives closing or crashing the app — on the next launch it is resumed automatically (for up to 24 hours).
- While a route is running, the app's automatic sign-out timer is disabled.
Checkpoint Missing or Moved
If a checkpoint has been moved, the tag is missing, or a room is not accessible, don't abort the route. Instead:
- Open the checkpoint list of the active route.
- Tap the affected checkpoint to expand it.
- Pick "Checkpoint not present".
- The camera opens — confirm with a photo (e.g. of the spot where the tag should be, or of the locked door).
The photo is stored together with timestamp and location and will later be visible as a deviation in the web portal. The affected checkpoint is automatically set to "Inactive" until it is successfully scanned again via NFC or QR.
:::info Scheduled routes only This action is only available on scheduled routes with a predefined checkpoint list — and only if photo fallback is allowed in the property settings. On free routes you only scan checkpoints that are actually reachable. :::
Location Lock
If the location lock is active for the property, the app checks at start, at finish, and on every single scan whether your device is at the property. Outside the property area, the action is rejected with the notice "Outside the property"; if the location cannot be determined (GPS off, no permission), a dedicated notice with possible causes appears.
Scan in the Wrong Property
If you accidentally scan a checkpoint of a different property you have access to, the app automatically switches there and performs the scan. If a route is running at that moment, the foreign point is instead recorded in the background for the other property ("Checkpoint recorded for …") — your running route remains untouched. Details on all scan special cases: QR & NFC Use Cases.
Good to Know
:::tip Note Routes also work offline. Scan results are stored locally and automatically synchronized as soon as a connection is available. If a planned route cannot be loaded — for example because it was deleted in the meantime or is not available offline — the app deliberately aborts the start and shows a notice, so that no scans are assigned to the wrong route. :::
Permissions
:::info Permission To perform routes, you need the Perform routes permission. Contact your administrator if you do not have access. :::