The mental load: why one parent carries the family admin — and how to share it

It has a name now, which helps. The mental loadis the invisible work of running a family: not doing the swimming lesson run, but being the one who knows it moved to Thursdays, that the kit needs washing by Wednesday, that the payment is due, and that next term's slot needs booking before half-term. Each item is small. Carrying all of them, all the time, is not.

In most households this work concentrates in one person — the "default parent" — regardless of how fairly the visible chores are split. Sociologists have written about this for decades (Arlie Hochschild's "second shift" is the classic; Allison Daminger's more recent work separates the anticipating, deciding, monitoringparts from the doing). You don't need the literature to recognise the pattern: one parent is the family's database, and being the database is exhausting in a way that's hard to explain to someone who has never been it.

Why it defaults to one person

Information flows to one inbox. The school has one contact email. The GP texts one phone. Whoever receives, owns.
Knowledge compounds. Once you're the one who knows where the swim kit is, asking you is faster than finding out — so everyone asks you, forever.
Monitoring is invisible. A packed lunch is visible work. Remembering that Tuesday is packed-lunch day is invisible work. Invisible work doesn't get renegotiated because nobody else sees it happening.
"Just ask me if you need help" keeps the load in place — delegation-on-request still leaves one person doing the anticipating and the asking.

What doesn't work

Trying harder doesn't work — the load isn't a discipline problem. Verbal handovers don't work — "I told you about the dentist" is not a system. And splitting tasks 50/50 without splitting the knowingdoesn't work: if one parent still has to brief the other before every handover, the briefing parent is still carrying the load, now with a project-management job on top.

What does: move the load out of a head and into a system

The mental load is fundamentally an information problem, and information problems have infrastructure solutions. The goal: no fact about family logistics should live only in one person's head.

One shared calendar, visible to everyone.Not “her calendar that he can technically open” — a family calendar on both phones and, ideally, on a screen in the kitchen where the plan is ambient and nobody has to ask.
Fix the inputs, not just the storage.The load re-accumulates because new information keeps arriving at one person. Get both parents on the school's email list, and better, make the inputs process themselves — forwarding school email into a system that extracts the dates automatically removes the secretarial layer entirely.
Reassign ownership, not tasks.“You own swimming” means owning the knowing: the schedule, the kit, the rebooking. Whole domains, end to end. The shared system is what makes this possible — the new owner can actually see everything.
Give kids their own interface.A child who can check their routines on the kitchen tablet isn't asking a parent to be their memory. Age-appropriate self-service (calm chores and routines, not nagging apps) shrinks the load at its source.
A weekly ten-minute review, together.Both parents, Sunday evening, next week's calendar on the table. Not one parent presenting a briefing — two people reading the same shared system.

A fair test of progress

Could the non-default parent run a full school week — kit, forms, clubs, the 50p for mufti day — using only what's in the shared system, with zero verbal briefing? If yes, the load is genuinely shared. If no, the gap between what the system knows and what one head knows is the remaining mental load, and it's now visible enough to fix.

None of this needs an app to be true. But this is the exact problem Less Mayhem was built around: one calm place where the calendar, the school admin, the lists and the kids' routines live — so the family runs on a system, not on somebody's memory.