Route Star - office platform Screen 13 of 13 · reporting {{ icoSparkles13 }} Concept preview All screens

Filter once, group any way you like

Reporting

A standard catalogue of reports, all built on the same two-stage engine: set the filters once, then change the grouping as often as you like without re-running them. Every report can be switched on or off per role, and the month-end pack sits in the same place as the operational ones.

Insights and reporting

Standard catalogue · two-stage engine

Module in build {{ icoUser16 }} Tom Bright · Director

Report catalogue

Every report can be switched on or off per role, hidden by default when off.

Non-Service Report

Every scheduled visit that did not happen, and why. Use it to see whether the losses are weather, access or customers, and which technician or route is carrying them.

1 Filters Run once, then regroup as often as you like

Date range

Technicians

Reasons

Route

Postcode area

2 Group by Change the grouping without re-running the filters.

{{ icoList16 }} Results 11 non-service visits Grouped by {{ groupLabel }}

CustomerServiceScheduledTechnicianPostcode

Subtotals recalculate with the grouping. Filters are untouched. 11 visits · 3 groups · £412 of work not delivered

{{ icoLock14 }} Every report can be switched on or off per role, hidden by default when off.

{{ icoSparkles14 }} The AI assistant respects the same report permissions.

Concept preview for discussion. All customers, technicians, dates, postcodes and figures are fictional. The reporting module shown here is in build and is an illustration of intent, not a committed specification.