How to Keep a Family Tree Research Log

A family tree can look finished even when the research behind it is still uncertain. A name may be spelled two ways. A birth year may come from memory rather than a record. A relationship may be likely but not fully confirmed.

That is why a research log matters. It keeps track of what you know, what you guessed, who told you, and what still needs checking.

MakeFamilyTree.org is a visual chart editor, not a full genealogy database. For serious research, keep a separate research log beside your chart. The log does not need to be complicated. A simple document or spreadsheet is enough.

What a Research Log Should Track

A useful family tree research log answers five questions:

1. What did you add or change?
2. Where did the information come from?
3. How confident are you?
4. Who should review it?
5. What is the next action?

This helps prevent a common problem: after several edits, nobody remembers which details came from documents and which came from family memory.

Simple Research Log Columns

Use these columns in a spreadsheet:

This structure is enough for most family chart projects.

Separate Facts From Stories

Family stories are valuable, but they should not be treated the same as verified records. A story can explain why someone moved, how relatives met, or why a nickname matters. A record may confirm a date, place, or legal relationship.

In your log, mark source types clearly:

• Interview
• Photo caption
• Birth record
• Marriage record
• Census record
• Obituary
• Family Bible
• Old letter
• Unconfirmed memory

This does not make family memories less important. It simply helps future readers understand what kind of evidence supports each detail.

Track Uncertainty Directly

Do not hide uncertainty. A family tree becomes more trustworthy when uncertain details are labeled honestly.

Examples:

• "Born about 1920"
• "Possibly lived in Osaka"
• "Relationship still being checked"
• "Name spelling varies in family notes"

If a chart is for public sharing, you may leave uncertain private details out of the visual tree and keep them only in the research log.

Keep Change Notes

Every time you make a major update, write a short change note:

• "Added maternal grandparents from interview with Uncle Rob."
• "Corrected surname spelling from Lee to Li after checking wedding record."
• "Removed unverified cousin branch until relationship is confirmed."
• "Exported reunion draft for review."

These notes are useful when relatives disagree. Instead of arguing from memory, you can review when and why the change happened.

Use the Visual Tree as a Review Draft

A visual family tree is a strong review tool. Relatives often spot mistakes faster when they see a chart instead of a spreadsheet.

Try this process:

1. Build a simple chart with names only.
2. Export it as PNG or JPG.
3. Send it to one relative for corrections.
4. Add every correction to the research log.
5. Update the chart only after deciding what is confirmed.

This keeps the chart clean and the research process transparent.

Privacy Notes for Living Relatives

Research logs can contain sensitive details. Keep private information out of public charts and be careful where you store the log.

Avoid sharing:

• Full birth dates for living relatives
• Addresses
• Medical details
• Family conflict notes
• Private photos
• Information about children

If you need to share a review draft, remove sensitive fields first.

A Practical First Log

For your next family tree project, create one spreadsheet with these tabs:

• People to add
• Unconfirmed facts
• Source notes
• Questions for relatives
• Export history

The export history tab can be very simple:

This helps you avoid confusing old drafts with corrected versions.

Final Thought

The visual tree shows the family. The research log shows how you got there. Keeping both makes your work more useful, easier to correct, and safer to share.

When you are ready, build a draft in the family tree editor, export a copy, and use your research log to collect corrections before making the next version.