RECURRING PROGRAMS + OPTIMIZATION ENGINE
The WEBFLEET planner is an A-to-B route planner with waypoints, traffic-aware navigation and HGV restrictions drawn from the TomTom map heritage, tuned around the day’s stops. Recurring or template routes are not surfaced as a named capability on the public product page. That covers a wide band of single-day fleet routing cleanly. At thousands of recurring stops a month, with SLAs that vary by contract or service line, with cadence drift to keep capacity balanced, and where the recurring program interacts with reactive break-fix for the same drivers, single-day planning is no longer the same thing as optimization. eLogii’s engine models task and route template groups as constraint inputs to the optimizer, plugged directly into WEBFLEET.connect.
A-B Route planning in WEBFLEET with the capability of sending routes direct to drivers, with waypoints, traffic-aware navigation and truck-specific routing for HGVs.
From webfleet.com/webfleet/products/webfleet/features. The WEBFLEET planner is positioned around the day’s A-to-B route. Recurring or template routes are not listed alongside the planner capabilities on the public page. Constraint-aware optimization across thousands of recurring stops with interacting SLAs is its own decision layer. Verified June 2026.
The WEBFLEET features page covers a single-day planner-facing tool with A-to-B routing and waypoints. The named capabilities span traffic-aware navigation and HGV restrictions (bridge heights, weight, hazardous-goods routing) drawn from the TomTom map heritage. The page does not surface recurring or template routes, multi-week horizons or cadence rules as documented capabilities. The Webfleet Work App, on the driver side, handles ePOD, two-way messaging, working-hours logging, OptiDrive scoring and secure-truck-parking booking; it shows the driver today’s assigned route, not the next quarter’s recurring book.
The platform tracks the day’s stops, holds the route on the WEBFLEET planner, captures the in-cab telematics, and runs the route calculation between assigned waypoints. The vocabulary is day-first: draw today’s A-to-B route on the WEBFLEET planner, send it to the driver’s Work App, capture the GPS, OptiDrive 360, tachograph and Webfleet Video stream as the route runs.
What the WEBFLEET planner does not position as the lead capability is constraint-aware optimization across the recurring program at full scale. The recurring program at scale isn’t just a calendar problem; it’s an assignment problem where SLAs interact (contract anniversaries, quarterly preventive cycles, customer service agreements), cadences drift, skill requirements pin specific drivers to specific stops, and capacity has to balance across the recurring program and the daily reactive break-fix. Webfleet’s own integration partner directory routes this type of work to a third-party route optimization tool.
The recurring programs that outgrow the WEBFLEET planner are concrete:
In each case, the engine doesn’t replace Webfleet’s telematics stack. It optimizes the work that the recurring calendar produces.
A European commercial maintenance organization running monthly, quarterly and annual PMs across a portfolio of customer sites in the UK, Germany and the Netherlands. Fifty-five drivers in the field. Around 3,500 recurring jobs per month from the contract book, plus daily reactive break-fix for the same drivers. SLA windows vary by contract: anniversaries pinned to fixed dates, calibration on a hard 6-month cycle, regulatory inspections within calendar months, commercial programs at four-week intervals.
Webfleet captures the telematics cleanly: GPS trail on every vehicle, Tachograph Manager handling EU HGV compliance, OptiDrive 360 scoring the drivers, Webfleet Video on the heaviest vehicles. The planning task that grows past the WEBFLEET planner is the balancing: reactive break-fix for the same drivers landing on top of recurring jobs; cadence drift to keep capacity even across the month; SLA windows that need protection from the optimizer rather than from a planner spotting them in time. The WEBFLEET planner runs A-to-B for today, and the team had been evaluating a third-party route optimization tool via the integration partner directory for the constraint side, but the second commercial relationship and the dual UI was off-putting. Template-group optimization in eLogii absorbs cadence drift within rules, protects SLA-locked stops, balances against reactive, and outputs one plan that’s already reconciled across the book, plugged directly into WEBFLEET.connect. Webfleet continues to own the GPS, OptiDrive, tachograph and Webfleet Video record; eLogii owns the optimization across it.
The workaround is the same as for the wider planning problem: the planner carries it, with either the WEBFLEET A-to-B planner alone or one of the integration partners (a third-party route optimization tool) bolted on. Recurring jobs are managed as separate calendar entries reconciled by hand against the day’s reactive book; the planner assigns them to drivers, balances against reactive break-fix, allows cadence drift to keep capacity even, and signs off on the day. At small recurring books, this is straightforward. At several thousand recurring jobs a month, with SLAs and cadences interacting, the planner becomes the optimizer. The friction shows up as SLA misses on specific contract programs, drive-time creep on the recurring book, and over-reliance on the one or two planners who know the recurring rules best. The partner-integration path solves the constraint side but adds a second commercial relationship and a second UI to manage.
Recurring programs are modeled as task and route template groups feeding the optimizer. Each template carries the cadence, skill requirements, SLA windows and depot rules; the optimizer treats them as first-class inputs alongside the daily flexible work.
Webfleet stays in place as the system of record for GPS, OptiDrive 360, tachograph and Webfleet Video record. The operational system of record (FSM or ERP) keeps the recurring calendar and the work record. eLogii reads vehicle, driver and live position data from Webfleet via WEBFLEET.connect, reads the recurring book and reactive break-fix from the FSM / ERP, and runs the optimization across them. Optimized routes dispatch into the eLogii driver app; completion data writes back to the FSM / ERP.
Most teams complete the connector build in 3 to 5 weeks. Typical first wave: the recurring program that is leaking the most against SLAs today, or the contract book where cadence interactions are hardest.
30-minute custom simulation with your actual recurring book, drivers and SLAs. Projected savings in drive time, SLA hit rate and planner hours.
Not as a named capability on the WEBFLEET planner page. The WEBFLEET planner is described as an A-to-B route planner with waypoints, traffic-aware navigation and HGV restrictions. Recurring or template routes are not surfaced on the public product page. The assignment and route within a single day is handled by the planner, with traffic-aware navigation filling within that day’s shape. What it does not position as the lead capability is constraint-aware optimization across thousands of recurring jobs with interacting SLAs, cadences and skill requirements, balanced against daily reactive break-fix for the same drivers in one solver run. That decision layer is where eLogii adds value, plugged directly into WEBFLEET.connect.
Recurring job calendar: a list of jobs at the right cadence (monthly preventive, quarterly compliance, weekly commercial maintenance) created in the operational system or a separate calendar. Recurring program optimization: take the calendar entries, plus the daily reactive break-fix, plus the driver pool, plus the SLAs and cadences, and decide assignments and routes that respect all of them at once. The WEBFLEET planner and the operational system can produce the calendar. eLogii does the optimization, modeled directly through task and route template groups that feed the optimizer as constraint inputs.
When the recurring program runs to hundreds or thousands of jobs per month, when SLAs vary by contract or service line, when cadence drift (a stop shifting from week 1 to week 2 to keep capacity balanced) becomes a planning task, when the WEBFLEET planner’s single-day scope can’t span the recurring program plus reactive break-fix in one run, and when the recurring program interacts with daily reactive break-fix for the same drivers. PM programs across hospital networks, multi-site PMs for industrial customers, recurring commercial maintenance contracts, inspection programs across regions: each of these hits the optimization decision layer rather than the day’s calendar.
Through task and route template groups: weekly, monthly, quarterly and bespoke cadences are modeled directly as inputs to the optimizer. Each template carries skill requirements, time-window constraints, SLA targets and cadence rules. When the run happens, the optimizer balances the recurring program against the daily flexible work, protects SLA-locked stops, allows cadence drift within rules, and outputs one consistent plan. Bristow & Sutor routes 200,000+ recurring case visits per year on eLogii.
Custom integration against WEBFLEET.connect (OAuth 2.0) and the operational system of record (FSM or ERP). eLogii reads the recurring calendar and the daily reactive book from the operational systems, plus the driver / vehicle / depot model. The optimization run considers them together. Routes and ETAs are written back over WEBFLEET.connect; the driver opens the Webfleet Work App or PRO Driver Terminal in the cab and follows the assigned route. Completion data flows back. Webfleet captures the in-cab GPS, OptiDrive, tachograph and Webfleet Video stream. Typical connector build: 3 to 5 weeks.
Last updated: June 2026. Webfleet scope is drawn from the WEBFLEET features page, Webfleet Work App page and Webfleet integration partner directory. eLogii capabilities documented at elogiiapidocs.apidog.io.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real jobs, depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you plan today. No slides, no generic benchmarks.
