A family history researcher lines up every record for one ancestor: birth, marriage, children’s births, a land purchase, a census entry, a death. Read individually, each record looks solid. Laid out in order on a single page, something jumps out that no single record revealed on its own — a marriage two years before the bride turns fourteen, or a birth recorded eight months after the father is documented living three states away. The records didn’t lie. They just weren’t read together. That’s the entire case for building a timeline: it’s not a filing system, it’s a diagnostic tool, and it catches problems that no amount of staring at individual documents ever will.

What a Timeline Actually Does

The Genealogical Proof Standard’s third element calls for analysis and correlation of the assembled evidence — not just collecting records, but reading them against each other.^[1] A timeline is the most direct way to do that correlating. Ordering every known event chronologically forces facts that arrived from different sources, on different days of research, months or years apart, to sit next to each other on the same page. Contradictions that were invisible when the records lived in separate folders become obvious the moment they’re side by side.

What a Good Timeline Catches

A handful of problems show up in timelines with remarkable consistency:

• Impossible overlaps. A person documented in Ohio in March and in Pennsylvania in April of the same year, with no plausible way to have made that trip, is either two different people or a record with a wrong date.
• Age math that doesn’t add up. A marriage record for a bride who would have been thirteen, or a mother who would have been forty-nine at a documented birth, is worth a second look — not automatically wrong, but worth checking rather than assuming.^[2]
• Births that precede marriages by suspicious margins, or follow a father’s documented absence. Sometimes this reflects a real and unremarkable situation. Sometimes it’s a sign that two families have been merged into one by mistake.
• Gaps. A ten-year stretch with no documented events at all is not evidence of nothing happening — it’s a flag that records for that period haven’t been found yet.

None of these findings prove an error on their own. Each one is a prompt to go back and check — which is exactly the point. A timeline doesn’t resolve conflicts by itself. It surfaces them so they can be resolved deliberately, instead of sitting quietly unnoticed in separate records.

A DFA Example of a Timeline Catch

DFA Family Group 5 has a problem. There’s a lineage out there, widely spread over many family trees on many sites over a long time. The problem is, it’s almost certainly wrong. And I was guilty of participating in and perpetuating that for a long time.

Group 5’s supposed immigrant ancestors were listed as Johann Michael Dillmann, b. 6 May 1755 in Lautzenhausen, Rhein-Hunsrück-Kreis, Rheinland-Pfalz, Germany, and Maria Elisabeth Eva Legrand, b. 26 Mar 1760 in Niederweiler/Hunsrück, Rheinland-Pfalz, Deutschland. They were married at Saint Leopold Church, Vienna, Austria, on 14 May 1785, and reportedly emigrated to the United States almost immediately afterward.

Johann and Maria supposedly had a son, Michael Dillman, widely reported to have been born in Ohio on 28 December 1810. Have you done the math? If Michael was actually Maria’s son, she would have been over 50 years old when she gave birth. While there have been modern examples of women having babies rather late, it seems absurdly unlikely that it could have happened in 1810, given the state of medical care at that time. To further highlight this, Michael supposedly has two sisters, Catherine and Christena, born in 1801 and 1812 respectively. It’s much more likely that these three were siblings than that any of them were children of Johann and Maria. And it’s likely there’s a missing generation in there somewhere. More research is needed.

The Same-Name Problem

Timelines are especially useful for the single most common identity problem in genealogy: two men of the same name, in the same county, in the same decade. Rather than trying to decide record by record which “John Dillman” a given document belongs to, the more reliable approach is to build two separate timelines and let each one accumulate its own internally consistent set of events — land purchases, children’s births, a specific neighbor’s name showing up repeatedly.^[3] A record that fits smoothly into one timeline and creates an impossible overlap in the other has just answered its own question. This works well alongside the FAN Club method discussed earlier in this series — the same witnesses, neighbors, and associates who help solve an identity problem on their own terms also tend to cluster consistently within one timeline and not the other.

When Two Records Disagree

The Genealogical Proof Standard’s fourth element requires that conflicting evidence actually be resolved, not just noted and left. A timeline is where that resolution usually starts. Take a common case: a death certificate gives one death date, and the tombstone gives another. A death certificate is typically completed within days of the death, often by someone who was present or notified immediately. A tombstone, by contrast, may not have been carved until months or years later, based on a family member’s recollection rather than firsthand knowledge at the time.^[4] Neither source is automatically right, but understanding how and when each one was created — exactly the source and information classifications discussed in earlier articles in this series — usually points toward which is more likely accurate, or at least explains why they disagree.

Most contradictions in genealogical records aren’t sinister. They’re structural — someone’s memory, a border that shifted without anyone moving, a name that changed with a remarriage or a new language.

That distinction matters. A conflict explained by a border redrawing a town’s country, or a woman’s name changing at remarriage, isn’t an error to fix — it’s a real historical transition the timeline just made visible.

Building One

A useful timeline doesn’t need special software (most genealogical software already includes a built-in tool to generate a timeline for any individual in your database, which is worth checking before building one by hand). A spreadsheet with columns for date, event, location, source, and a notes field for anything that seems inconsistent is enough. A few habits make the difference between a timeline that’s genuinely useful and one that’s just a list:

• Build one timeline per individual, not one for an entire family tree at once — the goal is to see one person’s life clearly, not to compress everyone into a single crowded page.
• Cite the source for every entry, right in the timeline, not in a separate document you’ll have to cross-reference later.
• Include approximate dates and ranges rather than omitting an event because the exact date isn’t known — a rough placement is still more useful than a gap.
• Add relevant historical context alongside the personal events — a war, a famine, a currency collapse, a border change — since these often explain a family’s decisions better than any single record does on its own.

For Dillman Researchers

Several fields already documented in the DFA’s Family Group Sheets are effectively timeline material waiting to be assembled: Date of Immigration, Geographic Coverage, and Subsequent Migration Events all record dated, sequential facts about a single family. Laying these fields out chronologically for a specific ancestor — rather than reading them as separate fields on a form — is often the fastest way to notice whether a family’s documented movements actually add up, or whether a gap or overlap in the record deserves a closer look before it’s repeated in a future article or accepted into someone else’s family tree.

A timeline won’t generate new records. It will tell you, clearly and quickly, which records you still need — and that is most of what a research plan actually is.

Sources

1. “Applying the GPS to Your Research,” Lineages.com (accessed July 2026).
2. “How (and Why) to Make a Genealogy Timeline,” Family Tree Magazine (accessed July 2026).
3. “Same-Name Ancestors, Part 1: The Time Method,” Ancestral Findings (accessed July 2026).
4. “How Historians Deal with Conflicting Historical Evidence,” Genealogy Foundation (accessed July 2026).

AI Disclosure: This article was researched and written with the assistance of Claude, an AI assistant developed by Anthropic. General claims about timeline research are drawn from the sources cited above; DFA-specific claims are drawn from the association’s own Family Group Sheet Database and prior published articles.

Notes

1. References to the DFA’s Family Group Sheets database, including its Date of Immigration, Geographic Coverage, and Subsequent Migration Events fields and the Group 5 lineage discussed above, are drawn from the Dillman Family Association, Family Group Sheet Database, compiled 2026.