Build a Family Tree Together: Preserve the Stories That Matter

There is a particular kind of quiet that settles in after a parent dies, when you realize the questions you meant to ask can no longer be answered. Who was the woman in the photograph with the pearl brooch? Why did Grandpa leave Scotland at seventeen? Which of the two spellings of the surname is the original one?

A family tree can’t recover every answer, but it can preserve the ones still within reach. Not a chart on the wall, but a living record that your family builds together, one name, one photograph, one story at a time. It becomes more useful, and more likely to survive, when relatives add their own memories, photographs, and corrections.

This article makes the case for starting one, shows how to run it as a family team rather than a solo hobby, helps you choose a tool, and explains where AI helps and where it will mislead you.

Why Start a Family Tree?

The obvious reason to begin is memory. You are, right now, the only person alive who knows certain things: the name of your grandmother’s village, the reason your uncle never married, which cousin ended up in Australia. Written down and attached to a record, those facts survive you. Left in your head, they don’t.

The less obvious reasons are about the present. Genealogy is one of the few hobbies that gives you a legitimate excuse to phone an elderly relative and ask about their life. Those conversations tend to be the best part. It also gives grandparents and grandchildren a shared task that neither finds boring: a fourteen-year-old can scan photographs and search databases faster than you can, and you can tell her who the people are. Research consistently links purposeful, socially engaging activity in later life with better well-being, and some studies associate a strong sense of purpose with slower cognitive decline. None of that proves a family tree will keep you sharp, but it does combine three things the research keeps pointing to: a reason to talk to people, something worth remembering, and a problem to solve.

And there is the simple satisfaction of solving puzzles. A census record from 1921 that lists a household you didn’t know existed is, for most people, more absorbing than anything on television.

Make It a Family Project

Most family trees are built by one determined person, and when that person is gone, nobody else knows how to open the file. A tree is far more likely to last when several relatives know how to use it and feel responsible for part of it. Goodwill isn’t enough to make that happen; you need a simple system. Here is one.

One shared tree, one coordinator. Put the tree somewhere everyone can log in, and name one person, usually whoever started it, as coordinator. The coordinator’s job is small but essential: resolve duplicate entries, settle conflicting dates, keep naming consistent, and hold the backups. Name a successor too. Every family project needs someone designated to carry it on when the founder steps back.

Give people a branch, not a task list. The best way to involve a cousin is to make them responsible for their own line: “You take Grandma Ruth’s side, I’ll take Grandpa Bill’s.” Ownership keeps people engaged in a way that assignments don’t. It also reduces collisions, since two people are rarely editing the same person.

Play to what each person is good at. Every family has a natural listener who can sit with an aunt for an afternoon and let the stories surface. There’s someone who owns a scanner and enjoys tidying things. There’s a teenager who’s fearless with databases. There’s usually one person with the family Bible or the box of papers. You don’t need everyone to do genealogy; you need everyone to do the part they’d enjoy.

Set a rhythm. A monthly video call of thirty minutes, where each person shares one thing they found, does more than any amount of nagging. Finds get celebrated, dead ends get fresh eyes, and the project stays alive between bursts of enthusiasm.

Agree on four rules at the start. First, every fact gets a source, and the source gets labelled honestly: an original record, a copy of one, a relative’s recollection, or a hunch. “Aunt May said so” is real evidence, but it’s oral history, and it gets checked against a record when one turns up. Second, nobody overwrites someone else’s entry without a conversation; if you disagree about a date, leave a note and talk about it on the call. Third, living people stay private. Their birth dates, addresses, and photographs don’t go on any public tree, and before you add a living relative at all, check exactly who will be able to see that profile. Fourth, ask before you record. Get a relative’s clear permission before recording an interview, uploading their photograph, or publishing a story they might consider private. Family history turns up things people would rather not have online.

Aim for stories, not just dates. Ask every contributor to write one paragraph about each person they knew personally. Where they lived, what they did, one thing you remember. Records supply the dates. Only you can supply what the dates meant.

Choose the Right Tool

You need one main tool and, optionally, a private backup.

For the shared tree, FamilySearch (familysearch.org) is the recommendation for most families. It’s free, run by a nonprofit, and gives you billions of historical records alongside the tree itself. Two things to understand before you start. FamilySearch is one shared world tree for deceased people: when you add your great-grandfather, a distant cousin may already have, and your branches join. That’s useful for discovery, but it also means a stranger can change a date you’ve verified, so the coordinator should “follow” key ancestors to get notified of edits. Second, living people on FamilySearch are private to whoever entered them, which means your cousin can’t see the living relatives you added. The fix is a feature called Family Group Trees, which lets a group of relatives share living-person entries among themselves. Set one up on day one or the team will be confused within a week.

If you’d rather run the tree yourselves, webtrees (webtrees.net) is free, open-source software for your own web hosting, with proper user accounts, configurable privacy, and the option to hold relatives’ edits for review before they go live. That’s what powers our own tree at family.fruitfulyears.com, which you’re welcome to browse as an example. Be honest with yourself about the overhead: it needs a web host and someone comfortable installing and updating software. If that isn’t you or a relative, FamilySearch is the better choice.

WikiTree (wikitree.com) is another free collaborative world tree, with strong expectations around sourcing. Profiles of long-dead ancestors become public; it suits families who like the community side of genealogy.

For a private master copy on your own computer, Gramps (gramps-project.org) is free desktop software with no subscription or tree-size tiers, though its dense menus take an evening to learn.

Ancestry and MyHeritage both let you start a tree free, but the tree is mainly a doorway to a subscription that unlocks their record collections and automated hints. Prices vary by country, plan, and promotion; check current pricing before you buy. My advice is to build for free first, then buy a single month when you hit a wall that a specific record set would solve, and turn off auto-renewal the day you subscribe. Their hints are useful, but every hint is a suggestion to verify, not a fact.

Keep a Backup

Whatever you use, back up two things every few months: a GEDCOM export of the tree, and a folder of your original scans and photographs. GEDCOM is the standard transfer format, but programs implement it differently, and photos and some notes don’t always transfer cleanly. Keeping the originals means your family is never locked in to one company.

Where AI Helps—and Where It Misleads

AI is becoming useful in genealogy, and it also makes unsupported answers look convincing. Both things are true, and the second one matters more for a beginner.

Where it helps. The most useful change is reading old documents. Given a scan of 1890s cursive, a German church register, or a faded ship manifest, an AI assistant can produce a first transcript in seconds, work that used to take an afternoon with a magnifying glass. The transcript won’t be perfect; handwriting, language, and image quality all affect it. The right habit is to ask it to transcribe, flag the words it’s unsure of, and offer alternatives, then compare its output against the image yourself, line by line. FamilySearch’s own full-text search uses the same approach to make certain handwritten collections searchable, particularly land, probate, and court records, so you can now find a name inside a deed or a will that was never indexed. Beyond transcription, general assistants like ChatGPT or Claude are good at translating old records, explaining a Latin abbreviation or an obsolete occupation, drafting questions for an interview, turning a rambling recording into clean notes, and summarizing a forty-page probate file into the two paragraphs that matter.

Where it misleads. AI can produce plausible ancestors who never existed. Ask a chatbot who the parents of John Gardner, born 1850 in Aberdeen, were, and it may give you a confident answer with no basis in any record. So treat AI as an eager research assistant that sometimes invents evidence: let it read, translate, and summarize documents you give it, but never let it supply a name, date, or relationship you haven’t seen in a source. When you do use it, keep the original scan beside the AI transcript, note that AI helped, and cite the record image, never the chatbot. And never paste a living relative’s personal details into a public AI tool; it’s the same privacy rule as the tree itself.

Your First Weekend

Saturday morning, phone the oldest relative you have and ask about their grandparents. Ask first whether they mind if you record it, then take notes either way. Saturday afternoon, create a FamilySearch account, enter yourself, your parents, and your grandparents with whatever you know, and set up a Family Group so relatives can see the living people you’ve added. Sunday, email three relatives: tell them what you’ve started, send the link, and ask each one for the single thing they know that you don’t. Then export a GEDCOM and email it to yourself.

That is enough for the first weekend. Every generation you uncover after that repeats the same three moves: ask a person, find a record, write it down with its source.