How to Plan a Family History Project With Relatives
Give a shared family history project a clear outcome, respectful roles, evidence standards, privacy rules, and a finish line.
A family history project works best when relatives agree on one outcome, divide work by interest, keep evidence in a shared system, and decide privacy and decision rules before disagreements arise. Start small enough to finish: one branch, one album, one migration story, or one anniversary publication.
Choose a concrete deliverable
“Research the family” has no natural end. Better outcomes include:
- identify and document all descendants of one couple to 1950;
- scan, describe, and safely return one album;
- record five oral histories about a shared place;
- produce a cited timeline and map for one migration;
- prepare a 20-page family booklet for a reunion.
Write what is in scope, what is not, who the audience is, and the target date. A narrow first project builds trust and reveals which tools and conventions the group actually needs.
Invite different kinds of contribution
Not everyone wants to search archives. Useful roles include coordinator, interviewer, scanner, photographer, transcriber, source checker, map maker, writer, editor, privacy reviewer, and family liaison. Someone who knows faces or owns an album may contribute knowledge no database search can replace.
Ask each person about time, access, skills, and comfort. Avoid quietly assigning all technical work to one relative or all family communication to another.
Create a one-page project brief
Record:
- objective and final format;
- people, places, and dates in scope;
- participants and roles;
- evidence and citation expectations;
- file naming and storage location;
- privacy and consent rules;
- how uncertain facts and disagreements will be shown;
- review dates and completion criteria.
Keep it understandable to a relative who joins later.
Agree on evidence standards
Separate family information, record evidence, and interpretation. Every significant factual claim should link to a source or be labelled as tradition or hypothesis. Preserve original wording in transcriptions. Record unsuccessful searches and conflicting evidence rather than overwriting them.
Decide whether changes require a citation, whether merges need review, and who can mark a relationship as proved. These rules protect everyone from well-intentioned but untraceable edits.
Set privacy boundaries
List living people and sensitive categories such as adoption, health, DNA, contact details, financial information, family conflict, and private correspondence. Decide who can view them, what can appear in the final work, and how consent will be recorded.
Use the least public setting while preparing. Do not assume that every participant has authority to publish photographs or letters they possess. Ownership of a physical copy and copyright or privacy permission are not the same.
Use one shared task and evidence system
Create a task for each research question or asset batch, with an owner, status, and next action. Store findings where the whole team can locate them. Messaging apps are useful for conversation but poor as the only archive: decisions, citations, and files disappear into a scroll.
A useful task is “Check 1901 census for Thomas Kelly household in Peel; record all occupants and citation.” An unhelpful task is “Do the census.”
Begin with a pilot
Test the workflow on one person, five photographs, or one interview. Can participants upload material, understand file names, add a source, see open questions, and recover an earlier version? Fix friction before importing thousands of records.
Hold short review sessions
Meet around evidence rather than general updates. Review:
- what was learned;
- which source supports it;
- conflicts or uncertainties;
- decisions needed;
- next actions and owners.
Write decisions in the workspace. Memory of a video call should not become the project’s only audit trail.
Resolve disagreements without voting on facts
When two relatives disagree, define the exact claim and list the sources on each side. Check identity, informant knowledge, record proximity, transcription quality, and independent corroboration. Record the conclusion and remaining uncertainty.
If evidence does not resolve the issue, present both possibilities. A family tree can show uncertainty; it does not have to manufacture agreement.
Design the final output early
A booklet, website, exhibition, or private archive has different requirements. Draft a sample page early with a story, image, caption, citation, and privacy treatment. This reveals whether scans are high enough quality, citations are readable, and permissions are sufficient.
Close and preserve the project
At completion:
- review facts, citations, captions, permissions, and living-person details;
- export the tree and reports in portable formats;
- preserve source files and the project brief;
- create multiple backups;
- record who holds the archive;
- list unresolved questions for a future phase;
- acknowledge every contributor.
Success is not the largest possible tree. It is a finished, evidence-based family resource that relatives trust and can continue without reconstructing how it was made.