Skip to content

Program

A Program represents a campaign or intervention targeting a specific group of beneficiaries for a specific operational need, such as Cash for Nutrition or Emergency Food Assistance.

Within the Analyst / Collector Workspace, the selected Program becomes the working context for beneficiary management. Imports, beneficiary records, Batches, validation, and related workflows all operate within the currently selected Program.

What a Program defines

A Program defines how beneficiary data is imported, validated, and displayed.

Beneficiary structure

A Program inherits its beneficiary structure from the selected Beneficiary Group.

Two structures are supported:

  • Household-based: each Household contains one or more Individuals.
  • People-only: Individuals are managed without Households.

The selected structure determines how beneficiary data is imported, validated, managed, and displayed throughout the workspace.

Validation configuration

Validation is based on:

  • DataCheckers that define the expected beneficiary fields;
  • a beneficiary validator that performs additional validation of the beneficiary structure;
  • the Alien validation enabled setting, which controls whether unexpected processed fields are checked during validation;
  • the Alien columns to ignore lists.

After import, validation is scheduled when Validate after import is enabled.

See Alien Fields for more information.

Default values

Programs can define default values for Households and Individuals.

These values are applied during Data Import when the corresponding beneficiary field is missing or has a null value. They help ensure that required beneficiary fields are populated consistently.

Display configuration

A Program defines which beneficiary fields are displayed in the Analyst / Collector Workspace.

Display settings affect only the user interface and do not influence imported or stored data.

Alien columns to ignore

Programs can define processed fields that should be excluded from Alien Field validation.

During import and reprocessing, matching fields are also removed before Transformers are applied.

See Alien Fields for configuration and processing details.

Deduplication settings

For Programs with Biometric deduplication enabled, the Program page displays the current deduplication settings retrieved from DedupEngine in real time.

The settings are not stored in the Country Workspace database. When permitted by the current policy, they can be updated from Country Workspace, with changes applied directly to DedupEngine.

If DedupEngine is unavailable, the settings may be displayed as N/A.

Start an import

Imports are normally started from the Program page by selecting Import Data.

The import always uses the currently selected Program and creates a Batch containing the imported records for that Program.

For an overview of the import workflow, see Data Import. Source-specific instructions are available in Data sources.

After import

After an import completes:

  • imported beneficiary records become available within the selected Program;
  • validation results become available after any scheduled validation finishes;
  • the created Batch can be reviewed and, if necessary, reprocessed.

See Batches to review import results, monitor validation, and reprocess existing Batches.