The longer I work in genealogy, the more I realize something about family tree research: a family tree isn’t simply something I find. I build it. Records give me names, dates, places, relationships, occupations, witnesses, neighbors, signatures, and dozens of other clues, but the records don’t come with instructions telling me exactly where every piece belongs.
That means I’m making decisions all the time. I decide whether the John Smith in one census is the same John Smith in the next. I decide whether a marriage record belongs to the couple I’m researching. I decide whether two conflicting birth years can still describe the same person, and whether a parent-child relationship has enough support to enter it as a conclusion rather than leave it as a possibility.
Those decisions can become so routine that I forget they’re decisions at all. A family tree may look like a collection of facts, but behind many of those facts is a judgment someone had to make. That thought changes the way I look at my own family tree research.
The Record Doesn’t Make the Decision
A record can be accurate and still be attached to the wrong person. I can find a perfectly legitimate census page, marriage license, death certificate, land deed, or probate file. The document itself may be genuine, and the information may have been copied correctly. The problem can still be mine if I decide it belongs to the wrong individual.
A name match is evidence, but it’s rarely the whole answer. The same is true of an age, a county, an occupation, or even the name of a spouse. I have to look at the record in the context of everything else I know. This becomes especially important when names repeat, because families reused given names and communities could contain several unrelated people with the same surname. Cousins could even have the same first and last names and be only a few years apart in age.
So the question isn’t simply, “Did I find a record for this name?” The better question is, “Why do I believe this record belongs to this person?” That small change in wording puts the responsibility back where it belongs. It forces me to explain the connection instead of treating a matching name as an answer.
Evidence Can Point in More Than One Direction
Genealogy would be easier if every record agreed, but they don’t. One census may place an ancestor’s birth in Virginia, while a later census says Kentucky. A death certificate may give a third answer. Ages can drift, names can change spelling, parents may be listed differently in different records, and even information carved into a headstone can be wrong.
When records disagree, I have to weigh them. I ask who supplied the information, how close that person was to the event, whether the record was created near the time of the event, and whether other independent records support the same conclusion. That’s where family tree research becomes more than collecting documents. I may have ten records in front of me, but the number of records isn’t enough by itself.
Five records can repeat information that came from the same mistaken source. One original record created near the time of an event may sometimes deserve more weight than several later accounts. I have to think about where the information came from and why one piece of evidence may deserve more confidence than another.
This is one reason the Genealogical Proof Standard is so useful. It gives genealogists a framework for thorough research, source citation, analysis, conflict resolution, and written conclusions. I’ve written about that standard before, but I keep coming back to the same simple point: the standard helps guide the work. It doesn’t make the decision for me.
When Does a Possibility Become a Conclusion?
I think this is where judgment becomes most visible. A man appears in the right county at the right time. A woman with the correct first name appears in a marriage record. A household contains a child whose age fits the ancestor I’m trying to identify. A probate record names someone with a familiar surname. Any one of those clues may lead somewhere, but a clue and a conclusion aren’t the same thing.
I try to think of the process in stages. A clue gives me a reason to look. A possibility gives me something to test. Evidence gives me something to compare. A conclusion comes after the pieces have been tested together. That distinction helps keep the tree from getting ahead of the research.
It’s tempting to attach something temporarily and promise myself that I’ll verify it later. The problem is that temporary information has a way of becoming permanent. Once a name appears in the tree, hints begin attaching themselves to it, new records are interpreted through that connection, and before long, I may be researching an entire family that rests on a decision I never really finished examining.
I’d rather leave a blank space than fill it with confidence I haven’t earned. A blank tells me there’s still work to do. A wrong answer can hide that need and send the research in the wrong direction.
Judgment Doesn’t Mean Guessing
There’s a difference between using judgment and making a guess. Good genealogical judgment comes from evidence, context, experience, and a willingness to reconsider. When I’m deciding whether a conclusion belongs in the tree, I want to ask questions that test it instead of questions that simply support what I already hope is true.
- Do the dates fit together without forcing them?
- Do the places make sense when I follow the person through time?
- Do relatives, neighbors, witnesses, and associates keep appearing around the same individual?
- Is there conflicting evidence, and have I accounted for it?
- What evidence would I expect to find if my conclusion were wrong?
That last question is especially useful because it pushes against confirmation bias. If I think two records belong to the same man, what would show that there were actually two men? If I think I’ve identified a woman’s parents, what evidence would make that relationship impossible? If a shared online tree gives me a new generation, what happens when I remove the tree itself and look only at the underlying records?
Those questions slow the process down, but sometimes slowing down is exactly what protects the tree. I don’t need to distrust every conclusion. I do need to know why I reached it and what could cause me to reconsider it.
The Family Tree Is Also a Record of My Reasoning
When I look at a finished family tree, I see names connected by lines. What I don’t immediately see are all the decisions behind those lines. I don’t see the record I rejected because the age was wrong, the second man with the same name living three townships away, or the conflicting birthplace that took several records to sort out.
The tree shows the conclusion, but my research notes should preserve the reasoning. That’s becoming more important to me because I don’t want a future researcher to inherit a tree full of conclusions with no way to understand how I reached them. A source citation tells someone where the information came from. A research note can explain why I believed that information belonged to this particular person or relationship.
Those aren’t the same thing. If I write, “1850 census, Greenbrier County,” I’ve identified a source. If I also note that the household sits beside two known relatives, the age matches earlier records, the occupation remains consistent, and the children’s names correspond with later records, I’ve begun to explain my reasoning.
That explanation may be more valuable years from now than I realize today. It gives my future self, or another genealogist, a way to test the conclusion instead of starting the whole question over again.
I’m Part of the Research
There’s something humbling about recognizing how much of a family tree depends on the person building it. I want the tree to represent my ancestors as accurately as the surviving evidence allows, but the records don’t arrange themselves. I choose which sources to search, which clues to follow, which conflicts need more attention, and when the evidence is strong enough for me to reach a conclusion.
That means I’m part of the research whether I acknowledge it or not. The goal isn’t to remove judgment, because I don’t think that’s possible. The goal is to make that judgment careful, visible, and open to correction.
The longer I work with genealogy, the less interested I’m in having the biggest tree or the fastest answer. I’d rather understand why a connection belongs there. Every line connecting two people in my family tree represents more than a relationship. Somewhere behind that line is evidence, and somewhere behind the evidence is a decision. I want to be able to explain mine.
Learn More
If you’d like to keep thinking about how we weigh evidence and make decisions in family history research, these articles may help:
- What Is the Genealogical Proof Standard and Why Should You Use It?
- The Temptation to Assume in Genealogy
- Same-Name Ancestors, Part 1: The Time Method
- Why Citing Sources Is Crucial in Genealogy and How to Do It Right
Board for Certification of Genealogists: Ethics and Standards
Review the standards for evaluating evidence, resolving conflicts, and explaining genealogical conclusions.
