You have a box of old photographs, a stack of handwritten letters, and a few recorded interviews that have been gathering on the kitchen table for months. The material is valuable, but without an organized index the family history book will be difficult for readers to navigate. An index lets you locate people, events, and dates quickly, turning a loose collection into a usable reference. The steps below guide you from defining the project’s boundaries to preserving the final digital master.
Define the scope
Begin by deciding which relatives, generations, and time periods will be included. Write down the earliest birth year and the latest death year you intend to cover, then list the families or branches that matter most. A clear scope prevents endless additions and helps you allocate space for each line. It also informs later decisions about structure and the amount of material you will need to gather.
If the family tree spans many branches, consider limiting the index to a core set of ancestors and their direct descendants. This focus keeps the project manageable and ensures that each entry receives sufficient detail.
Collect source material
Gather interviews, photographs, letters, certificates, and any other documents that relate to the people identified in the scope. Prioritize scanning items that contain names, dates, or locations, as these will become the backbone of the index. Use a high‑resolution scanner for paper items and save files in a lossless format such as TIFF or PNG. For audio or video recordings, create a transcript that captures who is speaking and the date of the recording.
Organize the digital files into folders named after the person or event they represent. A consistent naming convention—e.g., YYYY_MM_DD_PersonName_DocumentType—makes later searching easier and reduces the chance of duplicate files.
Choose a structure
Select a layout that matches the material you have collected. A chronological structure works well when dates are abundant and the narrative follows a timeline. A branch‑by‑branch approach suits families with distinct lineages, allowing each branch to have its own section. Thematic organization—grouping by topics such as military service, migration, or occupations—can highlight shared experiences across generations.
Map the chosen structure onto the index by creating top‑level headings that correspond to chapters or sections. Under each heading, list the relevant entries with page numbers or file references. This mapping ensures that the index mirrors the book’s flow and helps readers locate content without flipping through unrelated pages.
Select and caption photographs
Decide how many images will appear in each chapter based on the amount of narrative text. A useful rule of thumb is to include one photograph for every three to four pages of written material, balancing visual interest with readability. Choose images that illustrate key moments, relationships, or locations mentioned in the text.
Write concise captions that identify the subject, date, and context. Keep captions to a single sentence whenever possible, and place them directly beneath the image. Consistent caption formatting—such as italicized text followed by a period—creates a uniform look throughout the book.
Write connecting text
Draft brief paragraphs that link photographs, documents, and oral histories. The text should explain why each item is included and how it relates to the surrounding narrative. Use clear, factual language and avoid embellishment; the goal is to provide context, not to dramatize.
When a document contains a name or date that appears elsewhere, reference it in the text and note the corresponding page number. This cross‑referencing reinforces the index and helps readers see the connections between different sources.
Choose a print‑on‑demand service
Compare platforms such as Blurb, Mixbook, and Lulu for cost per page, binding options, and paper quality. Some services offer bulk discounts for larger runs, while others provide higher‑quality photo paper that better showcases images. Request sample swatches if available, and verify that the service supports the file formats you have prepared.
Calculate the total price by multiplying the per‑page cost by the number of pages, then adding any setup or shipping fees. Factor in the expected number of copies to determine whether a larger print run or a smaller, on‑demand approach is more economical.
Proof and distribute
First review the layout on screen, checking for missing pages, misaligned images, and correct page numbers. Then order a single proof copy to examine color fidelity, binding strength, and overall feel. Make any necessary adjustments before author the full run, as changes after printing can be costly.
Store the final digital master file in a secure, backed‑up location—such as an external hard drive and a cloud service. When distributing copies, keep a list of recipients and note any special requests for format, such as a larger print size for visually impaired readers.
Worth remembering: A well‑planned index begins with a clear scope, proceeds through systematic collection and organization of sources, and ends with careful proofing and secure storage of the master file. Following these steps ensures the family history book is both navigable and durable.
Common questions
What is the simplest way to start?
Start by writing down the earliest and latest dates you want to cover and listing the families or branches that matter most. This brief scope sheet gives you a concrete boundary and guides every later decision.
What mistakes should I avoid?
Avoid adding material that falls outside the defined scope, neglecting to scan documents that contain names or dates, and skipping the proof copy stage. Skipping these steps often leads to missing entries, poor image quality, and costly re‑prints.
How do I know when the project is finished?
The project is complete when the index lists every person, event, and document included in the book, the proof copy matches the intended layout, and the digital master file is safely backed up. At that point, additional changes would require a new edition.