A daycare staffing schedule is the plan for which adults are in which room, at which hours, across a whole week. It is built from three things: what each room needs in each block of the day, who is allowed to work in that room, and the limits you have set on hours, rest and days in a row. XShift AI is how you build it. You write those needs and those limits as plain sentences once, and every week after that is generated in seconds with all of them checked before a single shift is allowed to exist.
The nine sections below are the daycare staff scheduling best practices in the order you would actually do them, from an empty grid to a published week. Read top to bottom they are how to schedule daycare staff from nothing. Read one at a time they are the fix for whichever part is breaking this month. Every one of them runs on the same daycare: Brightwood Daycare, four rooms, open 6:00 in the morning to 6:30 at night, twenty-two people on the roster.
1. Decide what each room needs, hour by hour
A daycare day is not one shift. It is three or four blocks, and the number of adults you want on the floor changes at the edge of every one of them. So a daycare staffing plan starts as a grid: every room down one side, every block across the top, and the number of adults you want in that room during that block in the cell where they meet.
Name the blocks by what actually changes rather than by the clock. Doors open and the first families arrive over about three hours. The core of the day is the long middle where every room is full. Then the run-down to close, where the building empties one family at a time and rooms start to combine. Those are your daycare opening and closing shifts, and they are the two blocks that get staffed by memory when nobody has written the numbers down.
Underneath the blocks, put a floor. The floor is the number a room holds whenever no block names those hours, and it is what stops an odd shift somebody creates by hand from being staffed with nobody in mind. Write both. The floor is the standing number for the room, and a block wins for the hours it names.
The block grid
Adults on the floor at Brightwood Daycare, by room and by block.
| Room | Open 6:00 to 9:00 | Core 9:00 to 3:00 | Close 3:00 to 6:30 | The floor any other hours |
|---|---|---|---|---|
| Infants | 2 | 3 | 2 | 2 |
| Toddlers | 2 | 3 | 2 | 2 |
| Twos | 1 | 3 | 2 | 1 |
| Threes | 1 | 2 | 1 | 1 |
| On the floor | 6 | 11 | 7 | n/a |
Eleven adults at midday, six at the door and seven at close. That is the whole daycare room staffing question answered before a single name is placed.
XShift AI holds both halves of that grid at once. A room carries its own standing number, and a block carries its own number for the hours it names, and neither one deletes the other. When a shift is built on the hours a block names, the block’s number wins. When it is not, the room’s floor applies. So the whole grid above is one standing number per room plus the handful of blocks whose number is different, which on Brightwood’s grid is five blocks out of twelve.
What you type
“The Toddler room needs three adults from 9 to 3.”
What it does from then on
Any Toddler shift built on the 9 to 3 block asks for three. Outside those hours the room falls back to the standing number you set for it.
Two things to know before you set this up. Treating each room as its own room, and asking for people by their job rather than by headcount, are both switched off out of the box, so you turn them on first. Most of the switches on this page, including that one, you can flip by saying so in the chat window rather than going looking for them. And a block’s number applies to shifts built on the hours that block names, so build the shifts on the block boundaries you chose rather than inventing new ones every week. That is the whole reason the grid is worth writing down before anybody is scheduled.
2. Write down who is allowed in each room
A number of adults is not the same thing as the right adults. Each block in each room asks for people by the job they do, so a room needs one lead and two assistants rather than three bodies. The wrong person in a room is not a scheduling error. It is a conversation with a parent.
Write the jobs first and keep them few. Lead and assistant, split by room where the rooms genuinely need different people. Then attach every person to the rooms they are allowed to stand in, because that attachment is what rules somebody out before a schedule ever gets as far as their hours.
Infants
- 1 infant lead, every block
- 1 or 2 infant assistants, by block
Ms. Diaz is the lead. Two assistants hold the core.
Toddlers
- 1 toddler lead, every block
- 1 or 2 toddler assistants, by block
Ms. Thompson is the lead, and she is also an infant assistant.
Twos
- 1 lead, core and close
- 1 or 2 assistants, by block
The opening block is one adult, so it asks for the lead alone.
Threes
- 1 lead, open and core
- 1 assistant, core only
Ms. Nguyen holds this room and is a Twos assistant as well.
The person who holds two of those jobs is the one every daycare has and most schedules cannot describe. A second job sits alongside the first, and once it is recorded the person can be placed into either room. That is a setting you switch on, because out of the box a person is matched to a room by their main job only. For example, Ms. Thompson leads the Toddler room and is an infant assistant, so when the Infant core is one adult short she is in the list of people who can take it, and when the Toddler room needs its lead she is still the lead.
A rule can also be pointed at one job or one room rather than the whole daycare. So “nobody in the Infant room works more than four days in a row” is a rule about the Infant room and nowhere else, and “assistants never work more than thirty hours a week” is a rule about a job. That is what keeps the rulebook short, because most of what a director carries in her head is a rule about one room, not about everybody.
3. Write down who cannot work together
Some pairs of people should never be on the same shift, and a daycare is the place where that matters most, because a room is a small space for a long day. A pairing rule names two people and stops the second one landing on any shift the first is already on.
So once the pair is written down, the rule holds everywhere a shift can be staffed: when the whole week is generated, when a call-off is being covered, and when somebody is added to a shift by hand. You never have to remember it again, and neither does the assistant director covering for you on a Thursday.
What you type
“Never put Ms. Thompson and Ms. Walsh on the same shift.”
What it does from then on
It checks the pair every time a shift is staffed. Whichever of the two is placed first keeps the shift, and the other one is not offered it.
For example, the Twos room close is two adults and Ms. Walsh is already on it. When the week is generated, Ms. Thompson is not considered for the second place at all, so the shift is filled by somebody else on the first pass rather than being built wrong and unpicked on Monday. The pair is the rule, and the rule is what stops the room being built wrong in the first place.
4. Build the week once, then stop rebuilding it
Most of a daycare weekly schedule is identical to last week, so the work is in the small part that changed and not in the whole thing. Three mechanisms hold the part that repeats: a saved week you lay down again on new dates, a repeating series for a block that runs every weekday, and named people attached to every shift in that series.
So the question stops being how to build next week and becomes which week you are copying. A term week, a summer week and the week either side of a holiday are four or five different daycare weekly schedules, and once each of them exists as a daycare staff schedule template you pick one instead of building one.
Save a week you are happy with
Pick a range where the rooms were staffed the way you want them and save it under a name. It captures every shift inside it: the days, the times, the number of adults and the jobs each shift asks for.
Lay it down again on new dates
Apply the saved week starting on any date you choose, across every room or only the ones you name. That is the daycare schedule template doing the job the copy-and-paste column in a spreadsheet was pretending to do.
Put the repeating blocks on a series
A block that runs every weekday is one instruction, not twenty. The Toddler open, every weekday, until the end of June, built as one series with the same headcount and the same jobs on every shift in it. You can attach the named people to all of them as it is created, which is a setting you turn on first.
Every one of those paths runs through the same limits. A repeating series is not a way around your hour ceilings, because the series is checked shift by shift as it is built, with each shift counting against the ones already placed in that same week. So the fourth Toddler open in a week where somebody is already at their ceiling is refused inside the series, not discovered afterwards. That is how to build a daycare schedule once and then spend the rest of the term choosing which saved week to lay down. See how schedule generation works for what happens on the pass that fills the rest.
5. Build it by talking to it
The AI Copilot builds and changes a daycare schedule from plain sentences you type into a chat window. You write the instruction the way you would say it to an assistant director, and it comes back with a card showing exactly what it is about to do.
So the whole week, and every change to it afterwards, is something you say rather than something you click. Nothing is written until you approve the card, and you can cancel any part of it. Here is the sentence and the result, side by side, for the ten things a director does most.
You type
What comes back
“Generate next week’s schedule.”
Builds the whole week across every room in seconds, checking availability, approved time off, jobs, pairings, hours, rest and days in a row on every placement.
“Create a shift Friday 6 to 9 in the Toddler room with two people.”
Creates one shift with the headcount, the room and the jobs it needs.
“Every weekday 6 to 9 in the Toddler room until the end of June.”
Builds the whole series at once, each shift carrying the same headcount and the same jobs.
“Move Thursday’s Twos close to start at 2:30.”
Changes the hours on the shift that already exists rather than creating a second one, and shows you the old shift beside the new one.
“Take Ms. Park off Friday.”
Removes her from that shift and leaves the shift standing, so the room still shows what it is short.
“Put Ms. Nguyen on Friday’s infant open instead of Ms. Diaz.”
Swaps one person for the other in a single move, so the shift is never empty in between.
“The Threes core needs one lead and one assistant.”
Adds those job requirements to the shift, creates either job if it does not exist yet, and updates the headcount to match.
“The Toddler room needs three adults from 9 to 3.”
Writes that number against those hours, so every future Toddler shift on those hours asks for three.
“Save this week as my Term Week template.”
Captures every shift in the range with its days, times, headcounts and jobs, ready to lay down again on any date.
“Nobody works more than six days in a row, and auto-approve time off asked three weeks out.”
Turns each policy into a rule that is enforced from then on, and tells you if one of them cannot be enforced instead of saving it quietly.
It also takes more than one instruction in the same message. It splits what you wrote into separate instructions, runs each one, and shows a single card with everything it is about to do, which you approve once. If one of them cannot be done the others still go through. For example, “Move Thursday’s Toddler close to 2:30, take Ms. Park off Friday, and put Ms. Nguyen on Wednesday instead of Ms. Diaz” is three separate jobs written as one sentence and approved as one card. That is the Friday afternoon walk round the building, done from the chat window before you get to the office.
The same window is where the room numbers from section one and the limits from section seven get written, so the daycare scheduling software and the rulebook are the same thing rather than two places you have to keep in step. Book a demo and watch a week build itself.
6. Handle time off before it becomes a coverage problem
Daycare time off requests turn into coverage problems when they are answered one at a time, in the order they arrive, with nobody counting who is already off. So write the answer down as rules before the requests come in, and rank them so the software knows which one wins when two of them disagree.
Four rules cover almost everything a daycare needs, and the order matters more than the rules do. Top to bottom, the highest one wins, and you are told when two of them want opposite answers. Here they are ranked the way most daycares should rank them.
- 1
Deny anything that falls in the first week of September.
The week everybody comes back is the week nobody is off. A date range beats every other rule underneath it.
- 2
Deny it if two people are already off that day.
This is the rule that actually protects the rooms, because it counts the requests already approved across the same days instead of looking at this one alone.
- 3
Deny it if they already have three requests approved this quarter.
Stops one person quietly taking most of the term’s flexibility before anybody notices there was a pattern.
- 4
Approve anything asked three weeks out.
The reward for planning ahead, and it sits at the bottom on purpose, so the three rules above it can still say no.
The moment somebody submits, the ranked set decides, the employee is told, and the decision is stamped with which rule made it. That last part is what makes the answer defensible when somebody asks why hers was approved and mine was not. You can also point a rule at a person’s remaining allowance rather than only at the calendar, and you can answer a whole month of pending requests in one pass, with a reason the employee sees. How to run a fair time-off policy goes through the writing of the policy itself.
The other half of this section is the one nobody writes about, and it matters more in a daycare than anywhere. Daycare staff availability moves with school terms, second jobs and their own children, so a daycare teacher schedule built on availability from last September is built on something that is not true. The practice worth keeping is that a change is requested rather than made. The employee submits the hours she can now work with a reason, it sits in a queue as pending, and it does not take effect until a manager approves it. So the change is real by the time the next week is generated against it, and nobody arrives at a room they can no longer cover.
7. Protect the people you already have
A daycare staffing schedule that quietly leans on the same four people is a schedule that runs out of those four people. Six limits hold that line, and every one of them is written as a plain sentence and checked before a shift is allowed to save.
So the limit is not a report you read afterwards. It is a refusal that happens while somebody is still saving the shift, when changing it costs nothing. A spreadsheet and older scheduling software both count after the fact, which is why the seventh day in a row is something you find out about on the seventh day.
The limit
In a spreadsheet
In XShift AI
Days in a row
A day in the Twos room and a day at your second site are counted in two different places, so nobody sees the run.
Every day worked anywhere in your organisation extends the same run, and the day that goes over your number is never created.
Weekends
The same three people carry every Saturday, because they are the three who always say yes.
A rule checks the weekend before and the weekend after, and refuses the second one in a row.
Rest between shifts
The person who closed at 6:30 is on the 6 o’clock open, and nothing in the file measured the gap.
The gap between their last shift and the next one is computed and the short turnaround is refused before anybody is told they are working it.
A ceiling on hours
The hours are added up on the payroll run, which is the first count and also the last chance.
This shift’s hours are added to everything that person already holds that week, and the shift that crosses your number is turned away.
A floor under hours
Part-time staff who need their hours find out on Friday that they did not get them.
A weekly minimum is held as its own rule, so the person who needs twenty hours is not left at seventeen and a half.
Breaks
Breaks are covered by whoever is free, which means they are covered by whoever says yes.
A break carries a length, a rule for the shift length that triggers it, and the rooms it applies to, so the unpaid time comes out of the hours that are counted.
For example, Ms. Thompson works the opening and the core block Monday through Thursday. That is 9 hours a day and 36 daycare staff hours for the week. Her ceiling is 36, so the Friday opening block, which would take her to 45, is refused while it is being saved rather than corrected on Monday. Nothing is unpicked, because nothing was built.
Multi-site daycare scheduling breaks at exactly this seam, because the hours live in one file per site and nobody adds the files together until payroll. Every one of these limits counts the person, not the building. If Brightwood runs a second daycare and Ms. Nguyen covered Saturday there, she is on day two and not day one when Sunday is being staffed at the first one, and her hours from both sites are in the same weekly total. The rooms stay separate and the limits cross, which is the right way round.
The floor is the same mechanism pointed the other way, and it is the part-time daycare staff hours problem nobody writes about. Ms. Park works the closing block five days a week, which is 3 and a half hours a day and 17 and a half hours for the week. She needs twenty. A weekly floor of twenty is a rule in its own right, so one core block on Wednesday takes her to 23 and a half and she stops being the person who finds out on Friday that she was short again.
A daycare break schedule is the sixth of these and it works differently from the rest. A break rule carries a name, a length in minutes, whether it is paid or unpaid, and the shortest shift that triggers it, and each rule is attached to the rooms it applies to. Thirty unpaid minutes on any shift of six hours or more, in every room, means the 9 hour opening-and-core shift carries one and the unpaid half hour comes out of the hours that get counted. Recording breaks is switched off out of the box, so this is one you turn on. The rest of the limits, including the days-in-a-row count that adds up every day somebody worked anywhere in your organisation, are written in Autopilot as sentences in your own words.
8. Cover the call-off without making a phone call
Daycare call-off coverage is a search problem, not a phone problem. Somebody is not coming in, and the question is which of your other people is allowed to stand in that room at that hour. XShift AI answers it by running eight checks against every person on your roster and stopping at the first one who clears all eight.
So whenever somebody drops a shift, the people who are actually allowed to take it have been found before you have picked up a phone. Nothing in a spreadsheet holds those eight checks for you, so they get held in somebody’s head at half past five in the morning, which is why the answer is always the same three people. The checks run in this order, and anybody who fails one is out at that point.
Is this person attached to the room the shift is in
Do they hold a job the room is asking for, counting a second job if you use second jobs
Is this a day of the week they have marked as one they never work
Do the hours they have blocked off overlap this shift
Does this shift break any rule you wrote, including hours, rest, days in a row and pairings
Are they already on another shift at that time
Would this shift push them past their hours
Are they on approved time off
It works the list in two groups and empties the first before it touches the second. Everybody who clears all eight goes first. Everybody whose only problem is that the shift would push them past their hours goes second, because a covered room beats a clean hours report and you would make the same call yourself. If nobody at all can cover it, you get an email that names who was considered and the reason each person was ruled out.
What happens next depends on how far away the shift is, and you set the line yourself. Further out than your cutoff it picks the best qualified person and assigns them outright. Closer than your cutoff it messages everybody who qualifies and the first one to accept takes it.
More than 7 days out
It assigns somebody.
There is time to fix it if the person objects, so the room is covered now and the conversation happens afterwards.
Under 7 days
It asks everybody who qualifies.
Nobody is handed a shift tomorrow morning that they have not agreed to, and the first person to say yes gets it.
Seven days is the default and any number works. Covering a call-off automatically is switched off out of the box, so this is one more of the settings you turn on. For the full version of the practice, including how to write the policy your software then applies, read how to handle call-offs.
9. Publish it, tell everyone, and keep the record
A schedule nobody has seen is not a schedule. The last step is getting the week in front of the people who have to work it, and keeping a record of what changed and why, so a question three weeks later has an answer.
So publishing is a moment you choose rather than something that happens as you type. Six things sit around that moment, and every one of them is a thing a director currently does by hand or does not do at all.
- Draft first
A generated or edited week arrives as a draft and has to be published before anybody sees it, which is on unless you turn it off. Nothing reaches a parent-facing board because somebody was mid-build.
- Announce
One sentence posts an announcement every employee sees when they log in, plus an email for anybody who has those on. This is where the closed day and the early close belong.
- Message
One-to-one messages and group conversations both live inside the same place the schedule does, so the thread about Thursday is attached to the week it is about.
- Notifications
Seventeen separate email switches, on and off independently, covering shift assigned, shift changed, schedule published, time off approved, denied and requested, and eleven more. Employees also carry their own preferences.
- Who sees what
A manager can be limited to named rooms and sees nothing outside them, and each thing she is allowed to do is its own switch. A room lead can run her own room without being able to touch anybody else’s.
- The record
After a schedule is generated you get an explanation of that run: which shifts were filled and by whom, which came back unfilled, and who was considered and blocked and for what reason. Everything the software does on its own is written down separately with the rule that made it do it.
The record is the one worth setting up on day one even though nothing depends on it yet. Every refusal carries the reason for the refusal. When the week comes back with the Twos close one adult short, the explanation of that run says which people were considered for it and what ruled each of them out, so the next thing you do is fix the cause rather than guess at it. For example, if six people were ruled out because nobody is attached to that room for the closing block, the answer is not to place somebody by hand this week. It is to attach a second person to that room, and then it never happens again.
What the week looks like once all nine are in place
You type one sentence on a Tuesday and next week exists. Every room holds the number you set for it in every block. Nobody is in a room they are not attached to, nobody is on a shift with the person they cannot work with, nobody is on their seventh day, and the two people who need their hours have them. You read it once and publish it.
Then somebody calls off at twenty past five on a Wednesday morning and it is covered before you are awake, because the eight checks ran and somebody said yes. That is the part you would miss most if it went away: the mornings you spend opening a daycare instead of staffing one.
Written down once, held forever
- What every room needs, in every block, with a floor underneath it
- Who is allowed in which room, including the people who hold two jobs
- The pairs of people who are never on the same shift
- A ceiling and a floor on hours, rest between shifts, days in a row and weekends
- Who is off, decided the moment they ask, by the rule you ranked
- A call-off covered by a search instead of a phone call
Switching is the part people put off, so here is the honest version. You set it up by talking to the AI Copilot in plain English, in under ten minutes, and you bring your roster in from a spreadsheet, a photo or a pasted list. There is no implementation project and nobody comes to your daycare. You can leave your current tool running while you watch a week build itself. The trial is 21 days, a card is required to start it and you are not charged during it, and you can cancel before it ends with no charge at all. See the full pricing, or read what the product does for a daycare on the daycare staff scheduling software page.
Skip all of this if
You enjoy rebuilding a week that is almost identical to last week, every single week. You like holding eight separate checks in your head at half past five in the morning while a room stands short. You would rather your four most reliable people carried every close until they leave. Otherwise, write the grid and the limits down once and let them hold the week for you.
Frequently asked questions
How do I build a daycare staffing schedule?
Use XShift AI’s AI Copilot. You write the number of adults you want in each room during each block of the day, who is allowed in which room, who cannot work together and your limits on hours, rest and days in a row, all as plain sentences. From then on it builds the week and every one of those is checked before a shift is allowed to exist, so the grid you designed is the grid you get.
What is the best scheduling software for daycare?
XShift AI is the daycare scheduling software built for how a daycare actually runs, because it holds a different number of adults in each room at each block of the day and refuses the shift that breaks it. Most scheduling tools give a room one number and keep it from open to close. It also covers a call-off by working your roster in a fixed order, without anybody making a phone call.
How do I build a daycare schedule quickly?
Use XShift AI’s AI Copilot and type what you want in plain English. It generates the whole week in seconds across every room, checking availability, time off, jobs, pairing rules, hour limits, rest and days in a row as it places each person. You can also save a week you are happy with and lay it down again on new dates, which is how most daycare weeks get built after the first one.
How many adults do I need in each daycare room?
That number is set by your state, and it is the one question on this page you should not answer from a scheduling article. Your state’s daycare licensing agency publishes the required numbers by age group, and they differ from state to state and change over time. Get the current figures from them directly, and confirm them with your own local office rather than a summary published by somebody else.
How do I control labor costs at my daycare?
Use XShift AI’s Autopilot to set a dollar ceiling for the week and for the day, written as one sentence. Before any shift is saved it prices that exact shift for that exact person, including every hour past their overtime threshold at time and a half, adds it to what is already committed, and turns the shift away if the total goes past your number. The check runs while the shift is still free to change rather than on the payroll run.
How do I cover a daycare call-off?
Use XShift AI’s Autopilot. The moment a shift opens it works one list in a fixed order, ruling out anyone not attached to that room, anyone without a job the room is asking for, anyone who blocked those hours off, anyone already on something else, anyone a limit you wrote would stop, and anyone on approved time off. It stops at the first person left. For a shift far enough out it assigns them outright, and for one close at hand it offers the shift to everybody who qualifies. You switch the call-off agent on and set where that line sits.
How do I stop two daycare staff who clash from being scheduled together?
Use XShift AI’s Autopilot and write the pair down once: never put these two on the same shift. From then on it checks that pair every time a week is generated, every time a call-off is covered and every time somebody is added by hand, and blocks the second of them from landing on the shift. You never have to remember it while you are building, which is the moment it is always forgotten.
Can daycare staff swap shifts with each other?
Yes, and XShift AI lets you choose how much say you have in it. A trade can go through on its own, or come to you for approval every time, or go through only when it passes the checks and come to you when it does not. The third is the one most daycares want, because a swap that would leave a room without the right job in it is exactly the one you want to see.
How do I handle daycare time off requests fairly?
Use XShift AI’s Autopilot to set custom policies for automatic approval and denial. You write the rules once: how much notice earns an automatic yes, how many people may be off on the same day, how many requests one person can make in a period, and which rule wins when two disagree. The moment a teacher submits, the rule decides, she is told, and the decision is stamped with which rule made it, so the answer is the same whoever asked.
How do I stop a daycare teacher going into overtime?
Use XShift AI’s Autopilot to set the hour limit once and let it refuse the shift that breaks it. It reads your own overtime threshold rather than assuming forty hours, adds the new shift to everything that person already holds that week, and turns the shift away before it is saved. It holds separately at the level of the week, the single shift, the number of shifts, and the days worked in a row.
How do I schedule daycare staff who work in more than one room?
In XShift AI you give the person a second job alongside their main one and attach them to both rooms, and from then on she can be scheduled into either. A lead in the Toddler room who is an assistant in the Infant room is one person holding two jobs. This is a setting you switch on, because out of the box a person is matched to a room by their main job only. Once it is on, the second job counts everywhere the first one does, including when a call-off is being covered.
How do I cover daycare staff breaks without leaving a room short?
In XShift AI you write the break itself down as a rule, with how long it runs, whether it is paid, the shift length that triggers it, and which rooms it applies to. Then you set the number of adults for that block high enough to hold while somebody is away from the room, and the schedule is built to that number rather than to the number you need when everybody is standing in it. Break tracking is a setting you switch on.
How do I stop the same daycare staff working every closing shift?
Use XShift AI’s Autopilot to write it down as a limit rather than trying to hold it in your head while you build. A weekly ceiling on hours, a weekly ceiling on the number of shifts, a cap on days worked in a row and a stop on the same people carrying two weekends in a row each do part of the job and work together. Each is checked at the moment a shift is saved, so the fifth close of the week is never created. It also holds a weekly floor, the same mechanism pointed the other way, for part-time staff who need their hours.
What is a daycare schedule template?
In XShift AI a template is a saved stretch of days holding every shift inside it, with the days, the times, the number of adults and the job each shift asks for, ready to be laid down again on new dates. You save a range you are happy with under a name, then apply it starting on any date, across every room or only the ones you name. It saves the shape and not the people, so laying it down again never re-books somebody who has since left.
Can daycare staff change their availability during the year?
In XShift AI a teacher submits the hours she can now work and it does not take effect until a manager approves it. That matters in a daycare more than most places, because staff availability moves with school terms, second jobs and their own children, and availability that is out of date is worse than none at all. The request sits in a queue, and the next schedule is only built against the new hours once somebody has said yes.
How do I run one schedule across two daycare sites?
In XShift AI each room at each site carries its own numbers and its own people, so nobody is placed in a room they are not attached to, while the limits on a person count everywhere. Somebody who worked Saturday at your second site is on day two, not day one, on Sunday at your first. Multi-site daycare scheduling breaks at exactly that seam, because the hours usually live in one file per site and nobody adds the files together.
What should my assistant director be allowed to change in the schedule?
In XShift AI you decide that switch by switch, and you can hold each manager to named rooms so they see and touch nothing outside them. Creating and editing shifts, approving time off, approving trades, editing employees, sending announcements and running Autopilot are each granted separately. A room lead who runs her own room and nothing else is the common shape, and it is one sentence to set.