Reading a Vendor Claim

Scheduling software is sold on savings that depend entirely on what you were doing before.

"Reduces labour cost by N percent"

Usually: against a baseline of manual scheduling with no forecast at all.

Ask: against what baseline, and does the figure include predictability pay, overtime and recruitment?

Then measure your own six numbers first, which gives you the baseline the claim needs.

"Fair workweek compliant"

Compliance is a property of your configuration for your locations, not of a product.

Ask: which jurisdictions are in the rule library, how often is it updated, and what happens when an ordinance changes mid-contract?

And ask whether it distinguishes employer-initiated from worker-initiated changes, because the entire premium mechanism rests on that.

"AI-powered scheduling"

Ask what the objective function is.

If the answer is cost subject to coverage, that is the whole thing — and stability, fairness and hours distribution are absent unless you can add them.

Ask whether they can be added, which sorts the market quickly.

"Real-time optimisation"

Means rebuilding close to the day, which is the practice the law is moving against and which produces the changes you will pay for.

Ask what it does to a published schedule, and whether publication can be locked.

"Employee self-service"

Ask what the employee can actually do: see the rota, set availability, request a swap, see hours against what they asked for.

Several products mean only the first, which leaves the informal layer intact.

"Automated compliance"

Ask whether the constraints are hard or advisory.

A warning is not a control, and the demonstration will not show you which it is unless you try to publish a breach.

The general test

Any claim without a named jurisdiction, a number, or a screen you can break is a statement of intent.

Convert each into a question and ask it in writing, because written answers are more careful and can be attached to a contract.

Ask in writing

The difference between a sales answer and a commitment.

Send the questions by email rather than asking in a demonstration.

Ask for the answers to be attached to the contract.

Written answers are noticeably more careful, and the carefulness is itself informative.

Where a claim matters — which jurisdictions, hard or advisory constraints, what the optimiser weights — it belongs in a term rather than on a slide.

Check the difficult case

Use the current feature overview to frame one representative case. The useful evidence is what happens when an employee questions an entry and a manager must correct and export it.

Independent reference

For a thematic point of reference, see Capterra. Its current material provides useful context beyond product documentation.