KPI Dashboard (2026): An Executive Template with 17 KPIs, Owners and Thresholds

TL;DR

• A KPI dashboard is one view of the 12 to 20 numbers a leadership team uses to judge whether the company is on plan. Each number needs a definition, a formula, one owner, a review cadence and a threshold that turns it red.
• The template below covers revenue, customers, operations, people and cash, with example rows you can copy into a spreadsheet or BI tool today.
• Most KPI dashboards fail for the same reasons: too many metrics, no owner per metric, no threshold, and no written reason when a number moves.
• Sentra sits under the dashboard. The dashboard shows what moved. Sentra explains why from the emails, meetings and chats behind the number, and flags it to the owner before the review.

What is a KPI dashboard?

A KPI dashboard is a single view of the key performance indicators a team uses to track progress against its targets. A good executive KPI dashboard shows each metric against plan, its trend, and whether it has crossed a threshold that needs a decision.

The most quoted definition comes from Stephen Few: a dashboard is "a visual display of the most important information needed to achieve one or more objectives" that "has been consolidated on a single computer screen so it can be monitored at a glance" (dundas.com). Two words in that definition carry the weight. "Most important" means you leave things out. "At a glance" means a reader should know within seconds which numbers need attention.

Dashboards are usually grouped into three types: strategic, analytical and operational (toucantoco.com). A strategic dashboard is what most people mean by an executive dashboard, CEO dashboard or leadership dashboard. It tracks a small set of company outcomes weekly or monthly. An operational dashboard tracks the daily or hourly work of one function. An analytical dashboard lets an analyst slice data to find a cause.

Executive dashboard vs operational dashboard

An executive dashboard answers one question: are we on plan, and if not, where? It should fit on one screen, change rarely, and be read by people who do not have time to filter.

An operational dashboard answers a narrower question for one team, such as how many orders shipped today or how many tickets breached their response target. It can have more metrics and finer time grain.

The idea of balancing financial outcomes with operating measures goes back to Kaplan and Norton's balanced scorecard, first published in hbr.org in 1992. The template below follows the same logic. Revenue and cash show the result. Customers, operations and people show the drivers that will move the result next quarter.

Executive KPI dashboard template

Copy these rows into a sheet with six columns. The thresholds are examples. Replace them with values from your own plan before the first review, and agree them with each owner.

Revenue

Customers

The net revenue retention formula above excludes revenue from new customers, so it isolates what the existing base does (solidgate.com).

Operations

For the OTIF formula and its blind spots, see our OTIF guide.

People

Cash

Burn multiple is net burn divided by net new ARR, a measure popularized by David Sacks (wallstreetprep.com). The DSO formula follows financialprofessionals.org.

That is 17 KPIs. A software company might drop OTIF. A retailer might swap net new ARR for same-store sales. Keep the five areas and the six columns. The columns are what make the dashboard usable, because they settle arguments before the meeting starts: what the number means, who answers for it, and when it counts as a problem.

Add one more column: why it moved

Every row needs a seventh field the template cannot fill for you: a one-line reason whenever the metric changes color. "Pipeline coverage fell to 2.4x because two enterprise deals slipped to Q1 after procurement asked for a new security review. Owner: CRO. Next step by Friday." The reason, the evidence and the next step turn a red cell into a decision.

KPI dashboard examples by role

The same 17 rows can be laid out differently depending on who reads them first. These are three layouts that work.

CEO dashboard

• Top row. Revenue vs plan, net new ARR, cash runway, net revenue retention. These are the four numbers a board asks about.
• Second row. Pipeline coverage, gross margin, headcount vs plan, commitments delivered on time.
• Bottom. A short list of every red metric with its owner and its one-line reason.

A CEO dashboard should be readable in two minutes. If it takes longer, move rows to the functional views below.

COO dashboard

• Top row. OTIF, cycle time, gross margin, commitments delivered on time.
• Second row. Each operations metric split by site, region or product line, so the reader can see where the problem sits.
• Bottom. Open blockers by owner and age. Our bottleneck analysis guide covers how to find the step that limits throughput.

CFO dashboard

• Top row. Revenue vs plan, gross margin, cash runway, burn multiple.
• Second row. DSO, operating expense vs budget by department, forecast vs actual for the current quarter.
• Bottom. Every variance above the materiality threshold, with its driver and owner. Our variance analysis guide shows how to break a gap into price, volume and mix.

How to build a KPI dashboard in six steps

1. Start from the decisions. List the decisions the leadership team makes each month, such as hiring pace, spend, pricing and where to put sales capacity. Pick KPIs that inform those decisions. Drop metrics that nobody would act on.

2. Write the definition before the chart. Fill in the six columns for each KPI. Two teams using different definitions of "active customer" will spend the meeting arguing about data instead of the business.

3. Name one owner per KPI. One person, not a team. The owner explains every move and proposes the next step.

4. Connect each KPI to its system of record. Revenue from the ledger, pipeline from the CRM, headcount from the HRIS. Avoid manual copy and paste, which breaks the moment someone is on holiday.

5. Show each number against plan and trend. A number alone means little. Show it against plan, against the prior period and against the same period last year. Use the same chart type for every metric so readers learn what normal looks like.

6. Set the review cadence. Most executive KPI dashboards are read weekly and discussed in depth monthly. Our guide to the weekly business review covers the meeting itself.

Common KPI dashboard mistakes

• Too many metrics. A 60-tile executive dashboard has no priority. Move secondary metrics to drill-downs and keep the top view under 20.
• Vanity metrics. Page views and total signups rarely change a leadership decision. Each KPI should connect to revenue, cost, cash or risk.
• No owner. A metric owned by "Sales" is owned by nobody. Put a name in the owner column.
• No threshold. Without a red line, every movement becomes a debate. Agree thresholds when the plan is set, not when the number is bad.
• Lagging metrics only. Revenue and churn tell you what already happened. Pair them with drivers such as pipeline coverage and cycle time that move earlier.
• Definitions that drift. If finance changes how ARR is counted, annotate the chart. Otherwise the trend line lies.
• Green that hides a problem. A metric can read healthy while the reality underneath it has changed. Treat a sudden improvement with the same suspicion as a sudden drop.
• No reason attached. A red cell with no explanation produces a meeting about what might have happened. The owner should arrive with the cause.

Why a dashboard shows what moved but not why

A KPI dashboard is built from systems of record. The ledger knows the invoice price. The CRM knows the deal stage. Neither knows that a key account paused expansion after a support escalation, or that a supplier warned of a delay in an email two weeks ago. Those reasons live in conversations, and conversations are not in the dashboard.

So the work before every review is the same. An analyst or chief of staff sees a red number, messages the owner, reads the thread, sits in a call, and writes the reason. That loop takes days, and it starts only after the number has already turned.

The gap can also run the other way. At Lenskart, reports showed a top product line about 95% in stock, while Sentra measured 12.8% availability on the shelves. About $860K of sales were lost in the two weeks before the fix. The dashboard was green. The stores and the conversations about them said otherwise.

Our root cause analysis template gives a structure for writing the cause once you have found it.

Where Sentra fits

Sentra does not replace your BI tool or your dashboard. Tableau, Power BI, Looker or a spreadsheet stay where they are. Sentra is the layer underneath that knows why the numbers moved.

It connects email, chat, meetings and documents alongside ERP, CRM, HRIS and BI, through 200+ integrations. It works out what is true now and who is working on it, and it knows when a fact became true and when it stopped being true, so a reason from last quarter is not offered as this week's explanation. When a KPI starts to drift, Sentra finds the likely cause in the threads and meetings behind it, cites each source, works out who owns the metric, and tells that person before the review.

A named person approves anything Sentra raises before it reaches anyone else. Every answer respects the permissions of its source, so a reader sees only what they could already open. Leaders can ask follow-up questions in Slack, in the Sentra app, or inside ChatGPT, Claude, Copilot or Gemini over REST and MCP. Sentra holds SOC 2 Type II and ISO 27001 certifications and deploys in the cloud, in an isolated VPC or air-gapped on premises.

The result is a dashboard where every red cell arrives with a cited reason and a named owner, and an executive briefing that writes itself from the same evidence.

To see it on your own numbers, book a demo at /demo.

How to start

• If you have no executive dashboard. Start with the 17-row template in a spreadsheet. Fill the six columns, name owners, and run it for four weeks before buying a tool.
• If you have a BI dashboard but no owners or thresholds. Add the owner and threshold columns first. Most of the value comes from that, not from new charts.
• If the dashboard is solid but reviews stall on "why". That is a context problem, not a charting problem. Look at how long it takes to get from a red number to a confirmed cause, and who chases it. That time is what Sentra removes.
• If you run on several systems that disagree. Fix definitions before visuals. Write one definition per KPI and make every system report against it.

FAQ