




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.
Scheduling shouldn't equal firefighting. Add proven automation and optimization into your operations, and finally take control.
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
Timefold ships the core constraints you need, but remains easily extensible in case of business-specific requirements.
Mark jobs as mandatory or optional, and the solver always serves your highest-priority stops first when not everything fits.
Include breaks in employees' shifts and manage employees' time off, including making sure they get consecutive days off from work.
Assign multiple technicians, machines, or tools to tasks that require collaboration.
Enforce safety standards and maintenance intervals automatically.
Keep technicians working within defined zones to reduce travel and maximize local efficiency.
Schedule recurring or routine jobs intelligently around technician availability and building access.
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.
Reduce travel time and mileage per technician, increasing productivity and the number of jobs completed each day.
Favor assigning work to employees/contractors based on cost efficiency.
Ensure every job is assigned to a qualified technician while avoiding overqualification and idle time.
Include skill-based rotation logic so nurses gain experience across specialties without coverage gaps.
Automatically schedule while your customer is available.
Deployed in your own cloud account and region.
Self-hosted inside your own perimeter.
Split by policy and workload.
We run it for you, with in-region options.
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.
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.
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.
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.
Yes. Timefold plans across thousands of technicians and tens of thousands of weekly visits, and re-solves disruptions in seconds.
