Beneficiaries

A beneficiary record represents a household supported by a project. Field Coordinator records the beneficiary name, household size, location and vulnerability, then links the record to the project doing the work. Program Lead can review where the project is reaching households and which records carry a medium or high vulnerability setting.

The record describes a supported household; it does not by itself prove that a particular activity occurred. Activity history has its own date, summary and beneficiaries reached. Keep those records in their own roles when reporting outcomes. A household can be visible in the project roster while a planned activity is still waiting to take place.

• Household identity. Field Coordinator enters a clear beneficiary name and keeps the household size current.
• Project link. The project reference places the household in the correct delivery context.
• Vulnerability review. The low, medium or high setting helps Program Lead find households needing closer attention.

A practical example is a project with activities in two locations. The coordinator records each supported household’s location and links it to the same project. Program Lead can then review medium and high vulnerability households while checking the project’s activity schedule. The location is a text value, so agree its spelling and level of detail before comparing locations across records.

Decide what counts as one household record, how names should be entered and who may correct duplicates. Agree how the vulnerability values are assigned and reviewed. The field is a simple classification; establish the team’s own decision criteria and access rules for sensitive household information.

Agree when household size is updated and how historical activity reach is interpreted after a household changes size. Activity reach is entered as a separate numeric field on the activity record. The team should preserve the meaning of each number at the time it was recorded rather than silently using a current household size to rewrite earlier reach.

The project link deserves a specific check during migration. A beneficiary without the intended project cannot appear in a meaningful project breakdown. Import and review the project portfolio first, then link households to the correct project before using vulnerability or location summaries in operating decisions.

Choose a project with a planned activity and enter a supported household in its location. Set vulnerability to high and record household size. Supported Households should show the record with the project and location. Change the activity to in progress and record actual reach there; the household remains a separate source of information.

Now review Household Vulnerability by Project with Program Lead. Ask whether each high vulnerability record belongs to the right project and whether location names are consistent. Correct the source records before using the report to plan follow-up work. This rehearsal tests the household to project reference as well as the team’s classification rule.

• Supported Households — Medium and high vulnerability households with their project, size and location.
• Project Schedule — The project timing that gives household records their delivery context.

Start from the project delivery process. Use the data model to check the household to project reference before importing records.