Is This Kid Too Sick for Daycare Today? Writing a Real Exclusion Policy

A parent texts you at 6:45 a.m.: "She had a low fever last night but seems fine now, can I still drop her off?" You're standing in your kitchen with coffee half-made, four other kids arriving in the next hour, and no clean way to answer without either sounding like you're guessing or sounding like the fun police. This exact question — is this specific kid, this specific morning, too sick to be here — is one you'll field more often than almost anything else in the job. It deserves an actual answer, not a vibe. (Head lice is a related but genuinely different question with its own current guidance — see our head lice policy guide if that's what you're actually dealing with this morning.)

Why "use your judgment" isn't a policy

Plenty of home daycare handbooks have a single line about illness: "please keep your child home if they're sick." It sounds reasonable, and it fails constantly, because "sick" means something different to every parent. A stuffy nose that a parent shrugged off is, to you, a kid who's clearly miserable and possibly contagious. A policy that leaves the call entirely to a parent's read of their own child isn't a policy — it's a hope. A real exclusion policy names the specific symptoms that mean stay home, so the decision isn't a negotiation at your door every morning.

What a real policy actually needs to list

Instead of one vague line, your written policy should walk through categories of symptoms and what each one means for attendance that day. The exact numbers you land on (a fever threshold, an hours-symptom-free window) are yours to set — and worth checking against your state's licensing rules, since a handful of states specify minimums for family child care homes. What follows is the shape of the guidance, drawn from CDC and American Academy of Pediatrics material on child care exclusion — treat it as a starting framework to adapt, not a rule to copy verbatim.

Symptom category	General guidance	Notes
Fever	Exclusion is standard when a fever is combined with a behavior change or other symptoms (sore throat, rash, vomiting, diarrhea). The AAP's own consumer guidance cites a fever above roughly 101°F as a threshold worth attention — your written policy should state a specific number you'll actually hold families to.	A fever alone, with a child who's acting completely normal, is treated differently by different providers — decide where you land and write it down.
Vomiting / diarrhea	Repeated vomiting or diarrhea in a short window, or stool not contained in a diaper or by a toilet-trained child, generally warrants exclusion.	Frequency matters more than a single loose stool or one spit-up.
Rash	A rash paired with fever or a behavior change usually needs a medical okay before return; a rash alone, with no other symptoms, is judged case by case.	Contagious-looking rashes (spreading, blistering, weeping) are the ones to take seriously regardless of fever.
Eyes	Thick discharge, redness, and crusting together point toward pink eye, which is commonly excluded until treatment has started.	Watery eyes with a cold, alone, usually aren't treated the same way.
Respiratory	A cough or runny nose without fever is generally not an exclusion reason on its own — kids have colds constantly. Combine it with fever, and it typically is.	This is the category parents push back on most; being specific here reduces arguments.
Persistent pain or unusual lethargy	A child who's notably not themselves — unusually tired, in pain, inconsolable — is worth excluding even absent a clear diagnosis.	This one is judgment-based by nature; name it anyway so parents know it's a real category, not an excuse.

This table is a starting point, not a finished policy — confirm the specifics against current CDC and AAP guidance, and against your own state's licensing requirements, before you put numbers in writing. That last row is also where a symptom can cross the line from "send home" to "this needs immediate attention" — which is exactly why keeping your own CPR and first aid certification current matters as much as any written illness policy.

The return-to-care question

Almost as important as "can they come today" is "when can they come back." Many pediatric and public-health sources point to a common benchmark for fever specifically: symptom-free for a set number of hours without fever-reducing medication, so you're not looking at a fever that's simply being masked by ibuprofen. The exact window (and whether it applies the same way to vomiting, diarrhea, or a contagious rash) varies by source and by state — some programs use one standard across all of it, others set separate windows per symptom. Decide on numbers, write them down, and apply them the same way to every family, every time. Consistency is what makes a return-to-care rule defensible when a parent pushes on it.

Whatever you decide, note it the same day you make the call — a quick line in your daily report ("fever at pickup, sent home, return after 24 hrs symptom-free") does double duty: it keeps the family informed and it gives you a dated record if the same symptom pattern shows up again next week.

Holding the line with a parent who has to go to work

This is where policy meets real life. A parent standing at your door with a kid who has a fever and a client meeting in forty minutes is not being unreasonable — they're stuck, and you're the immediate obstacle to their day working. A few things make this go better:

• Point to the written policy, not your opinion. "My policy is 24 hours fever-free without medication before returning — I know that's hard this morning" lands very differently than "I don't think she should be here," even though you're saying the same thing. The policy is the bad guy, not you.
• Don't negotiate symptom by symptom in the moment. If you wrote the categories down in advance, you're applying a rule, not making a judgment call on the spot — which is a much easier position to hold at 7 a.m. with a line of other families behind them.
• Say it before it's urgent. Every family should see this policy at enrollment, not for the first time the morning it applies to them. Your enrollment agreement is the natural home for a short version of it, with this article as the detailed backup if anyone wants the reasoning.
• Acknowledge the bind without changing the answer. "I get that this is a bad morning for you" costs you nothing and it's still true even while you hold the line.

The billing question, briefly

A sick day at home doesn't usually mean a credit on tuition — most home daycare agreements charge for the enrolled spot, not attendance, precisely because your costs (space, your time, your other commitments) don't change when one child stays home. That's a separate topic worth its own space: see do parents pay when their child is absent for how to think through and explain that policy. A messier version of the same question comes up when a child isn't absent all day but is picked up mid-morning after you've already called a parent — see whether you still charge for the full day for how that's different from a planned absence.

When it's not just one kid

Everything above is about the daily call on a single child. A different, harder problem shows up when several kids are sick at once — that's a cleaning, notification, and possible-closure decision, not an admission-at-the-door one. If you're facing that right now, jump to managing a daycare illness outbreak instead — this article is about the individual threshold, not the group response.

Where DaycareFlow fits

DaycareFlow doesn't make the medical call for you — no app should. What it gives you is a place to keep the pieces that make the call easier and the conversation more defensible: each child's profile holds notes where you can log a symptom pattern or a "sent home, fever, [date]" entry the same day it happens, alongside their allergy and medical information. The calendar's planned attendance view means an unplanned sick-day absence stands out against what was scheduled, instead of being buried in memory. Automated daily-report templates that prompt you for symptoms are on our roadmap, not live yet.

Free during early access, no per-child fees. Start free →

Frequently asked questions

What temperature is too high for daycare?

There's no single number that applies everywhere — it's set by your own written policy and, in some states, by licensing minimums. Consumer guidance from the American Academy of Pediatrics points to roughly 101°F as a threshold worth attention when paired with other symptoms, but you should pick a specific number, write it into your policy, and confirm it doesn't conflict with your state's family child care rules.

How long should a child be symptom-free before returning to daycare?

Many providers use a "symptom-free for a set number of hours without fever-reducing medication" rule, most commonly applied to fever, so a fever isn't simply being masked by medicine at drop-off. The exact hours vary by provider and by state guidance — decide on a number, write it down, and apply it consistently to every family.

Can I refuse to accept a mildly sick child at daycare?

Yes, within a written policy you apply consistently. A private home daycare can set its own exclusion criteria as long as they're documented, shared with every family at enrollment, and don't function as a form of discrimination against a protected condition or disability.

What if a parent disagrees with my sick-child policy?

Point them to the written version in your enrollment agreement rather than debating the individual case in the moment. A policy you apply the same way to every family, every time, is far easier to defend than a judgment call you're making fresh at the door.

Does my daycare need a separate policy for outbreaks versus one sick kid?

Yes — they're different problems. One sick child is an admission decision at your door; several sick children at once is a cleaning, notification, and possible-closure decision that affects your whole roster. See managing a group illness outbreak for that side of it.