--- title: "Planned vs. actual in employee charter transport | Merus Tracker" description: "How to compare planned with executed in chartered transport: punctuality, route, stops served, occupancy and mileage, trip by trip." url: https://merustracker.com.br/en/plataforma/auditoria/previsto-vs-realizado/ language: en updated: 2026-10-22 --- # Planned versus actual in employee transport: the practical guide How to compare planned with executed in chartered transport: punctuality, route, stops served, occupancy and mileage, trip by trip. **Published** Oct 22, 2026 **Updated** Oct 22, 2026 **Reading time** 4 min read **Byline** Merus Tracker team ## Quick answer Planned versus actual is the trip-by-trip comparison between what was planned for transport (route, stops, schedules, vehicle and capacity) and what was executed and measured. In employee transport, it shows delays, deviations, stops not served, incomplete trips and occupancy outside what was expected. In Merus Tracker, planned and actual sit on the same trip, with punctuality indicators and the history of each incident. ## In short - Planned × actual only works if the plan is well defined: route, stops, schedules, vehicle and capacity. - The main indicators are punctuality, route adherence, stops served, occupancy and mileage. - Looking at the history reveals patterns, such as a line that is always late at the same time. - Each difference needs context before it becomes a charge or a route change. - In Merus, the comparison is made automatically from independent measurement. ## Why compare planned with executed Employee transport has a direct effect on the company: a late bus means a shift that starts late, a production line that stops or employees who arrive tired and dissatisfied. Even so, few companies can answer with data whether the service is going as planned. The **planned versus actual** is the tool for that. It answers, for each trip: what should have happened, what happened and what the difference is. ## What goes into “planned” The plan is the reference. If it is incomplete, the comparison loses value. In Merus Tracker, the plan for each trip includes: - **Route and path** the vehicle must follow; - **Stops**, in the planned order; - **Schedules** of departure, passage through the stops and arrival at the site; - **Vehicle** and its capacity; - **Passengers** assigned to that trip, when there are reservations or allocation. This plan comes from routing and the operation setup. During implementation, the Merus team does this loading together with the company's team. ## What goes into “actual” The actual comes from the [independent measurement](https://merustracker.com.br/en/plataforma/auditoria/medicao-independente/): GPS positions, virtual fence crossings at stops and at the site, observed times and, when configured, boardings identified per passenger. ## The planned × actual indicators | Indicator | Question | How it is calculated | | --- | --- | --- | | Departure punctuality | Did the vehicle leave on time? | Observed departure time × planned, with the contract's tolerance | | Arrival punctuality | Did the shift start without delay? | Entry into the site's fence × planned time | | Route adherence | Did the vehicle follow the agreed route? | Positions compared with the planned route | | Stops served | Were all stops served? | Crossings of each stop's fence | | Trips completed | Did the trip happen and was it complete? | Presence of execution consistent with the planned trip | | Occupancy | Is the vehicle well sized? | Boardings ÷ vehicle capacity | | Mileage | Does the distance driven match the planned distance? | Measured route × planned route | ## How to read the results ### One-off differences An isolated delay on a day of heavy rain says little about the service. What matters is recording the incident and the justification. ### Recurring patterns This is where planned × actual shows its value. Examples of patterns that appear in the history: - a line that is late every day on the same stretch; - a stop that almost never has boardings; - a time when the vehicle always leaves full; - a route whose mileage is always above the planned one. Patterns like these call for a decision: adjust the schedule, change the route, swap the vehicle or talk to the carrier. ## Example: investigating delays on a line 1. The dashboard shows that Line 07 had late arrivals on a good share of morning-shift trips last month. 2. Opening the trips, the team sees that the delay always starts on the same stretch. 3. Overlaying the measured route on the planned one shows that the vehicle makes a detour to avoid a road under construction. 4. The team records the cause, simulates a new route in routing and agrees the change with the carrier. 5. In the following weeks, planned × actual shows whether the change solved the problem. ## Planned × actual and the invoice Beyond service quality, planned × actual feeds the [operational reconciliation](https://merustracker.com.br/en/plataforma/auditoria/conciliacao-operacional/): trips not completed, incomplete or with divergent mileage must be considered before approving the charge. ## Precautions for a fair comparison - **Use the contract's tolerance.** A one-minute difference is rarely relevant; the contract defines what counts as a delay. - **Separate missing data from missing service.** Trips with no position stay inconclusive until analyzed. - **Record authorized changes.** An agreed detour is not a route deviation. - **Compare equivalent periods.** Holidays, collective vacations and shift changes alter the operation. ## Who uses planned × actual | Area | Main use | | --- | --- | | Operations and facilities | Handle incidents and hold the carrier accountable the same day | | HR | Understand the impact of transport on delays and on employee satisfaction | | Contracts | Measure service levels and support renegotiation | | Planning | Adjust routes, schedules and fleet based on real execution | Together, independent measurement, planned × actual and reconciliation form the [contracted transport auditing](https://merustracker.com.br/en/plataforma/auditoria/) in Merus Tracker. The planned reference comes from the route; see [how to build routes from addresses and shifts](https://merustracker.com.br/en/blog/roteirizacao-do-fretamento/). In public transport, the same logic supports [public transport oversight: trips, kilometres and subsidy](https://merustracker.com.br/en/blog/fiscalizacao-do-transporte-coletivo/). ## Want to see this in your operation? The Merus team shows how this flow looks with your data, routes and contract, and supports the implementation until the system is 100% functional. [Talk to the Merus team](mailto:vendas@rioservice.com) FAQ ## Frequently asked questions **What does planned versus actual mean in transport?** It is the comparison between the planned service (routes, schedules, stops, vehicles and capacity) and the executed service, measured by GPS, virtual fences and boardings. It is used to find differences and understand their causes. **Which indicators should be tracked in planned × actual?** Departure and arrival punctuality, route adherence, stops served, trips completed, occupancy per trip and mileage executed. **How do you measure charter punctuality?** By comparing the planned departure, passage and arrival times with the times observed by independent measurement, applying the tolerance defined in the contract. Merus calculates this per trip, line and period. **Is a delay always the carrier's fault?** No. Traffic, roadwork, weather and changes requested by the company itself also cause delays. That is why Merus keeps incidents and justifications tied to each trip. **Does planned × actual help change routes?** Yes. Recurring delays, stops with no boardings and very high or low occupancy are signs that the route or vehicle should be reviewed. Merus routing lets you simulate the change before applying it. **Do I need equipment to do planned × actual?** A vehicle position source is required. Merus integrates the main telemetry hardware already installed or sells telemetry with installation included. ## Talk about your operation. [Talk to Merus](mailto:vendas@rioservice.com)