Tell RosterAxis your shifts and your team. It builds the schedule, flags every conflict right where it happens, and leaves you in control.
This is the board you'll work in. Every issue points to its cell and the change that clears it.
Tom Baker, Sat 8
DOUBLE_BOOKED
Marco Silva, Fri 7
REST_GAP
Sun 9, Opening
UNDERSTAFFED
Sun 9, Closing
NO_QUALIFIED_STAFF
Priya Shah, Wed 5
OUTSIDE_AVAILABILITY
Dee Okonkwo, Thu 6
CLOPENING
Sat 8, Closing
OVERSTAFFED
Ana Ruiz, this week
OVER_TARGET_HOURS
Tom Baker, this week
MAX_SHIFTS_WEEK
Marco Silva, this week
FAIRNESS_IMBALANCE
Dee Okonkwo, Fri 7
PREFERENCE_VIOLATED
Priya Shah, this week
UNDER_TARGET_HOURS
Roles, hours, time off, and the limits you won't cross. Paste in the sheet you already keep.
A repeating shift is one line: when, how often, and who you need. See every date it creates before you save.
Auto-fill proposes, you approve. Nothing changes until you hit Apply.
Auto-fill plans the whole week and shows you the result before anything changes. Every pick shows the eight weighted components behind it, and the runners-up are one click away. Disagree? Swap them in.
A broken rule appears on the cell that broke it, with the numbers behind it and the change that fixes it. If a one-click fix wouldn't actually work, you get the reason instead of the button.
Hours she would rather work. Auto-fill reaches for these first.
Drag across the week to say when somebody can work. Scheduling against hours she ruled out is an error; scheduling outside hours she never mentioned is a warning.
| Name | Roles | Availability | Max / week | Target | Status |
|---|---|---|---|---|---|
| Ana RuizShift lead | Barista, Shift lead | Mon-Fri, days | 32h | 24h | Regular |
| Dee Okonkwo | Barista | Most evenings | 20h | 16h | Regular |
| Jo Marsh | Barista, Kitchen | Not stated | Default 40h | Default 30h | Regular |
| Priya Shah | Kitchen | Weekends only | 16h | 12h | Regular |
| Marco SilvaShift lead | Barista, Shift lead | Mon-Thu | 40h | 37h | Regular |
| Tom Baker | Barista | Fri-Sun | 24h | 18h | Regular |
| Sam Lee | Kitchen, Closing | Nights | 30h | 24h | Regular |
| Noor HaddadAs needed | Barista | Not stated | Default 40h | — | As needed |
| Type a name, press Enter | |||||
RosterAxis checks 24 rules. Which ones matter depends on what you're staffing.
A schedule that changes every week, built around who can actually come in.
Paste the availability sheet from your phone and cover open, rush, and close with people who can work all three. A double-booked shift lead gets caught before service, not during it.
Store hours on one side, contracted hours on the other.
Set target hours for each person and RosterAxis works toward them. Someone on two days a week doesn't get a full share of Sundays, because unpopular shifts are split in proportion to hours.
The rules aren't optional, and neither is the paper trail.
Rest between shifts and short turnaround are enforced as errors, and every error has to be accepted in writing before the schedule goes live. Who accepted what, and when, is kept with the publish record.
Every visit needs someone qualified to make it.
Each shift names the role it needs, so it's only filled by someone who holds it. When no one fits, you see everyone who was considered and the rule that ruled each of them out.
Peak weeks, without blowing through your limits.
Days-in-a-row and hours-in-a-week limits hold no matter the volume, and last week is your starting point, not a retype. Generating repeating shifts only adds, so running it twice never removes what you've already staffed.
A pattern you can read out loud, and change without breaking the week.
Morning, 06:00 to 14:00, repeats M T W T F, needs 4 x Operator. Change that line after the shifts are staffed and nothing moves under the people on them. You get a list of what's changed and choose which shifts to update.
Overnight work, counted the way the clock actually ran.
A shift that ends before it starts gets a next-day badge automatically, and the night the clocks change is counted in hours actually worked.
Cover the shifts no one wants, fairly.
Rate how unpopular each repeating shift is. RosterAxis spreads them in proportion to each person's hours and shows the balance as a bar, so fairness is something you see at a glance.
Until you publish, your team can't see the schedule at all. Not the shifts, not who's on them. That's enforced at the database level, not just hidden.
When you do, each person gets one phone-friendly screen with their own shifts and nothing else. No grid of everyone, no issues that aren't theirs.
4 shifts, 30h in total, at Fold Street Coffee.
Everyone sets their own availability, asks for time off, and offers up a shift they can't work. Nothing changes hands until you say so.
Everyone marks when they can work and asks for whole days off. A shift they said they can't work is an error on the cell, and one outside hours they never mentioned is a warning. You can still schedule either.
They put it up, and a colleague takes it outright or offers one of their own in trade. The shift stays theirs until you decide.
Every swap shows both people's hours before and after, against their weekly limit, and every issue it would create or clear. Approve it and the published schedule updates, and both of them get an email.
Locations run schedules. Groups organize locations. One roster covers every one of them.
Stores, sites, departments: name them the way you name them, and nest them however they sit. Each location plans its own week, and the same week somewhere else doesn't get in the way.
Anyone can be scheduled anywhere. Put someone on a shift when they're already working somewhere else and you get told which location and which hours clash.
Coverage, scheduled hours, and everyone who worked at more than one place. Pick a location or a group and everything under it rolls up.