Route Log
The route log is the detail view of a single route. You open it by clicking a route row in the Tasks & Routes workspace.
What Is This View For?
The log answers the question "What exactly happened on this route?" — point by point, with timestamps, positions, and evidence. It is the view you show the client in case of dispute: who was at which checkpoint when, what was skipped, which incidents were created along the way.
Structure of the View
Header
The header summarizes the route: start and end, planned vs. actual time window, duration, scanned checkpoints (actual/target) with a progress bar, number of incidents, property, route name, runs and frequency, plus the status (Successful, Incomplete, Failed, Missed, or Running).
Map
The map shows the positions of all scans of the expanded run, optionally with a chronological connecting line between the scans (toggled on/off via a switch) — so you see the path actually walked. A legend explains the symbols for start, end, scans, and incidents. The map can be hidden entirely; on large screens, map and timeline share the space with a draggable divider.
Timeline
Every run of the route is an expandable section with its own summary (time, duration, scans, incidents, status). The timeline inside lists chronologically:
- Checkpoint scans (NFC, QR, or photo fallback — photos open full-screen on click)
- Unscanned checkpoints — missing points are explicitly marked as "Not scanned"
- Start, pause, resumption, abort (with the reason entered in the app), time exceeded, and completion
- Incidents created during the route — with a jump into the incident detail
Use the arrow buttons to jump directly to the previous or next route log without leaving the view.
Actions
Download (PDF/CSV)
Use the download menu to export the log as PDF (with embedded evidence photos, optionally in your own branding) or as CSV. Via "Schedule export" you set up a recurring delivery instead — see Export & Delivery. Requires the Export round evaluation permission.
Acknowledge a Missed Route
Missed or failed scheduled routes carry the Acknowledge button (permission "Edit routes"). Acknowledging documents — with timestamp and person — that the incident was taken note of, and stops running escalation notifications from the automation rules. Free routes cannot be acknowledged.
Correct Times (Free Routes)
For free routes, start and end time can be corrected afterwards — typically after a forgotten finish. Fixed rules apply:
- Mandatory justification: pick a reason (Technical issue, Forgotten booking, Interrupted by an operational situation, Other) plus free text.
- The correction may deviate from the original by at most 24 hours and is only possible up to 30 days back.
- Every change lands in a change history (old value, new value, person, time, justification), available as its own tab in the correction dialog. The original times remain stored.
Scheduled routes are deliberately not correctable — their time window is the target specification.
Good to Know
:::tip Note
- Scans made outside the enforced order appear in the log as additional evidence, but do not count as completing the point.
- A route can be fulfilled jointly by scans from multiple devices — the log merges all scans.
- You find the chronological scan log across all routes under Dashboard → Activity (filter "Routes"). :::
Permissions
| Action | Permission |
|---|---|
| View the log | View reports |
| Download PDF/CSV, schedule export | Export round evaluation |
| Acknowledge a missed route | Edit routes |
| Correct times (free routes) | Edit reports |