eLogii + BigChange: When to Add eLogii to BigChange

Where each platform leads

BigChange and eLogii sit in different layers of the same field-service stack. BigChange is the all-in-one workflow product: CRM, scheduling board, mobile app, vehicle tracking, financials, BI, the Lightning AI agent layer, subcontractor Network. 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: BigChange stays the system of record for jobs, customers, invoicing, mobile field execution and BI. eLogii reads jobs, engineers, vehicles and depots from BigChange’s RestAPI, runs the optimization across the horizons BigChange’s built-in scheduler is not designed for, and writes optimized routes and ETAs back. The engineer opens the JobWatch app on site; the route they take is the one eLogii planned. BigChange keeps the workflows it owns end to end; eLogii handles the optimization layer underneath.

What BigChange does well, what eLogii adds

This is not a head-to-head FSM comparison. BigChange is the FSM workflow and eLogii is the routing engine that runs underneath it. The tables below cite BigChange’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 BigChange’s scheduling and routing covers

What eLogii adds on top of BigChange

Sources: BigChange Job Scheduling, BigChange Features, BigChange pricing; eLogii optimization engines. Verified June 2026.

Field execution and customer experience

This is where BigChange shines and eLogii deliberately does not compete on the FSM workflow itself. Both platforms publish capable mobile and customer-facing surfaces; BigChange’s is broader because it is the entire job lifecycle, eLogii’s is deeper specifically on routing and delivery execution.

API surface and developer experience

Sources: eLogii API documentation, BigChange pricing – RestAPI module. Verified June 2026.

Scale, security and commercial

Sources: bigchange.com, BigChange pricing, Capterra, GetApp reviews. Verified June 2026.

Route optimization, in detail

This is where BigChange and eLogii do different jobs. BigChange’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.

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

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

• Drag-and-drop assignment, then route calculation. “Drag jobs onto your team’s calendar and watch them appear instantly on mobile devices.” The accompanying route optimization is described as: “calculate the fastest route between jobs while accounting for traffic, engineer skills, and vehicle equipment.”
• Multi-day and multi-engineer supported as assignment. “Create jobs that span multiple days and assign them to one or more engineers.” Multi-engineer reassignment is supported via bulk drag-and-drop.
• Recurring PPM supported as schedule generation. “Set up recurring service schedules for PPM work” with automatic generation at the specified intervals.

BigChange’s reported planning outcomes, taken from the same product page, are 11% less drive time, 10% time saved per job and 10% less fuel used. Those are real numbers for a real workflow product. What BigChange’s docs don’t claim 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: BigChange’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 BigChange’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 repeat jobs onto today, slot the new ones in, look at the map”, BigChange 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 four depots, balance against next week’s recurring program, protect the SLA-locked stops, route around the engineer who’s off Tuesday”, BigChange’s scheduler is being asked to do a job it wasn’t built for. eLogii covers that side via REST API; BigChange stays in place for everything else.

When eLogii’s depth starts to matter

BigChange’s scheduler covers a wide band of field-service operations 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. BigChange’s “calculate the fastest route between jobs” model assumes the assignments are already correct.
• 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. BigChange treats depot as a per-engineer starting point.
• Recurring programs at thousands of stops. Quarterly compliance programs, monthly PPM books, recurring commercial service contracts where SLAs and cadences interact. BigChange generates the schedule; the optimization across the generated stops 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, BigChange’s built-in scheduler is the right tool and adding eLogii is over-engineering. The honest answer for many BigChange 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

BigChange 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 BigChange’s own 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 BigChange and the wider stack

The typical field service stack: an FSM for the job workflow (BigChange, Simpro, Joblogic, Salesforce Field Service, MS Dynamics 365 Field Service, ServiceTitan), an ERP for finance, inventory and customer master data (SAP, NetSuite, MS Dynamics 365 BC, Sage, Acumatica), telematics for the vehicles (BigChange’s integrated tracking, Samsara, Geotab, TomTom), 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 BigChange, Simpro or whichever FSM is already in place as the routing layer, leaving CRM, mobile field execution, invoicing, BI and the Lightning AI agents where they already are. The engineer opens the JobWatch app on site; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into BigChange. The common patterns:

• BigChange + eLogii. BigChange owns CRM, scheduling board, JobWatch mobile, vehicle tracking, financials, BI and the Lightning agents. eLogii owns the optimization layer where planning is dominated by multi-day commercial books, multi-depot regional teams or recurring programs at scale. Integration via the BigChange RestAPI module and eLogii’s REST API.
• BigChange + ERP + eLogii. When the financial system of record sits outside BigChange (SAP, NetSuite, MS Dynamics 365 BC), eLogii reads operational data from BigChange and customer/SKU master data from the ERP via REST API, runs the optimization, and writes routes back to BigChange for execution.

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 BigChange, 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 BigChange, Simpro, Joblogic, Salesforce FS or MS D365 FS use eLogii for the optimization layer alongside whichever FSM they already chose.

BigChange itself exposes a RestAPI module under the “Extras” section of its plan, with REST/JSON endpoints across the job, customer, engineer and vehicle data model. The two APIs combine cleanly: eLogii calls BigChange to read jobs, engineers, vehicles, depots and skills, runs the optimization across the routing horizons BigChange’s built-in scheduler is not designed to solve, and writes optimized routes and ETAs back. BigChange’s mobile JobWatch app picks up the planned route; completion data flows back into BigChange’s financials, BI and Lightning agents.

API surface, side by side

Both products expose a REST API. BigChange’s is the integration surface for an all-in-one FSM data model. 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, BigChange, Simpro, ServiceTitan, FieldRoutes, Salesforce Field Service, Joblogic, Samsara and Geotab.

BigChange API

• REST API exposed as the “RestAPI” module on the BigChange plan, listed under “Extras” on bigchange.com/pricing. Paid add-on alongside the Standard (GBP 79.95/license/month) or Plus (GBP 99.95/license/month) tier.
• Coverage: jobs, customers, engineers, vehicles, financial records, BigChange’s tracking data model. Designed for integration with accounting (Xero, Sage, QuickBooks, NetSuite via add-on connectors), ERP, marketplaces and customer-facing apps.
• Sandbox: customer-arranged through BigChange support rather than a self-serve developer environment.
• Webhooks across job lifecycle events; live-GPS event coverage is product-feature-driven via the vehicle-tracking module rather than the public API.
• What’s not externally callable: BigChange’s scheduling and route-calculation surface runs inside the product; there is no public “run optimization” REST endpoint with assignment and load-balancing modes.

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

Pricing and time to live

eLogii runs alongside BigChange; it does not replace what you’re paying BigChange 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 BigChange + eLogii rollouts complete in 3 to 5 weeks including the integration.

BigChange publishes pricing directly on bigchange.com/pricing: Standard at GBP 79.95 per license per month (vehicle tracking, fleet management, quote/invoice, job card management, customer booking portal, BI dashboards) and Plus at GBP 99.95 per license per month (everything in Standard plus team planning/scheduling, device management, rugged hardware, free installation, 2-year warranty). Add-ons charged on top: AI Dashcams, Fleet, Fuel Cards, RestAPI module. The pricing models compose cleanly: BigChange charges per license 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 BigChange starts to pay off

Adding eLogii alongside BigChange

Three steps for BigChange customers whose planning problem has grown past what the built-in scheduler is designed to solve. BigChange 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

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

Frequently asked questions

Is eLogii a BigChange alternative or a complement?

Complement, in most cases. BigChange owns the FSM workflow end to end: CRM, job scheduling, mobile JobWatch app, vehicle tracking, financials, business intelligence and the Lightning AI agent layer. eLogii is the routing and optimization depth layer that runs alongside BigChange when the planning problem starts to dominate: dense multi-day commercial books, recurring service programs at scale, multi-depot regional teams, optimizer-driven assignment under heavy constraints. BigChange stays the system of record; eLogii reads jobs and writes back optimized routes over its REST API. The connection between the two products is custom-built using BigChange’s RestAPI module (a paid add-on on the BigChange plan) and eLogii’s REST API.

When does adding eLogii on top of BigChange make sense?

When the planning problem stops looking like “route between the jobs the planner already assigned today” and starts looking like “decide the assignments themselves under hundreds of competing constraints, across multiple days, multiple depots and recurring cadences”. BigChange’s scheduler is built around drag-and-drop, route-between-jobs heuristics, with route optimization that “calculates the fastest route between jobs while accounting for traffic, engineer skills, and vehicle equipment”. That fits most field service operations well. Once the operation needs the optimizer to do the assignment work, multi-depot to a regional book, multi-day across crews, recurring patterns at thousands of stops, eLogii layers on top via REST API.

Does BigChange handle multi-day, multi-technician and multi-depot routing?

Yes for the basics, with operator effort. BigChange’s job scheduling explicitly supports multi-day jobs (“create jobs that span multiple days and assign them to one or more engineers”) and multi-engineer assignment via drag-and-drop. PPM and recurring schedules are supported. What BigChange’s published docs don’t claim is constraint-aware optimization across all three at once, multi-depot routing as a first-class input, or programmatic re-optimization with operator-visible rules. That’s where eLogii’s two-engine, six-mode optimizer adds depth, with the FSM workflow staying in BigChange.

How does eLogii integrate with BigChange?

Integration runs over both products’ REST APIs. BigChange exposes a RestAPI module that customers add to their plan; 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, engineers, vehicles and depots from BigChange, runs the optimization across the routing horizons BigChange’s scheduler doesn’t reach, writes optimized routes and ETAs back. The engineer opens the BigChange mobile app on site; the route underneath is the one eLogii planned. Completion writes back to BigChange for invoicing and reporting.

How does pricing compare?

BigChange publishes two tiers on bigchange.com/pricing: Standard at GBP 79.95 per license per month and Plus at GBP 99.95 per license per month, with the RestAPI module, AI Dashcams and Fleet/Fuel Cards charged on top. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from $3,000 per month. The pricing models compose: BigChange charges per license 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, driven by drive-time reduction, planner-hour reduction and SLA improvements.

How long does adding eLogii to a BigChange stack take?

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

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

Three reasons. First, BigChange’s scheduler is built around “fastest route between jobs” calculation after the planner has assigned them; once the operation needs the optimizer to do the assignment, BigChange is not the tool. Second, BigChange’s reported customer outcomes (11% less drive time, 10% time saved per job, 10% less fuel) reflect operational improvements at small to mid-sized teams; eLogii customers at scale report multiples of those outcomes (Brymec 30% productivity and 20% routing efficiency; ATS Building Products 98% improvement in deliveries per route; Porcelanosa 60%+ planning time cut). 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.