Our whole family wants to do this together
The steward's operating manual: an honest approval mode, one-tap onboarding for the non-technical, memory nights, the bulldozer relative, kids through the guardian gate, and the art of celebrating contributions.
- About 30 minutes to set up roles and send invites
- A family group chat, or wherever your family actually talks
- One evening, eventually, for a memory night
A whole family building one archive together is the best version of this — and it puts one person, probably you, in a role that deserves its own manual: the steward. The steward isn't the person who writes the most. The steward is the person who sets things up so everyone else can contribute easily, keeps the peace when memories collide, and makes contributing feel so good that people keep doing it. This playbook is that manual.
1. Pick your approval mode honestly
Every archive has an approval mode, and choosing it honestly — based on your actual family, not the family you wish you had — is the steward's first real decision:
- Review everything — every contribution waits for your approval before it lands. Maximum care, and maximum work: if thirty memories arrive after a reunion, all thirty wait on you. Right for archives with delicate history or a wide-open contributor circle.
- Trusted contributors — the people you trust (your sister, your uncle) are auto-approved; everyone else waits for review. The setting most families land on.
- No review — everything lands immediately. The wild west. Genuinely fine for a small, close family that talks every day; choose it knowingly.
One line the steward should know cold: whatever mode you pick, contributions from minors and anything touching sensitive topics always wait for review. That floor isn't a setting you could turn off — it's how the archive works, and it means even "no review" is never actually reckless about children.
2. Roles, briefly
Members of the archive hold a role — owner, admin, editor, or viewer — and outside the membership entirely there are invited contributors, who need no account at all and can be submit-only. The practical translation: make your co-steward an admin, make the relatives who'll organize things editors, and give everyone else the contributor link. Most of the family never needs an account, and that's by design.
3. Onboarding the non-technical relatives
Here is the entire onboarding process for your eighty-year-old uncle, and it's important not to add to it: send him the contributor invite link with a one-line text — "tap this, type your memory, done — no account." That's it. No app to install, no password to invent, no account to abandon. The moment onboarding involves a second step, you lose the exact people whose memories go back the furthest.
For the relatives who won't type at any age: "or just call me and tell me the story, and I'll put it in." A steward with a phone and ten minutes is the best onboarding system ever built. Record the call if they're willing — then it's a voice memory, which is better anyway.
4. Run a memory night
Nothing fills an archive like a memory night: one evening, in person or on a video call, where the family does nothing but tell stories while someone captures them live. It works because stories summon stories — Uncle Joe's version reminds your mother of the part Joe always leaves out, and suddenly you have both.
- Appoint one scribe (not the best storyteller — they'll be busy) to capture as things flow: quick voice recordings on a phone, or rough typed notes straight into the archive. Rough is fine; polish later.
- Seed it with three or four prompts from the archive, or bring five photos and ask "okay — who remembers this?" A photo of the old house does more than any question.
- Capture the laughter takes too. The room cracking up in the background of a recording is itself a memory.
- Afterward, spend twenty minutes turning the raw captures into entries while the night is fresh. That twenty minutes is where the evening becomes permanent.
5. The bulldozer relative
Every family has one: the relative whose version of events is loud, confident, frequent, and — per everyone else — wrong. Two tools keep the bulldozer from becoming a war, and neither is the reject button.
First, alternate tellings. When their version collides with your mother's, keep both, side by side, each in its teller's own words. Nobody's memory gets ruled against; the archive holds multiple truths on purpose, and "we kept both versions" ends arguments that "we went with Mom's" would start.
Second, the aside. Some contributions don't belong on display — the axe-grinding one, the one that would wound — but rejecting them starts a feud. Setting them aside doesn't: an aside is kept, preserved in full, just not displayed. The contributor's words aren't erased; the family's peace isn't spent. And needs-clarification is the gentle middle path — it goes back to the contributor as a kind question ("can you tell us more about when this was?") rather than any verdict at all.
Rejection wounds — in a family archive, deleting someone's memory reads as deleting them, and contributors who get rejected once rarely contribute twice. Reach for aside, alternate tellings, or needs-clarification first. Outright rejection is for spam, not for relatives.
6. Kids, through the guardian gate
Children are often the most eager contributors — and grandchild questions unlock stories no adult thinks to ask for. Child contributors go through a guardian gate, and here's how it actually runs:
- Invite the child as a contributor, naming their parent or guardian.
- The child adds their memory — a story about Grandma, a drawing photographed, a recorded question-and-answer with Grandpa.
- Before anything enters the archive, it goes to the guardian for sign-off. No guardian approval, no entry — the steward can't waive this, and neither can anyone else.
- After guardian sign-off, it flows into the normal review queue like any other contribution.
The gate is a floor, not a hoop: it means a nine-year-old can be a real contributor to the family's record while their parent stays fully in the loop, and no steward ever has to be the one policing what somebody else's child shared.
7. Celebrate contributions — the flywheel
The steward's most underrated job is applause. When a good memory arrives, quote one great line from it back to the family — a sentence in the group chat: "Aunt Rose just wrote: 'He danced like the floor owed him money.'" Two things happen: Aunt Rose glows, and three other people think "oh, I have one about his dancing" and go add theirs. One quoted line recruits the next contributor more reliably than any reminder ever sent.
Do it steadily and the archive starts running on its own delight — which is the real finish line of this playbook: an archive the steward no longer has to push, because the family pulls.
Nothing a contributor adds is ever silently lost or quietly rewritten — every memory keeps its revision history, asides are preserved in full, and every contribution stays private (or pending) until the family chooses otherwise.
Still stuck? [email protected] — a person reads every message.