Skip to main content

KPIs explained

Purpose​

The four KPI cards along the top of the Dashboard summarise the climate finance portfolio in numbers that fit on one screen.

The four KPIs​

1. Total Mobilized​

  • What it is: the total amount committed across all submissions counted by KCFIS.
  • Unit: KES (Kenyan Shillings), shown in thousands, millions, or billions as appropriate.
  • Use it to: understand the pledged size of the climate finance portfolio.

2. Total Disbursements​

  • What it is: total actual expenditure — the amount that has actually been spent against commitments.
  • Unit: KES.
  • Use it to: see how much of the pledged finance has actually flowed.

3. Validation Success Rate​

  • What it is: the share of submissions that passed validation on first attempt (no repair needed).
  • Unit: percentage.
  • Use it to: gauge the quality of the data being submitted across entities. A low rate suggests common template misunderstandings or data quality issues at source.

4. BTR Quality Score​

  • What it is: a composite quality measure (0–100) computed across all data KCFIS has, accounting for completeness and consistency.
  • Unit: 0–100, also rendered in the radial chart.
  • Use it to: track quality improvements over time.

Reading a KPI card​

Each card shows:

  • The title of the KPI (e.g. "Total Mobilized").
  • The headline value.
  • A small trend indicator: a green up arrow for an improvement compared with the previous period, or a red down arrow for a regression. If KCFIS does not have a previous period, no arrow is shown.

Common questions​

The figure looks low — is something missing?

It almost certainly is. KPIs only count submissions that have reached the Locked state (the final state after admin approval). Submissions that are still in draft, validation, review, or have been rejected are not in the totals.

Why is the validation success rate not 100%?

A small share of failed first-attempt validations is normal. Look at the Submissions list filtered by Validation Failed status to see which entities or templates are causing it.