How to Use the Genealogy Research Log and Proof Summary Prompt to Resolve Conflicting Ancestor Records

Every family historian eventually meets an ancestor whose records disagree. A death certificate says one birth year, a census says another, and an old parish book in the home country says something else. Online trees usually pick one answer and copy it forever. The Genealogy Research Log and Proof Summary: Genealogical Proof Standard Analysis, Evidence Explained Style Citations, and GEDCOM Ready Source Records for a Conflicting Ancestor prompt helps you do what professional genealogists do instead: log every search, analyze each source for who supplied the information and how close they were to the event, weigh the conflict openly, and write a short proof summary that explains your conclusion. It also formats citations and source records you can paste into your tree software.

What the prompt produces

1. A research log table listing every search with repository, collection, terms, and result, including searches that found nothing.
2. Source analysis that classifies each record as an original, derivative, or authored source, the information as primary or secondary, and the evidence as direct, indirect, or negative.
3. A conflict table that lines up each competing value with its supporting records and the weight each deserves.
4. A proof summary or proof argument that states a conclusion and explains why, or says the question is not yet proven and names the next records to search.
5. Citations in a layered style that move from the specific entry out to the collection and repository.
6. GEDCOM ready source entries with source records, page details, and a quality value for each fact.

How to fill the inputs

ResearchQuestion should be one clear sentence naming the person, the fact you want, and the place and time. A focused question keeps the analysis focused too.

RecordsFound lists each record with where you found it, the collection, any image or film number, and the exact wording of the entry. Quote the record rather than summarizing it, because small details such as an age or an informant name matter.

NegativeSearches records places you looked and found nothing. A missing record can be evidence, and it shows a reviewer how thorough you were.

KnownContext includes relatives, neighbors, and migration details that help confirm you have the right person.

TreeSoftware names your program and the GEDCOM version it exports, so the source records match what your software expects.

Reading the example output

The example works on a Swedish immigrant whose birth year appears as both 1868 and 1871:

• The log includes a nil search. The state birth index was checked and had no entry, which is expected for someone born abroad.
• Each source is weighed by its informant. The death certificate came from a son decades later, so its birth date is secondary information. The parish household roll was kept close to the event.
• The conflict is laid out openly. Two sources support 1871 and two lean toward 1868, and the table explains why the parish record carries more weight.
• The conclusion names a next step. Viewing the original parish birth register would confirm the answer.
• Citations and source records are ready. They can be pasted into a tree program and exported cleanly.

Tips for better results

• Record nil searches as you go. They are easy to forget and hard to reconstruct later.
• Note who gave the information for each record. The informant is often the key to resolving a conflict.
• Look for records in the home country. Parish books and household rolls often settle questions American records cannot.
• Keep one research question per session. Mixing questions makes the analysis muddy.

Mistakes to avoid

• Do not treat other people's online trees as evidence. Use them only as leads.
• Do not discard a record because it disagrees with your favorite answer. Explain the conflict instead.
• Do not invent film numbers or page references. Leave a placeholder until you have the real value.
• Do not call a conclusion proven while important records remain unsearched.

Who it is for

Family historians working on a stubborn ancestor, genealogy society volunteers who help members, people preparing a lineage society application, and anyone who wants their tree to hold up when a cousin asks how they know.

Related PromptDig links

Start with the Genealogy Research Log and Proof Summary: Genealogical Proof Standard Analysis, Evidence Explained Style Citations, and GEDCOM Ready Source Records for a Conflicting Ancestor prompt and paste your records with their exact wording. To find more prompts for hobbies and research projects, Browse more prompts. If you have a research workflow prompt others could use, Share a prompt.