Daily use
Daily use — technician (mobile app)
6.1 Open the Waypoint section
Once the plugin is installed and the technician's profile has the right permissions, a Waypoint entry appears in the app's main menu.
6.2 Create the route
If there is no route in progress, the screen shows an empty state. Tap the "+" button to start planning.
A list of eligible tickets opens — those linked to a route and assigned to the technician. Select the ones to visit. When you confirm, the optimal order of stops is calculated automatically based on distance and traffic conditions.
If a particular ticket must be visited first regardless of what the optimiser suggests, long-press it before confirming. A star marks it, and it will be placed as the first stop; the remaining stops are optimised around it.
"There is no active Route" — the empty state, with the "+" button to start planning.
"Choose your tickets" — two tickets selected, #39 additionally marked with the star that forces it as the first stop.
6.3 The route screen
Once created, the route is shown as an ordered list of stops, each with its ticket and location. Each stop offers two buttons:
- Play: opens the travel panel for that stop, where the trip is started and stopped.
- Map: opens your usual maps application (Google Maps, Waze, etc.) with the destination already set, so you can start turn-by-turn navigation there.
Tapping the body of a stop opens a summary of the ticket — title, location, status and assigned technician — with a shortcut to open the full ticket without leaving the route.
- Edit route: add stops, remove them or change the order. Each change creates a new version of the route and keeps the previous one in the history.
- Cancel route: ends and discards the current route if it will not be completed.
The route screen: current ticket, current stop and the upcoming stops queued below.
Ticket summary panel — location and description, with a shortcut to view the full ticket.
6.4 Complete a stop
This is the core cycle, repeated for every stop on the route.
- Set off. Tap Play on the stop and then Start. GPS tracking and the travel timer begin. Use the Map button whenever you want guided navigation.
- Arrive. Tap Stop. The trip is closed, the distance actually travelled is recorded, and the work timer starts on its own — you do not need to start it manually.
- Work on the ticket. The work timer keeps running, and a notification on the phone shows it is active even if you leave the app.
- Finish. Tap Stop on the work timer. The stop is marked as completed and the route moves on to the next one.
When the last stop is completed, the route is closed automatically. There is no separate "finish route" button.
Travel panel before departure — GO button, timer at 00h 00m:00s.
"On the way" — the travel timer running, END button to mark arrival.
"Working on site" — the work timer already running right after the trip was stopped, with no manual start needed.
The phone's notification tray showing the active ActualTime timer while the app is in the background.
Daily use — supervisor (GLPI web)
Profiles with the corresponding rights get two new sections in the GLPI administration area.
7.1 Geolocation
Focused on where technicians are. It has four tabs:
- Last Geolocation: the most recent recorded position of each technician on an interactive map — where the team is right now.
- All Geolocation: the full position history, using GLPI's standard search filters. Narrow the results by date range, technician, linked ticket or location, and export them for analysis.
- Waypoints: the same kind of search, but over the raw GPS trail (every point recorded during a trip) rather than the start/end positions — useful to inspect exactly how a route was walked or driven.
- Live Routes: only the routes currently in progress, for real-time follow-up of each technician.
"Last Geolocation" — the most recent position of each technician. Only one technician has reported a position in this environment.
"Waypoints" — searchable GPS trail, filterable by date, user and more. The cluster marker groups nearby points; click it to zoom in.
"Live Routes" with a technician actively running a route — the marker shows the current position, numbered pins are the remaining stops.
7.2 Routes
Focused on the detail and history of each journey. The list shows all routes, completed and in progress, with configurable columns: route, technician, creation date, status, number of stops, distance and accumulated time. As with any GLPI list, columns can be customised, sorted and filtered.
Opening a route shows its itinerary on a map with every geolocated point, making it easy to see the order followed, the distance between points and the partial times. It is the quickest way to analyse efficiency or spot a deviation from the plan.
Because a technician may add or skip stops on the road, each route keeps its version history. Reading a route means choosing which version you are looking at — the original plan, or the one that was actually executed.
The Routes list — Status added as an extra column via the column picker (⚙), showing routes in different states.
Route detail: distance, duration and date at the top, the itinerary on the map, and the per-ticket breakdown (order, status, location, billing distance/duration) below.
The version selector (top bar) on a route with two versions — "v2 — Completed" and "v1 — Edited".
7.3 Waypoint tab on the ticket
A ticket that has been visited within a route gains a Waypoint tab. It shows one card per trip made to that ticket, comparing the estimated, actual and billable figures described in section 2.4.
The Waypoint tab on a ticket — Estimated / Real / Billing comparison for one visit.
Exporting data (CSV)
The export is launched from the ticket list, not from the Routes section:
- Filter and select the tickets you want to report on.
- Choose the Export routes CSV massive action.
- Optionally set a date range to restrict the export to journeys made between those dates, or export everything.
- Download the file.
The CSV contains one row per visit, with the route and its version, the position of the stop in the itinerary and whether it was marked as priority, the ticket and its title, the technician, start and end times, the four distance/time metrics from section 2.4, and the time actually worked on the ticket.
Two summary blocks are appended at the end of the file: totals per technician and totals per day, each with number of visits, distance, travel time, billable figures and time worked. This makes the file usable for invoicing without any further processing.
Durations are exported in seconds and distances in metres, deliberately: raw units are easier to aggregate in a spreadsheet than pre-formatted text.
Three tickets selected in the ticket list, with "Export routes CSV" chosen from the massive action dropdown.
The optional date-range step — set a range and click "Generate CSV", or skip it with "Export everything".
The resulting CSV: one row per visit (columns A–Q), followed by the "Summary by technician" and "Summary by day" blocks.