Metrics
CAO Metrics Dashboard: KPIs that matter
A CAO dashboard should show whether administrative services are meeting their commitments, what they cost, and where risk is building. This guide sets out the KPIs most CAOs choose from, how to define them, how often to review them, and how to lay out a dashboard that leads to decisions rather than discussion about the numbers.
Updated 2026-10-029 min read
Dashboard goals
- Visibility
- Service quality
- Cost control
- Risk clarity
KPIs
CAO KPIs: definitions, purpose, and cadence
The table lists the metrics CAOs most commonly draw on, grouped by category. For each, it gives a working definition, the reason it earns a place on a dashboard, and a typical review cadence. Pick a few per category, not all of them.
| Category | Metric | Definition | Why it matters | Typical cadence |
|---|---|---|---|---|
| Service delivery | SLA compliance | Share of requests completed within the agreed service level, by service. | The clearest signal of whether internal customers are getting what was promised. | Weekly |
| Service delivery | Backlog volume and aging | Open requests, grouped by how long they have been waiting. | Aging reveals hidden queues that an average resolution time can mask. | Weekly |
| Service delivery | Internal customer satisfaction | Short post-service survey score or periodic stakeholder survey. | Captures quality issues that timeliness measures miss. | Monthly or quarterly |
| Service delivery | First-contact resolution | Share of requests resolved without a handoff or reopen. | Handoffs drive cost and frustration; this shows where routing breaks. | Monthly |
| Efficiency | Cost per service unit | Fully loaded cost of a service divided by its volume (per invoice, per hire, per ticket). | Lets you compare cost over time and test whether changes saved money. | Quarterly |
| Efficiency | Process cycle time | Elapsed time from start to finish of a key process, such as procure-to-pay or hire-to-onboard. | End-to-end time is what the business experiences, not each team's slice. | Monthly |
| Efficiency | Automation or self-service rate | Share of transactions completed without manual intervention. | Shows whether technology investment is actually changing how work gets done. | Quarterly |
| Financial | Budget variance by service line | Actual spend against budget, with the reason for any material gap. | Keeps the CAO and CFO working from the same numbers. | Monthly |
| Financial | Vendor performance | Supplier results against contracted service levels for major contracts. | Large administrative contracts can fail quietly without a scheduled check. | Quarterly |
| Financial | Savings delivered vs committed | Savings realized against the savings promised in approved business cases. | Separates savings that were booked from savings that were claimed. | Quarterly |
| Risk and compliance | Open audit findings and age | Number of open findings, by severity and days past agreed close date. | Overdue findings are a common source of board and audit committee concern. | Monthly |
| Risk and compliance | Policy compliance rate | Share of sampled transactions that followed policy, such as purchasing or travel. | Shows whether controls work in practice, not just on paper. | Quarterly |
| Risk and compliance | Continuity readiness | Share of critical services with a tested continuity plan in date. | Untested plans tend to fail when they are needed. | Quarterly |
| People | Vacancy and time to fill in the CAO portfolio | Open roles in administrative teams and how long they stay open. | Persistent vacancies are often a leading indicator of service decline. | Monthly |
| People | Staff engagement or turnover | Engagement survey results or voluntary turnover for administrative teams. | Service quality rarely holds up for long when the teams delivering it are under strain. | Quarterly or annually |
Treat this as a long list to choose from, not a dashboard to copy. Most executive views work best with a few metrics per category; the rest belong on service-level views.
Reporting
How to present CAO metrics
Metrics should support decisions, not just reporting. Keep dashboards focused and tied to outcomes.
Dashboard design tips
- Use trend lines and benchmarks, not single numbers.
- Highlight leading indicators for risk.
- Include narrative context for variances.
- Keep the executive view to a set the audience can read in a few minutes.
Executive reporting cadence
- Weekly summaries for service health.
- Monthly deep dives on cost and utilization.
- Quarterly trend analysis for governance updates.
Selection
How to pick the right KPIs
A common dashboard failure is picking metrics that are easy to measure rather than metrics that change behavior. Start from the question the dashboard should answer for the executive audience, then choose the smallest set of metrics that, taken together, can answer it. Every other metric belongs on a deeper view, not the executive page.
Three questions a CAO dashboard must answer
- Are administrative services meeting commitments to internal customers?
- Is the cost of those services moving in the direction the organization needs?
- Are the risks attached to those services trending up, down, or holding steady?
What a strong KPI looks like
- It has a single owner who can move it.
- It has a target that is non-trivial to meet and credible to defend.
- It updates on a cadence that matches the decision it supports.
- It is paired with a leading indicator that gives early warning.
Pitfalls
Common dashboard pitfalls and how to avoid them
Even well-designed dashboards drift. The patterns below show up often enough that it is worth designing around them from the start.
Vanity metrics
Metrics that look impressive but are not tied to a decision waste executive attention. If a number cannot trigger an action when it changes, it does not belong on the executive view. Move it to the operations layer where the team that owns the service can use it day-to-day.
Single-period numbers
A dashboard that shows only this month's number invites overreaction to noise. Pair every KPI with a trend line and a benchmark — a previous period, a peer, or a target — so the audience can read direction and not just position.
No narrative
Metrics without a sentence of context get misread. A short narrative that explains why a metric moved — driver, one-off, intervention in progress — is the difference between a useful review and a guessing game. Keep narratives short; one or two sentences per movement.
Too many KPIs
The fastest way to weaken a dashboard is to keep adding metrics. Set a firm cap on the executive view, commonly somewhere between a dozen and twenty KPIs, and hold the line. The discipline of adding by removing forces real prioritization. Lower-level metrics belong in service-specific views, not in the CAO summary.
Definitions that drift
If the way a metric is calculated changes without notice, trend lines become meaningless. Record definition changes in the metric dictionary and mark the break on the chart so readers do not mistake a new method for a real change.
Targets that invite gaming
A single target pursued in isolation can be met in unhelpful ways, such as closing tickets early to protect a resolution-time number. Pair speed measures with quality measures, such as reopen rates or satisfaction, so one cannot improve at the expense of the other.
Layout
How to lay out a CAO dashboard
A dashboard that tries to serve every audience on one page usually serves none of them well. Many CAOs organize reporting in three layers, each with a different audience and level of detail, built from the same underlying data.
Executive summary
One page for the CEO, board, or council: headline status by category, trends, and the few items that need a decision.
Portfolio view
For the CAO and direct reports: each service line's KPIs, targets, owners, and the actions under way on anything off track.
Service view
For service managers: daily or weekly operating detail such as queues, volumes, and individual exceptions.
What belongs on the executive page
- A status indicator per category, with the rule for each color written down.
- Trend over several periods, not a single number.
- The target or comparison next to each metric.
- One or two sentences on any significant movement.
- A short list of decisions or support requested.
What to leave off
- Activity counts that do not connect to a decision.
- Metrics with no owner or no target.
- Raw data tables that the audience will not read.
- Metrics that have not moved and are not at risk; report them by exception.
Build
Building the dashboard step by step
The hardest part of a CAO dashboard is rarely the visualization. It is agreeing on definitions, owners, and data sources. Working through these steps in order avoids rebuilding the dashboard after its first review.
Define
- Write down the questions the dashboard must answer for its main audience.
- Choose candidate metrics for each question and draft a one-line definition for each.
- Agree the calculation, data source, and refresh frequency with the metric owner.
- Set a target or comparison point, and agree what counts as amber and red.
Run and refine
- Run a few cycles manually before investing in automation; definitions usually change.
- Review each metric after a few periods: did it prompt any decision?
- Retire metrics that never change behavior, and record why.
- Keep a metric dictionary so definitions survive staff changes.
Agree definitions with finance early. Cost and budget metrics should reconcile with the figures the CFO reports. If they do not, every review turns into an argument about whose number is correct. The CAO vs CFO guide covers how the two roles usually share this ground.
Sector notes
How CAO dashboards differ by sector
The core categories hold across sectors, but the audience and the emphasis change. Adjust the executive layer to fit the people who will read it.
Government and public bodies
Reports often go to elected officials and may become public documents. Expect more emphasis on budget adherence, resident-facing service levels, and audit status, and write narratives that a non-specialist reader can follow. See the CAO in government guide.
Healthcare
Administrative metrics sit alongside clinical quality and safety reporting. Facilities, supply chain, and regulatory readiness tend to carry more weight. See the CAO in healthcare guide.
Higher education and schools
Academic cycles drive demand peaks, so compare metrics with the same point in the previous cycle rather than the previous month. Governing boards often want enrollment-linked cost measures.
Private enterprise
Cost per unit and cost as a share of revenue tend to dominate, with internal chargeback data making service cost more visible. Link administrative metrics to business-unit performance where you can.
Related guides
FAQ
CAO metrics dashboard questions
What KPIs should a chief administrative officer track?
Most CAOs track a small set of measures in four or five categories: service delivery (such as SLA compliance and backlog aging), efficiency (such as cost per service unit and cycle time), financial stewardship (such as budget variance), risk and compliance (such as open audit findings), and people (such as vacancies in administrative teams).
How many KPIs should be on a CAO dashboard?
Keep the executive view small enough to read in a few minutes, commonly somewhere between a dozen and twenty measures in total. Additional metrics belong on portfolio or service-level views where the teams who own them can act on them.
How often should a CAO dashboard be updated?
Match the cadence to the decision each metric supports. Service health metrics are often reviewed weekly, cost and utilization monthly, and trend, risk, and governance reporting quarterly for the CEO, board, or council.
What is the difference between a leading and a lagging indicator for a CAO?
A lagging indicator reports a result that has already happened, such as SLA compliance last month. A leading indicator gives early warning, such as a growing backlog or rising vacancies, so the CAO can act before the lagging measure slips.
Who should own each metric on a CAO dashboard?
Each metric should have one named owner who can influence it, usually the leader of the service it measures. The CAO owns the dashboard as a whole and the conversation about which metrics stay on it.
Build your dashboard fast
Start with the ready-made metric list and customize to your organization. Pair this with the operating model guide to make sure each metric has an owner who can act on it.
Download KPI list