One take
Three minutes, no cuts.
A real venue, its real settings, and a week that has already been solved. Nothing here is sped up, trimmed or staged — including the parts where somebody scrolls.
Raw Bar · 11 staff · 6 shift templates · 61 places filled
01
The week that already ran
Roster health for a real venue, scored out of 100 with every point traceable — rules kept, cover, even spread — and the six weeks before it.
02
The settings the solver reads
Standing rules, shift templates, and the staff table: minimum and maximum hours, days off, blocked days. These are hard constraints, not preferences.
03
What staff see
The other side of the same week — marking availability shift by shift, and requesting leave that becomes a hard day off once approved.
04
The assistant, mid-task
Opened from the roster page with a generated week behind it, answering a question about locking beside the grid rather than over it.
05
The week itself, and getting it out
The grid at real scale, an assignment edited by hand, and the roster leaving: printed for the wall, copied into a staff chat, or exported for payroll and Deputy.
Then take the parts of it apart.
The three claims underneath what you just watched, each with its own evidence.
Do that with your own week.
Set your venue up once, generate a week, and see whether it holds.