Welcome to the performance app.  This app is designed to help a decentralised team to track performance against a pre-determined set of indicators.  The app includes the following user roles:


Plan creator - May create a new plan and complete configuration, but not approve it

Plan approver - May approve configuration changes to a plan

Node performance capturer - May capture data on a node, if assigned to that node

Node performance owner - May assign a user to capture or authorise data on the node

Node approver - May approve data captured on a node

Node target capturer - May capture target data on a node

Node target approver - May approve target data on a node


The app has the following components:


  • Indicators - This is a library of indicators that may be shared across performance plans
  • Taxonomies - A taxonomy is a set of criteria used to disaggregate an indicator or a hierarchical structure used to organise indicators on a performance plan
  • Performance plan profiles - Each profile represents a separate performance plan.  This could be a logical framework, results framework or other type of performance plan, depending on your terminology.  Each performance plan profile has it's own start and end data and set of indicators


Each performance plan profile functions at two levels:


  1. Profile level functions affect the entire plan.  These include:
    • Configuring the start date, duration, reporting frequency and hierarchical structure of the plan.  From this information the plan is created, including:
      • A hierarchical set of nodes that are used to organise indicators
      • A set of reporting periods (months, quarters or years) that control which time period indicator data is reported against
    • Controlling the reporting periods for the plan
      • This enables the person managing the plan to close a reporting period (a month, quarter or year), locking it, and open the next one, enabling people to begin entering data for the new period
  2. Node level functions that affect a specific node on the hierarchical structure of the plan.  These include:
    • Configuring the name used for the node, the indicator(s) that is linked to the node and if the indicators on the node are disaggregated.  From this information the node is configured.
    • User role assignments, including which users must capture target or performance data and which must approve data captured
    • Entering target data for any indicators linked to the node (assuming they have a target specified)
    • Entering performance data for any indicators linked to node (for the current reporting period only)
    • Auditing data already entered on the node, entering a variance and a reason if a change is required


Once the plan has been configured - and the roles to capture and approve data assigned to users - the person managing the plan may track where data has been entered and where it is missing.  They may advance the reporting period, moving through the months, quarters or years over which data is reported against indicators.  This cycle continues until all reporting periods have been completed, after which the plan is completed and the data is locked.


Data entered on the plan is available to analyse using the reporting app.  This is covered in a separate article.


Please refer to other articles for more detailed explanations of the areas above.