Pick a group, then choose what to sort by — one factor at a time; clicking the active one turns it off. The two shift chips toggle on and off the same way (keeping their picked shifts); use their ▾ arrow to open the day/meal picker. Each factor is scored 0–100 within the group, and the list ranks by the factor you've turned on.
Day of week:
Employee:
Everything here is read straight off the saved weeks — nothing is scored or weighted, and there are no fixed thresholds. Each who-works-it line is sorted by frequency and split at its natural break — the biggest drop in the line — so "normally works it" is decided per day, per meal, by the data itself. A fill-in is anyone below the break who showed up in a week someone above it missed. A double counts as both a lunch and a dinner, but the rules keep them separate — someone whose only lunches happen inside doubles is not called a lunch worker.
Next week's draft —
Shift limits — min–max people per shift:raising a min pushes the max up with it; a max can never drop below its min
Click any cell to cycle blank → lunch → dinner → double → request off → party. Hand-placed cells are kept when you hit Generate — the engine only adds around them (editing a generated cell makes it yours, so reconciliation won't touch it either). The draft lives in your data, so the normal Save button is what saves it as a draft; Add to schedule turns it into a real week.
Extra days — pre-placed before the schedule is generated
Parties & banquets — a custom shift with its own time; they're working, but unavailable for normal shifts
Availability — per person, per shift (what the engine may use)
Set = their set schedule — filled first, up to their usual shifts/week. Whenever = happy to fill in; auto-used when a day is under its minimum. Rarely = can fill in but it's a last resort — never auto-placed, only suggested in the notes when a day runs short. ✕ Never = never scheduled. Click a cell to change it. Until you touch someone, their row follows the auto rules: Set on their natural-break days (with their usual meal), Rarely where they've worked at least once, Never where they have no history.
How Generate The Schedule drafts the week: each person's usual days are ranked by how often they work them (recent weeks count double) and filled with their usual shift, stopping at their average shifts per week; then coverage is reconciled against the min/max limits — trimmed above max, topped up toward min using people marked Whenever in the Availability tab, and anything unresolved is listed in the notes for your call. Parties pin a pink Party shift the moment you assign staff, so those people count as working but get no normal shift that day. Requests off aren't predicted — add those by hand. Generation runs entirely from your saved weeks on this device — no internet call. Everything on this tab is saved with the normal Save (JSON).
Clarity
Hi, I'm Clarity. Ask me anything about the schedule — totals, comparisons, who works more on a given day, requests off, schedule stability, and so on.