Reveal Driver fleet-scale limits: the documented 500-vehicle threshold

What Verizon Connect documents about the Reveal Driver app at scale

Reveal Driver is the driver-side mobile app in the Verizon Connect platform. The standard sign-in flow surfaces a suggested vehicle for the driver, drawn from the relationship between the driver, their depot and the vehicles assigned to that depot. The Reveal Driver help center documents the following constraint:

• 500-vehicle threshold. For fleets over 500 vehicles, the auto-suggested vehicle list is replaced with a manual search-and-select flow. Drivers find their assigned vehicle in a list each time they sign in.
• OS support. iOS 15 to 17 and Android 11 to 14 per the help center as of April 2024. Drivers on older devices may face their own constraints.
• Manager apps separate. Spotlight is the manager mobile app; Reveal Field is the technician-side app for service operations. Each has its own surface area and sign-in flow.

The 500-vehicle threshold is documented; the user-facing implication is that drivers spend time on a lookup that the system used to do automatically. For a fleet of 800 drivers across three depots, that is 800 manual lookups every morning. For a fleet of 1,500 drivers, the cost scales linearly. The data quality of the lookup also depends on the driver picking the right vehicle from a long list; a wrong selection means a vehicle is associated with the wrong driver in the telematics record.

None of this means Verizon Connect’s telematics stack is the wrong tool above 500 vehicles. GPS, ELD, dashcams and Coach driver behavior scoring work at any scale. What hits the design ceiling is the operational surface around driver-vehicle assignment and the routing that follows.

What changes at the 500-vehicle threshold in practice

The threshold matters in three concrete ways:

• Sign-in friction at scale. Drivers search a list of 500+ vehicles each morning. At 60 seconds per driver, a 1,000-driver fleet absorbs roughly 16 driver-hours a day on a step the system used to do automatically.
• Wrong-vehicle data quality risk. A driver picking the wrong vehicle from a long list creates a misattribution in the telematics record. GPS, ELD compliance, Coach driver score and dashcam footage all hang off the driver-vehicle linkage. The further from auto-assignment, the more attention has to be paid to data validation downstream.
• Routing decision is outside the assignment. The vehicle is one input to the routing problem; the driver, depot, skills, time windows, stops and SLAs are the rest. When vehicle assignment is decoupled from route assignment, the planner has to reconcile them. At small fleets this is invisible; at fleets above the threshold, the reconciliation becomes a planning task.

In each case, the right answer is for the optimizer to decide driver-vehicle-route assignment as one constraint problem. The driver opens the cab with the assignment already made; the planner doesn’t reconcile a lookup against a route.

At a glance: a 1,200-driver distribution fleet on Verizon Connect

A regional distribution operation running 1,200 drivers across five depots. Verizon Connect for the telematics stack: Reveal for GPS and ELD, Coach for driver behavior scoring, dashcams on the heaviest vehicles, asset trackers on plant equipment. The Reveal route planner runs per depot; Reveal Driver carries job status, route review and vehicle assignment for the driver.

The 500-vehicle threshold hits at sign-in. Each morning, every driver opens Reveal Driver, searches a depot-scoped vehicle list, finds their vehicle, and selects it. At the depot with 300 drivers, that’s roughly 5 driver-hours absorbed before the day starts. Wrong-vehicle selection happens at low single-digit rates; the depot manager has to spot-check and correct telematics misattribution before week-end reporting. The Reveal route planner runs per depot for today’s shape with cloud assistance; multi-depot routing isn’t a documented capability, so cross-depot rebalancing falls back to the planner. The fleet is past the band the documented surfaces were built around.

Adding eLogii moves driver-vehicle assignment into the constraint model. The optimizer reads the day’s stops, the driver roster (with skills and certifications), the vehicle pool (with capacity, vehicle profile and planned maintenance), and the depot graph. It produces one consistent assignment: this driver, this vehicle, this route. Reveal Driver opens with the assignment already decided; no manual lookup is required. Verizon Connect captures the in-cab GPS, ELD, behavior and dashcam stream against the now-correct driver-vehicle linkage.

What eLogii adds, in one place

The constraint-based optimization decision layer that runs alongside Verizon Connect at scale:

• Driver-vehicle assignment as a constraint output. The optimizer matches drivers to vehicles based on home depot, skills, certifications, capacity, vehicle profile and planned maintenance windows. No manual lookup at sign-in.
• Two engines. Default engine for high-throughput daily planning (100 tasks in under 10 seconds). Advanced engine for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Six configurable modes. Three assignment modes (Optimize Everything; Add to Routes, Keep Existing Assignments; Add to Routes, Keep Existing Assignments and ETAs). Three load-balancing modes (Most Efficient Routes; Balance the Minimum Number of Routes; Use All Vehicles / Finish as Soon as Possible).
• Multi-day, multi-depot, multi-driver in one run. Single optimization across the routing horizons the Reveal route planner is not designed for.
• Rule-based protection. Pin specific drivers to specific vehicles where the operation requires it; protect customer-confirmed slots; exclude depots from a given run. Visible rules, not buried defaults.
• REST-callable. All six modes plus optimization triggers exposed as REST endpoints. Seven webhook events including live driver GPS and Route ETAs Update.

How the integration sits with Verizon Connect

Verizon Connect stays the system of record for GPS, ELD, driver behavior and dashcam record. The operational system (FSM or ERP) stays the system of record for the work record. The connector between eLogii and the stack is custom-built; there is no published eLogii to Verizon Connect integration on either side. Verizon Connect documents a telematics API through the Reveal developer portal.

1. Read from the operational source. eLogii reads stops, drivers, vehicles, depots and skills from the FSM, ERP or Verizon Connect directly via the Reveal API.
2. Optimize in eLogii. The run produces driver-vehicle-stop assignments respecting all constraints. Driver-vehicle linkage is part of the output.
3. Write back to the operational system. Routes, ETAs and driver-vehicle assignments are written back to the FSM / ERP. The route dispatches into the eLogii driver app with the assignment already made.
4. Driver experience improved. No manual vehicle lookup at sign-in; the routing they follow is the one eLogii planned. Verizon Connect captures the GPS, ELD, behavior and dashcam stream against the correct linkage.

Most teams complete the connector build in 3 to 5 weeks. The most common first wave for large fleets is the depot where the 500-vehicle threshold is biting hardest.

Frequently asked questions

What is the documented 500-vehicle threshold in Reveal Driver?

Verizon Connect’s Reveal Driver mobile app help center documents that for fleets over 500 vehicles, drivers cannot use auto-suggested vehicle assignment. Instead they must search and select their assigned vehicle manually each time they sign in. This is one documented surface where the app is built around a smaller fleet shape than the operation needs.

Does this mean Verizon Connect is the wrong tool above 500 vehicles?

No. Verizon Connect’s telematics stack (GPS, ELD, dashcams, driver behavior, asset trackers) runs across fleets of all sizes. The Reveal Driver app is a useful telematics-side surface even past 500 vehicles. The 500-vehicle threshold is one of the documented places where the planning and driver-app surface was built around small and mid-size fleets. Once the operation grows past that shape, the optimization decision layer (which driver gets which vehicle, which stops, on which route, under which constraints) is what an enterprise routing engine adds on top.

What changes for the driver above the 500-vehicle threshold?

Per the documented Reveal Driver behavior: instead of opening the app and confirming the vehicle the system has assigned, the driver opens the app, searches for their vehicle in a list, selects it, and proceeds. At 800 drivers across three depots, that’s 800 manual lookups every morning. At 1,500 drivers it scales linearly. The data quality of the lookup depends on the driver picking the right vehicle from a long list. Wrong selection means a vehicle is associated with the wrong driver in the telematics record.

How does eLogii handle large-fleet driver-vehicle assignment?

Driver-vehicle assignment is part of the constraint model the optimizer solves. Each vehicle has a depot, capacity, vehicle profile, capabilities, planned maintenance window. Each driver has a home depot, skill set, certifications, shift pattern. The optimizer assigns drivers to vehicles as part of the route output, respecting constraints. The driver opens Reveal Driver or Verizon Connect Navigation in the cab with the assignment already decided; no manual vehicle lookup is required. Verizon Connect captures the in-cab GPS, ELD, behavior and dashcam stream on top of the planned route.

How does the integration work for large fleets?

Custom integration against the Reveal API and the operational system of record (FSM or ERP). eLogii reads stops, drivers, vehicles, depots and skills from the operational systems; the optimization run produces driver-vehicle-stop assignments respecting constraints; routes and ETAs are written back. The driver opens Reveal Driver or Verizon Connect Navigation in the cab; Verizon Connect captures the in-cab GPS, ELD, behavior and dashcam stream. Typical connector build: 3 to 5 weeks.