Choosing Scheduling Software

Almost every product here can build a rota. They differ in what they will let you constrain and what they measure success by.

The constraint questions

Can minimum rest between shifts be a hard constraint, not a warning?

Can under-18 limits be enforced, with term-time variation and automatic re-check at a birthday?

Can capability requirements be enforced per shift type, including on swaps?

Can maximum hours be checked over a reference period, not just per week?

A product that answers "we show a warning" to these is not enforcing anything, because warnings are dismissed at eight in the evening.

The stability questions

These are the ones nobody asks.

Can the optimiser be given a stability objective — keeping people on similar shifts week to week — or only cost?

Can it be told to preserve last week's pattern where possible?

Does it report schedule variability per person, or only cost variance?

Can it lock a published rota so changes require a deliberate action that is recorded?

The compliance questions

Does it know the fair workweek rules for your locations, and is the rule library maintained?

Does it calculate predictability pay, and can it attribute it to the site?

Does it distinguish employer-initiated from worker-initiated changes? This is the distinction the whole premium rests on.

Does it retain records for the required period, commonly three years?

The worker-facing questions

Can people see the rota on a phone without an account nobody uses?

Can they set and update availability themselves?

Can they request a swap and see its status?

Can they see their hours against what they said they wanted?

A product that is only an administrator tool will produce the informal layer the record then misses.

The trial

Build one real week for your hardest site, yourself.

Include the awkward cases: a split shift, an under-18, a single-staffed break period, a keyholder constraint.

Try to publish something that breaches a rest rule and see whether it stops you.

Then change a published shift and see what it records and calculates.

Red flags

Cost optimisation presented as the headline and only feature.

On-call scheduling as a supported workflow.

No distinction between employer and worker-initiated changes.

Compliance described as a feature rather than as a configurable rule set per location.

Try to publish a breach

The trial step that tells you whether constraints are real.

Build a rota with an eight-hour turnaround and attempt to publish it.

If it warns and lets you through, the constraint is advisory, which means it will be overridden on a busy evening.

Do the same with an under-18 limit and a capability requirement, because the demonstration will never show you this.

Turn the principle into a test

For a concrete product reference, employee scheduling software pricing can help turn the principle above into a test. Verify the current behaviour in a trial and judge the record it creates, not the wording on the page.