Skip to article

GapBridge Institute

← All articles

GapBridge Institute Articles

How to choose programme indicators your team can use

Start with a real decision, define exactly what counts, and test whether two people can calculate the same result.

Conceptual illustration of layered evidence maps and a pathway connecting three points.

A programme dashboard can tell you how many activities took place without telling you whether to change anything. A useful indicator begins with a decision your team expects to make. If the figure rises, falls or stays unchanged, what could you do differently? If nobody can answer, the measure may belong in an occasional report rather than on the working dashboard.

Start with the decision

Imagine a regional training team deciding whether districts need extra support to introduce a new reporting process. Counting workshops tells the team whether it delivered the training. It does not tell the team whether districts have begun using the process. A more useful follow-up measure would be the share of eligible districts that submitted a complete practice report by the agreed deadline. Pair it with a short explanation of what held up districts that missed it. The number flags where to look; the explanation helps the team decide what support to offer.

Write down what counts

Give each measure a one-page reference sheet. State the decision it supports, who is included, what qualifies as complete, the reporting window, the source and who checks the result. For the example above, the numerator is the number of eligible districts that supplied a complete practice report by the deadline. The denominator is the number scheduled to report in that cycle. Decide in advance how to handle a district that joins mid-cycle and a district that sends a report after the deadline. If there are no eligible districts, mark the measure not applicable rather than entering zero percent.

Try it before publishing it

Ask two colleagues to calculate the indicator independently from the same small set of fictional records. Include a late report, a duplicate and a missing field. Compare what each person counted. Differences usually reveal a definition worth fixing before the team invests in a dashboard. If the source is unreliable, decide whether to improve it or choose a simpler measure you can collect consistently.

Review your shortlist after the first reporting cycle. Keep measures that support an actual decision, revise definitions when the team interprets them differently, and document changes so old and new figures are not compared as though they meant the same thing. A short set the team can explain and use is more valuable than a long set it updates out of habit.

Further reading: USAID Health Reform Support: Annex C, Performance Indicator Reference Sheet Template.