The Handover Problem: Keeping a Household Running When Staff Change
Every well-run household has someone who knows where everything is. Which breaker feeds the pool equipment. Which plumber actually shows up. What the alarm company needs before they'll talk to you. The quirk in the irrigation controller that the manual doesn't mention. That person might be a house manager, a long-tenured housekeeper, or the principal themselves — and the household runs on what's in their head.
Then they give notice.
What follows is the handover problem: the discovery that the household's operating system was a person, and the person is leaving. The next six months become expensive archaeology — re-learning vendors, re-discovering maintenance schedules by watching things fail, resetting codes nobody's sure haven't been shared, and paying for service calls whose entire purpose is to tell you what the last person already knew.
Why households are unusually exposed
Businesses survive employee turnover because they're forced to externalize knowledge — procedures, systems, documentation exist because auditors, regulators, and shareholders demand them. Households face no such forcing function. Knowledge stays tacit because nothing ever requires writing it down, and the people involved are busy running the place. The exposure grows quietly with every year of tenure: the longer someone runs a home well, the more of that home exists only in them.
The irony is that excellent staff make the problem worse. A great house manager absorbs complexity so the principal never sees it — which means the principal has no map of what will go dark when they leave.
What a household actually needs documented
The test for each item: if the person who knows this left tomorrow, would someone else need it within ninety days?
- The property itself — systems and their quirks, equipment locations, shutoffs, breaker maps, seasonal procedures (openings, closings, storm preparation).
- The maintenance calendar — what recurs, at what interval, done by whom, with the history of what was actually done and when.
- The vendor bench — who serves the property, their rates, their history, their paperwork, and the judgment layer: who's reliable, who needs supervision, who to call at 6 PM Friday.
- Assets and documents — appliance models and serials, warranties, manuals, insurance policies, service contracts, receipts for anything with a claim horizon.
- Access — every code, key, fob, and credential; who currently holds what; stored encrypted, not in a spiral notebook in the kitchen drawer.
- The rhythm — the weekly and seasonal cadence that makes the house feel run: what happens Mondays, what happens in November.
Written once, this is a binder. Maintained as the working system the household actually operates from, it's continuity — the difference matters, because binders go stale the month after they're written. Documentation that people use daily to run the place is the only documentation that stays true.
The transition, run properly
When someone leaves: their departure should be an access event, not a knowledge event. Revoke their account and rotate the codes they held — in a system with role-scoped access and encrypted storage, that's an afternoon, not a locksmith week. The tasks they owned reassign visibly instead of silently stopping. Their history — what they did, which vendors they used, what they logged — stays.
When someone arrives: their first week shouldn't be oral tradition. A new house manager who can read the property's maintenance history, the vendor bench, and the open task list starts operating in days. The standard worth aiming for: a competent professional could take over from the record alone.
Before anyone leaves: the honest audit. Ask, for each property: what does only one person know? Every answer is exposure. This is also the right lens for principals who currently run everything themselves — self-dependency is still single-person dependency, as anyone who has tried to hand a household to a new manager mid-renovation can attest.
Where the system earns it back
The objection to all of this is real: documentation is work, and household staff didn't sign up for clerical duty. This is precisely the gap an AI-first platform closes. When logging reality is as light as photographing a receipt or typing "replaced the pool pump capacitor, $340, pool vendor" — the record builds itself as a byproduct of the work. Continuity stops being a project and becomes a property of how the household already operates.
That's the design position behind Hauseora: the household's operating knowledge — properties, maintenance, vendors, assets, documents, access — living in structured, role-scoped, encrypted records that any authorized person can operate from, with an AI interface doing the clerical labor. Staff changes still cost you a person. They stop costing you the system.
If you're staffing up, transitioning managers, or quietly aware that too much of your household lives in one head, walk through it with us — and for the broader coordination picture, see managing staff across multiple properties.