What
Most fleet managers approve a new depot by looking at device price and a monthly subscription line, then get surprised six months later when the real multi-branch fleet telematics cost turns out to sit somewhere else entirely. The hardware cheque is the easy part. The recurring money goes into data volume and the hours people spend making numbers agree with each other. Understanding that shift changes how you budget.Start with data volume. When you run one site, reporting looks flat. Add depots and the curve bends in several directions at once. Position updates scale with vehicles, but geofence events scale with how many yards, client sites and loading bays you touch. Diagnostic streams scale with vehicle type and how much you want to know about engine behaviour. So doubling your fleet rarely doubles your data. It can triple it if new branches operate in dense stop-and-go conditions where events fire constantly. Reporting frequency is the dial that decides this. Move from a long interval to a short one and storage, transmission and processing all climb together. Before approving a branch, ask what interval it needs, how many geofence events it will realistically generate per vehicle per day, and whether anyone has modelled that growth. If the answer is nobody, your cost forecast is a guess.The second driver is reconciliation labour, and it is the one most often left out of total cost of ownership. Picture two branches. One counts idle time from ignition status, the other from motion. Both are honest. At month end, fuel totals will not reconcile, and someone has to open the raw data, rebuild the day, and explain the gap to finance. That work repeats every month and it grows with each site. The same thing happens with stop and arrival definitions. If branch-level reporting is built on different meaning for the same word, no dashboard will ever match, and a manager will spend their week as a human translation layer. Count those hours. They are a real cost line, and they are usually larger than the savings anyone hoped to find.The third driver is rework caused by delayed or inconsistent geofence events. Vehicles pass through tunnels and underground loading bays, so a device buffers positions and sends them later. That burst of points can flag a driver who arrived on time. If that flag flows into compliance records or a client invoice, you are now spending time on disputes rather than on operations. One late event can surface weeks later as a billing argument. Multiply that by every depot and every client site, and you can see why event routing needs to be central rather than configured depot by depot.Do not overlook training and change management. When you replace branch-specific habits with one standard, people have to relearn thresholds, alert ownership and report routines. That time is not free, and treating it as free is how good reconfigurations quietly fail.So the decision path is simple. Reconfigure when one standard can be applied centrally and branches accept it. Redesign when devices or integrations genuinely cannot carry consistent reporting into payroll, billing or maintenance systems. Replace only when audit-ready, timestamp-stable logs are impossible. Replacement is the expensive door, not the default one, and inconsistent branch data is usually a configuration problem before it is a hardware problem.Before and after any change, measure four things: manual reporting hours per branch, reconciliation discrepancies per month, alert volume per branch, and how long it takes to close month-end fuel totals. Those four numbers will tell you whether real-time tracking has actually improved or whether you simply bought more screens to watch.Then set your pre-approval checklist for the next branch: one definition per metric, one reporting cadence, one alert routing owner, and a baseline measurement taken before anything changes. Do that, and multi-branch fleet management stops being an argument about which dashboard is right. It becomes a single current picture that fuel, route and staffing decisions can all trust, which is the outcome that actually controls cost.Related FAQs: When should I consider replacing my current GPS trackers versus updating software? | Does having more vehicles make spoofing detection easier or harder?