A shared family calendar is a good idea until it is not. Most families who try one start well: they enter the term dates, add a few events from the first newsletter, share the calendar between both parents. For a few weeks, it works. Then the updates slow down, then stop, and eventually nobody checks the calendar because it has drifted so far from reality that checking it is worse than not checking it.
We spent time thinking about why this pattern is so consistent. The failure mode is not, usually, lack of motivation. It is a structural problem with how shared calendars are maintained. Understanding the structure helps you avoid the failure, whether you use Molo or just a shared Google Calendar.
The single-maintainer problem
In most households with children, one parent receives the majority of school communications. The school has one registered email address per child, and whichever parent's address that is becomes the default recipient for all notices, newsletters, and letters. This creates an asymmetry: one parent has the information, and both parents need the calendar to reflect it.
The single-maintainer problem is that keeping the calendar updated falls entirely to the information receiver. Even with a shared calendar where both parents can edit, only the parent who received the newsletter knows what is in it, and only that parent can add the events. If that parent has a busy period, or simply does not get round to it, the calendar goes stale.
The practical consequence is that the non-receiving parent is always in a position of asking "is the calendar up to date?" rather than trusting it. Once you cannot trust a calendar, you stop relying on it, and once you stop relying on it, it stops being maintained, because maintenance without use is not rewarding.
The visibility asymmetry
Related to the single-maintainer problem is what we call visibility asymmetry: one parent's inbox is the actual source of truth for the family's schedule, but the other parent has no view into it unless the first parent manually transfers the information. This matters particularly for events that require both parents to be aware: parents evening, medical appointments, work-heavy weeks when school pickup needs covering.
The fix for visibility asymmetry is not a shared calendar application. It is making the original source of the information available to both parents at the same time it arrives. This can be done by adding the second parent's address to the school's communication list (many schools allow multiple addresses per family), or by using automatic forwarding so that both parents' inboxes receive the same notification.
When we built Molo's family member sharing feature, this was the underlying logic: both parents should see an event appear in their shared calendar at the moment it is extracted from the incoming email, not at the moment one of them has time to add it manually.
The update and amendment problem
Shared calendars also decay because schools change dates. An inset day gets moved. A trip is rescheduled. A parents evening slot gets amended. Each amendment arrives as a new communication, often buried in a newsletter rather than flagged prominently. A manually-maintained calendar requires noticing the amendment, finding the original event, and updating it.
This step is frequently skipped, not because it is impossible but because it requires matching a new communication to an existing calendar entry, which requires either remembering what was entered or searching the calendar. On a day when you are trying to get children to school, respond to work emails, and process three other notifications from the school, that matching step does not happen.
Duplicate detection helps here. If an amendment arrives as a forwarded email, extraction can identify that an event with a similar description exists near the date in question and flag the potential conflict for review. The parent still needs to confirm the amendment, but the flagging reduces the risk of a quietly stale event sitting in the calendar undetected.
What makes the difference in practice
Calendars that stay active have a few things in common. The update load is distributed: both parents can add events, and both know what is expected of them. The source of information is accessible to both: both parents receive school emails, or the school calendar is synced automatically. And there is a habit loop that keeps it relevant: checking the calendar is rewarded by it being accurate, so it stays in use.
The habit loop is the hardest to establish, because it requires the calendar to be reliable before the habit forms. Most families start with the habit before the reliability, find it unreliable, lose the habit, and blame themselves for being disorganised. The actual problem was that the tool required more maintenance than the household could sustain.
We are not saying that automatic extraction is the only way to maintain a reliable family calendar. Some families do it successfully with shared Google Calendar and conscious habits. What we are saying is that removing the maintenance step removes the failure mode. A calendar that updates itself when the school emails arrive does not go stale during a busy fortnight. The reliability comes first, and the habit follows.
A note on over-crowded calendars
One failure mode we did not expect to encounter as often as we did is the over-crowded calendar: a shared calendar that has so many events, many of them recurring school reminders, that it has become difficult to parse at a glance. Every Friday reminder, every weekly club, every fortnight newsletter date compounds into a view that is technically accurate but practically unreadable.
The Molo Events layer in your calendar is separate from your personal calendar entries, which helps with this. The school events are visible but filterable. If you want to see only work and personal events for a planning conversation, you can turn off the Molo layer. If you want the full family view, both layers are visible. This is not unique to Molo; Google Calendar and Apple Calendar both support layered calendar views. But it requires deliberate setup, which is worth doing when you first configure a shared calendar rather than discovering the problem six months in.