When we were designing Molo, we spent time mapping the full set of scheduling events a UK primary school generates across an academic year. The total, for a single child at a typical state primary, is somewhere between 40 and 60 discrete events that a parent needs to be aware of and, in many cases, respond to. For two children at the same school the overlap reduces that number; for two children at different schools it effectively doubles it.
The annual planning problem for working families is not a shortage of information. Schools communicate extensively. It is that the 40-to-60 events arrive in pieces, across different formats, at uneven intervals, and require different kinds of response. Understanding where things fall through requires understanding the categories those events fall into.
Term dates and the local authority variable
UK school term dates are set within a framework published by local authorities, but individual schools have discretion over some of the dates within that framework. This means that a family with children at two different schools in the same borough may have different term start and end dates for each child. It also means that the local authority term dates published in the spring, which families often use for holiday planning, may not be the exact dates either school follows.
Most schools send their confirmed term dates in September and again in January. These are the highest-value scheduling documents of the year: they define the boundaries of school attendance and, crucially, the holiday windows available for family travel. Getting these into the shared calendar accurately, at the point they arrive, determines whether holiday booking decisions are made on real data or remembered estimates.
Inset days: the predictable surprise
Inset days are school staff training days when children do not attend. UK state schools are entitled to five inset days per academic year. The dates are set by the school and are typically communicated in September's term dates document, but they are also subject to change. An inset day moved after the original notice is a meaningful event: it requires arranging childcare, adjusting work plans, or both.
The difficulty with inset days is not that they are unannounced. Schools communicate them. The difficulty is that inset day communications often arrive as a short note within a longer newsletter, sometimes months after the original term dates were set. A parent who entered the inset days from the September letter may not notice the amendment in a February newsletter unless they are specifically looking for it. The result is an inset day arriving in the calendar that has already been superseded.
This is one of the cases where duplicate detection in Molo is particularly useful. When an inset day amendment arrives in a forwarded newsletter, Molo detects that an event with a similar name and a nearby date already exists in the calendar, flags the potential conflict, and surfaces it for review rather than silently adding a second contradictory entry.
Parents evenings and appointment coordination
Parents evenings typically arrive in the calendar as three separate communications: the initial announcement with the date range, the booking confirmation from whichever system the school uses (many UK schools use an online parents evening booking tool), and a reminder notice closer to the date. Each of these contains slightly different information. The announcement has the date. The confirmation has the time and room. The reminder may add a note about where to go on arrival.
For a two-parent household, the coordination question is which parent is attending, which slot they booked, and whether both parents can see the details. If the booking confirmation arrives in the email of the parent who made the booking, and that parent's calendar is not shared, the other parent may arrive at parents evening with no information about the time or teacher.
This pattern is one of the practical reasons shared calendar setup matters for parents evening: the event needs to be in a calendar both parents can see, with the time and room information attached, not just in one person's email inbox.
School trips and consent deadlines
School trips generate at least two calendar events: the trip date itself and the consent form deadline. The consent deadline is almost always earlier, sometimes by several weeks, and the penalty for missing it is that a child cannot attend the trip. The trip date is the visible, memorable one. The consent deadline is the actionable one.
When Molo processes a trip notification letter, it extracts both dates and creates both events. The consent deadline gets a note indicating that it requires action (returning the form or completing an online consent), and the trip event gets the contextual details: destination, kit requirements, any dietary notes for packed lunches.
The cumulative calendar
The reason the annual planning problem feels manageable to some families and overwhelming to others is usually about the density of processing that happens in the first two weeks of each term. September and January are the months when the most scheduling information arrives at once, because they are the points at which schools plan forward and issue documents for the upcoming period.
A family that processes September's first newsletter and gets all the term dates, inset days, and early-term events into a shared calendar starts the year in a different position than one that files the newsletter to read later. The calendar position compounds: each subsequent communication is easier to process when it arrives in the context of a calendar that already has the structural dates.
The goal Molo is designed to serve is not perfect calendar coverage. It is a baseline that does not require manual effort to maintain: a shared view of what is happening, updated from the communications that are already arriving, so that the planning decisions families need to make are made on current information.