How we measure

Scheduling results depend on the group being scheduled. So we measure on one fixed group, the same every time, and report every month we run, not the best one.

The reference group

An entirely fictional emergency medicine group. No customer's data is in it.

The rules

The defaults a new SahVir site starts with, as hard limits: at most 5 days in a row, at least 3, 2 days off between runs, 10 hours' rest between shifts, at most 2 weekends a month (more only for someone who opted in), and nobody over their maximum hours. A shift that can only be filled by breaking one of these is left open and listed.

Results: SahVir Optimize, all six sites together

MonthShiftsFilledLeft openRules broken
November 20261,00897.9%210
December 20261,05297.9%220
January 20271,03697.4%270
February 202794499.6%40

Optimize as it runs in production: the strict version (no extra hours, no extra weekend), 90 seconds per month. Every schedule is scored by one independent rule check. Measured October 2026.

Optimize and instant generation

Every plan includes instant generation, which builds a month in seconds. Optimize, on the Professional plan, builds every site together and takes a few minutes. On this group, Optimize left fewer shifts open than instant generation in every month, with no rule broken by either. How many fewer depends on the group and the month, so in a pilot we build your own month both ways.

What this does not show

There are no human-built schedules for a fictional group, so this cannot show how SahVir compares with your scheduler. That is what the free audit and a pilot are for: the audit scores your own last month on the same checks, and in a pilot your scheduler and SahVir build the same month side by side.

See where your own month stands: run the free schedule audit.