Module 5 — Research Strategy and GPS Application

A step-by-step research strategy for finding a Puerto Rican ancestor in colonial military records, integrating military evidence with church and civil sources, and writing a GPS-compliant research conclusion.

Intermediate

Part of the Spanish Colonial Military Records course.

Learning Objectives

By the end of this module, you will:

Know how to build a profile of an ancestor before submitting a military record request
Apply the GPS Three-Layer Framework to evaluate military evidence
Know how to integrate filiación data with church and civil records to resolve conflicts
Write a GPS-compliant research conclusion that incorporates military evidence

5.1 Before You Request: Build Your Search Profile

A military record request is most productive when you have already gathered everything you know from other sources. Before contacting Segovia, AGPR, or any other repository, build a written profile of your ancestor using the following elements:

Name: Both surnames, in Spanish naming order (paternal + maternal). Note variant spellings you have encountered: Valentín/Ballentín, Mendez/Méndez, Rodriguez/Rodrigues. Include any nickname or alias noted in church records.

Approximate birth year and municipality: The naturaleza field in a filiación records the municipality. If you know the town from a baptism or marriage record, include it. If you know only the region, include that.

Approximate dates of military service: You do not need exact dates. Work from what you know: if your ancestor appeared in a marriage record dated 1820 as 28 years old, he was born roughly 1792 and would have been of militia age (roughly 16-50) from the 1810s through the 1840s. That gives you a search window.

Unit identification, if known: If any record mentions military service, note the unit name. Church records sometimes identify men as cabo de la compañía de… or soldado de milicias. Census-equivalent documents (padrones) sometimes note militia rank. Any unit identifier narrows the search at Segovia significantly.

Family members: Father’s name, mother’s maiden name, wife’s name. These names may appear in the filiación and provide confirmation when you find a record.

Racial/social classification: This determines whether to search white militia or Pardo Militia records. Church records record racial classification in baptismal and marriage entries using the same period vocabulary (blanco, pardo, moreno). The classification in your church record should match the militia record series.

Search tip: Write out your search profile on paper or in a document before you contact any archive. The discipline of writing it down often reveals what you know and do not know — and what you can find in sources you already have.

5.2 The Recommended Search Sequence

Follow this sequence to maximize efficiency and minimize cost:

Step 1: Exhaust Puerto Rico Church and Civil Records First

Before searching military records, confirm identity in the records most available to you:

FamilySearch Puerto Rico Civil Registration (1885-2001) and Catholic Church Records (1645-2021): establish the ancestor’s name, birth municipality, and parents’ names in a record that does not require a foreign archive request
Cross-reference with census records (1910, 1920) and any surviving padrones

If your ancestor served before civil registration began (1885), you will be working primarily from church records. The Navigating Civil Records course covers these in detail.

Step 2: Search PARES (Free, Online)

Spend 30-60 minutes on pares.mcu.es. Search the ancestor’s surname and municipality. Check AHN Ultramar, military sections, and any relevant collection.

Step 3: Check FamilySearch Military Catalog

Review the FamilySearch catalog under “Puerto Rico — Military records.” Search the main database for the ancestor’s name. Takes 15-30 minutes.

Step 4: Contact AGPR (If Applicable)

If the ancestor served in a locally organized unit, or if you are researching a Pardo Militia line, write to the Archivo General de Puerto Rico to ask whether records survive for the relevant unit and time period.

Step 5: Submit a Request to Segovia

Using the request guidance in Module 4 (Section 4.2), submit an email request to the Archivo General Militar de Segovia. Include your search profile. Wait for a response before moving to the next step.

Step 6: Analyze and Correlate

When you receive a record (or a negative response), apply the Three-Layer Framework before drawing conclusions.

5.3 Applying the Three-Layer Framework to Military Records

The Three-Layer Framework (from the Genealogical Proof Standard) evaluates every document at three levels: source, information, and evidence.

Layer 1: Source

A filiación is almost always an original source: the record was created at the time of enlistment, by a military clerk, for administrative purposes.

A certified copy or photographic reproduction of a filiación is a derivative source: it reproduces the original but adds a step of potential error.

An index entry or database transcription of a filiación is also a derivative source and may contain transcription errors; always request the original image.

Layer 2: Information

The birthplace (naturaleza) field in a filiación was typically reported by the soldier himself at enlistment. He was a participant with firsthand knowledge of his own origin: primary information. His age, parents’ names, and wife’s name are also primary information, assuming he reported them accurately.

However, accuracy is not guaranteed. A soldier might misreport his age to meet an enlistment age requirement. A soldier with reason to conceal his origin might misstate his municipality. These are considerations for Layer 3 (Evidence), not reasons to automatically distrust primary information — but they must be acknowledged in your analysis.

Layer 3: Evidence

A filiación’s naturaleza field provides direct evidence of birthplace: it explicitly states the municipality.

A filiación’s filiación field (parents’ names) provides direct evidence of parentage.

A muster roll that shows a soldier as Fallecido on a specific date provides direct evidence of approximate death date (or at least the date the death was recorded).

A muster roll that does not list a man where you expected to find him provides negative evidence: the expected entry is absent. Negative evidence is meaningful and should be noted, not ignored.

5.4 Resolving Conflicts Between Military and Other Records

Military records will sometimes conflict with church or civil records. The most common conflicts are:

Age Discrepancy

A filiación gives age 25 at enlistment in 1810 (implying birth circa 1785). A baptismal record found at FamilySearch gives birth date 1779 (implying he was 31 at enlistment). A six-year discrepancy.

How to evaluate: Apply the preponderance principle. The baptismal record is an original source with primary information recorded close to the event of birth. The filiación’s age field is primary information but recorded 6-31 years after the birth, depending on when the man enlisted. The baptismal record has higher source reliability for birth year. The most likely explanation: the soldier underreported his age, possibly to seem more fit for active duty, or the clerk approximated from appearance. Document the discrepancy and your reasoning.

Name Variant

A filiación gives the soldier’s name as “Juan Valentín” (single surname). A marriage record gives “Juan Valentín Méndez.” A baptismal record gives “Juan Balentín Méndez.”

How to evaluate: Name variants were routine in 18th- and 19th-century Puerto Rican records. Single surnames in military records are common when the clerk recorded only the most commonly used name. The V/B substitution (Valentín/Balentín) is a well-documented paleographic pattern in Puerto Rican records. These variants are consistent with a single individual. Note each variant in your research log and explain the consistency.

Municipality Discrepancy

A filiación gives naturaleza as “Añasco.” A baptismal record was found in Rincon parish records. Añasco and Rincón are neighboring municipalities.

How to evaluate: Before concluding these are different people, consider: (1) Municipal boundaries changed during the colonial period; some barrios were transferred between towns. (2) A person might describe themselves as being from the larger or better-known nearby town. (3) The baptism may have occurred in the nearest accessible church, which was not always in the municipality of birth. Research the boundary history of both towns before treating this as a conflict.

5.5 Writing a GPS-Compliant Conclusion

When you have gathered sufficient evidence, you need a written conclusion that ties it together. The GPS requires that conclusions be expressed in writing with reasoning shown.

Choosing the Right Proof Vehicle

Proof statement: A single sentence works when the evidence is direct and uncontested. “Juan Valentín Méndez, born circa 1785 in Rincón, Puerto Rico, was the son of Pedro Valentín and María Josefa Méndez, as established by his filiación in the Archivo General Militar de Segovia.”

Proof summary: One to three paragraphs, used when there are minor discrepancies or multiple source types to reconcile.

Proof argument: A detailed narrative with full analysis, used when evidence is indirect, conflicts are significant, or multiple records must be correlated to establish a single conclusion.

Elements of a GPS-Compliant Military Research Conclusion

Every conclusion that uses military evidence should include:

The sources examined: Name each repository searched and what you found (or confirmed absent)
The evidence extracted: What each record says, field by field for the key data points
The classification: Source type, information quality, evidence value for each record
Conflict resolution: How you addressed any discrepancies (age, name, place)
The conclusion statement: What you have established and to what standard of certainty

Example Conclusion Structure

Sources examined: The Archivo General Militar de Segovia provided a filiación for Juan Valentín, dated 15 March 1812, for the Compañía de Milicias de Añasco. FamilySearch provided a baptismal record for “Juan Balentín Méndez” recorded in the Rincón parish register in 1786.

Evidence extracted: The filiación records naturaleza as Añasco, age 26 (implying birth circa 1786), parents as “Pedro Valentín y María Méndez.” The baptismal record gives parents as “Pedro Valentín Rodríguez y María Josefa Méndez,” birthdate 3 February 1786, parish of Rincón.

Classification: Both the filiación and the baptismal register are original sources. The filiación’s naturaleza and parentage fields carry primary information from the soldier; the baptismal record’s parentage fields carry primary information from the parents present at baptism.

Conflict resolution: The municipality discrepancy (Añasco vs. Rincón) reflects the proximity of the two towns and possible boundary ambiguity; the ages align precisely. The V/B name variant is consistent with known patterns. The parents’ names match across both records (allowing for the addition of the paternal surname “Rodríguez” in the baptismal record, which the filiación did not record for the mother).

Conclusion: The preponderance of evidence supports the identification of Juan Valentín (filiación, 1812) and Juan Balentín Méndez (baptism, 1786) as the same individual. This conclusion meets the Genealogical Proof Standard.

Glossary of Key Military Terms

Spanish Term	English Meaning
Filiación	Enlistment/service record (for enlisted men)
Hoja de servicio	Service record (for officers)
Lista de revista	Muster roll
Revista de inspección	Inspection review
Naturaleza	Birthplace (municipality)
Vecindad	Current residence
Oficio	Occupation
Estatura	Height
Compañía	Company (basic militia unit)
Batallón	Battalion
Regimiento	Regiment
Milicia de Pardos y Morenos	Militia unit for free men of African descent
Soldado	Private (enlisted soldier)
Cabo	Corporal
Sargento	Sergeant
Teniente	Lieutenant
Capitán	Captain
Dado de baja	Discharged from service
Fallecido	Deceased
Fuero militar	Military privilege (exemption from civil courts)

← Module 4 · Course Overview

Notice: Found a broken link or error? Report it here.