How to Write a Family History
Most family histories are never written, and the reason is almost always the same: the scope was too big. "The whole family, all the way back" is a project without an ending, and it stalls at the point where research feels endless and writing feels premature. The histories that get finished start small โ one ancestor, one branch, or one generation โ and treat the writing as a way of finding the gaps rather than something you do once the research is complete. This page covers choosing a scope, structuring a narrative, handling missing information and difficult truths, and actually getting a draft down. A visual companion helps enormously, so the printable family tree is worth having beside you.
How Do You Choose a Scope You'll Actually Finish?
The single most useful decision, and it's about subtraction.
Narrow projects that work:
| Scope | Rough length | Time |
|---|---|---|
| One ancestor's life | 3,000โ10,000 words | Weeks |
| One event โ a migration, a war, a business | 2,000โ6,000 words | Weeks |
| One generation โ your four grandparents | 10,000โ20,000 words | Months |
| One surname line, four or five generations | 15,000โ30,000 words | Months |
| One family across two countries | 20,000โ40,000 words | A year or more |
Why "everything" fails: every ancestor has two parents, so scope doubles every generation back. Ten generations is over a thousand people. There's no natural stopping point, no shape to the narrative, and no moment when it feels ready to write.
Pick the story, not the family. Ask what you'd tell someone at a dinner table โ the ancestor who emigrated with nothing, the great-aunt who ran a business when women rarely did, the branch that vanished. That's your subject.
Start where the evidence is richest. A relative with letters, photographs and living memory makes a far better first project than one who exists only as a name in a register.
Write the small thing first. A finished 4,000-word account of one grandmother is worth more than four abandoned chapters of a comprehensive history โ and it teaches you the process cheaply.
What Should You Gather Before Writing?
Enough, not everything. Writing reveals the gaps far more efficiently than research does.
Documents: birth, marriage and death records; census returns; military service; immigration and naturalisation; wills and probate; land and property. Most are covered across the records guides on this site, and trace family tree free is a sensible starting point.
Living memory, which is the material that disappears. Interview older relatives before anything else โ how to interview a relative covers doing it properly. Every family historian has a story about the relative they meant to record.
Photographs, with whatever identification you can still get. How to preserve old family photos covers handling and storage.
Objects and papers: letters, diaries, family bibles, certificates, recipe books, employment records.
Historical context, which is what turns a list of dates into a story. What was happening in that town, that industry, that year? Local newspapers, parish histories and social histories fill in the world your ancestors moved through.
Keep track of sources as you go. Retrofitting citations to a finished draft is miserable, and unsourced claims are the thing that makes a family history unusable to whoever comes next. A simple consistent note โ what the record was, where you found it, and when โ is enough.
How Should You Structure It?
Four approaches, each suiting different material.
Chronological โ earliest ancestor forward. The default, easy to follow, and it can read as a list if you're not careful. Best when the story has genuine forward momentum, like a migration.
Reverse chronological โ from yourself backwards. Readers meet familiar people first, which is more engaging for a family audience, and each generation raises a question the next chapter answers.
By branch โ one surname line at a time. Cleanest structure when you're covering several families, though it repeats shared events.
Thematic โ chapters on work, migration, war, faith, houses. The most readable option and the hardest to organize. Works well when the same patterns recur across generations.
A structure that works for most first projects:
- Introduction โ who this is about, why you wrote it, what you used
- Setting the scene โ the place and period
- The main narrative โ three to eight chapters
- What's still unknown โ a genuinely valuable chapter
- Sources and how to continue โ for whoever picks it up next
- Appendices โ the tree, transcriptions, document images
Chapter length: 1,500 to 3,000 words is comfortable. Longer and it becomes hard going for family readers, which is who this is for.
How Do You Write It So People Read It?
The failure mode of family history writing is the genealogical report โ accurate, exhaustive, unreadable.
Lead with people, not dates. "Mary Hutchings was nineteen when she boarded the ship, and she never saw her mother again" beats "Mary Hutchings (b. 1848) emigrated in 1867."
Put the dates in but don't lead with them. They belong in the sentence, not at the front of it.
Use context to explain choices. Why did they leave? What was the town like? What did that job actually involve? A paragraph on the local mill closing explains a move better than the move itself does.
Quote directly from letters, wills, newspapers and interviews. A single line in an ancestor's own words is worth pages of paraphrase.
Include the ordinary. What they ate, what a day cost, how many rooms the house had. Readers remember detail, not lineage.
Write in your own voice. You aren't producing an academic paper. Warm and plain reads better than formal, and it's what family members will actually finish.
Be honest about uncertainty. "Probably", "the records suggest", "we don't know" are all fine. Inventing bridges between facts is the one thing that destroys a family history's value.
Read a paragraph aloud. If you run out of breath or lose interest, so will everyone else.
How Do You Handle Gaps and Difficult Truths?
Every family history has both, and how you handle them is what separates a good one from a defensive one.
Gaps. Say so plainly. "We don't know what happened to Thomas after 1871" is a legitimate and interesting sentence. Distinguish clearly between what a record shows, what you've inferred, and what family tradition claims โ and mark speculation as speculation. A chapter of open questions is a gift to the next researcher, and it's often the part relatives find most engaging.
Family stories that don't check out. Include them as stories. "The family has always said we're descended from a Huguenot weaver; I've found no evidence, and here's what I did find" is more interesting than either repeating the myth or silently dropping it.
Difficult material โ illegitimacy, crime, poverty, institutions, addiction, abuse, or an ancestor on the wrong side of history. Some principles that help:
- Context, not judgment. Explain the circumstances of the time rather than condemning or excusing
- Consider the living. Recent events involving people still alive need care and, often, consent. Older material is generally fair to include
- Leave things out deliberately if publishing would hurt someone living โ but note that you've done so
- Don't sanitize the distant past. Poverty, illegitimacy and hardship are the ordinary texture of most family histories, and removing them leaves a story nobody recognises
DNA surprises deserve particular care. Unexpected parentage is common enough that most large family projects encounter it, and it affects living people directly. Think hard about who has a right to know, who wants to know, and whether it belongs in a document circulated at Christmas.
The general rule: write for a reader in fifty years, who will value honesty and context far more than tidiness.
What Tools and Formats Should You Use?
Nothing exotic is needed, and the choices that matter are about longevity rather than features.
Write in something plain. A word processor is fine. What matters is that the file opens in twenty years, so save in a common format and keep a plain-text or PDF copy alongside anything proprietary. Genealogy software is excellent for data and poor for narrative โ write the prose separately.
Keep the research separate from the writing. One file, spreadsheet or database for facts and sources; another for the narrative. Mixing them produces a document that is neither.
Number your images and documents and reference them in the text, so a photograph can be matched to the passage it belongs with even if the files get separated later.
Back it up in three places, one of them off-site or in the cloud. Family histories are lost to failed hard drives with depressing regularity, usually about eighteen months of work in.
Keep a research log โ what you searched, where, and what you found or didn't. It stops you repeating searches, and it tells the next researcher which avenues are already exhausted.
Decide early how you'll number people. Even a simple convention โ a generation number, or the standard genealogical numbering systems โ prevents confusion when three men in a row are called James.
Don't over-engineer it. Plenty of excellent family histories were written in a single document with photographs pasted in. The tools are not what makes it good.
How Do You Actually Get It Done?
Set a deadline and a length. Open-ended projects don't finish. "Six thousand words by my mother's birthday" works.
Write badly first. The first draft exists to be revised. Research feels productive and is often avoidance โ you can always add a detail later.
Write the easiest chapter first, not the first chapter. Momentum matters more than order.
Leave markers for gaps โ a bracketed note โ and keep going rather than stopping to research.
Write regularly rather than in bursts. Five hundred words a week is a book in a year.
Show a draft to a family member who isn't interested in genealogy. They'll tell you exactly where it becomes boring.
Then produce it properly. Even a spiral-bound copy for each family member gives the project a real ending and gets it out of your computer, which is the only way it survives โ see how to create a family history book.
Frequently Asked Questions
How do I start writing a family history?
Choose a narrow scope you can finish โ one ancestor, one generation, or one event โ rather than the whole family. Gather what you have, interview living relatives first, then write a rough draft and let it show you which gaps matter.
How long should a family history be?
A single ancestor's story works well at 3,000โ10,000 words; one generation at 10,000โ20,000. Chapters of 1,500โ3,000 words read comfortably. Length matters far less than finishing, and shorter finished histories are read more often than long unfinished ones.
How do I make a family history interesting to read?
Lead with people rather than dates, quote directly from letters and interviews, and include historical context and ordinary daily detail. Write in your own voice. Reading a paragraph aloud is the quickest test of whether it works.
What do I do about gaps in the research?
Say so openly. "We don't know" is a legitimate sentence, and a chapter of unanswered questions is genuinely useful to whoever researches next. Distinguish clearly between documented fact, inference and family tradition.
Should I include difficult family history?
Generally yes, with context rather than judgment, and with care where living people are involved. Poverty, illegitimacy and hardship are ordinary in most family histories, and removing them produces a version nobody recognises as true.
Do I need to cite sources in a family history?
Yes, and keep them as you go rather than adding them later. Unsourced claims can't be verified or built on, which makes the work far less useful to future family members. A simple consistent format is enough.
The family histories that get finished are the narrow ones. Pick a person or an episode, write it plainly, be honest about what you don't know, and put a copy in people's hands. You can always write the next one. Keep the relationships straight while you write with the printable family tree.




