The easiest way to upgrade your field service operations
An API, not another platform
Plug our scheduling and routing engine into the stack you already run to automate and optimize your field work. No migration, no new system of record, no change management, just a clean REST API. 
Your systems already hold the plan, Timefold builds it
Optimize your field service operations, without replacing your stack
Timefold optimizes the data that's already in your systems and returns the result. No new system of record, no new UI for your team to adopt.

Integrate advanced scheduling optimization into the systems you already use

No matter the GIS, EAM, FSM, or ERP you use, the data a good schedule needs is already there. Timefold reads the data through an API, and returns it optimized. The only work on your side is making that data available and structuring it for the API.

ThE Field Service routing api in numbers

Works in production, at scale

Scheduling shouldn't equal firefighting. Add proven automation and optimization into your operations, and finally take control.

50+ constraints

Business rules in the API, purposefully designed for Energy and Utilities field operations. 

<1 second to re-optimize

In case of emergency requests, traffic, sick calls, or other real-time dirsuptions.

Up to +50% productive time

More jobs per day by batching jobs, matching skills, and

-25% travel time

Average customer results after implementation.

40,000 jobs

Largest dataset optimized in one run so far.

Proof before commit

Run a free PoC and see the impact of scheduling optimization on your KPIs. 

/
Send us field work data of a certain period
/
We run the data through our optimization API
/
Compare the bottomline of your current schedules against ours
How it works

JSON in, JSON out

Timefold is tech-agnostic: Problem JSON in, solution JSON out, nothing retained between calls.

Production-ready model / No setup required / Works with any stack via REST API / Start with sample data or your own

Feature-rich out-of-the-box, extensible if you need it to be

Timefold ships the core constraints you need, but remains easily extensible in case of business-specific requirements.

Priority stops

Mark jobs as mandatory or optional, and the solver always serves your highest-priority stops first when not everything fits.

Breaks and time off

Include breaks in employees' shifts and manage employees' time off, including making sure they get consecutive days off from work.

Multi-resource coordination

Assign multiple technicians, machines, or tools to tasks that require collaboration.

Safety and compliance

Enforce safety standards and maintenance intervals automatically.

Geofencing & area coverage

Keep technicians working within defined zones to reduce travel and maximize local efficiency.

Preventive maintenance windows

Schedule recurring or routine jobs intelligently around technician availability and building access.

Visit SLAs 

Attach contractual response time commitments directly to visits so deadlines are met automatically, not manually monitored. High-priority accounts are protected by the schedule itself, not a dispatcher's memory or a last-minute check.

Route optimization

Reduce travel time and mileage per technician, increasing productivity and the number of jobs completed each day.

Cost optimization

Favor assigning work to employees/​contractors based on cost efficiency. 

Advanced skill & certification matching

Ensure every job is assigned to a qualified technician while avoiding overqualification and idle time.

Training and skill development

Include skill-based rotation logic so nurses gain experience across specialties without coverage gaps.

Recommended time windows

Automatically schedule while your customer is available.

Flexible hosting options
Run it where your policy says it must.
Timefold runs where you need it (with air-gapped and in-region options) so scheduling data stays where you choose. Compliance is your call, not the ours.

Your cloud

Deployed in your own cloud account and region.

On-premise

Self-hosted inside your own perimeter.

Hybrid

Split by policy and workload.

Managed

We run it for you, with in-region options.

IT FAQ
The questions IT leaders ask first
Do we have to replace our FSM, ERP, or GIS?
+

No. Timefold reads data from the systems you already run, optimizes it, and returns the plan to them. Your platforms stay the system of record and your dispatchers keep working where they already do. It is an add-on, not a migration.

How much integration work is on our side?
+

Less than you would expect. Your side is making the data available and structuring it for the API: an event listener, a problem-construction step, an HTTP call, and a write-back, typically a few hundred lines. You decide how the optimized plan flows back into your stack.

Where does our scheduling data live, and can we self-host?
+

Wherever your policy requires: on-premise, in your own cloud, hybrid, or managed, with air-gapped and in-region options. Timefold is stateless, so nothing is retained between calls. One major European rail operator runs it on-premise on Kubernetes to meet its data-protection requirements.

Is it a black box, or can we audit its decisions?
+

It is auditable by design. The optimization is deterministic, so the same input always produces the same plan, and every assignment comes with a score breakdown showing which constraints applied and what each one cost. Dispatchers can review, override, and re-solve.

Can it handle utility-specific rules like certifications, crews, SLAs, and emergencies?
+

Yes. Timefold plans across thousands of technicians and tens of thousands of weekly visits, and re-solves disruptions in seconds.

When scheduling works, everything works
Get the most out of what you already have. Benchmark it for free, on your own data.