The last census in a sitio comes back from the field as a stack of handwritten forms. The field encoder who collected them is no longer reachable. Some of the house numbers are ambiguous — two households in the same purok share similar identifiers. Three signatures are missing. There's no way to verify which data is from the most recent round and which is carried over from the previous one.
This is the standard outcome of paper-based barangay data collection. The data exists; its integrity doesn't.
What the Field Encoder's Record Actually Requires
A barangay census record needs to solve two simultaneous problems: capturing complete household demographic data in one entry, and capturing it in a way that is attributable and verifiable after the fact.
The Field Encoder text field addresses the second problem. Every household record carries the name of the person who collected it. When data quality questions arise during aggregation — a date of birth that can't be right, an educational attainment that doesn't match the listed occupation — you can trace the entry back to the specific encoder who worked that section. This creates accountability without requiring a supervisor to be present during every data collection interaction.
Location (GPS coordinates) anchors each household record to a physical point. Combined with House Number and Street, Purok, Sitio, Subd., a household is identifiable both by administrative address and geographic coordinate — the administrative address for official records, the GPS for field verification. In a barangay where informal settlements may not have formalized street names, the coordinate is often more reliable than the address.
Signature captures a digital consent confirmation from the household head, which provides documentary evidence that the data was collected with the respondent's participation — relevant for any subsequent data governance requirements.
Ten Family Members, One Household Record
The template's most distinctive structural choice is the repeated family member blocks — up to ten additional household members beyond the household head, each tracked with Name, Position in the family, Date of Birth, Age, Civil Status, and Occupation.
This design captures household composition as an integrated unit rather than as separate individual records. For a barangay census that needs to understand household size, generational structure, and dependency ratios across the population, this structure allows filtering by household-level indicators: how many households in Sitio 3 have more than five members? How many households have a head of household with no formal educational attainment and at least three children?
Those queries are impossible when household composition data is scattered across separate individual records without a linking identifier. They're straightforward when the entire household is one record.
The Educational Attainment multichoice and Occupation text field for the household head are the demographic indicators with the most analytical weight. Educational attainment drives employment eligibility analysis; occupation cross-referenced with civil status and household size produces the income vulnerability indicators that barangay development programs use to prioritize interventions.
At a Thousand Household Records
A sitio-level census at 800-1,200 households is a dataset with enough entries that the structure of each record determines what analysis is possible. A database where every household head's religion, civil status, and educational attainment is a clean categorical field produces cross-tabulations in seconds. A database where those fields are free-text entries produces a string normalization problem.
The Religion field here is free text, which allows for granular denominational precision — "Iglesia ni Cristo" rather than a collapsed "Christian" category — at the cost of requiring normalization before aggregation. The Gender multichoice is a controlled vocabulary, which avoids the normalization problem entirely.
The Email and Phone Number fields move the record beyond pure demographic documentation into contact management — a household census that also functions as a residents' directory for barangay communications.
The Date Added context is implicit in the Field Encoder attribution and the GPS timestamp — any census with a defined data collection round can be filtered by encoder, then by location cluster, then by household size, to produce the sorted working output that a barangay captain actually needs to present at the LGU level.