How do I handle a sick kid day when I'm new in a job?

Question

Accepted Answer

Plan for it before it happens. The sick kid day is going to come — usually within the first six weeks of any new role, because your immune systems are colliding with new childcare environments — and the way you handle the first one will set a quiet precedent for how all subsequent ones get handled.

Three preparations before the first sick day. First, in your first week, set the expectation explicitly. Tell your manager: "I want to flag that I'm a primary caregiver. I expect to have one or two sick-kid days a quarter where I'll need to drop offline mid-day. I'll always communicate as soon as I know, and I'll catch up the work the next day." Naming this in the first week, before it happens, makes the actual day a non-event. Naming it after the first incident makes it feel like an excuse.

Second, identify your "drop-everything-able" work and your "needs-uninterrupted-time" work. The drop-everything-able work — code review, documentation, async messages, light triage — is what you can do in 90-minute pockets between care moments. The needs-uninterrupted-time work — coding the new feature, drafting the strategy doc, leading the customer call — needs to be moved when you have a sick kid. Tag your tasks this way mentally so on the actual day you don't waste 30 minutes deciding what to work on.

Third, identify backup coverage in advance. A neighbor, a grandparent, a sick-care nanny service, an older sibling, a partner who can shift their day. Knowing exactly who you'd call lets you make the call instead of spiraling. For a high-fever-stay-in-bed kid, you can often do four hours of usable work after they fall asleep at 1pm; for a cranky-but-functional kid, you can sometimes do two hours of focused work in the morning if you have a movie queued. Know which scenario you're in and adjust.

On the actual day, the script is short. Send your manager a Slack message before the workday starts: "Both kids home with a fever. I'll be on async only today, no meetings. I'll cover the customer email I owe by EOD and push back the Tuesday review by one day. Will be fully back tomorrow." Don't apologize. Don't over-explain. Treat it like any other planning communication.

What to actually do with the limited hours: pick the one or two work items that have an external dependency (someone is waiting on you), do those, and ignore everything else. Trying to do a normal workday in fragmented chunks while parenting a sick child is the recipe for both bad work and a worse parent. Pick the smallest set of essential things, ship them, and shut down.

If the sick day stretches into a sick week, escalate early. "This is going to be a multi-day situation. Here's what I'll cover async; here's what needs to wait; here's what someone else should pick up." Most teams handle a known multi-day absence fine; what they handle badly is a string of half-promises that don't deliver.

The deepest move is to treat sick-kid days as a load-bearing part of the job, not as an exception to it. They will be a regular feature of caregiving life. The companies that work for caregivers are the ones where this is normalized; the companies that don't work are the ones where each one feels like an extraction. If three sick days into a new job your team is making you feel guilty, you've learned something important about the culture and you should start watching for the next role.

How do I handle a sick kid day when I'm new in a job?

More questions