Set Targets for Project Indicators using the Lightning Web Component Interface

This page covers:

Targets are anticipated values for a Project Indicator. Typically, organizations compare their Results against Targets to evaluate their performance or progress toward their goals. 

Depending on an organization's impact measurement processes, they can set Targets by Project Indicator for different timeframes (Reporting Periods) and locations (Geographic Areas). Organizations often set Targets for all of their Project Indicators across multiple timeframes (even through the life of the project) to plan out the intended progress of Project Indicators over time*.

*Lightning Web Component The Lightning Web Component Set Targets interface allows users to set Targets for multiple Reporting Periods simultaneously, making it easier to plan out goals for a longer period.

Before you can set Targets for your Project Indicators, there are a couple of Project setup-related tasks to complete:

1. Set project-specific Reporting Periods

2. Create Geographic Area records

3. Set up Project Indicators

Here is a screenshot of what you’ll see if the data setup is done correctly. When the Set Targets table is loaded, the “Target Frequency” and “Geographic Area” dropdowns have default values selected. The Project Indicators corresponding to these selections are displayed on the Set Targets table.

Open

1. Select a value from the “Target Frequency” dropdown - It shows all the frequencies for which Reporting Periods and related Project Indicators exist in the Project. For example, an organization might set targets for annual, quarterly, and monthly timeframes and have Reporting Period records for four years to cover those timeframes (e.g. Annual = 2022, 2023, 2024, 2025; Quarterly = Q1 2022, Q2 2022, up to Q4 2025, etc.) The first Target Frequency is selected by default so remember to check and update the value if you’re setting targets for another period.

Open

On selecting a particular Target Frequency (eg, Quarterly), all Reporting Periods with that frequency (eg, Q1 2022, Q2 2022 etc) are displayed on the Set Targets table.

1. The Lightning Web Component allows you to set Targets for multiple Reporting Periods in one go.

2. The Set Targets table will only display the Project Indicators for the Target Frequency that you selected.

2. Select a value from the “Geographic Area” dropdown - It shows all the active Geographic Areas that exist in the Project. On selecting a value, all Project Indicators for the Geographic Area that you selected will be displayed on the Set Targets table.

1. Targets can only be set for one Geographic Area at a time.

2. Remember to check and update the Geographic Area value in the dropdown, if you’re setting Targets for any other Geographic Area than the one that is shown by default when the page is loaded.

   Open

   

In the table:

• Each Project Indicator is hyperlinked to its record. Clicking on it will open the Project Indicator record in a new tab.

• Each Project Indicator also has an Information icon in the Project Indicator column. When you hover over the icon, a pop-over displays the additional information stored on the Project Indicator record. Read more about the Information Popup here.

Once your Project Indicator and related Project data setup are done, you’re ready to start setting targets. Typically, there are two kinds of Project Indicators to set targets for:

Not sure if Target Values are Disaggregated?
A simple way to know if the Targets for a particular Indicator are disaggregated or not (on loading the page initially) is to look at the input field.

• A rectangular input box indicates that the Target is not disaggregated.

• A “+” icon denotes that a Target is disaggregated.

Open

For both disaggregated and non-disaggregated Project Indicators, targets values need to be entered depending on the Data Type of the Indicator. This is defined on the Project Indicator level and summarized in the table below. These Target values are saved in the Result record.

Organizations often need a way to track an Indicator’s Baseline data prior to their interventions. Users can enter Baseline data on the Set Targets Lightning Web Component to both define the initial state of their stakeholders prior to their intervention and to set Targets according to the assumed change from the Baseline state.

1. To set Baseline values for Project Indicators select Baseline from the “Target Frequency” dropdown. The Baseline frequency will only be displayed in the dropdown once Reporting Period for Baseline has been created. Visit this page to review instructions for creating Baseline Reporting Periods.

   Open

   

2. When you select “Baseline” in the “Target Frequency” dropdown and a selection is made in the “Geographic Area” dropdown, all Project Indicators that have a baseline will be displayed in the Set Targets table. 

4. Baseline values for Project Indicators (for the Baseline Target Frequency) can be entered for multiple Reporting Periods periods similarly to Targets.

5. Baseline data can also be compared and viewed against Result data. Read more about it here. 

When the “Track Numerator Denominator for Baselines” checkbox is selected for a Numerator/Denominator type indicator, the Baseline input popup displays separate Numerator and Denominator fields. The Baseline value is then automatically calculated using the formula: (Numerator ÷ Denominator) × Calculation Factor.

Open

The final resultant Baseline value after the calculation is displayed with 0 decimal places by default. This value is controlled using the “Number of Decimal for Resultant Value” field. Users can show upto 2 decimal places.
Amp Impact supports upto 15 characters for the Resultant Baseline Value for Numerator/Denominator indicators.

The entered numerator/denominator Baseline data can then be compared with Results on the addResults LWC popups.

Open

If the “Track Numerator Denominator for Baselines” checkbox is not checked during the creation of a Project Indicator, users can manually enter only the final Baseline Percent value, rather than separate Numerator and Denominator values:

Open

 Enter the Target values next to the relevant Project Indicator for the relevant Reporting Period. For non-disaggregated Project Indicators, Target data is auto-saved for each input field after you enter a value and click out from the data input cell. Target data is not deleted by simply removing values from this table. Target data has to be manually deleted from the Results object. Contact your System Administrator if you require support with this.

Additionally, each Project Indicator row on the Set Targets table has a Comment icon. A comment pop-up is displayed when you click on this icon to add or edit any additional qualitative information about that Target value. Hover over the comment icon to display a preview of the comment after entering its target(s).

Open

Open

The Set Targets table also allows you to capture Targets for Project Indicators that are Disaggregated by Sex, Age, Income, etc. The fields that control disaggregation of Target data on the Set Targets table are:

• Targets are Disaggregated?  

• Cross-Disaggregation by Sex

• Disaggregation Group(s)

• Disaggregation Type (introduced in Phoenix 1.45)

These fields are populated while creating or editing a Project Indicator. 

There are a few clicks to enter disaggregated Target values for a particular Reporting Period: 

1. Click on the plus (+) icon displayed. 

   Open

   

2. A pop-up appears when entering Targets, with the number and format of input fields dynamically determined by the following fields:

   • Data Type

   • Disaggregation Group(s)

   • Cross-Disaggregated by Sex?

   • Calculate Total

   • Disaggregation Type (added in the Phoenix Release, v1.45)

   The pop-up header displays, in order:

   1. The Indicator Definition

   2. The selected Geographic Area

   3. The Reporting Period for which targets are being entered

   To view more details about a Project Indicator, hover over the information icon.

   Open

   

   The format of the input fields in the pop-up aligns with the selected “Data Type”. The layout of the pop-up adjusts based on the values selected for “Calculate Total”, “Disaggregation Group(s)”, and “Cross Disaggregation by Sex”. For more details refer to this page. If a Project Indicator is disaggregated by more than one group, the “Disaggregation Type” field (introduced in v1.45) also influences the display. You can scroll horizontally or vertically within the pop-up to view all input fields.

   1. Phoenix v1.45 Onwards If the “Disaggregation Type” is set to Nested, users will see the Disaggregation Groups displayed as columns in the pop-up.

      The order of these columns follows the sequence in which the groups were added in the Disaggregation Group(s) field when creating the Project Indicator:

      • The first group (primary group) appears as the leftmost column.

      • All subsequent groups are nested within it, displayed as columns to the right.

       

      For example, if the Disaggregation Group(s) field includes Age Group (Women) followed by Economic Activity Sector, the columns in the pop-up will reflect that order: Age Group (Women) on the left, and Economic Activity Sector nested within it to the right.

Open	Open

Open	Open

Phoenix v1.45 Onwards For Project Indicators disaggregated by multiple groups, where Disaggregation Type = Nested, users have the option to hide totals while entering or analyzing targets.
This applies to indicators with Number, Currency, data types where Calculate Total = Sum Total.

Open	Open

Open	Open

b. Phoenix v1.45 Onwards If the “Disaggregation Type” is set to Stacked, users will see Disaggregation Groups displayed as rows in the pop-up.

The order of these rows follows the sequence in which the groups were added in the Disaggregation Group(s) field when creating the Project Indicator:

• The first group (primary group) appears at the top.

• Its disaggregation values are listed as rows directly beneath it.

• All subsequent groups are also stacked as rows below, with their group names highlighted in grey for clarity.

For example, if the Disaggregation Group(s) field includes Age Group (Women) followed by Economic Activity Sector, the rows in the pop-up will reflect that order from top to bottom: Age Group (Women) on top, and Economic Activity Sector stacked below it.

Open	Open

Open	Open

4. Enter the targets in the pop-up. Target data will only be saved when the “Save” button is clicked.

   1. As of the Phoenix Release (v1.45), for Project Indicators disaggregated by multiple groups with Disaggregation Type = Stacked , a warning message will appear upon clicking “Save” if the totals across groups are not equal. In such cases, the total for the primary group will be highlighted with an orange border to help users quickly identify the mismatch. This is applicable to Data Types = Number, Currency with Calculate Total = Sum Total.

      Open

      

5. On clicking the “Save” button and navigating back to the Set targets table, the plus (+) icon, will either be replaced by

   1. A hyperlinked numerical value (for Quantitative Indicators that have Calculate Total set to Sum Total), or

   2. A pencil icon (for all Qualitative Indicators and those Quantitative Indicators that have Calculate Total equal to Don’t Sum Total).  

      Open

      

c. Phoenix v1.45 Onwards When Disaggregation Type= Stacked and totals across groups do not match, the target of the primary group will be displayed on the Targets table.

For disaggregated Project Indicators, the Comment icons will be shown inside the Disaggregation pop-up. 

1. For Project Indicators that are Disaggregated by Sex, one comment icon is entered across the Male, Female, and Unknown Targets. 

   Open

   

2. For Project Indicators that are Disaggregated by Group, one Comment can be entered for each Disaggregated value in the group. 

   Open

   

Click on the comment icon to display or add new comments. Hovering over the Comment icon displays a preview of the saved comment.

As of the Orion Release (v1.41), it possible to lock comments after submitting the targets and results through a design attribute.

As of the Phoenix Release (v1.45), the comments are displayed in the rightmost column on the popup.

Open

Validation ranges for Project Indicators facilitate better data quality. These are set at the Project Indicator level.

If the Target value entered is less than the value set in the “Validation Range Minimum” field or more than the value set in the “Validation Range Maximum” field on the Project Indicator, a warning message appears at the top of the page and the input field is highlighted with an orange border. The Target value will still be saved even if it falls outside of the Validation Range.

Open

Some organizations have a process in place to submit, review, and lock Target data for editing once it is approved. If this feature is enabled, the “Submit” button can be used to lock the Targets. 

Open

1. Click on the “Submit” button.

2. Select the Reporting Periods for which the Targets need to be submitted.

   Open

   

3. A pop-up then confirms if Targets need to be submitted for the selected Reporting Period or not. Click  Submit to confirm. Click back to go to the previous step.  

   Open

   

The Targets are submitted once the user clicks the “Submit” button. If a Reporting Period has been submitted, its column will display as read-only, with a lock icon in the header. The “Upload” button is also greyed out to prevent any additional Targets from being uploaded. 

Open

Disaggregated target data or qualitative targets can still be viewed by clicking on the hyperlinked total value or eye icon, which will open a read-only version of the disaggregated data entry popup.

When Targets/Baselines/Reporting Periods are locked via the “Submit and Lock Wizard” users will see the same interface as mentioned above. This Wizard is available from Mira Release (v1.37) onwards

Often, there are a number of users in the system, entering and managing data simultaneously. If another user makes and saves updates on a component or a related component (like the Framework or Project Indicators) while you’re working in the system, you’ll see a notification that alerts you that changes have been made. Click on the “Refresh” icon to load and reflect the latest data on the Set Targets component along with all the Targets that have been previously recorded. For example, if the Project Indicator Definition is edited or a Geographic Area is marked Inactive, these changes will be reflected once the Set Targets component is refreshed. 

Open