A schedule template that actually works with school hours

A worked example of structuring a 30-hour week around school dropoff, pickup, and the in-between.

Most "remote work tips for parents" advice is written by people who don't have small children. The honest version is that the school day is short, unevenly broken up by sick days and early dismissals, and that you will get nothing important done in the 20 minutes before pickup. A schedule that pretends otherwise will collapse by week three. Here's a template that survives contact with reality.

The constraint set

Assume two children in elementary school, a school day of roughly 8:30am to 3:00pm, and that you want to work 30 hours a week of mostly-async knowledge work. The non-negotiables are dropoff at 8:15, pickup at 3:00, dinner prep starting at 5:00, and bedtime routine starting at 7:30. That gives you four blocks of potentially-usable time every weekday.

The blocks

Morning deep work block: 8:45am - 11:30am. The biggest, sharpest, hardest block. Use this for the work you'd be most embarrassed not to ship — coding, writing, analysis, the thing that needs your best attention. Two hours and 45 minutes, five days a week, is 13.75 hours. That's the spine of the week.
Lunch admin block: 11:30am - 12:30pm. Eat, walk, handle quick admin. Don't try to do deep work here; your brain is in a transition. One hour, five days, is 5 hours.
Afternoon shallow work block: 12:30pm - 2:30pm. Email, code review, meetings if you must, documentation, reading. Two hours, five days, is 10 hours. Leave 2:30pm-3:00pm as buffer for the pickup commute and the inevitable "I forgot a permission slip" call.
Evening soft block: 8:00pm - 9:00pm, two or three nights a week. Use this for the work that benefits from quiet but not from sharpness — reading, planning the next day, async catch-up. Two to three hours.

That's 28 to 31 hours. Add an occasional weekend morning block of 2-3 hours when something is genuinely urgent, and you're at the 30-hour line.

Defending the morning block

The morning deep work block is the most valuable real estate in the schedule and the most fragile. Three rules to defend it:

No meetings before 11:30am. None. If a colleague proposes one, decline with "my mornings are deep-work time; I have availability after lunch."
No Slack until 11:00am. Open it once at 11:00 to triage. The world will not end.
No errands during this block. Errands feel productive but they break the cognitive thread. Save them for the lunch admin block.

What to put in the afternoon block

The afternoon block is for work that benefits from being done but doesn't need your best brain. The most valuable use is making other people unblocked: review their pull requests, answer their questions, ship the small documentation update, give the design feedback. This is also the right block for one or two scheduled meetings, capped at 30 minutes each.

Plan for the broken weeks

One week in four will be broken — sick kid, snow day, school holiday, dental appointment. Build the schedule assuming you have four good weeks per month, not five. If you're at 30 productive hours in three out of four weeks, you're at 22 weighted hours overall. Either accept that as your real number, or build the fourth week explicitly into the calendar with grandparent help, partner coverage, or a babysitter.

What to tell your team

Make the schedule visible. Put your core hours in your calendar as a recurring event called "deep work." Set your Slack status to show your hours. Pin a one-line description in your intro: "I work 30 hours a week, 8:45am-2:30pm Eastern with an evening block. Async-friendly; please don't expect a Slack reply during school pickup or evening routine." Predictability beats availability every time.

Track for one month, then adjust

The template above is a starting point, not a prescription. Track your actual hours for four weeks, then adjust the blocks to where the work actually happened versus where you planned it to happen. Some people are sharper from 6am to 8am than from 8:45 to 11:30. Some weeks are wrecked by recurring meetings that need to move. The template works because it survives modification, not because it's right out of the box.