A drafted week you can question.
Generate the week and read it like a colleague's work. Every shift says why it exists and why that person got it. Every open shift says who could not take it, and why.
Your needs. Your ranking.
Tell it how many people each part of the day needs and mark the peak. Rank your team by sales per hour worked. The draft fills peak hours from the top of that list, inside your rules.
Ranked by sales per hour worked.
Higher-ranked people get more hours and the peak shifts first. A manager can set any value by hand.
Ask any shift why.
Two answers on every draft shift: the need it covers, and the person's place in the ranking.
A gap with a reason is a decision.
When a shift stays open, the draft lists every person and the rule that stopped each one. "Can anyone work Sunday?" becomes a choice you can make in a minute: allow a six-day week, move a day off, or leave it open.
What you learn, and when.
On each shift
The need it covers, such as "5pm – 8pm peak, 3 people needed", and the person's place in the ranking, such as "rank 1 of 7".
On each open shift
A count of who could not take it and why: "7 people can't: 3 already working then, 2 at their days limit, 2 on time off."
On preferred days off
Preferred days off are kept first. When one has to give to cover a need, the draft lists it, so you can make the call and tell the person.
In the draft details
The whole run in one view: needs not filled, preferences not kept, each person's shifts, hours and peak shifts, and what stopped them getting more.
On the board
Your hours budget against the week's scheduled hours, updated as you edit.
Does the draft go live on its own?
Where do sales-per-hour numbers come from?
How does the hours budget work?
What happens to edits if I generate again?
See it on a week from your own stores.
Bring your store hours and your Saturday problem. We will draft a week together, and you can ask any shift why it is there.
Book demo