
Family & Kids · Career & Money
You have a capture problem.
Things vanish between hearing and writing. A better calendar fixes none of it.
60
seconds to record something you've just been told
10
minutes a week the whole system depends on
1
field that reveals driver clashes: who's taking them
The Problem
Someone told you. At the gate.
And you meant to add it when you got home
That's the exact moment most things disappear.
Meanwhile two events, overlapping, one driver
A calendar won't flag it — neither entry is wrong.
Then the costume was needed Tuesday, for Friday
Calendars record events, never their prerequisites.
And one person holds all of it in their head
Which is real work, and collapses the week they're ill.
What You Get
Capture first. Calendar second.
The Leak Calculator
How much survives to the calendar.
One Capture Point
Scrappy and immediate beats tidy and later.
Transport Clash Finder
The kind calendars can't see.
Prerequisite Entries
Dated by when they're needed.
The Ten-Minute Review
The habit everything else rests on.
Sharing The Load
Not just sharing the view.
How It Works
From finding out late to knowing on Sunday.
1
Find the leak
Count the channels and what survives them.

~10 minutes
2
Build the capture point
One place, within a minute, however messy.

~5 minutes
3
Review the week ahead
Clashes, prep and who's driving.

10 min/week
0
calendars connected or messages read — capture is a human job, and no tool can promise nothing gets missed when the failure happens before the system
3
kinds of clash, and only one is visible in a calendar
1
entry per prerequisite, on its own day
0
load shared by reading alone
Questions
Everything you need to know.
Can it pull in everyone's calendars automatically?
No, and it's worth being straight about that. Nothing here connects to a calendar, reads email or messages, or gathers anyone's plans — and no tool can promise nothing gets missed, because the usual failure is information never reaching the system at all. What it does is help you design the capture habit and find the clashes in what you've entered, including the ones a calendar can't see.
We have a shared calendar and still miss things.
Then the calendar isn't the problem. Events arrive by school letter, a class group chat, a note in a bag, an email and a remark at pickup — most are lost before any calendar is involved, and a better app does nothing about that. The fix is one capture point, always to hand, used within a minute of hearing something, however scrappily. Tidying up happens once a week; capture happens immediately.
Why do we keep getting caught out by the prep?
Because calendars record events and almost never their prerequisites. The costume is needed on Tuesday for a Friday event; the form is due Wednesday for a trip in a fortnight. Each prerequisite needs its own entry on the day it has to be done, not on the day of the event — a note buried inside Friday's entry only gets seen on Friday, which is exactly too late.
How do we stop the driver arguments?
Add a who's-taking-them field to every entry. Two events overlapping with one driver is the clash a calendar never flags, because neither entry is wrong on its own — making it explicit is what surfaces it on Sunday rather than at half past five on Thursday. And ask about lift-sharing more than you do: people avoid asking because it feels like an imposition, while most parents are glad to be asked.
One of us does all of this. How do we split it?
Start by naming what the work actually is: noticing, capturing, deciding and remembering — not looking. That's why reading a shared calendar isn't sharing the load, and why a system where one person enters everything has redistributed nothing. The workable split is both adults entering their own commitments and each owning specific recurring areas, rather than one person allocating tasks, since allocating is itself the work.
Reviews
Real weeks, nothing found out late.
Loading reviews…