Population Data Approval

Data Approver Flow

The Data Approver is responsible for validating population data collected by data collectors. The role primarily ensures that population data used for microplan resource estimation is accurate and consistent with predefined rules. Data approvers play a crucial role in identifying discrepancies and ensuring the validity of population numbers before final approval.

Responsibilities:

  • Validate population data collected from the field.

  • Identify discrepancies in population estimates.

  • Approve or flag data for further review and corrections.

Note : In the current version we are not including data collectors. Population data uploaded in the system admin flow will be sent for approval


Steps

Workflow for Data Approver Flow

The following describes the step-by-step workflow for the Data Approver:

Step 1: Log in to the Platform

  • Actor: Data Approver

  • Objective: Access the data review dashboard.

  • Process: The Data Approver logs into the microplanning platform with their credentials.

  • Outcome: The system displays all pending data that needs to be validated.


Step 2: Review Submitted Population Data

  • Actor: Data Approver

  • Objective: View population data collected by Data Collectors.

  • Process:

    • The Data Approver navigates to the population data review section.

    • The system presents the population data per administrative level (village, district, etc.).

    • Data is compared against previously uploaded data or other authoritative sources for discrepancies.

  • Outcome: The Data Approver views all population-related information for selected regions, including:

    • Total Population

    • Target Population (e.g., children aged 3-11 months and 12-59 months for SMC campaigns)

    • Latitude and Longitude (if available)


Step 3: Identify Discrepancies

  • Actor: Data Approver

  • Objective: Identify and highlight any discrepancies in the population data.

  • Process:

    • The Data Approver can manually review records to ensure the accuracy of the data.

  • Outcome: The system flags any discrepancies for further review, such as:

    • Significant deviations from earlier data (e.g., a village's population is reported as 5,000 when the previous figure was 2,000).


Step 4: Modify and Correct Data (If necessary)

  • Actor: Data Approver

  • Objective: Make necessary corrections to flagged data before approval.

  • Process:

    • If the Data Approver identifies errors or discrepancies, they may either:

      • Request corrections from the Data Collector.

      • Manually correct the data in the system, if they have the necessary authority and information.

    • Corrections may involve:

      • Adjusting total population numbers.

      • Updating target population estimates.

      • Correcting missing or incorrect geographic data (e.g., coordinates).

  • Outcome: The flagged data is corrected and updated in the system, ready for re-validation.


Step 5: Approve Population Data

  • Actor: Data Approver

  • Objective: Final approval of population data for use in resource estimation.

  • Process:

    • Once all discrepancies are resolved, the Data Approver selects the data records for final approval.

    • The system allows bulk approval or individual record validation based on user preferences.

  • Outcome: Approved population data is locked and made available for further processes, such as microplan resource estimation.


Step 6: Monitor Data Changes

  • Actor: Data Approver

  • Objective: Continuously monitor any changes to population data during the campaign.

  • Process:

    • The system provides alerts if any new data is submitted or if there are significant changes to previously approved data.

    • Data Approvers can review and re-approve any updates or revisions during the campaign.

  • Outcome: All data changes are tracked, ensuring continuous data integrity throughout the microplanning process.

Web Sequence Diagrams

Last updated

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.