PRP
  • PRP Documentation
  • Introduction
    • Glossary / Terminology
    • Indicators
      • Disaggregations
      • Calculating progress
    • FAQ
    • Releases / Changelog*
    • Report an Issue / Contact us
  • Product / End-user Documentation
    • IP Reporting
      • Overview
      • Partner roles and permissions
      • User Interface
      • Setting calculation methods for indicators
      • Progress Reports
        • Reporting Overview
        • Special Reports (SR)
        • Humanitarian Reports (HR)
        • Quarterly Progress Reports (QPR)
        • Reporting Process
        • Data Uploader for QPR and HR
      • Various data exports
    • Cluster Reporting
      • Overview
      • User Authentication, Roles and permissions
      • AD Integration
      • Response Plans
      • Cluster Indicators
      • Response Plan Dashboard
      • Response Parameters setup
      • Planning your action as a Partner
      • Reporting on results
        • Reporting to UNICEF
      • Analysis of results
      • OCHA Integration
    • ID Management
      • Overview
      • AD Integration & Sign In
      • Email Notifications
      • User Statuses
      • Permissions
      • IP ID Management
        • User Interface
        • Users screen
      • Cluster ID Management
        • User Interface
        • Users screen
        • Partners screen
  • Technical Documentation
    • Architecture
    • Development Setup
    • Deployment / DevOps
    • Data Model
    • API Documentation
      • Error Handling
    • CartoDB location sync
    • OCHA Integration - Research Summary
      • Response Plan Import
      • Project Import
    • ID Management
      • Backend API's
    • Handover session question
Powered by GitBook
On this page
  1. Introduction
  2. Indicators

Disaggregations

PreviousIndicatorsNextCalculating progress

Last updated 7 years ago

In some cases data reported by the partner for an indicators progress needs to be broken down further and not just be a total number.

This concept is referred to as disaggregated data reporting. An example of what that might look like for say data broken by age, gender, height (made up scenario) is as shown below.

The PRP system supports up to three disaggregations per indicator. Each disaggregation can contain any number of disaggregation groups (options). The partner is then expected to report data for the specified disaggregations. It it possible though for the partner to choose to report at a lower or no (totals only) disaggregation as well, since they may not have the granular data available.

In either case for a particular indicator report for one location, the progress against targets is always the total that is calculated by summing the disaggregated data.

Defining Disaggregations

For IP reporting the disaggregations are defined by the PO in the PMP system. PRP simply picks these disaggregations up and uses them.

For cluster reporting though the IMO can define these disaggregations for the entire response and then use these in a consistent manner for the indicators they or the partners create in any cluster within the response plan.

Entering disaggregated data for a indicator report for a particular location.
Defining disaggregations for the entire response plan