Making KPI entry easier

Many KPIs are automatically calculated in the platform but entering KPI data manually is useful because not every value can be derived from a system.

Below is a view of how a user configures a KPI. Notice the inclusion of the Reporting Period which allows the user to set the KPI entry to be for the Current or Previous period, i.e.,

  • Current Period means data summarising performance in March is entered during March
  • Previous Period means data summarising performance in February is entered in March.

This is often the case as the reporting period must complete to make the data available for entry during the early part of the next reporting period.

Based on the current month being March if a user selects Previous Period, when the KPI is due and they go to input the KPI value, the user will be prompted to input the value for February, saving the user from having to change the month they’re entering the KPI for.

If Current Period is selected then the user will be asked to input the value for March.

Of course, whether a KPI is Leading or Lagging has no influence on its input period, so these options continue to be separate; leading indicators lead a trend, lagging indicators show the trend, e.g.,

  • VOWD is a lagging indicator; it shows you what you’ve spent, even if you’re entering it for today.
  • Time-on-tools may be a leading indicator; it may show that the execution schedule is at risk because there are issues in executing the work.


We’re always interested in hearing from you with any comments or suggestions, feel free to get in touch.

Start typing and press Enter to search