Family organisation apps have existed for years. Cozi, FamilyWall, Picniic, OurHome. There are shared todo apps and chore rosters and meal planners designed specifically for households with children. Many of them are well-designed. And yet, the household calendar problem persists.
When we were thinking about what to build, we kept asking why. Why do apps that are designed for this exact problem not solve it? The answer, when we looked at it closely, is that every family organisation app asks you to do something. Open the app. Enter the event. Check the shared list. Review what has been added.
For working parents with primary-age children, the window in which you have the time and attention to do those things is extremely narrow, and it almost never coincides with the moment the information arrives.
The mismatch between information arrival and processing time
A school newsletter arrives at 3:15pm on a Thursday. That is pickup time for a lot of parents, or the handoff moment between work and domestic responsibilities for parents who are not doing the pickup. It is not a moment for carefully processing a PDF and entering its events into a shared calendar app.
The alternatives are: deal with it immediately at a bad time, or deal with it later. "Later" is 8pm when the children are in bed, if the day has not burned that window too. For many working households, "later" becomes a stack of unprocessed newsletters that sits until half-term, when somebody finally opens them and finds a permission slip deadline that was two weeks ago.
This is not a failure of organisation. It is a structural timing mismatch. The information arrives in a window that is wrong for processing it, and the apps that could hold it require a manual step that happens at that wrong moment.
What asynchronous means in this context
Async scheduling means the calendar updates when the information arrives, not when you have time to process it. The forwarded email arrives, the extraction runs, the events appear. You do not need to take any action for the calendar to be current. The processing step happens independently of your attention.
This is different from an app that reminds you to enter events. It is different from a system that emails you a digest asking you to confirm dates. Both of those still require a response from you at a specific moment. Async means the calendar is already updated by the time you open it.
The practical effect is that the shared calendar becomes a view of reality rather than an aspiration. When you check what is happening next week, you are seeing what is actually happening, not what was entered six weeks ago and may or may not have been updated since.
The app graveyard problem
Every family has at least one app that was adopted with enthusiasm and quietly abandoned within two months. Usually something happened: a period of high work pressure, a new routine, a phase when nobody had the bandwidth to maintain the system. The app fell behind reality. Once a shared system is behind by a few weeks, it becomes unreliable as a source of truth, and once it is unreliable it stops getting used, which makes it more unreliable.
Async scheduling resists this failure mode because it does not require maintenance. The calendar does not go stale because nobody maintains it from above: it is populated from the stream of emails that arrive regardless of whether anyone has time to think about it. A busy fortnight at work does not mean the school events from that fortnight are missing from the calendar. They were extracted when the newsletter arrived.
The limit of what async can do
We are not arguing that interactive scheduling apps are useless. There are things that async extraction cannot do: it cannot capture a verbal reminder from a teacher, a WhatsApp message in the class parent group, or a change that is communicated entirely via a school app push notification with no email counterpart. For anything that does not arrive as an email or email attachment, a manual entry step is still required.
The claim is not that async scheduling replaces all scheduling work. The claim is that it handles the portion of scheduling that arrives by email, which in most UK families is the majority of school and clinic scheduling information. Handling that portion automatically means the manual steps that remain are genuinely irreducible, not just the portion that went unprocessed during a busy week.
Why we built for this rather than for the interactive layer
When we were in early conversations with other parents in Manchester about what would actually help, the theme was not "a better interface for entering events." It was "I do not want to enter events at all." The aspiration was not a nicer input form. It was the calendar being right without any input.
That is a harder engineering problem. It requires document understanding, date normalisation across inconsistent formats, duplicate detection, and calendar write access. It requires handling failure gracefully when a document is ambiguous rather than guessing wrong. But it is the problem worth solving, because it is what actually removes the scheduling friction for the families who experience it most acutely.
More apps that require engagement at the wrong moment are not the answer. A system that does the work when the work arrives is.