A DNA Match Needs a Paper Trail Before It Becomes Family History

Genetic matches can reveal a promising connection while leaving the exact relationship open. Linking them to a digital family tree calls for identity checks, documented reasoning, and a way to retain uncertainty. This article explains how to keep that work intact when reviewing hints, moving between programs, and preparing a family archive for someone else.

The line on the screen should lead back to the evidence

A family tree can remember a relationship while losing the reason we accepted it. The names remain, the line between them looks settled, and the research note is somewhere else. Months later, we may struggle to tell whether the link came from a document, a match, or a suggestion we meant to check. That uncertainty matters most when a discovery changes our understanding of the family. We want to preserve the reasoning while it is still clear, including the doubts that prevented an early conclusion. A digital tree becomes more useful when it lets us recover those decisions as easily as the names.

Matches from MyHeritage DNA can give us a starting point for that work. They offer connections to investigate, not a completed account of how each person fits into our history. We still need to identify the tester, assess possible relationships, and check the records along a proposed family path. Our notes should show how a clue became a conclusion, or why it remains unresolved. The same care matters when we export the tree or share it with relatives. A file may retain a relationship while leaving out the message or explanation that made us question it. We can reduce that risk by treating evidence, conclusions, and private information as things that need deliberate handling. The aim is a tree we can revisit without reconstructing every decision from memory. It should also give another researcher enough context to question our work fairly and continue where we last stopped.

The person managing the kit may not be the person who tested

Before attaching a match to a profile, establish whose sample produced the result. Someone may manage several relatives' kits, so the account name or message sender may not identify the tester. Compare the information available with the tree profile you are considering. When the identity is unclear, keep the research separate from the main tree. A private note is easier to revise than an incorrect relationship that has already been shared.

Capture the information needed to return to the finding:

• The testing service, match identifier, and review date.

• The tester's identity, where established.

• The manager's role, if someone else handles the kit.

• The reported shared DNA amount in centimorgans, or cM.

Record the suggested relationship separately from the relationship your research supports. A shared amount can fit more than one family relationship, so a label on the results page is a possibility to assess. Consider ages, known relatives, locations, and the records connecting each generation. Shared matches can help direct attention toward a branch, but they do not establish every parent and child link along it. Keep other possible family paths in view, especially when families have several connections.

Contact can clarify a detail without requiring a request for someone's full history. Ask about the particular ancestor or place relevant to the proposed link, and accept that a match may decline. Retain only the personal information needed for the work, with appropriate permission for messages or material supplied privately. If a biological connection differs from a recorded caregiving relationship, describe the distinction carefully. Genetic research should add an account of inherited connections without removing the people who raised, supported, or belonged to a family. Where evidence is incomplete, a dated note preserves the lead without making a public claim that others may copy.

A research note should explain the decision a hint cannot make

A useful match note separates three things: what was observed, what is proposed, and what the evidence supports. A match amount belongs among the observations. A possible shared ancestor belongs among the proposals until the family paths have been assessed. Give the note a short reference linked to the relevant tree profiles. Keep the source beside the claim it supports, so a later reader can follow the reasoning without guessing which attachment matters.

Describe the path from each tester toward the proposed common ancestor. Check identities and relationships at every generation, using records you can assess. A name repeated across several online trees is worth investigating, but those trees may all copy the same unsourced entry. Automated hints can reveal a plausible route without proving it. Read original documents where available, check dates against known events, and consider whether two people with the same name have been combined. An attractive path should survive those checks before changing the main tree.

Before accepting a new relationship, the note should answer:

• Which records support the links along the proposed path?

• Do dates, places, and identities fit across those records?

• Which conflicts remain, and could another path explain the match?

• Why is the conclusion stronger than the alternatives considered?

Finish with a dated assessment and the name of the researcher. State whether the link is supported, remains a working theory, or has been rejected. Keep earlier reasoning when a new record changes the conclusion, clearly marking the revision. An abandoned theory can explain why a familiar-looking hint should not be accepted again. Once the evidence supports a tree edit, attach a concise explanation and a reference to the fuller note. This lets the tree stay readable while preserving the detail someone would need to challenge or verify the decision.

A successful export needs a check in the receiving program

Moving a tree can preserve its names while changing the way notes, sources, or images appear. Treat the exported file as something to test before relying on it. Keep your main tree intact while using a separate copy for the trial. The useful question is whether the evidence still makes sense after the move.

1. Confirm the format at both ends

Software implementations and supported versions vary, so confirm what both the exporting and receiving programs handle. A shared format name does not guarantee that every feature of your working tree will transfer.

2. Test profiles with more than names and dates

Choose a small sample that includes source citations, notes, images, unusual characters, and relationships needing explanation. Import the copy into a separate test tree, then compare it with the original. Open attached files and check whether an image is included or merely points to an online location; record missing or changed content before deciding that the export can serve as a dependable saved copy.

3. Keep match research outside the export when necessary

Do not assume a family-tree export contains the service's match database, private messages, or all your research notes. Maintain a separate log with stable references back to the tree profiles, and check those references after importing. Save the export date, software name, and chosen format alongside the files. Preserve the original export untouched while using working copies to investigate any problems, so your testing does not obscure what the program actually produced. If a transfer loses important context, keep using the earlier system until you have a reliable way to preserve that material.

Protection includes recovering a mistake as well as a lost file

A tree can be damaged through a well-meant edit as easily as through a failed device. Keep a dated copy before a large merge or a major change in parentage. Sync can spread a mistaken deletion across devices; it should not be treated as proof that an earlier version remains recoverable. Decide where older copies will live and how you would restore them before you need to do it.

For each saved version, retain:

• The tree export and any included media.

• Research logs and source files stored separately.

• The date and reason for making the copy.

• Notes about formats, access, and known export limits.

The U.S. Geological Survey sets out four levels of digital preservation in guidance updated in January 2022. Its Level Two storage requirements call for three physically separate copies, with at least one in another geographic location. They also call for documentation of the storage system and media. This guidance is designed for scientific repositories; its storage principles offer a useful model for a home archive rather than a certification standard for your family tree.

Keep the copies separate enough that one event will not remove them all. Test recovery by opening a saved export and checking complete profiles, supporting notes, and media. Review who can view or edit the live tree, and avoid putting private match messages or raw genetic files into a general family handover. Share a summary of the reasoning when that meets the purpose, seeking permission before including another person's private information. Leave a trusted person clear instructions for locating the archive through a secure access arrangement. A preserved file is only useful if the person receiving it can find it, open it, and understand its limits.

Leave the reasoning available for the next person to examine

We can welcome a new connection without asking the tree to look finished before the research is ready. A clearly marked possibility gives us room to investigate. A supported link, attached to its evidence, gives our relatives something they can assess rather than accept.

Before sharing a revised tree, we can ask someone to follow one relationship from the profile to its sources and research note. Let them identify the points where our explanation becomes unclear. Repair those gaps, then confirm that the explanation survives in the saved export and backup. This makes sharing a useful check on the work itself. We pass on the family names together with the reasons we connected them, leaving room for later evidence to improve the account.