workforce scheduling.

Build shift plans that match staff to demand. Respect labour law, works agreements, qualifications, preferences and budget.

problem familyscheduling
complexityNP-hard
methodsMIP · CP · ML demand forecasting
flagshipsmanifest · takt
The question your planners askWho works which shift next month, so every position has a qualified person and every rest period holds?
In mathematical terms

Workforce scheduling combines integer programming for shift assignment with constraint programming for complex labour rules. kint handles several skills and locations at once and takes demand forecasts as input.

MIP · CP · ML demand forecasting

Why it is hard

where workforce scheduling gets hard.

01dense labour rules

Working-time law, rest periods, maximum consecutive days and overtime rules form a dense set of constraints that differs by contract and region.

02demand changes by the hour

Staffing needs shift across the day and the week. Matching people to that curve is hard by hand.

03every person is different

Skills, certificates, part-time contracts and availability make each assignment a separate choice.

How kint solves it

from the rules to the bound.

kint's decision agent writes the model from the planners' description. In the pilot, kint's forward deployed engineers review it with the experts. Then the solver does this.

01

forecast the workload

Workload per hour and location comes from your history, or from the operational plan it depends on.

02

model shifts and rules

Availability, qualifications, labour law, budget and fairness rules all become constraints.

03

solve MIP and CP together

Integer programming assigns the shifts. Constraint programming enforces the complex rules.

04

publish and adjust

Swap requests and absences trigger a new run. Coverage stays valid as the plan changes.

What the answer contains

a workforce scheduling plan, with its reasons.

Below are the parts of a workforce scheduling result. Planners check them before the plan is released.

the anatomy of an answer
  • plan
    A shift plan per person and day, checked against every rule.
  • binding limit
    For example: the number of certified people on night shift binds, not the headcount.
  • sensitivity
    What one more certification, or one more part-time contract, would cover.
  • bound and gap
    Bound and gap for the roster, stored with the run.
  • record
    Data version, model version, who reviewed the model and who released the plan.

Illustrative. Content comes from your data and rules.

bring us this decision.

Bring one recurring workforce scheduling decision with its rules and data. Your planners get a first model they can read.

Results
Plan, binding limit, sensitivity, bound and gap, record
Data centres
Operated in Germany, or in yours
all problem types
routes, schedules, stock and price
Contact
hello@kint.pro