Household vs individual beneficiary records: how to model both
If eligibility or impact is counted per family but services go to individuals, you need both: a household record and an individual record for each member, linked by ID. If nobody ever reports on families, individual records alone are simpler and safer. Decide this before you build a single form, because changing it later means re-registering people.
This deep dive extends our guide to the beneficiary management system, where household vs individual is one decision among many. Here we cover the decision tree, the fields, and one build where it mattered.
A three-question decision tree
- Does any funder, scheme or indicator count families? If yes, you need households.
- Does eligibility depend on household facts such as ration card type, income band or family size? If yes, you need households.
- Do you serve several members of one family across programmes? If yes, a light household record still helps you avoid three visits for one family.
Three “no” answers mean individual records only: a scholarship, a youth skilling cohort, a teacher training programme.
What each record holds
| Household record | Individual (member) record |
|---|---|
| Household ID (own prefix) | Person ID (own prefix) |
| Head of household (a link to a member, not free text) | Household ID (stored on the person) |
| Location: village/ward, block, district | Name, DOB or age band, gender |
| Ration card type, income band | Relationship to head |
| Household-level consent contact | Individual consent, by purpose |
| Status rolled up from members | Enrolments, services, outcomes |
Two rules matter more than any field.
Store the household link on the person, not the other way round. Marriages, migration and joint families splitting are normal. When someone moves, you change one field on their record, and their history moves with them.
Never create a new person when someone changes household. A new record breaks the baseline-to-endline chain and inflates your unique count. Our deep dive on unique beneficiary IDs covers how to catch the duplicates that slip through.
Children in household records bring extra duty. Under the DPDP Rules, processing a child’s data needs verifiable parental consent from May 2027; our guide to verifiable parental consent for NGOs explains what that means for family registration.
How counts roll up
Count people at the member level and families at the household level, and never mix them in one headline. Services and outcomes attach to individuals. Household status is calculated from members, not typed in. That way “families reached” and “individuals reached” always reconcile.
Worked example: welfare scheme access for families
A Pune-based nonprofit helps underserved families get the government welfare schemes they are entitled to: education, health, livelihood and social security. Its field workers visit households, register families, collect documents and support applications. Before the build, family IDs lived in separate sheets per field worker, scheme eligibility was matched by hand, and nobody could say how many families had actually received a benefit.
We built around this on Zoho Creator over four months:
- Household head plus member records. Schemes are applied per person, but many benefits are counted per family. A family is marked complete only when every member’s schemes reach “benefit received with proof”.
- A rule engine for eligibility. With more than 100 schemes, manual tagging was impossible. On registration, each member is matched to eligible schemes by age, gender, category and other attributes.
- Separate offline intake forms, with duplicate review before records enter the main beneficiary list.
- Two-point phone verification. Telecallers, assigned automatically by workload, confirm registration details and later confirm the benefit was received.
- Role-scoped access. Five roles (admin, project lead, field worker, telecaller and donor), each seeing only their own rows, including donor dashboards limited to their own project.
The system now manages more than 5,000 families and 20,000 individuals.
What we learned after go-live mattered as much as the build. Storage limits arrived faster than expected, so audit history is now archived weekly. Dashboard numbers drifted when different reports used different filters, so the team agreed one source report for every headline figure. And because figures go to donors against a target, only admins can remove a proof once it is counted. None of this is glamorous. All of it keeps funders trusting the numbers.
Get the model right before the forms
Household logic is one of the decisions that’s cheap on paper and expensive in code. Before you configure anything, get a clear read on what your programmes actually need.