The Calendar Default Is the Policy: Designing Team Time Around the School Gate

The meeting time that isn’t neutral

At 8:45 on a weekday morning, a lot of UK teams are doing two jobs at once. One is work. The other is the school gate: the last-minute shoe hunt, the forgotten reading folder, the queue at the crossing, the handover to breakfast club or a grandparent. By 9am, some people are at their desks. Others are walking back through the front door, putting the kettle on, and trying to remember what they were supposed to say in the standup.

None of this is unusual. What is unusual is how often our calendars pretend it isn’t happening. A recurring 9am meeting is not a neutral container for work. It is a design choice about whose morning is assumed to be free. The same goes for a 5pm handover, which lands exactly when another group of parents and carers is doing pick-up, tea, bath, and the long, negotiated slide towards bedtime.

The point isn’t that every meeting must move. It’s that the default deserves a second look. In a collaboration stack, the default is the policy. If the default says 9am, the team is saying something about who counts as reliably available. Often, nobody meant to say it.

Flexibility without the shadow shift

Most UK teams have got the memo on flexible working. Fewer have worked out what it means in practice. ‘Just be flexible’ sounds generous until it turns into: be available when everyone else is available, then catch up later. That later bit is the problem. It becomes a shadow shift — the 8pm email, the 9:30pm Slack tidy-up, the Sunday evening scroll through a channel to see what was decided on Friday.

If flexibility only moves the work, not the expectations, it hasn’t solved anything. It has just made the cost invisible. The school run is not an emergency or a lifestyle perk. It is a recurring constraint with a timetable. Teams that treat it as a planning input, rather than an exception to be managed, tend to get better attendance, calmer handovers, and fewer people quietly doing their best work after the kids are asleep.

A useful test: if someone leaves at 3:10 for pick-up, can the rest of the team describe what happens next without asking them to justify it? If the answer is no, the calendar is doing the talking, and it’s saying the wrong thing.

Core hours are a band, not a starting gun

One of the simplest fixes is to stop treating core hours as a single starting time. A team doesn’t need everyone online at 9am. It needs a reliable band when people can expect each other to be around. Something like 10am to 3pm is a common starting point: late enough to clear the worst of the school run, early enough to leave room for handovers before the afternoon pick-up.

That band doesn’t have to be rigid. It can be reviewed. It can be different for different teams. The important thing is that it is written down and treated as a shared norm, not a secret rule that only full-time, office-based people seem to know. If the team agrees that 10am is the collaboration anchor, then a 9am standup is no longer the default. It’s a choice that needs a reason.

For teams that like a morning check-in, there are options. Move it to 9:30. Make it async. Run it as a written thread that people can read at 9:05 or 9:35. Keep the live meeting for decisions, not announcements. The goal is not to make everyone’s morning identical. It is to stop designing the day around a version of the morning that only some people have.

Audit the edges of the day

Before changing anything, look at what the calendar actually does. Pull up the recurring meetings that start before 9:30 and the ones that run past 4pm. Ask three questions about each one: who is excluded by this slot, what would break if it moved, and could it be a thread instead?

Some meetings will survive the audit. A daily operational handover might genuinely need a live slot. But even then, the slot can rotate or the handover can be partly written. A short note at 4:15 can do more for continuity than a 5pm call that half the team attends from a car park.

It also helps to make school-run holds visible without making them confessional. A calendar block called ‘School run’ is not a weakness. It’s a constraint, like a train time or a client call. If your collaboration stack supports status notes or focus settings, use them to normalise the edges: ‘Available 10–3, async outside that’ is a perfectly good signal. It saves everyone the guesswork.

Async rituals that don’t become homework

Async work has a bad habit of turning into homework. The thread gets longer, the expectations get vaguer, and the person who was already busy ends up reading it at night. To avoid that, keep async rituals small and bounded. A written standup can be three lines: what I’m doing, what I need, what’s blocking me. It doesn’t need a reply from everyone. It needs a reader and a decision owner.

Handovers are another place to be deliberate. Instead of a 5pm call, try a short written handover before the school gate: what’s in progress, what’s risky, who’s picking it up. In Kula, a channel post can carry that handover without demanding an immediate response. The point is to leave a trail, not to create another inbox.

Set response expectations too. ‘Read by 10am’ is different from ‘reply within five minutes’. If the team knows that messages sent before 9:30 may not be read until later, people stop treating the early morning as a silent test of commitment. That’s better for parents, carers, commuters, and anyone who does their best thinking before the office wakes up.

Measure the right thing

Don’t measure the success of a calendar change by 9am attendance. Measure the things that actually matter: meeting load, decision latency, after-hours messages, how often handovers get missed, and whether the same few people are always the ones adapting. Ask who speaks in the meetings that remain. Ask whether the people with school runs feel like they are constantly asking for a favour.

A four-week trial is enough to learn something. No meetings before 9:30. Async standup by 10. Core hours 10–3. A written handover by 4:30. Review it together. Keep what works. Drop what doesn’t. The point isn’t to build a perfect calendar. It’s to build one that doesn’t quietly ask some of the team to do their job twice.

The best meeting time might not be anybody’s first choice. That’s fine. A good team default is rarely the most convenient slot for the loudest diary. It’s the one that lets everyone do the school gate, the handover, and the work without turning flexibility into a second shift.