Same Name, Different Man: Separating Soldiers Who Share a Name
Finding a service record with your ancestor's name is the start of the work, not the end. Common names repeat across towns and counties, cousins were named for the same grandfather, and record-keepers spelled freely. Lineage reviewers check this, so plan to prove it before you submit.
How often this goes wrong
A DAR staff genealogist describes sorting six men named Thomas Gillespie in South Carolina.[1] In the end only four of them had properly sourced service.[1] DAR names multiple people of the same name in an area as a common reason to re-examine a patriot's service.[1] It also checks whether another ancestor of the same name has been established since, to make sure there are two distinct people.[1] SAR presenters list weak parent-to-child proof, including unresolved naming conflicts, among the most common reasons applications are pended.[2]
How the federal files handle same-name veterans
The pension files are arranged by surname. When two or more veterans share a surname and given name, the files are further arranged by the state or organization each man served for.[3] Cross-reference cards also exist for variant spellings.[3] So search every spelling, then open every same-name file for the state, not just the first.
The disambiguation checklist
Work through these for each candidate record. Every "no" is a reason the record may belong to someone else.
| Test | What to compare | Why it matters |
|---|---|---|
| Residence vs. service | Where he lived and where the service was performed | A residence and service location that do not match is a standard DAR review trigger[1] |
| Distance | Towns, not just counties | DAR's example: two Middlesex County towns nearly 45 miles apart pointed to two men, not one[1] |
| Alive at the time | Death date vs. service date | DAR adds a service date for patriots who died during the war, to show he was alive then[1] |
| Right age | Birth range vs. service | SAR wants the patriot's generation to show he was alive, of the right age, and resident where the service was claimed[2] |
| Same household over time | Age brackets across censuses | Census brackets help track one head of household among same-name men[4] |
| Same place, several records | Census, deed and court order in one county | NSCDA: three such records in the same county MAY be enough to show one man[5] |
| Unit and officers | Names of officers and companies in each record | A pension application normally states rank, unit and period of service[3] |
| Witnesses and neighbors | Who swore affidavits, who appears on deeds | Compare each witness against known kin and neighbors |
Watch for these traps
- Cousins with identical names. NSCDA's own example is two cousins named Cadwalader Jones, each the son of a different father, in a county whose records burned.[5]
- Service in another state. In NARA's Daniel Ide example, the key pension file belonged to a man who served from Massachusetts though the family lived in Vermont, and was easy to pass over for that reason.[6]
- A record that only matches on name. A name match with no supporting place, age or kin detail is a lead, not proof. Log it as indirect.
- Spelling variants. Check the variant-spelling cross-references before deciding a man has no file.[3]
Build a conflict log
For each candidate man, keep one line per record: the record, the place, the date, the age it implies, and the people it names. Then:
- Group records that agree on place, age and kin into "Man A", "Man B" and so on.
- Mark any record that fits more than one man as unresolved.
- Only attach service to your ancestor when it sits in the same group as a record that ties him to your line.
The Lineage Evidence Matrix has a conflict flag for exactly this. A flagged cell keeps its conflict label until you clear the flag.
Related guides: How to Read a Pension File, The Patriot Lineage Proof Roadmap.
What to do next
- List the records you have for each generation in the free Lineage Evidence Matrix. It gives you a to-do list of what is missing, where to look, and a plan you can print.
- Check your patriot's service dates with the free Service Window Checker.
- Find a local chapter. DAR's Chapter Locator finds DAR chapters in your area.[7] For SAR, your sponsor is often the local chapter registrar; pick your state on SAR's contact page.[8]
- Start the application with that person's help: a DAR member, or your SAR sponsor, helps guide you through it.[9][8]
Sources
- Today's DAR (DAR staff genealogist) — Why Was His Service Removed? (Feb 26, 2021). Retrieved 2026-10-31. https://blog.dar.org/2021/02/26/why-was-his-service-removed
- SAR presentation, OHSSAR Annual Meeting (May 5, 2023) — How to Produce Approval-Ready Applications. Retrieved 2026-10-31. https://cincinnatisar.org/wp-content/uploads/2023/05/Presentation-How-to-Produce-Approval-Ready-Applications-and-Reduce-Turnaround-Time.pdf
- NARA M804 descriptive pamphlet — Revolutionary War Pension and Bounty-Land-Warrant Application Files. Retrieved 2026-10-31. https://www.archives.gov/files/research/military/army/dc/m804.pdf
- NARA — Clues in Census Records, 1790-1840. Retrieved 2026-10-31. https://www.archives.gov/research/census/1790-1840.html
- NSCDA (South Carolina) — Standards of Proof (rev. 7/14/2025). Retrieved 2026-10-31. https://nscdasnc.memberclicks.net/assets/membership/Standards%20of%20Proof%202025.pdf
- NARA Prologue (Summer 2015) — Using Revolutionary War Pension Files to Find Family Information. Retrieved 2026-10-31. https://www.archives.gov/publications/prologue/2015/summer/rev-war-pensions.html
- DAR — Chapter Locator. Retrieved 2026-10-31. https://www.dar.org/discover/become-member/chapter-locator
- SAR — Apply in 4 Easy Steps. Retrieved 2026-10-31. https://www.sar.org/how-to-apply/
- DAR — How to Join. Retrieved 2026-10-31. https://www.dar.org/discover/become-member/how-join