Docs
  • Solver
  • Models
    • Field Service Routing
    • Employee Shift Scheduling
    • Pick-up and Delivery Routing
    • Task Scheduling
  • Platform
Start Free Trial
  • Timefold Platform
  • More information
  • FAQs
  • Modeling your planning problem

Timefold Platform

  • Basics
    • Introduction
    • Getting started
    • Scheduling API concepts
    • Platform concepts
    • Available models
      • Model catalog and documentation
      • Model maturity and versioning
      • Trialing Timefold models
      • Bring your own model
  • How-tos
    • Model and dataset management
      • Dataset lifecycle
      • Dataset details
      • Datasets overview
      • Dataset revisions with /from-patch
      • Configuration profiles and parameters
      • Maps service
    • Analyze
      • Insights
      • Comparisons
      • Experiments
      • Timefold Copilot
    • Manage organization
      • General
      • Members
      • Tenants
      • Tenant type and model release lag
    • Manage tenant
      • Details
      • API Keys
      • Secrets
      • Members
      • Models
      • Notifications
      • Solve queue
      • Audit log
    • Manage user
      • Personal access tokens
      • Command palette
    • Job-oriented guides
      • Balancing different optimization goals
      • Validating an optimized plan with Explainable AI
      • Uncovering inefficiencies in operational planning
      • Responding to disruptions with real-time planning
      • Designing better routing plans with (just enough) traffic awareness
  • API integration
    • Before you integrate
    • Model API usage
    • Receiving model API results
      • Webhooks
      • Server sent events (SSE)
      • Polling
    • Handling changes to your planning data
    • Integration scenarios
      • Multiple environments and clusters
      • Data residency requirements
      • Air-gapped environments
    • Platform API usage
  • More information
    • FAQs
      • Modeling your planning problem
      • Planning horizon and replanning
    • Changelog
    • Feature requests
    • Pricing plans and capabilities
    • Self-Hosted
      • Self-Hosted vs. Timefold Cloud Platform
      • Installation instructions
      • Upgrade instructions
      • Troubleshooting
    • Support
      • Contacting support
      • Platform status
      • Troubleshooting
    • Trust
      • Risk profile
      • Product security
      • Data security
      • Legal and privacy
      • AI legislation compliance
      • Trust center
Ask Claude Ask ChatGPT

Modeling your planning problem

Answers to common questions about modeling your planning problem in the Timefold Platform.

  • Which model fits my planning problem?
  • Should I plan my whole operation in one dataset or split it up?
  • Which rules belong in the model, and which can I handle in my own system?

Which model fits my planning problem?

Choose the model based on what you assign, and whether travel between locations is part of the work.

Model Use it when Typical use cases

Field Service Routing

People travel between locations during their shift, and the order of their visits matters.

Field service, home care, and facility maintenance

Pick-up and Delivery Routing

Drivers pick up people or goods at one location and take them to another.

Non-emergency medical transportation, and courier and express delivery

Employee Shift Scheduling

Employees work shifts at a location, and you decide who works which shift.

Hospitals and healthcare, retail, security, and hospitality

Task Scheduling

Jobs run on machines, employees, or other resources, often with dependencies between jobs.

Discrete manufacturing, project scheduling, and single-site maintenance

If employees travel between several locations during a shift, and the route or the order of visits matters, use the Field Service Routing model. The Employee Shift Scheduling model calculates straight-line distances between locations and doesn’t plan routes.

The Task Scheduling model has Preview maturity, so backward-incompatible changes can still be introduced.

If your planning problem matches more than one model, contact us to discuss which one fits best.

For more information, see the model catalog.

Should I plan my whole operation in one dataset or split it up?

Split your operation into separate datasets when its parts don’t share resources or work. Keep the parts in one dataset when they do.

For instance, if each branch has its own employees and its own work, solve one dataset per branch. Smaller datasets solve faster, and a problem in one branch’s data doesn’t affect the others.

If some resources, for instance employees, vehicles, or machines, work for more than one branch, keep those branches in one dataset. The model can then decide where the shared resources are needed most. When you split them, each dataset is planned without knowing about the others, which usually leads to a worse plan overall.

If you need different kinds of plans, for instance shift schedules and routes, use a separate model for each. Solve them in order, and use the output of one plan to prepare the input for the next. For instance, use the shifts from your shift schedule as the vehicle shifts when you plan routes.

Which rules belong in the model, and which can I handle in my own system?

Include a rule in the model when it can make one plan better than another. When a rule doesn’t change which plan is best, handle it in your own system, before you submit the dataset or after the model returns the plan.

For instance:

  • Leave work out of the dataset when it can’t be done yet, for instance a job that’s waiting for parts or materials. Add it to a later dataset when it’s ready.

  • Handle steps that only depend on the finished plan in your own system, for instance creating work orders or notifying customers.

Some work can’t be expressed with the model’s features. Leave that work out of the dataset, and show it in your planning tool so planners can schedule it manually. If that work takes up a resource’s time, make sure the dataset shows the resource as unavailable for that time, so the model plans around it.

  • © 2026 Timefold BV
  • Timefold.ai
  • Documentation
  • Changelog
  • Send feedback
  • Privacy
  • Legal
    • Light mode
    • Dark mode
    • System default