eLogii + Joblogic: When to Add eLogii to Joblogic

Where each platform leads

Joblogic and eLogii sit in different layers of the same field-service stack. Joblogic is the all-in-one UK FSM workflow product: CRM, scheduling board, mobile engineer app, asset and PPM management, compliance documentation, financials, customer portal. eLogii is the routing engine that sits underneath the scheduling board for operations where the optimizer needs to do the heavy lifting.

The combined deployment pattern: Joblogic stays the system of record for jobs, customers, mobile field execution, PPM, compliance documentation and invoicing. eLogii reads jobs, engineers, vehicles, sites and recurring PPM templates from Joblogic, runs the optimization across the horizons Joblogic’s built-in scheduler is not designed for, and writes optimized routes and ETAs back. The engineer opens Joblogic’s mobile app on site; the route they take is the one eLogii planned. Joblogic keeps the workflows it owns end to end; eLogii handles the optimization layer underneath.

What Joblogic does well, what eLogii adds

This is not a head-to-head FSM comparison. Joblogic is the FSM workflow and eLogii is the routing engine that runs underneath it. The tables below cite Joblogic’s own product pages verbatim where they describe scheduling and route optimization scope, and stack them against the optimization-driven side of the problem.

What Joblogic’s scheduling and routing covers

What eLogii adds on top of Joblogic

Sources: Joblogic features, Joblogic scheduling software; eLogii optimization engines. Verified June 2026.

Field execution, compliance and customer experience

This is where Joblogic shines and eLogii deliberately does not compete on the FSM workflow itself. Joblogic’s mobile, compliance and customer-portal depth is real and broad; eLogii’s is deeper specifically on routing and delivery execution underneath.

API surface and developer experience

Sources: eLogii API documentation; Joblogic API surface confirmed with vendor against plan tier. Verified June 2026.

Scale, security and commercial

Sources: joblogic.com, Capterra, GetApp reviews, and Joblogic’s Vista Equity acquisition (September 2025). Verified June 2026.

Route optimization, in detail

This is where Joblogic and eLogii do different jobs. Joblogic’s scheduler is built around drag-and-drop assignment by the planner, then a route calculation between the assigned jobs. eLogii’s optimizer is built around constraint-aware assignment and routing in one pass. Both are valid approaches; they fit different shapes of the same problem.

Joblogic’s scheduling and routing scope, as Joblogic describes it

Three claims, taken directly from Joblogic’s own product pages:

• Drag-and-drop assignment, then route calculation. “Joblogic’s drag-and-drop calendar makes job scheduling and dispatch far more efficient.” The accompanying route optimization is described as: “Schedule, manage and optimise the daily routes of your field engineers” with capabilities to “dispatch tasks to nearby team members, reassign jobs to reduce transit time, and automatically schedule jobs to follow a more efficient travel route”.
• Multi-engineer and multi-client supported as assignment. “Organise multiple visits for multiple clients simultaneously” with bulk reassignment and batch deployment; a “shunt” function pushes or pulls subsequent visits for the selected engineer or team.
• Recurring contracts and PPM supported as schedule generation. “Schedule jobs as either one-off visits or as recurring contracts”; PPM schedules at site and asset level with task-driven maintenance and auto-renewing compliance dates for gas safety and boiler servicing.

Joblogic’s workflow depth across 30+ UK trade verticals is broad and the F-Gas, gas certificate and compliance side is a genuine differentiator. What Joblogic’s public docs do not describe is constraint-aware optimization across multi-day, multi-engineer and multi-depot in one pass, programmatic re-optimization as a public surface, or a documented optimization API. That’s a deliberate product choice: Joblogic’s scheduler is a workflow tool that solves “route between the jobs the planner has put on the calendar”. It is not the wrong tool. It is the tool for that shape of the problem.

eLogii’s routing scope

eLogii’s optimizer is built around two engines and six configurable modes, all callable via REST and exposed to the planner as controls they can see and adjust.

• Two engines. The Default engine optimizes 100 tasks in under 10 seconds for high-throughput daily planning. The Advanced engine takes more factors into account and is the choice for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Three assignment modes. Optimize Everything (creates fresh routes including all assignments), Add to Routes, Keep Existing Assignments (incorporates new tasks into existing routes while preserving driver assignments), and Add to Routes, Keep Existing Assignments and ETAs (inserts new tasks into available slots without modifying existing stop sequences or ETAs).
• Three load-balancing modes. Most Efficient Routes (fewest vehicles), Balance the Minimum Number of Routes (across load, time, distance or job count), and Use All Vehicles / Finish as Soon as Possible (maximize speed).

Beyond the modes, eLogii ships the operational surface Joblogic’s scheduler isn’t designed to lead on: multi-day and long-haul routing (“plan a single day or an entire month in one run”), multi-depot (“route across multiple depots, branches, or home start locations in a single run”), recurring patterns via task and route template groups (weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer, not as generated schedules to be hand-rebalanced), multi-engineer crew jobs with skills, capacity and SLA constraints, and rule-based re-optimization the operator can see and steer.

What this means in practice

If the planner’s morning routine is “drag yesterday’s recurring jobs onto today, slot the new ones in, use the shunt function to push the rest”, Joblogic is the right tool and adding eLogii would be over-engineering. If the planner’s morning routine is “run the optimizer against today’s open jobs across three depots, balance against next week’s PPM book, protect the SLA-locked compliance stops, route around the engineer who’s off Tuesday”, Joblogic’s scheduler is being asked to do a job it wasn’t built for. eLogii covers that side via REST API; Joblogic stays in place for everything else.

When eLogii’s depth starts to matter

Joblogic’s scheduler covers a wide band of UK trade and field-service work well. The signal that the planning problem has grown past it tends to be operational rather than headcount-based. Three patterns show up:

• Optimizer-driven assignment, not drag-and-drop. When the planner is spending the morning hand-balancing jobs across engineers, depots and skill sets, the optimizer should be making those calls. Joblogic’s drag-and-drop calendar plus “shunt” function is designed for an experienced planner steering the day; once the placement itself is the bottleneck, the optimizer needs to step in.
• Multi-depot rebalancing as a daily input. A regional contractor with three or four depots, or a distribution arm running parallel to the field-service business, needs the optimizer to see all depots as part of the same problem. Joblogic treats depot as a per-engineer starting point.
• Recurring PPM and compliance at thousands of stops. Quarterly compliance programs, monthly PPM books, gas-safety and F-Gas cadences across a property portfolio. Joblogic generates the schedules and tracks the certificates; the optimization across the generated stops, interacting with reactive work, is the part that needs the engine.

Where any of these is the dominant shape of the work, eLogii is the routing layer. Where none of them is, Joblogic’s built-in scheduler is the right tool and adding eLogii is over-engineering. The honest answer for many Joblogic customers is “you don’t need eLogii.” The honest answer for the operations where the optimizer is the bottleneck is that eLogii is built for exactly that.

What changes once eLogii is in place

Joblogic continues to do the FSM work it’s built for. The difference shows up where the planning problem used to dominate. Brymec lifted productivity 30% and routing efficiency 20% on eLogii. ATS Building Products improved deliveries per route by ~98%. Porcelanosa runs eLogii with 95%+ ETA accuracy on daily distribution. Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. These are operational outcomes that come from moving the assignment problem from the planner’s morning into the optimizer:

• Slot booking co-pilot. When a customer is offered a time window, eLogii’s slot availability returns only slots that already fit the current optimized plan. Cuts failed visits ~35%. Plugs into whichever booking layer is in use, including Joblogic’s customer portal over REST.
• Customer-driven rescheduling. Around 70% of reschedule requests handled without coordinator involvement. The customer picks a slot that already fits the plan and the route re-optimizes.
• Embedded tracking content. NPS surveys, safety briefings, access codes, treatment instructions, pushed onto the tracking page itself rather than handed off to a separate channel.
• Multi-brand tracking. Three brands run from one dispatch desk, each with its own logo, colors and layout.
• Map-native dispatch ops. Drag-and-drop reassignment with automatic ETA recalc on both routes; polygon, freehand and rectangle map selection; bulk actions on hundreds of stops; Gantt-style route timeline alongside the map; 13 historical segments refreshed overnight.
• Rule-based exception handling. Reroute a no-access visit to the nearest engineer with the right skill, but don’t move any customer-confirmed slots in the next 90 minutes. Visible to the planner, not buried in a black-box optimizer.
• Workflow analytics. Average time per step, skip rates, error patterns, completion data. Where engineer hours actually went, not just where the routes went.

Running eLogii alongside Joblogic and the wider stack

The typical UK trade and field service stack: an FSM for the job workflow (Joblogic, BigChange, Simpro, Salesforce Field Service, MS Dynamics 365 Field Service, ServiceTitan), an ERP or accounts package for finance and customer master data (Sage, Xero, QuickBooks, NetSuite, MS Dynamics 365 BC), telematics for the vehicles (Samsara, Geotab, TomTom or the FSM’s own tracking), and a routing layer underneath the scheduling board for operations where the optimizer is the bottleneck.

eLogii is built for that shape. It plugs into Joblogic, BigChange, Simpro or whichever FSM is already in place as the routing layer, leaving CRM, mobile field execution, invoicing, BI and compliance documentation where they already are. The engineer opens Joblogic’s mobile app on site; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into Joblogic. The common patterns:

• Joblogic + eLogii. Joblogic owns CRM, scheduling board, mobile engineer app, asset and PPM, compliance documentation, financials and customer portal. eLogii owns the optimization layer where planning is dominated by multi-depot regional teams, recurring PPM at scale, or constraint-driven assignment for commercial work. Integration runs over Joblogic’s API surface and eLogii’s REST API.
• Joblogic + Vista AI roadmap context. Vista Equity Partners acquired Joblogic in September 2025 with over £100m for an AI-first roadmap; the group has continued an active M&A strategy across UK FSM and CMMS. eLogii’s role is independent of Joblogic’s product direction: the optimization engine layer, callable over REST.
• Joblogic + ERP + eLogii. When the financial system of record sits in Sage, Xero, QuickBooks or NetSuite via Joblogic’s native accounts integrations, eLogii reads operational data from Joblogic and runs the optimization, writing routes back for execution. The accounts integration stays where it is.

What makes the stack pattern straightforward:

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Zones, Schedules, Forms and Optimization, designed for clean integration into a wider stack.
• Full-parity sandbox at api-sandbox.elogii.com so integration work can run in parallel with the existing FSM/ERP rollout.
• Webhooks with live driver GPS and ETA stream push real-time state back to Joblogic, dispatcher view or customer-facing app. No polling, no cron jobs, no stale data.
• Bulk operations. POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• FSM, ERP and telematics independent. Customers running Joblogic, BigChange, Simpro, Salesforce FS or MS D365 FS use eLogii for the optimization layer alongside whichever FSM they already chose.

Joblogic exposes an API to customers and partners against plan tier. The two APIs combine cleanly: eLogii calls Joblogic to read jobs, engineers, vehicles, sites and recurring PPM templates, runs the optimization across the routing horizons Joblogic’s built-in scheduler is not designed to solve, and writes optimized routes and ETAs back. Joblogic’s mobile engineer app picks up the planned route; completion data flows back into Joblogic’s financials, compliance and BI.

API surface, side by side

Both products expose a REST API. Joblogic’s is the integration surface for an all-in-one UK FSM data model, available to customers and partners against plan tier. eLogii’s is the integration surface for a routing and optimization engine, with the optimizer itself callable as REST endpoints.

eLogii API

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Customers, Zones, Forms, Schedules and Optimization. Full reference.
• Authentication: ApiKey header, generated in Dashboard > Configuration > API Keys. Machine-to-machine without an OAuth round-trip.
• Sandbox: api-sandbox.elogii.com, full parity with production at api-35.elogii.com.
• Bulk operations: POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• Optimization callable via REST: all six modes available programmatically; planners can lock specific routes, manually reorder stops, or re-run with new constraints.
• Seven webhook event types, including Driver/Task Tracking Update with live GPS stream and Route ETAs Update. No polling, no cron jobs.
• Custom fields end-to-end through driver app, webhooks and reporting.
• FSM, ERP and telematics independent via REST API, including SAP, Oracle NetSuite, MS Dynamics 365 Business Central, Sage, Acumatica, IFS, Infor, Joblogic, BigChange, Simpro, ServiceTitan, FieldRoutes, Salesforce Field Service, Samsara and Geotab.

Joblogic API

• REST API available to customers and partners against the Joblogic plan tier. Joblogic does not lead with API documentation on the public site; tier and quota are confirmed directly with the vendor.
• Coverage: jobs, customers, engineers, vehicles, sites, PPM templates, financial records, compliance documents. Native accounts integrations to Sage, Xero, QuickBooks, KashFlow and FreeAgent.
• Sandbox: customer-arranged through Joblogic support rather than a self-serve developer environment.
• Webhooks: coverage depends on plan and integration partner; confirm against your tier.
• What’s not externally callable: Joblogic’s scheduling and route-calculation surface runs inside the product; there is no public “run optimization” REST endpoint with assignment and load-balancing modes documented.

For an integration team, the typical pattern when both products are in the stack: Joblogic owns the system of record for jobs, customers, engineers, vehicles, sites, PPM and compliance; eLogii reads jobs/customers/engineers/vehicles/sites from Joblogic over the API, runs the optimization across the horizons Joblogic’s scheduler is not designed for, writes optimized routes and ETAs back; Joblogic’s mobile app shows the route to the engineer; completion writes back to Joblogic for invoicing, compliance and reporting.

Pricing and time to live

eLogii runs alongside Joblogic; it does not replace what you’re paying Joblogic today. The question is what eLogii adds on top, and what it costs to add it.

eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined Joblogic + eLogii rollouts complete in 3 to 5 weeks including the connector build.

Joblogic publishes an entry point from £45 per month and runs three tiers (Standard, Premium, Enterprise) plus a dedicated Compliance product. Third-party reviewers report typical pricing scaling from around USD 79 per user per month up to about USD 6,500 per month for 100-user deployments, with feature and module variation across tiers. The pricing models compose: Joblogic charges per user for the FSM workflow, eLogii charges a platform fee for the routing layer. There is no per-seat cost from eLogii.

When eLogii on top of Joblogic starts to pay off

Adding eLogii alongside Joblogic

Three steps for Joblogic customers whose planning problem has grown past what the built-in scheduler is designed to solve. Joblogic stays in place for the FSM workflow; eLogii layers on as the routing engine.

Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.

Each layer, in depth

Joblogic’s scheduler is excellent at what it’s built for. Four patterns where operations grow past the layer where drag-and-drop plus the shunt function works, and where eLogii adds the optimization engine underneath. Each has its own deep dive:

Frequently asked questions

Is eLogii a Joblogic alternative or a complement?

Complement, in most cases. Joblogic owns the UK FSM workflow end to end: CRM, drag-and-drop scheduling, mobile engineer app, asset management, PPM, F-Gas and gas-certificate compliance, boiler servicing, customer portal, invoicing, job costing, stock control, accounts integrations. eLogii is the routing and optimization layer that runs alongside Joblogic when the planning problem starts to dominate: multi-depot regional teams, recurring PPM at scale, optimizer-driven assignment under constraint. Joblogic stays the system of record. the integration runs over Joblogic’s API surface and eLogii’s REST API.

When does adding eLogii on top of Joblogic make sense?

When the planning problem stops looking like “drag jobs onto the calendar and let the route calculation between them sort drive time” and starts looking like “decide the assignments themselves under hundreds of competing constraints, across multi-depot, recurring PPM and reactive work for the same engineers”. Joblogic’s scheduler is built around drag-and-drop, with route planning that “dispatches tasks to nearby team members, reassigns jobs to reduce transit time, and automatically schedules jobs to follow a more efficient travel route”. That covers a wide band of UK trade work. Once the operation needs the optimizer to do the assignment work under heavy constraints, eLogii layers on top.

Does Joblogic handle multi-engineer crews, PPM and multi-depot routing?

Yes at the workflow level. Joblogic’s scheduling page documents support for organising “multiple visits for multiple clients simultaneously”, recurring contracts and one-off visits, a “shunt” function that pushes or pulls subsequent visits for an engineer or team, and PPM schedules at site and asset level. What Joblogic’s published docs do not describe is constraint-aware optimization across multi-depot operations as a first-class input, programmatic re-optimization with operator-visible rules, or a documented optimization API. That’s where eLogii’s two-engine, six-mode optimizer adds depth, with Joblogic’s FSM workflow staying in place.

What changed when Vista Equity Partners acquired Joblogic in September 2025?

Vista’s investment included over £100m specifically for an “AI-first roadmap”. Since the acquisition, Joblogic has continued an active M&A strategy, acquiring Arantico (December 2025, HVAC/fire safety/waste/property FSM), Invida, Protean Software and Clik Software (CAFM/CMMS). The combined group covers wider UK trade verticals and adds CMMS capability. None of this changes the layer that eLogii fills: the routing and optimization engine underneath the FSM workflow, callable over REST.

How does eLogii integrate with Joblogic?

Integration runs over both products’ APIs. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook events including live driver GPS and Route ETAs Update. The typical pattern, Typically: eLogii reads jobs, customers, engineers, vehicles, sites and recurring PPM templates from Joblogic; runs the optimization across the routing horizons Joblogic’s scheduler doesn’t reach; writes optimized routes and ETAs back. The engineer opens Joblogic’s mobile app on site; the route underneath is the one eLogii planned. Completion writes back to Joblogic for invoicing, compliance and reporting.

How does pricing compare?

Joblogic publishes a “from £45 per month” entry point and tiered plans (Standard, Premium, Enterprise, plus a dedicated Compliance product). Third-party reviewers report typical pricing scaling from around USD 79/user/month up to USD 6,500/month for 100-user deployments. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from USD 3,000 per month. The pricing models compose: Joblogic charges per user for the FSM workflow, eLogii charges a platform fee for the routing layer. Customers typically report 3 to 4× return on investment within 6 months on eLogii.

How long does adding eLogii to a Joblogic stack take?

Typically 3 to 5 weeks from kickoff to a phased go-live, including building the custom connector against Joblogic’s API. eLogii reads jobs, customers, engineers, vehicles, sites and PPM templates from Joblogic; routes, ETAs and completion data flow back. Most teams start with the business unit where Joblogic’s built-in scheduler is leaking the most: usually a multi-depot regional book, a large compliance/PPM program, or the part of the operation where the planner is hand-rebalancing every morning. Joblogic stays in place for everything else.

Why would a Joblogic customer add a second routing engine instead of using Joblogic’s built-in scheduler?

Three reasons. First, Joblogic’s scheduler is built around drag-and-drop assignment plus route calculation between assigned stops; once the operation needs the optimizer to do the assignment work, the drag-and-drop board is not the tool. Second, eLogii customers at scale report operational outcomes that go past what FSM scheduling alone delivers: Brymec 30% productivity and 20% routing efficiency; ATS Building Products 98% improvement in deliveries per route; Porcelanosa 60%+ planning time cut; Unimasters 50% less planning time and 49% fewer service calls. Third, eLogii exposes the optimizer as REST endpoints with seven webhook events, so the routing layer integrates cleanly with whatever else the operation runs.

Is eLogii enterprise-grade?

Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo Pest Management (400 technicians, Tyro Group), Bristow & Sutor (200+ enforcement agents, 200,000+ case visits routed annually), Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.