Solving the full problem instead of simplifying it away

Why the scheduling method matters

Why the scheduling method matters

Creating a schedule is not about filling boxes.
It is about balancing coverage, contracts, skills, fairness, and cost at the same time.

The way a scheduling engine makes decisions determines whether the result is:

  • Just workable
  • Or consistently reliable
Why APOLLO uses ILP

Why APOLLO uses ILP

As scheduling becomes more complex, intuition and best-effort logic stop scaling.

More agents, more skills, stricter rules, and tighter coverage create trade-offs that are impossible to manage manually.

APOLLO uses ILP because it:

  • Guarantees compliance without manual checking
  • Balances service, cost, and fairness transparently
  • Reduces planner rework
  • Produces schedules that hold up under change

APOLLO does not approximate schedules.
It computes the best schedule that can exist under your rules.

Comparing the differences

Rule-Based Scheduling

Fixed rules, applied one by one

Rule-based systems follow instructions written by people.
Each rule is applied in a fixed order.

Typical rules sound logical:

  • Assign full-time agents first
  • Do not exceed weekly hour limits
  • Fill early shifts before late shifts

What the system does

The system applies the first rule, then moves to the next.
Once a decision is made, it is rarely reconsidered.

What this means in practice

If an early rule uses too many skilled agents, later rules may fail.
The system does not step back to ask: “Is this the best overall schedule?”

Result

  • Easy to understand
  • Works for simple environments
  • Becomes fragile as rules grow
  • Planners often need to fix the output manually

Rule-based scheduling follows instructions, not outcomes.

Heuristic Scheduling

Best-effort decision making

Heuristic systems try to improve on rules by choosing what looks best at the moment.
Instead of strict instructions, they use scoring and priorities.

What the system does

  • Scores assignments based on cost, skills, or preferences
  • Chooses the highest-scoring option first
  • Adjusts parts of the schedule if problems appear later

What this means in practice

A decision can look good locally but cause issues elsewhere.
The system may correct this, but it has no full picture of the entire schedule.

Result

  • More flexible than rule-based systems
  • Fewer obvious mistakes
  • Results can change as data or tuning changes
  • Still no guarantee the schedule is the best possible one

Heuristics aim for “good enough,” not certainty.

Integer Linear Programming (ILP)

Looking at the whole puzzle at once

ILP takes a different approach.
Instead of making decisions one by one, the system looks at the entire schedule at the same time.

A simple way to think about it

Imagine laying all the rules, agents, and shifts on the table at once.
The system asks one question:
“What is the best possible schedule that satisfies all mandatory rules and balances everything else as well as possible?”

What the system does

  • Treats each assignment as a clear yes or no decision
  • Applies all rules simultaneously
  • Never breaks hard rules such as labor laws or contracts
  • Optimizes preferences and fairness where possible

What this means in practice

If demand, availability, or rules change, the system recalculates the entire schedule.
It does not patch or guess. It recomputes.

Result

  • Schedules you can trust
  • Predictable outcomes
  • Clear trade-offs when preferences conflict
  • Scales without becoming harder to manage

ILP does not follow rules in order. It finds the best overall result.

Summary
Rule-BasedHeuristicAPOLLO ILP
How decisions are madeRules are applied one by one in a fixed orderBest-looking option is chosen at each stepAll decisions are evaluated at the same time
View of the scheduleLocal and sequentialPartially globalFully global
Handling of rulesLater rules adapt to earlier decisionsRules may be adjusted if conflicts appearAll rules are applied simultaneously
Hard rules (laws, contracts)May require manual checksUsually respected but not guaranteedAlways enforced
Preferences and fairnessHard to balance consistentlyOptimized where possibleOptimized with clear trade-offs
Reaction to changeManual rework requiredPartial recalculationFull schedule recalculated
ScalabilityWorks only at small scaleMedium scale with tuningScales to hundreds or thousands of agents
Result qualityValid but fragileGenerally acceptableOptimal or near-optimal
Planner effortHighMediumLow