Every government entity in Saudi Arabia reports on performance. The harder question is whether its key performance indicators (KPIs) actually tell leadership what is working, what is drifting and what to do next. KPI management is the discipline that answers it: choosing the right indicators, defining them precisely, collecting reliable data, and turning the results into decisions on a fixed rhythm.
This guide covers the full KPI lifecycle for public entities, from design through measurement to reporting and review. It is written for strategy offices, performance teams and the managers who own indicators. Where Saudi-specific practice matters, it points to the official sources, chiefly the methodologies published by the National Center for Performance Measurement (Adaa). If you want a step-by-step walkthrough focused on those methodologies, read our companion KPI guide for Saudi government entities.
What KPI management means in a government entity
A KPI is a measure, tied to an objective, that shows whether the objective is being achieved. KPI management is everything around that measure: who defines it, how it is calculated, where the data comes from, how often it is updated, who reviews it, and what happens when it goes off track.
In a private company, KPIs usually roll up to financial results. In a government entity, they roll up to a mandate and to national priorities. That changes three things:
- The audience is wider. Indicators are read by the entity's leadership, by sector bodies, and in many cases by national performance and oversight bodies.
- Outcomes matter more than activity. A ministry is judged on what changes for citizens, residents and businesses, not on how many workshops it ran.
- Evidence matters. A reported value usually needs supporting documents that someone outside the team can check.
Good KPI management makes these demands routine rather than a scramble at the end of each quarter.
Where KPIs sit: national direction, entity strategy and the operational plan
KPIs only make sense in relation to the plan they measure. In the Saudi public sector there are three layers to keep in view.
National direction. Vision 2030 is organised around three pillars: a Vibrant Society, a Thriving Economy and an Ambitious Nation. According to the official Vision 2030 site, the Vision was cascaded into overarching, branch and strategic objectives and is delivered through Vision Realization Programs (VRPs), national strategies and major projects. The Vision 2030 Annual Report 2025 explains that its performance indicators are defined across three levels: the first and second levels measure progress toward strategic objectives, and the third tracks the implementation of initiatives under the VRPs and national strategies.
The entity's strategy. Each entity translates its mandate, and its share of national and sector priorities, into strategic objectives. Adaa's published performance measurement framework starts here: a "strategic direction" component that looks at how the entity's objectives fit the national strategic direction, which in turn leads to the right indicators. We cover this layer in depth in our pillar on strategy management for Saudi government entities.
The operational plan. Annual activities, owners and budgets turn the strategy into work. Operational KPIs track whether that work is delivered, and they should trace back to a strategic objective rather than living in a separate spreadsheet.
The practical test is traceability. Pick any KPI on your dashboard and you should be able to say which objective it measures, which plan it sits in, and, where relevant, which national objective it contributes to.
Designing KPIs that hold up
Most KPI problems begin at design. A vague definition, an unclear formula or a missing data source will surface later as a reporting dispute.
Outcome KPIs first
Adaa's published methodology states that, when selecting KPIs, the focus is on outcome KPIs, which measure the final impact of strategic objectives rather than interim results. Output and activity measures still have a place, especially in operational plans and project tracking, but they should not crowd out the outcome measures that leadership needs at the strategic level.
A useful habit: for each strategic objective, write the outcome you want to see in plain language first ("faster licence decisions for small businesses"), then ask what measurable change would prove it.
Six conditions every KPI should meet
Adaa's measurement methodology lists the conditions that selected KPIs must meet: clarity, importance, added value, sufficiency, measurability and traceability. In practice, these translate into questions your team can ask in a design workshop:
- Clarity: Would two analysts calculate the same value from the same data?
- Importance: Does the KPI measure something leadership actually needs to steer by?
- Added value: Does it tell you something another KPI does not already show?
- Sufficiency: Taken together, do the objective's KPIs cover what the objective is meant to achieve?
- Measurability: Is there a reliable data source today, at the frequency you need?
- Traceability: Can progress be followed over time, and can the reported value be traced back to its evidence?
The question wording is ours; the six conditions are Adaa's. Always check the current methodology on adaa.gov.sa before a design cycle, because Adaa notes that its mechanisms are continuously developed.
The KPI definition card
Adaa's methodology asks entities to develop a card for each KPI and initiative, with detailed data, according to the standard form approved by the Center. Use Adaa's current form for anything you submit to Adaa. For internal design work, a good KPI card generally records:
- name and plain-language definition
- the objective it measures
- formula, unit and polarity (whether higher or lower is better)
- data source, collection method and frequency
- baseline value and baseline period
- targets by period
- owner (a named role, not a department)
- the evidence that supports each reported value
That internal checklist is general good practice, not Adaa's official form. Treat the card as a contract: once approved, any change to the formula, source or target goes through a documented change request.
Baselines, targets and thresholds
A target without a baseline is a guess. Before committing to a target, establish where the indicator stands today, using the same formula and source you will use for reporting. If no baseline exists, say so on the card and plan a baseline period rather than inventing a number.
When setting targets, consider:
- Direction and ambition. Is the target a stretch, a maintenance level or a floor?
- Phasing. Annual targets often need quarterly milestones so that drift shows up early.
- Dependencies. If the target depends on another entity's data or delivery, record that dependency.
Many entities also define thresholds, such as on track, at risk and off track, so that dashboards flag drift consistently. Agree the thresholds when you approve the KPI, not after the first bad quarter.
Data collection, evidence and verification
Under Adaa's published methodology, public entities collect performance data for indicators and initiatives periodically and provide actual values with supporting documents. Adaa then reviews and verifies the accuracy and reliability of the data against its quality standards before analysing results.
The internal lesson is simple: build verification into your own cycle before anything leaves the entity.
- Collect the value from the agreed source, on the agreed date.
- Attach evidence at the same time, not weeks later.
- Review by someone other than the person who entered the value.
- Approve by the KPI owner or the delegated authority.
- Lock the approved value so that any later correction is visible as a correction.
Keeping values, evidence and approvals together also makes it easier to respond to external assessments. For example, the Digital Government Authority (DGA) runs the Digital Transformation Measurement (Qiyas) for government entities and publishes Digital Transformation Basic Standards. Check dga.gov.sa for the current cycle's requirements; an evidence-ready KPI process supports that work but does not replace it.
From numbers to decisions: analysis and reporting
Adaa's methodology describes a data analysis stage that compares actual performance with planned performance and identifies the reasons for underperformance, along with challenges and risks. It then describes reports that show how far entities are reaching their strategic objectives by meeting targets, and the progress of initiatives, shared with stakeholders under data-sharing governance. Adaa's FAQ adds that it issues performance reports on public entities on a quarterly basis.
Inside the entity, a useful performance report answers four questions for each objective:
- Where are we? Actual against target, with trend.
- Why? The drivers behind the movement, not just the movement.
- What is at risk? Indicators approaching thresholds, dependencies slipping, data gaps.
- What do we do? Decisions requested, owners and dates.
Keep the strategic dashboard short. Leadership should see the outcome KPIs for each objective and a clear status, with the ability to drill into operational and initiative measures when needed.
Governance: ownership, review cycles and change control
KPI management is a governance process as much as an analytical one.
- Ownership. Each KPI has one accountable owner. Data entry, review and approval can be separate roles.
- Rhythm. Adaa's published framework includes an evaluation and improvement stage with quarterly KPI updates and an annual strategy review. Many entities mirror that rhythm internally: monthly operational checks, quarterly performance reviews and an annual review of the KPI set itself.
- Change control. Changes to definitions, formulas, targets or owners go through a recorded request and approval. This protects comparability over time.
- Escalation. Agree in advance what happens when a KPI breaches a threshold: who is told, by when, and who decides on corrective action.
Approval routes and escalation rules work best when they are written down and followed every time, whether in a policy, a workflow tool or both.
Common pitfalls in government KPI management
- Too many KPIs. When everything is key, nothing is. Prune indicators that fail the "added value" test.
- Activity dressed as outcome. "Number of awareness campaigns" is an output; what changed as a result is the outcome.
- Definitions that drift. A quiet formula change between quarters makes the trend meaningless.
- Evidence as an afterthought. Chasing documents at the deadline is the most common cause of late or disputed reports.
- No link to risk. KPIs going off track are often early signs of risks the entity has already identified. Reviewing them together saves time.
- Dashboards with no decisions. A report that changes nothing is a cost, not a control.
Where a platform helps, and where it doesn't
Spreadsheets can run a small KPI set. As the number of objectives, units, initiatives and reporting audiences grows, the burden shifts to version control, evidence tracking and consolidation.
Masarkum is a Saudi-built, AI-native integrated management platform. For KPI work, the relevant modules are Strategy Performance, which tracks KPIs linked to objectives with dashboards and periodic reports; Operational Plan Management, which ties annual activities, owners and KPIs back to strategic objectives; and Strategy Management, where the objectives themselves are defined and cascaded. Workflow Management supports approval routes, and GRC Management keeps risks in the same place as the objectives they threaten.
AI features such as the Adaptive Dashboard, AI Insight and AI Escalation are designed to surface drift and suggest where to look. The judgement, approvals and accountability stay with your people.
What no platform can do is choose good KPIs for you or make a weak definition strong. The design discipline in this guide comes first; tooling makes it repeatable.
If you would like to see how this works on your own KPI set, request a demo.
Related guides
- Strategy Management for Saudi Government Entities