How to Create a Genealogy Research Log (With a Simple Template)
Create a research log that records questions, searches, results, source references, and next steps without slowing your genealogy down.
A genealogy research log records what you looked for, where and how you looked, what you found, and what to try next. Its greatest value is not administrative neatness: it prevents repeated searches, preserves negative results, and lets you compare evidence across sessions.
Start with a question, not a surname
Create a separate log or filtered view for a specific objective. “Find Sarah Kelly” is too broad. Try: “Identify the parents of Sarah Kelly, who married Thomas Quayle in Peel on 14 May 1884.”
At the top, record known facts with citations, distinguishing proved facts from family information or working assumptions. Add criteria that would identify the correct person—spouse, occupation, age, address, witnesses, children, or religion.
A simple research log template
Use these columns in a spreadsheet, database, or notebook:
| Field | What to record |
|---|---|
| Date | When the search was performed |
| Objective | The question this search addresses |
| Repository or website | Archive, library, database, book, or person consulted |
| Collection and coverage | Exact collection title plus place and date range |
| Search terms and filters | Names, variants, dates, places, record type, browse path |
| Result | Match, possible match, no result, or access problem |
| Source reference | Call number, reference, volume/page/image, stable URL |
| Analysis | Why the result matters and how reliable it appears |
| File or citation link | Where the captured record and citation live |
| Next action | One concrete follow-up |
Copyable header:
Date | Objective | Repository | Collection/Coverage | Search/Filters | Result | Reference | Analysis | File | Next Action
Record the scope of negative searches
“Nothing found” is almost useless. Record exactly what was searched:
13 Aug 2026 — FamilySearch, Isle of Man civil marriages, 1880–1888. Exact surname Kelly plus given Sarah; then variants Sara and Sally; place Peel. No candidate with spouse Quayle. Images for 1884 volume not browsed.
This tells you what a negative result does and does not mean. The index might omit a record, the name may be mistranscribed, the event may be outside the stated place, or the relevant images may require separate browsing.
Capture searches as you work
Keep the log open beside the record site. Create a row before opening many results, then update it. Do not rely on browser history: it does not capture filters, browse paths, image numbers, findings, or why a candidate was rejected.
For a long browse session, one row can cover a defined range such as “Parish register volume 4, pages 1–120,” with notes for relevant entries. Avoid one row for an entire website.
Link the log to evidence
When you find a record, save the full image where permitted, create the citation, transcribe relevant text, and link all three back to the log. A search result is not the same as a source: record enough information to locate and evaluate the underlying item.
For physical archives, record the repository, collection, series, box, folder, volume, and page or item number. Note photography restrictions and whether you checked adjacent material.
Analyse immediately, briefly
Write two or three sentences while the result is fresh:
- Which identity details agree?
- Which conflict?
- Is this an original record or a derivative index?
- Who supplied the information and when?
- What claim does it support?
- What new question follows?
This turns a list of links into research reasoning.
Use status and confidence carefully
Simple labels can help:
- Relevant: directly bears on the objective.
- Candidate: plausible but identity not proved.
- Excluded: not the person, with the reason retained.
- Negative: defined search produced no relevant result.
- Blocked: unavailable, restricted, or awaiting a visit.
Do not use a confidence score as a substitute for explanation. “High” means little without stating which evidence agrees and what remains unresolved.
End every session with a next action
Write a task that can be started without reconstructing your thinking: “Browse Peel marriage register images for May 1884 and capture witnesses,” not “Look more.” If there are several paths, order them by likely value and cost.
Review the log periodically. Repeated place names may suggest a map; recurring witnesses may reveal a relationship; several negative index searches may justify browsing original volumes.
Example row
| Date | Objective | Repository | Collection/Coverage | Search/Filters | Result | Reference | Analysis | Next Action |
|---|---|---|---|---|---|---|---|---|
| 2026-08-13 | Identify Sarah Kelly’s parents | Manx National Heritage | Peel parish marriages, 1884 | Browse May entries | Match | Vol. 7, p. 42 | Father named John Kelly; witness Margaret Kelly may be sister | Find Margaret in 1881 census with Sarah |
Common logging mistakes
- Recording only successful finds.
- Pasting a URL that depends on a temporary session.
- Omitting collection coverage and filters.
- Mixing several unrelated objectives in one row.
- Writing conclusions without linking the record.
- Keeping the log so elaborate that it is never used.
Start with the ten fields above and remove any you consistently do not need. A complete modest log is better than an ideal template abandoned after one evening.