National Proofreading Day: Your Family Tree Is Lying to You (And You Probably Helped)

National Proofreading Day: Every March 8th, the world observes National Proofreading Day. Most people shrug, maybe glance at a work email, and move on with their lives. Genealogists, however, should be treating this day like a minor religious holiday—complete with ritual sacrifice of every unverified Ancestry hint they’ve ever accepted. I’m only half joking.

Save 24% on The Copyeditor’s Workbook:
Exercises and Tips for Honing Your Editorial Judgment

What Is National Proofreading Day?

National Proofreading Day was created to honor Judy Beaver, born March 8, 1947, whose passion for correct written language was legendary. The holiday exists to remind us that words matter—that the difference between “public” and “pubic” in a legal document is, shall we say, significant.

In genealogy, the stakes are even higher. We’re not editing a marketing brochure. We’re reconstructing human lives from fragmentary evidence, and a single misread letter can send you chasing the wrong family for years. I’ve seen it happen. I’ve watched otherwise sharp researchers disappear down rabbit holes because a census enumerator in 1880 wrote a “K” that looked like an “R,” and nobody bothered to look at the original image before copying the indexed name into their tree.

The Genealogy Proofreading Disaster Hall of Fame

Let’s talk about the greatest hits of family tree errors, because if I’m going to make this point, I’m going to make it with receipts.

• The Surname Scramble. Indexers on major platforms—Ancestry, FamilySearch, FindMyPast, all of them—are doing heroic work, but they’re human (and sometimes algorithm). “Kowalski” becomes “Kowalzki.” “Wojciechowski” becomes a cry for help. If your ancestor had an unusual surname, treat every indexed result like a suspect in a lineup: don’t trust it until you’ve verified it against the original document.

• The Transposed Date. Your great-grandmother was born in 1892 and married in 1889? Congratulations, you’ve discovered time travel—or more likely, someone transposed two digits and you’ve been calculating wrong ages for three generations. Transcription mistakes in dates are insidious because they cascade. Wrong birth year means wrong age on every subsequent record. Wrong marriage date means wrong children’s ages. One bad number, infinite bad math.

• Aunt Mildred’s “Research.” You know who I’m talking about. Every family has one. She handed you forty pages of handwritten notes at the last reunion, beaming with pride, and none of it—none of it—has a source citation. Just names and dates hanging in the air like genealogical ghosts. And the worst part? People upload this stuff directly to shared trees without verifying a single claim. It spreads like a rumor at a church potluck.

• The Place Name Problem. Your ancestor was born in “Prussia.” Cool. That narrows it down to about 200,000 square miles that no longer exists as a political entity. Or someone recorded the county seat instead of the actual township, and now you’re searching the wrong set of records entirely. Botched place names in genealogy aren’t just inconvenient—they’re research dead ends dressed up as answers.

Genealogy Proofreading Tips That Will Actually Help

Here’s the thing about genealogy research tips for proofreading: they’re not about grammar. They’re about verification. There’s a difference.

• Always view the original image. The index is a finding aid, not a source. If a platform gives you access to the original document, use it. Every single time. The indexed version of your ancestor’s name is one human’s best guess under time pressure. The original is the truth—or at least as close to it as you’re going to get.

• Cross-reference dates across multiple records. A birth year that shows up consistently across a census record, a death certificate, and a marriage license is probably right. A birth year that appears in exactly one place and conflicts with everything else is a red flag. Genealogy proofreading means triangulating, not accepting.

• Read your own work out loud before you publish. Before you share that family tree or upload that GEDCOM, sit with it. Read the notes you’ve written. You will catch errors you’ve been staring past for months. Your brain autocorrects silently; your mouth doesn’t lie as easily.

• Be skeptical of shared trees. Someone else’s tree is not a source. It’s a hypothesis. Treat it accordingly.

The Part Where I Get Serious for Exactly One Paragraph

Bad genealogical data doesn’t just affect your research. It pollutes shared databases for everyone who comes after you. When you upload an unverified, error-riddled tree to a platform that serves millions of users, you’re not just making a personal mistake—you’re becoming part of someone else’s problem for the next decade. The genealogy community is only as good as the data we collectively contribute. On National Proofreading Day, that’s worth remembering.

Now Go Verify Something

March 8th is your annual permission slip to be the picky, detail-obsessed researcher you know you should be every day but sometimes aren’t. Pull up a record you’ve been meaning to double-check. Compare that indexed name against the original image. Question Aunt Mildred’s notes. Verify the date.

Your ancestors went to the trouble of being born, living actual lives, and leaving documentary evidence behind. The least we can do is read it carefully.

* * *

Author’s Note: I want to be transparent that this content – National Proofreading Day: Your Family Tree Is Lying to You (And You Probably Helped) – was created in part with the help of an artificial intelligence (AI) language model – Claude Sonnet 5.4. The AI assisted in generating an early draft of the content, but every paragraph was subsequently reviewed, edited, and refined by me. The final content is the result of extensive human curation and creativity. I am proud to present this work and assure readers that while AI was a tool in the process, the story, style, and substance have been carefully shaped by the author.