Documenting Genealogy Research Sources

Why Source Documentation Matters in Professional Genealogy

Documentation turns research into a professional deliverable instead of a private notebook only you can interpret.

Clients hire genealogists when answers matter—legal heirship, immigrant origins, identity of biological parents, or preserving family history for the next generation. They need more than a name attached to a tree icon. They need to know:

• Which records support each relationship or event
• Whether the evidence is direct or circumstantial
• What was searched and not found
• Where conflicts remain unresolved

Without source documentation, you cannot demonstrate diligence. With it, you can show that conclusions follow from evidence—even when the answer is "not proven from available records."

Sources, Information, Evidence, and Conclusions

Professional documentation distinguishes what you looked at from what you concluded—four layers that amateur trees often collapse into one.

A death certificate is a source. The named parents on it are information. Whether that parentage claim resolves your research question is an evidence judgment—the informant may have been wrong. Your statement that parents are "likely X and Y but not proven" is a conclusion. Client reports read clearly when each layer is handled explicitly rather than implied.

What to Document for Every Source

Use a repeatable capture checklist so no project depends on memory.

• Research question or person the source relates to
• Source creator and record type (census, probate, baptism register, etc.)
• Title or description of the specific item
• Repository or website where it was accessed
• Collection name, film number, call number, or database identifier
• Item-level locator—page, entry number, image number, URL path
• Date accessed (especially for online collections)
• Transcription, abstract, or image copy stored with citation ID
• Reliability notes—original vs derivative, informant, conflicts
• Link to research log entry for the search that produced it

Not every field applies to every record—a tombstone photograph differs from a database index entry. Your standard should require every applicable field, not every possible field on a rigid form that researchers skip under time pressure.

Research Logs and Research Notes

The research log is the chronological record of what you did—not only what you found.

A useful log entry typically includes:

• Date of search
• Research objective or sub-question
• Repository or website
• Collection or database searched
• Search parameters—names, dates, places, filters
• Result summary—matches found, no match, partial lead
• Citation IDs or links to sources saved
• Next action suggested

Research notes differ slightly: they analyze what a source means—conflicts, identity problems, handwriting difficulties, translation issues. Logs track activity; notes track interpretation. Both belong in the project file; clients may receive edited versions in the report appendix depending on your deliverable agreement.

Citation Standards and Formats

Consistency matters more than memorizing every punctuation rule—pick a standard, apply it on every project, and verify client-specific requirements when they exist.

Genealogical citation guides emphasize identifying sources so they can be found again—whether the record is an original manuscript in a county archive, a microfilm publication, or an online image behind a paywall. Academic citation styles alone often omit locators genealogists need.

Choose one approach for your business:

• Follow a genealogical citation manual your clients and partners recognize
• Use template fields in your software and export consistently
• Document your house style in an internal one-page guide for subcontractors

Verify requirements when a client submits work to a lineage society, court, or institution—some specify format or evidence standards you must meet before delivery.

Online sources need access dates because URLs, indexes, and image sets change. Derivative sources—indexes, transcripts—should identify both the derivative and the original when possible.

Footnotes, endnotes, or source lists

Client reports typically use one of two presentation patterns:

• Inline or footnote citations — each factual statement links immediately to a source; best when clients read sequentially and question specific claims.
• Narrative with source list — report body references citation numbers or keys; full citations appear in an appendix; best when clients want a readable story with a separate reference section.

Choose one pattern per project and state it in your deliverable description. Switching mid-report confuses clients and breaks automated citation tools.

Evaluating and Documenting Source Quality

Finding a record is not the same as trusting it. Evaluation notes belong in documentation, not only in your head.

Questions to document when assessing a source:

• Is this an original record or a copy, abstract, or index?
• Who created it and for what purpose?
• Did the informant likely have firsthand knowledge?
• Was information recorded near the time of the event?
• Does the record contradict other sources?
• Could identity confusion explain the match?

Client reports gain trust when you write "the informant was the deceased's second wife, who may not have known exact birth date" rather than silently treating every certificate field as fact.

Documenting Negative and Inconclusive Searches

What you did not find—and where you looked—proves diligence as much as a successful match.

Negative searches belong in the research log and may be summarized in the client report's limitations section. Document:

• Which collections were searched thoroughly
• Variant name spellings attempted
• Geographic and date filters used
• Why a promising index hit was ruled out
• Repositories not searched—and whether that was in or out of scope

Inconclusive results differ from negative ones: you found candidates but cannot prove which applies. Document why each candidate fails or remains open. "No parents identified" is honest; "parents not found because I didn't search church records" is a scope failure clients should not discover later.

Organizing Source Files and Record Copies

Digital chaos becomes client confusion. File organization is part of documentation, not optional filing.

Practical organization principles:

• One project folder per client engagement with subfolders for images, reports, and admin
• File names that include citation ID, surname, record type, and year
• Matching IDs between log, citation list, and image filenames
• Version control when reports or transcriptions are revised
• Backup routine separate from your working copy

When delivering record copies, verify repository terms, copyright restrictions, and client agreement scope. Some archives permit research use and client sharing; others restrict reproduction. When rules are unclear, verify with the repository or qualified counsel rather than assuming online availability equals unrestricted redistribution.

Privacy also matters: living people, adoption details, and sensitive findings may require redaction or separate handling—confirm expectations at intake and document your delivery choices.

Example folder structure (model)

Adapt depth to project size—a record retrieval may need only admin, source, and delivery folders. A multi-generation report needs the full structure.

Connecting Documentation to Client Deliverables

Documentation standards should match what the client purchased—not every project needs a 40-page appendix.

Define documentation depth in your scope proposal. Under-documented deliverables generate revision requests; over-delivering raw logs without explanation overwhelms non-expert clients. Edit research logs for client-facing appendices when needed—while retaining the full working log in your project archive.

Pre-delivery documentation checklist

• Every genealogical assertion in the report has a citation
• Conflicting sources are described, not hidden
• Limitations and negative searches are stated honestly
• Record copies match citation IDs in the report
• Living-person and privacy handling matches intake agreement
• Repository reproduction rules were verified for delivered images
• Research log is complete through final search session

Documentation Workflow During a Project

Document as you research—not the night before delivery when citations become reconstruction exercises.

1. Intake — record client-supplied sources and prior research with citations where provided
2. Plan — list intended repositories and record types in the log
3. Search — log each session with parameters and results
4. Capture — save images, assign citation ID, transcribe or abstract
5. Evaluate — write brief reliability notes on significant finds
6. Analyze — link evidence to research questions in working notes
7. Draft report — embed citations; flag conflicts and gaps
8. Quality check — verify every conclusion traces to a citation
9. Deliver — send agreed report and file set; archive working project

Practical takeaway: Never close a research session without updating the log. Even fifteen minutes of documentation at session end saves hours of reconstruction later—and protects billable time already spent.

Common Documentation Mistakes

Most documentation failures are workflow failures, not skill gaps.

• Citing only database names — include collection and item locators, not "Ancestry."
• Deferring citations to the end — reconstructing sources wastes time and invites errors.
• Omitting negative searches — clients cannot see diligence you did not record.
• Treating indexes as originals — note derivative status; pursue originals when scope allows.
• Overclaiming in reports — document uncertainty; do not upgrade guesses to proof.
• Inconsistent file names — breaks the link between report and images.
• Sharing restricted records — verify reproduction rights before delivery.
• Discarding working logs — archives support follow-up work and disputes.
• Copying client trees as sources — undocumented trees are leads, not evidence.
• Skipping evaluation notes — conclusions look arbitrary without them.

Building a Documentation System for Your Business

A documentation system is repeatable templates, naming rules, and habits—not perfection on one project and chaos on the next.

Start with:

1. A one-page citation and file-naming standard
2. A research log template—spreadsheet or software field set
3. A report template with citation placeholders
4. A project folder structure copied for each new client
5. A pre-delivery checklist: every claim cited, conflicts addressed, scope limits stated

Run one practice project using the full system before your first paying client. Time how long documentation takes and build that time into quotes—you already account for research hours; documentation hours should not be invisible.

Source documentation connects to every other part of a professional practice: scoped packages, intake, reporting, and client trust. When you embed these habits early in starting a genealogy business, deliverables hold up under scrutiny instead of relying on reputation alone.