The Daycare
Staffing Playbook

Most daycare policies on time off are either non-existent or buried in a 40-page employee handbook nobody has read since orientation. Neither works.

You need a single page that answers these five questions:

1. How much notice do I need to give? (We recommend 2 weeks for planned time off, as-soon-as-possible for sick days.)
2. How do I make a request? (One channel. Not texts to you personally, not sticky notes, not hallway conversations. One place.)
3. Who approves it? (Name a person. If it's you, say so. If you have a lead teacher who handles it, say so.)
4. What might get my request denied? (Be honest: "If approving your request would put us below ratio, we can't approve it." Staff respect honesty far more than vague "we'll see.")
5. How many days do I get? (By category. Vacation, sick, personal. Clear numbers.)

Print it. Post it in the break room. Hand it out at your next staff meeting. When someone asks "how do I request a day off?" the answer should be "look at the sheet on the wall."

Your number is the minimum staff you need to legally operate every classroom. In most states, it's a ratio — 1:3 for infants, 1:15 for school-age, and everything in between. You already know yours. The question is whether you know — right now, today — if tomorrow is covered.

If you can't answer that in under 10 seconds, you have a visibility problem.

Here's the minimum you need:

• A daily headcount — who's scheduled, who's approved off, who's pending.
• A per-day capacity limit — the maximum number of staff who can be off on any given day without breaking ratio. This is your "hard no" number. If 2 people off means you're at ratio, then 3 off is a licensing risk. Period.
• Visibility for your team — when staff can see that a day is already "full" with approved time off, they self-select different dates. This prevents 90% of awkward denial conversations.

If approved time off lives in three places — your head, a wall calendar, and a spreadsheet that was last updated in March — you don't have a system. You have a series of guesses.

Pick one place where all approved time off goes. It could be:

• A shared Google Calendar (free, but manual)
• A whiteboard in the office (visible, but easily missed)
• A shared spreadsheet (trackable, but tedious)
• A purpose-built tool (does the updating for you)

The tool matters less than the rule: if it's not on the calendar, it's not approved. Say that out loud to your team. Say it in the staff meeting. Say it until it becomes culture.

This one change — a single visible calendar that everyone checks before requesting time off — eliminates the "I didn't know she was off that day too" problem that causes most staffing emergencies.

Fairness eliminates drama. When requests are approved in the order they're received, nobody can claim favoritism. It also rewards planning — staff who request early get the dates they want.

This is especially important during high-demand periods: spring break, the week between Christmas and New Year's, summer Fridays. Without a clear rule, you end up mediating conflicts between staff members and making judgment calls that feel political no matter what you decide.

The conversation changes from:
"Why did she get that week off and I didn't?"
To:
"She requested it on September 3rd. You requested on November 10th. The spots were full by then."

That's not you making a decision. That's a policy working. And it means you don't have to be the bad guy.

If your employee handbook says "10 vacation days per year, accruing monthly," then every staff member is silently doing math in their head about how many days they have left. And their math doesn't match yours. It never does.

You have two choices:

1. Track it accurately — every hire date, every accrual rate, every day used, updated after every approval. This is tedious in a spreadsheet but it's the honest approach.
2. Simplify the policy — "All full-time staff receive 10 vacation days per calendar year, available January 1." No accrual math. Just a bank of days.

Both work. What doesn't work is promising accruals and then not tracking them. That leads to the ugliest conversation in childcare: "You said I had 3 days left. My count says 5." Nobody wins that argument.

When a staff member requests a day off and hears nothing for three days, two things happen: they assume it's approved, and they resent you for not responding. Then when you finally say no, it's a fight.

The best directors we've talked to share one habit: they respond the same day. Usually within an hour. Not because they're available 24/7, but because their system makes the answer obvious.

If you know your number (Chapter Two) and you have your calendar (Chapter Three), the answer to most requests is immediate:

• Is the day under capacity? Approved.
• Is the day at capacity? Denied, with explanation.
• Is it a gray area? "Let me check coverage and get back to you by end of day."

Fast responses build trust. Staff don't need to always hear "yes." They need to not be left hanging.

And when the answer is no, say why: "We already have 2 people off that day and we'd be below ratio with a third. Can you pick a different day?" Staff who understand the reason accept the answer. Staff who get a bare "no" start job searching.

Every licensing visit includes a staffing review. Inspectors want to know: were you at ratio? How do you handle absences? Do you have documentation?

If your answer is "I keep it in my head" or "we use a spreadsheet somewhere," you're one surprise inspection away from a finding. Not because you were actually short-staffed, but because you can't prove you weren't.

What inspectors want to see:

• A record of who requested time off and when
• A record of who approved it and when
• Evidence that coverage was maintained

This doesn't have to be complex. A folder of printed request forms, a log book, or a system that timestamps everything automatically. The point is that when someone asks "how do you ensure adequate staffing?" you can show them, not just tell them.

Bonus: this record also protects you in employee disputes. If a staff member claims they were denied time off unfairly, you have the history: when they requested, what the coverage looked like, and why the decision was made. Documentation turns "he said/she said" into "here's what happened."

None of these rules are complicated. The hard part isn't knowing what to do — it's doing it consistently when you're already managing 15 other things before 9am.

Start with the rules that address your biggest pain:

• Drowning in random text requests? Start with Chapter One (write the policy) and Chapter Three (one calendar).
• Caught off guard by coverage gaps? Start with Chapter Two (know your number) and Chapter Four (first come, first served).
• Spreadsheet is a mess? Start with Chapter Five (track accruals or simplify).
• Staff frustrated or distrustful? Start with Chapter Six (respond fast).
• Nervous about licensing? Start with Chapter Seven (paper trail).

You don't have to do all seven at once. Pick two. Implement them this week. See what changes. Then add the next one.