UC-E-USCT-001: Eligibility Determination and Benefit Package(s) Design - Unconditional Social Cash Transfer

ID

Name

Description

From https://solutions.dial.community/use_cases/unconditional_social_cash_transf/use_case_steps/eligibility_determination_and_be

NOTE: Depending on the country and programme, eligibility determination takes different forms e.g. categorical by age without income screening , poverty-targeted, etc. often via “Proxy Means Test” calculation to screen and rank households by ‘inferred’ income.

"Clean" data from a Social Registry that have undergone the data verification and validation step is used to screen eligible beneficiaries and establish the recommended benefit and services ‘package’. The amount of transfer often varies depending on household composition, and beneficiaries may qualify for other add-on services based on analyzed socioeconomic / demographic information being used for other welfare or social programmes.

Workflows

The following are contextual workflows where the generic transactions support:

●      Client Case Management for determining and assigning benefit packages and benefit levels to specific user groups

●      Data Analysis and Business Intelligence / Decision Support potentially for identifying different benefit levels / types in correlation to target groups’ socioeconomic / demographic information, based on existing eligibility criteria (e.g. via proxy means test, means test or category-based)

Also see https://www.gov.za/covid-19/individuals-and-households/social-grants-coronavirus-covid-19 for a specific example on the ground

Trigger
(the event that triggers the use case)

Preconditions
(list of conditions that MUST be met in order for the use case to be successful)

1. Beneficiary has registered

2. Beneficiary’s case has been assessed

3. Beneficiary’s data has been verified and validated

Note that some preconditions come from the other user journeys and use cases, see steps 2-3 of https://solutions.dial.community/use_cases/unconditional_social_cash_transf/use_case_steps/

Data inputs

Actors
(a person, a company or organisation, a computer program, or a computer system - hardware, software, or both)

SRIS Registry (potential beneficiaries)

Benefit and Service Package Registry

Benefit administrator

Client Case Management Registration(Screenflow) BB application

Workflow(Data Analysis and Business Intelligence / Decision Support) BB to delegate scoring to heuristic and/or AI-based scoring engine

Security(SSO)

Normal Course (what happens if the event is triggered and the preconditions have been met)

In the case management Registration(Screenflow) application:

1. Admin logs in via Security(SSO)

2. Admin is shown a pool of cases for their team

3. Admin claims a case to work on

4. Admin is shown the case beneficiary’s ‘clean’ data from the Registry(SRIS)

5. Admin is shown the benefit eligibility rules and guidelines from the Registry(Benefit and Service Package)

6. Depending on the exceptions on the case, Admin may request data from for example:

   1. Above the age of 18 by checking national ID registry

   2. And Unemployed by checking employment registry

   3. And Not receiving any income by checking tax registry

   4. And Not receiving any social grant by checking the SRIS registry

   5. Compute and return a score between 0 and 100, along with the reasons for the computation as booleans for each step, e.g. unemployed is true

7. Admin screens the beneficiary for eligibility in the program

8. Admin approves or declines eligibility

9. Admin can refer beneficiary to another program

Alternative Course
(links to other use cases in case there are different ways how to solve the same use case)

Data output

Post-Conditions (the success criteria)

Exceptions
(error situations)

Related BBs
(working groups related to that particular use case)