Family Handoff Docs: Keep the Homelab Alive Without You

The audience is not you

Write for someone who can follow a checklist but does not know Docker vocabulary. If a sentence needs a glossary, rewrite it. The reader is your partner, a trusted friend, or future you after anesthesia — not a homelab forum.

Operator rule: every page must answer "what do I click or type first" within ten seconds. Background philosophy belongs in a separate doc they never open during an incident.

Minimum viable handoff pack

Include: where the hardware lives and how to power-cycle safely (which switch, which UPS beeps mean what); the homepage URL that shows green/red status; how to connect to the LAN or VPN (app name, not "WireGuard config in the repo"); which three services matter most to the household; where backups live in plain language ("Backblaze bucket named homelab-backups"); and how to open a ticket to you with screenshots and the exact error text.

Store the pack in three places: printed in a labeled folder near the rack, PDF in the household vault, and a copy on a relative's encrypted USB that updates quarterly.

Runbooks that fit on one page

For each critical service write four lines: how to restart (Portainer stack name or one compose command), health URL that should return 200, backup location and last successful date, and "if red, do X then stop and call me."

Example shape for a photo app:

# Only if photos won't load — run on the mini-PC in the office
cd /opt/compose/immich
docker compose restart
# Then open https://photos.home.example.com and scroll to last week's album

Link to Getting started guides only as optional background — the handoff pack must stand alone when GitHub and your blog are unreachable.

The three-service priority list

Force-rank what the household feels within an hour of outage: usually photos, password vault, and internet/DNS or the router — not your torrent box or analytics. The handoff doc covers the top three in order; everything else is "wait for operator."

Document who is allowed to restart what. A well-meaning relative running `docker compose down -v` on the wrong project causes more damage than leaving a flaky service up.

Network and access without jargon

Draw modem → router → Proxmox host. Circle the machine that must stay on for photos. Write the VPN app name with a screenshot of the connect button — not "VLAN 20 management interface."

Backup pointers a human can use

Name the vendor portal, bucket name, and vault entry for the login. One line: "Backups nightly at 2 AM; restore drill log older than 60 days → nag operator."

Practice once — silently

Ask the designated person to restart the homepage and open Immich (or your photo app) while you watch without speaking. Note every hesitation: wrong bookmark, fear of the terminal, unclear which machine. Fix wording until they succeed without improvising. Repeat after any hostname or VPN change.

Failure story: the sticky-note master password

One household kept router and vault passwords in a shared Google Doc. A relative found it while fixing Wi-Fi. Fix: break-glass points to a sealed envelope and Vaultwarden emergency contact — no plaintext masters in shared drives.

Lab notes from careful ops practice

One-page table (Service | Restart | Check | Backup) fits three services at 11pt. Portainer handoff says "Restart only, never Recreate" with a screenshot after someone deleted volumes.

Legal and privacy note

Do not put plaintext master passwords in shared docs. Point to the vault and break-glass instructions instead. Note which cameras or logs exist for household privacy conversations. Update the pack when you change hostnames, retire services, or add a relative to emergency access.

Related reading

See Restore drill playbook, Docker Compose hardening, Cost of self-hosting, and the Homelab ops essentials collection.