Loading route foundation…
getting started
Relatives do not need genealogy training to make valuable contributions. They can identify people, explain relationships, share memories, locate originals, describe places and traditions, correct mistakes and say what should remain private. A clear, low-pressure contribution process turns family knowledge into material that can be checked, attributed and preserved.
Family members can help build a family history archive by contributing one small, well-described piece at a time: a name correction, photograph identification, memory, document, place, recipe, voice note or unanswered question. Every contribution should record who supplied it, when, what they know firsthand, what they heard from someone else and how the family may use it.
The person coordinating the archive can then link the contribution to people and events, preserve the original wording, assess factual claims where relevant, and record privacy or access restrictions. Participation should be optional and accessible; no relative should need to understand citation systems or family-tree software before helping.
A relative who says “I am not the family historian” may still know that Aunt May was called Mimi, recognize a school uniform, remember the route to a former home or hold the only labelled copy of a photograph. This information supplies context that formal records rarely provide.
Useful contribution types include:
The contributor does not need to decide whether the information is “proof.” Their role is to share knowledge with context; the archive records and evaluates it.
“Send me your family history” is too broad. Offer one clear action:
Let people respond in the format that suits them: a voice note, telephone call, handwritten page, email, annotated image or guided interview. Mobile-friendly prompts and short sessions reduce barriers. Provide a close or skip option for forms; identifying the contributor is valuable, but participation should not be coerced.
Explain the project in plain language: what is being collected, who will see it, whether it may be published, how the contributor can request a correction and who is responsible for the collection. Do not promise secure login, permanent hosting or automatic backup unless those services actually exist.
For each contribution, record:
This protects the contributor and improves evidence. “The family lived above the bakery” is more useful as “Recalled by Ana Cruz in 2026 from her childhood visits in the late 1960s.” If Ana heard it from her father rather than saw it herself, record that chain.
Preserve the original contribution before editing it into a profile. A polished narrative may normalize spelling or remove repetition, but the archive should retain the source recording, note or transcript when permission allows.
Work with a small batch of images, preferably in a quiet setting. Show the entire front and back. Ask open questions before suggesting identities: “What do you notice?” and “Where might this have been taken?” Then ask how confident the person is and why.
Record disagreements as separate attributions. Do not let the most confident speaker erase other accounts. Details such as clothing, buildings and age estimates can help later, but automated face recognition and image enhancement should not be treated as identification proof.
Give each image a stable number. Record the original holder, photographer if known, inscriptions, physical format and permission to copy or publish. The US Copyright Office notes that the photographer is generally the initial copyright owner in the United States; possession of a print does not automatically settle reproduction rights, and laws vary elsewhere.
The Oral History Association's current principles recommend clear project communication, informed consent, respect for narrator autonomy and discussion of what will happen to the interview. For a family project, that means no surprise recording and no assumption that consent to speak equals consent to post publicly.
Use prompts rather than interrogation. Ask about sensory and ordinary details as well as major events. Allow silence. Let the narrator refuse, pause or restrict a section. At the end, ask what the interviewer missed and whether anything should remain private for a period of time.
Create a brief index or transcript and offer it back for review. Record any corrections without silently rewriting the original recording. A narrator may accurately remember an experience while misremembering a calendar date; preserve the account and verify date claims separately.
Make correction easy and non-defensive. Ask the contributor for the preferred wording and the basis of the correction. Attach the new evidence or attribution; do not delete an earlier version merely because a later contributor disagrees.
Use neutral labels:
Some disputes cannot be resolved. The archive can preserve more than one perspective without publishing harmful allegations as fact. A coordinator should pause publication when a story could expose a living person to harm, reveal parentage or adoption, or intensify conflict.
_Fictional example:_ Joel uploads a photograph and writes, “Grandpa Tomas at the sugar mill, about 1940.” The archive asks who provided the identification and whether Joel remembers the scene himself. He explains that his mother Lina labelled the print in 1988.
The coordinator records Joel as the supplier, Lina as the identifier and “circa 1940” as unverified. Another cousin recognizes the second man but gives a different mill location. Both identifications remain attached. A city directory and employment card later support the second location and a 1942 date. The final caption explains the evidence without treating Joel's good-faith contribution as a mistake to hide.
One person can coordinate intake and filenames. A careful reader can transcribe letters. A local relative can photograph a cemetery or family house where access is permitted. A bilingual contributor can produce a literal transcription and a separate translation. An older relative can identify images; a younger relative can help record and transfer files.
Use a simple review queue so contributions do not vanish in messages. Each item can move through: received, needs description, needs permission, ready for research, verified or partly verified, and added to archive. Return a copy to the contributor and acknowledge their role if they consent.
Collect only what the archive needs. Limit dates of birth, addresses, contact details and identifying documents for living people. Ask before including health, financial, immigration, adoption, parentage, sexuality, trauma, allegations or images of children. Permission may need to come from more than the person who supplied a story or photograph.
DNA data affects relatives as well as the tester. Raw DNA files, match lists and unexpected-parentage findings should not be placed in a general family contribution area. The Federal Trade Commission's genetic-data enforcement work shows why security, sharing and deletion promises deserve scrutiny. Do not upload sensitive contributions to an unverified AI service.
Respect community and cultural protocols for sacred knowledge, names, burial information and restricted records. Copyright, privacy and access requirements vary by jurisdiction and circumstance; seek local professional advice when necessary.
The Roots Adventure Lite Archive is designed around approachable family participation: a basic tree, clear profiles, stories, photographs and prompts such as “Start here,” “Add a story,” “Add a photo” and “Add family information.” A contributor-identification prompt may be skipped or closed. Lite should not be described as providing accounts, cloud synchronization, automatic backups or real-time multi-user editing.
The Roots Adventure Full Archive may suit a project that also needs deeper evidence, citations, research notes, timelines and open questions. Families can compare the approaches, explore Lite, or learn about the Full Archive.
Family participation works when the request is specific, the process is respectful and the archive preserves attribution. A nickname, uncertain face, remembered route or correction may unlock a much larger history. The goal is not to make every relative a genealogist. It is to give their knowledge a clear, ethical path into a record that can be understood and checked.
Editorial basis: Oral History Association principles, best practices and ethics; US National Archives preservation and genealogy guidance; US Copyright Office photography guidance; Society of American Archivists archive definitions; FTC genetic-data privacy enforcement; Smithsonian transcription and archival-description examples.
A digital family history archive is an organized home for the records, research and stories that explain a family across generations. It connects a family tree to photographs, documents, memories, places and evidence so that people can understand not only who belongs in the family, but how those lives were lived and how each conclusion was reached.
Preserving family material means protecting both the object and the knowledge attached to it. This guide covers a practical sequence for inventory, description, safe digitization, storage, backup and responsible sharing.
Genealogy research needs enough structure to show what was searched, what each source reports and why a conclusion is reasonable. Family history needs room for voice, relationships, place and uncertainty. The answer is not to choose between a database and a narrative, but to connect them through people, events, sources and research questions.
