Impact/Outcome Reporting (Indicators, Targets, Results, Impact Stories): Key Relationships
This page covers:
Related pages:
Impact/Outcome Reporting: Overview
This functional area is where impact measurement comes together. This is the functionality for defining the key indicators (or metrics/KPIs as some organizations might refer to them) for a Project, Grant, or other initiative, setting targets, reporting results, and capturing stories throughout the project lifecycle.
Impact/Outcome Reporting: Data Model
Below is the Impact/Outcome Reporting data model subset:
Impact/Outcome Reporting: Summary of Key Relationships
There are thirteen key relationships that are foundational to Impact/Outcome Reporting:
Indicator: This relationship allows organizations to measure the performance of projects based on the indicators linked to the project.
Project Indicator: This relationship allows organizations to manage the specific indicators that are associated with a project.
Indicator Thematic Area: This relationship allows organizations to associate indicators with thematic areas.
Project Indicator Thematic Area: This relationship allows organizations to associate project indicators with thematic areas.
Project Indicator Geographic Area: This relationship allows organizations to associate project indicators with project geographic areas.
Disaggregation Groups: This relationship allows organizations to divide indicators into smaller groups.
Disaggregated Value: This relationship allows organizations to capture the values for certain disaggregation groups.
Disaggregated Indicator: This relationship allows organizations to associate indicators with disaggregation groups.
Disaggregated Project Indicator: This relationship allows organizations to associate project indicators with disaggregation groups.
Reporting Periods: This relationship allows organizations to break down the duration of a project into different time periods.
Project Indicator Reporting Period: This relationship allows organizations to relate project indicators with reporting periods.
Result: This relationship allows organizations to keep and display the results and targets for a project at an indicator level.
Impact Story: This relationship allows organizations to capture stories, observations, learnings, or qualitative results for a project.
Here is a summary of these relationships:
Amp Object Label | Amp Object API name | Abbreviation | Object Description | Sample Use | Also Sometimes Called | Key relationships (Amp object's relationship in parentheses) | Sometimes connects to |
---|---|---|---|---|---|---|---|
Indicator | ampi_Indicator__c | None | The Indicator object contains indicators or metrics that are used on projects to measure performance. Both Standard (or 'catalog') and Custom Indicators have records in this object. Ticking the 'Include In Catalog?' checkbox makes Indicators available in the Indicator Catalog on the Manage Indicators component. Several key fields (Data Type, Reporting Frequncy, Geographical Disaggregation, Disaggregation Group, etc) control how, when, and where Indicators are reported on. | "# of beneficiaries served" is an indicator used in the "Breaking the Barriers" project as well as "Invest in Women - Ghana" project. Because the Include In Catalog box is checked, this indicator is available in the Catalog to be added to other projects. It's reported on Quarterly at the Country level and disaggregated by age and sex. | Metrics, KPIs | Indicator (self lookup for Parent/Child Indicators) | Call for Proposals (eg where certain KPIs are required for applications) |
Project Indicators | ampi__Project_Indicator__c | PI | The Project Indicator Object is used manage specific indicators linked to a project. It allows for tailoring an Indicator to a particular project, for instance if it's reporting or target frequency is different. | The "# of beneficiaries served" has 12 Project Indicator records for the 12 projects that use it to track progress. | Project Metric, Project KPI | Indicator (child in lookup) | Sometimes it makes sense to build a direct lookup from Project Indicator to Framework Objective if an organization always uses a many-to-one relationship between PIs and Outcomes/Outputs. This is less flexible but makes analyzing data a bit easier. |
Indicator Thematic Area | ampi__Indicator_Thematic_Area__c | ITA | Indicator Thematic Area is a junction object which connects Indicators and Thematic Areas. Marking an ITA as Required means that an Indicator is required for a particular TA --> any time that TA is added to a Project, the Indicator will be added to that project as a PI. | SDG Indicator 13.1.2 is related to a Thematic Area called 'Climate Action'. |
| Indicator (child in lookup) |
|
Project Indicator Thematic Area | ampi__Project_Indicator_Thematic_Area__c | PITA | Project Indicator Thematic Area is a junction object connecting Project Indicators and Thematic Areas. | SDG Indicator 13.1.2 on the 'One for Change' project is tagged with the Thematic Area 'Climate Action' |
|
|
|
Project Indicator Geographic Area | ampi__Project_Indicator_Geographic_Area__c | PIGA | Project Indicator Geographic Area is a junction object connecting Project Indicators and Project Geographic Areas. Records in this object are created by an Apex trigger automatically when Project indicators or Project Geographic Area records are added to a project, matching the PI's Geographical Disaggregation with the GA's Type (one PIGA per match). | SDG Indicator 13.1.2 on the 'One for Change' project will be tracked in 2 countries: Uganda and Kenya (each country has a Project Geographic Area related to the project) | PIGA | Project Indicator (child in lookup) |
|
Disaggregation Groups | ampi__Disaggregation_Groups__c | DG | Disaggregation groups allow users to define common ways that Indicators can be broken down into relevant smaller sets for more granular management and reporting. | Age Group is a Disaggregation Group used by many different Indicators. It has 3 Disaggregation Values. | Indicator Component Group | Indicator (many-to-many) | You can configure a lookup to Project if end-users need to be able to easily create DG's in the context of planning a project without leaving the page. |
Disaggregation Value | ampi__Disaggregation_Value__c | DV | Disaggregation Value object captures the values/options for a particular disaggregation group. Results (and sometimes Targets) are captured and stored per Disaggregation Value if an Indicator has a Disaggregation Group. | Disaggregation Values for Age Group are: 18-30 Years, 31-60 Years, and 60+ Years) | Indicator Component | Result (parent in lookup) |
|
Disaggregated Indicator | ampi__Disaggregated_Indicator__c | None | The Disaggregated Indicator object connects Indicators to Disaggregation Groups. Amp uses this junction object to allow for a future feature through which users will be able to define multiple Disaggregation Groups per Indicator. Records in this object are created automatically by a trigger when a Disaggregation group is selected for an Indicator. | The '# of beneficiaries served' indicator is disaggregated by Age Group. A Disaggregated Indicator record connects those two records |
| Indicator (child in lookup) |
|
Disaggregated Project Indicator | ampi__Disaggregated_Project_Indicator__c | DPI | The Disaggregated Project Indicator object serves the same purpose as the Disaggregated Indicator object, just at the Project Indicator level (since it's possible that a PI might be disaggregated in a different, project-specific way than the Indicator it links to). | The '# of beneficiaries served' project indicator is disaggregated by Age Group. |
| Project Indicator (child in lookup) |
|
Reporting Periods | ampi__Reporting_Period__c | RP | Reporting periods represent time periods during a project. The object is commonly used to manage grant reports or progress reports (including narrative, results, financials, and files). It is an important object for Indicator Management and also for Financial Management (every Financial must link to an RP). | The 'One for Change' project has 3 annual reporting periods (2019, 2020, 2021) and a Life of Project reporting period. | Period, Report, Grant Report, Progress Report, Time Period | Project (child in lookup) | Submission (parent in lookup, eg in the context of a narrative grant report) |
Project Indicator Reporting Period | ampi__Project_Indicator_Reporting_Period__c | PIRP | Project Indicator Reporting Period is a junction object which connects Project Indicators and Reporting Periods. Records in this object are created by an Apex trigger automatically when Project indicators Reporting Periods are created for a project. The automatically filled Data Tracked field controls whether Targets, Results, or Both are tracked for a PI in a particular RP (in case, for instance, Results are needed for some RPs and Targets for others). | SDG Indicator 13.1.2 on the project "One for change" will be tracked every quarter (each quarter is a Reporting Period related to the project and Indicator 13.2 is created as a Project Indicator for the project). | PIRP | Project Indicator (child in lookup) |
|
Result | ampi__Result__c | None | The Result stores all the actual Results achieved and the Targets for a Project on a Project Indicator in a Geographic Area during a Reporting Period (and potentially for a specific Disaggregation Value). If Baseline data need to be disaggregated, they should be stored on this object as well (Baselines are effectively 'actuals' that existed before the project started). | For an organisation working to vaccinate young children, the Results object stores # of doses delivered (Project Indicator) in January (Reporting period) in India (Geographical Area), disaggregated by sex and rural/urban. | Actual, Target, Milestone | Project Indicator (child in MD) |
|
Impact Story | ampi__xx_Story__c |
| The Impact Story object captures stories, observations, learnings, or qualitative results for a grant or project in an unstructured or semi-structured manner. It allows rich text, links, photos, and videos. Impact Stories can connect to Projects, Reporting Periods, Geographic Areas, and/or Thematic Areas. | A grantee submitted an Impact Story for a microfinance project about the entrepreneurship journey of women in a rural area whose income increased as a result of the project. The story speaks to the new opportunities created for the community. To facilitate searching, the story is connected to the Project, to India (Geographic Area), to the Q3 2022 grant report (Reporting Period), and to Economic Opportunity (Thematic Area). | Story, Case Study, Lessons Learned, Evaluation Findings | Project (child in lookup) |
|