How It Works
Nexrou follows a route through its entire lifecycle: built once, run and managed day to day, and it automatically generates the information you need to bill, settle pay, and control the operation.
In the routes module, the full structure of the service is defined once: client company, stops, start and arrival times, operating days, vehicle and driver, price, shift, and contract validity.
Its behavior is also defined here:
The route is ready to run. There's no separate planning step.
This is the central view of daily operations. It shows the day's routes and upcoming ones not yet run, with every field editable inline.
The entire operation is managed from here:
With filters by past and future date, company, vehicle, and driver, plus search on every column.
The key point: last-minute adjustments — a bus swap, an unavailable driver, a route that won't run — get resolved right here, in the moment, and stay on record.
Every time a route runs, it generates a service. A single route produces many services over a period, and all operational and financial analysis is built on top of those services.
| Report | What it answers |
|---|---|
| Services by Company | A view of routes and their details with the number of services completed over a given period, with the option to see route price and totals to invoice. |
| Services by Driver | Services completed by each driver, with schedules, bus, route price, and driver/vehicle payment amounts, with the option to view punctuality, stops, and service routes. |
| Driver Productivity | How many services each driver completed and their share of the period's total. |
| Bus Productivity | How many services each vehicle completed and its share of the total. |
| Commercial Mileage | How many kilometers each bus covers on active routes versus empty runs, and its commercial efficiency percentage. |
All with filters by company, route, driver, vehicle, and date range, and export to PDF and Excel.
To operate, routes need a price entered, and drivers and vehicles need their payment scheme configured.
An executive view with the day's indicators:
The mobile app completes the flow on the passenger's side:
When passengers can see where the bus is, calls asking about it stop reaching the operator or the school.
What changes
| Area | Typical situation | With Nexrou |
|---|---|---|
| Route planning | Manual changes, scattered versions, and dependence on spreadsheets. | Digital planning, route reuse, and centralized control. |
| Operational tracking | Hard to confirm whether a route ran, at what time, and with what deviations. | Comparison between scheduled and actual route, with status and evidence. |
| Passenger management | Paper lists, manual counts, and incomplete records. | QR, barcode, or NFC validation, with boarding and alighting traceability. |
| Passenger information | Calls and texts asking where the bus is. | Location and route status visible from the app. |
| Reports and auditing | Manual consolidation from different sources. | Automatic reports and historical evidence by route, vehicle, and passenger. |
| Payment and contract control | Doubts about which services were actually completed. | Objective evidence of execution, schedules, and passengers carried. |
| Incident management | Scattered information and slow response. | Route status and centralized information. |
| Fleet usage | Under- or over-loaded routes that are hard to spot. | Analysis of demand, frequency, timing, and commercial mileage. |
