Building a KPI report that stakeholders actually act on

Creating a KPI report takes five steps in order: define the audience, select KPIs and thresholds, connect and validate the data, choose a format, then add commentary and set a cadence. Done well, every period’s report names what changed, why, and who owns the fix. Data comes before design because Gartner names inconsistency in data across sources as the most challenging data quality problem.

How to create a KPI report: the steps at a glance

The full procedure fits in five steps:

1. Define the audience, goals and scope. Name who reads the report, which decisions it feeds, and what period and business units it covers.
2. Select KPIs and set targets and thresholds. Pick a small set of KPIs tied to objectives, mix leading and lagging indicators, and write down each target and its red/amber/green bands.
3. Connect, clean and validate your data. Pull from the source systems, assign an owner to every metric, document each definition, and reconcile figures that appear in more than one system.
4. Choose a format and visualizations. Decide between a live dashboard and a snapshot report, then match each KPI to a chart that answers its question.
5. Add commentary, distribute and set a cadence. Lead with the bottom line, explain each variance with a cause, an owner and a due date, and review it on a fixed schedule.

What a KPI report is and what it must contain

A KPI report is a recurring summary of the few measures that show whether the business is reaching its objectives, compared against targets and paired with the actions needed to close gaps. The KPI Institute defines a KPI as “a measurable expression for the achievement of a desired level of results” and draws the line with ordinary metrics this way: “when metrics reflect the achievement of a desired state, they become Key Performance Indicators.”

A metric is any value you can measure. A KPI is a metric you have chosen because it tracks a specific objective.

That is why selection starts with strategy. Bernard Marr puts it directly: “KPI development has to start with your strategy and the objectives the business is aiming to achieve.” The KPI Institute adds that using an indicator “simply because it appears on a popular KPI list does not guarantee that it will be relevant to a particular organization.”

David Parmenter goes further and splits measures into key result indicators for the board, result indicators for management, and performance indicators for what teams deliver. A third-party summary of his work describes his central argument as follows: lumping all of these measures together as KPIs is the reason measurement programs fail.

Across the KPI Institute, PwC, Domo and FanRuan guidance, the same components recur:

• Executive summary: PwC recommends a one-to-two-page summary of prioritized information for board pre-reads, plus a clear statement of what is needed from readers (a decision, endorsement, feedback or awareness).
• Scorecard: Each KPI shows its target, actual, variance in value and percentage, trend direction, and status such as on track, at risk or off track.
• Trend view: A single data point shows where you are; a trend shows direction and seasonal patterns.
• Commentary: Every KPI with a significant variance carries an explanation of what happened, why, and what happens next.
• Actions and owners: Each corrective action has a named owner and a due date.
• Definitions: A glossary or definition card gives each KPI’s formula, data source, owner and refresh timestamp.

How to build a KPI report: step by step

Start with the decision: decide who reads the report and what they will do with it, choose a small set of KPIs, typically five to seven per audience and up to fifteen for a leadership scorecard, lock their definitions and owners before building anything, then design the page around exceptions and close every review with owned actions.

Step 1: Define the audience, goals and scope

The audience sets everything downstream: which KPIs appear, how much detail sits behind them, and how often the report runs. The KPI Institute notes that operational teams need detailed measures for day-to-day monitoring while senior management needs a concise strategic overview. Tableau’s visual best-practices guide makes the same point for dashboards: show executives aggregated, summary-level KPIs rather than row-level transactions.

Write three things down before choosing a single metric:

• Readers: The board, the leadership team, a functional lead, or a frontline team.
• Decisions: What the readers will approve, change or escalate based on the report. PwC’s board guidance asks for an explicit statement of whether you need a decision, endorsement, feedback or awareness.
• Scope: The reporting period, business units, regions and products covered, plus what is deliberately left out.

If one report has to serve two audiences, build two views from the same data. A board summary and an operations floor report differ in grain and cadence, and forcing both into one page tends to satisfy neither.

Step 2: Select KPIs and set targets and thresholds

Choose the fewest KPIs that cover the objectives in scope, and give each one a written target and threshold. Practitioner guidance clusters around small numbers:

MIT Sloan Management Review states that goals and metrics “need to be clear and simple, and the fewer the better.”

Mix leading and lagging indicators. Lagging indicators record outcomes and leading indicators move first, and Kaplan and Norton found that a scorecard of lagging indicators alone “did not satisfy management’s goal of providing early indicators of success,” so they paired core outcome measures (lag) with performance drivers (lead). In sales, pipeline coverage is a common leading indicator and closed revenue the lagging one; in operations, preventive maintenance compliance leads and equipment downtime lags.

Set targets from evidence. The KPI Institute says a target should reflect organizational objectives, historical results, available resources and other evidence, and recommends SMART targets that are “realistic but at the same time challenging.” APQC advises establishing a baseline before collecting data and using benchmark gaps to prioritize improvement. Document the reasoning behind each target; the KPI Institute recommends a target-setting form for exactly this.

Define red/amber/green bands per KPI. No universal standard exists. The Intrafocus KPI guide states that “there are no hard and fast rules to the meanings attributed to each of the coloured areas.” Two published conventions are common:

• Tolerance band: UK councils including Hounslow, Wakefield and Somerset rate a KPI green when it meets target, amber when it falls within 10% of target, and red when it falls further short. Hounslow notes that thresholds vary by indicator.
• Percent-of-target band: Several public reports and tutorials use 100% or more as green, 80% to 99% as amber, and below 80% as red.

Neither the councils nor the tutorials state why they chose their band widths, so pick one convention, apply it consistently, and record it in the definition. Two cautions come with thresholds. The World Customs Organization’s handbook restates Goodhart’s Law: “when a measure becomes a target, it ceases to be a good measure.” And NHS England’s Making Data Count guide introduced statistical process control to address the limits of two-point comparisons and RAG reports in understanding variation.

Step 3: Connect, clean and validate your data

Lock the definition of every KPI before connecting a single source. Freshly’s CFO told CFO Dive the company “was using five versions of CAC,” one counting media spend, another agency fees, another creative assets and discounts. HBR identified conflicting or competing data sources as the most-cited reason marketers lose trust in metrics.

A definition card for each KPI should carry these fields, drawn from Domo’s and the KPI Institute’s guidance:

• Name and plain-language definition: What the KPI measures, in one sentence a non-analyst understands.
• Formula: The exact calculation, including numerator, denominator, filters and exclusions.
• Source system: The single system of record for each input.
• Owner: The person accountable for the number. DAMA’s DMBOK defines a data owner as “a business person accountable for decisions within a domain.”
• Target and thresholds: The value and the red/amber/green bands from Step 2.
• Refresh cadence and timestamp: How often the figure updates and when it last did.
• Change log: Every edit to the definition, communicated to readers.

APQC’s glossary computes days sales outstanding as average gross accounts receivable divided by total gross annual sales over 365, while an APQC blog uses 360 days and net sales. Pick one version and keep it across periods.

Deloitte’s guidance on KPI disclosure makes the same point for public companies: disclose any change in calculation from one period to the next.

Then reconcile figures that live in more than one system. Steele Consulting describes the typical drift: sales counts revenue at booking, finance at invoice, marketing at campaign attribution. Pick one system of record per figure, compare the others against it each period, and log every unexplained gap with an owner.

In a 2026 survey of 505 data leaders sponsored by Precisely and run with Drexel LeBow, 71% of respondents with an ongoing data governance program reported high or very high trust in their organization’s data, against 50% without one.

Step 4: Choose a format and visualizations

Choose the format by how readers use the report: a live dashboard suits people who monitor daily and act on changes, while a snapshot report (a PDF, deck or document frozen at a period end) suits review meetings and board packs, where everyone needs to discuss the same numbers. PwC’s board guidance combines them: a short written summary up front, with detailed dashboards and commentary as an appendix. Whichever you choose, Domo recommends a last-updated timestamp on every tile.

Match each chart to the question the KPI answers:

Gauges draw the strongest criticism. Few wrote that the circular gauges of early dashboard products “conveyed too little information, did so unclearly, and wasted a great deal of space on the screen,” and the IBCS standards advise preferring columns, bars and lines to pies and gauges.

Google’s Data Studio and Microsoft’s Power BI still offer gauges for a single measure’s health against a goal, and an ACM paper notes that research comparing gauges and bullet charts “offers conflicting findings.”

A bullet graph does the same job in less space, which matters when twenty KPIs share one screen.

Two smaller rules keep charts honest. Label units on every figure (percentage, currency, hours or count), as the KPI Institute advises. And use color sparingly; Few notes that highlighting only draws attention when it is used sparingly, so reserve red and amber for the KPIs that need a decision.

Step 5: Add commentary, distribute and set a cadence

Open the report with the bottom line. Army Regulation 25-50 calls this “bottom line up front”: put the main point at the beginning and use the active voice. Barbara Minto’s Pyramid Principle applies the same order to business writing: conclusion first, then key arguments, then supporting detail.

For every KPI with a significant variance, write commentary that covers the four elements Domo lists: the variance, its drivers, the recommended action, and the owner and timeline.

The FP and A Guy shows the difference. A weak line reads “Account: 406010 Subscription Revenue was unfavorable by $0.45M.” The stronger version breaks the $0.45M into causes:

• $0.3M from the cumulative effect of three trained sales reps resigning.
• $0.1M from product mix.
• $0.05M in customer credits after a server outage.

That version tells readers which problem is structural and which is one-off.

Report by exception. AccountingTools describes management by exception as bringing only the most important variances to management, with smaller ones routed to lower-level managers. Amazon’s weekly business review works the same way: if a metric is on track, the owner says so and the group moves on, and discussion time goes to variances.

Set the cadence by audience:

McKinsey adds that the best companies keep “the cadence of meetings and reviews constant, so they become an intrinsic part of the rhythm of everyday operations.” Keep the KPI set stable between reviews, too: CFO Dive advises CFOs to present the same metrics at every board meeting so members build a clear picture over time.

Maintain the report on purpose. A KPI Institute mid-year review checklist looks for KPIs that no longer reflect current priorities, reporting practices that take too much time, and data that lacks context. Review the definition cards at least once a year and retire any KPI nobody has acted on.

Tools for building KPI reports: spreadsheets vs dashboard software

The right tool depends on how many sources feed the report and who assembles it each period. Spreadsheets work for a handful of sources and one builder. BI software suits interactive dashboards over a governed data model. When the problem is the weekly assembly across many tools, an AI employee who runs the job on a schedule is the third option.

The main options compare as follows:

Spreadsheets. For single-owner reports and finance models, Excel supports sparklines (line, column and win/loss), conditional formatting, PivotTables and Power Query, which Microsoft says connects to hundreds of data sources. For shared, lightweight reports, Google Sheets offers the SPARKLINE function, color-scale conditional formatting and pivot tables that return up to 100,000 rows from BigQuery through Connected Sheets.

Both now include built-in AI: Copilot in Excel creates charts and PivotTables from a description, and Gemini in Sheets builds and edits spreadsheets, each on eligible plans. Microsoft retired the COPILOT worksheet function on September 14, 2026; the Copilot pane remains.

Dashboard software. Google renamed Looker Studio back to Data Studio on April 10, 2026, and renamed the paid edition Data Studio Pro. The free edition has no charge for creators or viewers; Pro costs $9 per user per project per month.

Power BI Pro lists at $14.00 per user per month paid yearly, and Microsoft no longer sells new Premium per-capacity P SKUs, directing customers to Fabric F SKUs. Power BI data alerts work only on gauges, KPIs and cards.

Tableau Cloud Standard lists Creator at $75, Explorer at $42 and Viewer at $15 per user per month, billed annually, and Tableau Public is free but every published workbook is public.

Where an AI employee fits. BI tools display data once someone has modeled it, and spreadsheets need someone to refresh, check and send them. Viktor takes the assembly job itself (what an AI employee is explains the model): he pulls figures from the connected tools, builds the report, and delivers it on a schedule, and he can also produce the Excel file with formulas that finance already works from. If the need is one interactive dashboard over one warehouse with an analyst maintaining it, a BI tool built for that scope may fit better. Start your first recurring report free with up to $100 in credits, no credit card →

KPI report examples by department

The KPIs below are common starting points, with the formulas their sources give. Write your chosen version into the definition card, because several have competing formulas:

Teams need a definition card for CAC. HBR notes that both its numerator and denominator require judgment, and distinguishes blended, channel, cohort and marginal CAC.

Worked example: a weekly operations KPI report. The report below is an illustration, not a benchmark. Every target and actual is invented; replace them with your own operating numbers and targets. Status uses the 10% tolerance rule from Step 2.

Bottom line: OTIF fell to 91% against a 95% target (amber), and late carrier pickups at one distribution center caused most of the misses. The logistics lead owns a carrier review, due Friday. The planning lead needs to decide on the slow-moving SKU list because inventory turns are red.

The commentary block for the two exceptions would read:

• OTIF (amber): OTIF dropped three points week over week. Missed carrier pickup windows at one DC account for most late orders; complete-shipment rates held. The logistics lead reviews carrier performance and reports back by Friday.
• Inventory turns (red): Turns have stayed below 7.0 for two weeks because slow-moving SKUs grew. Decision needed: approve markdowns or a pause on reorders for the flagged list. The planning lead brings the list to Monday’s review.

The annotations put each result in context, but published benchmarks rarely match your definitions exactly. McKinsey found no standard definition for OTIF in the consumer sector: 67% of respondents preferred measuring on-time against the requested delivery date. Set targets from your own baseline first and use benchmarks as a reference.

How an AI employee can build and send your KPI report

Viktor takes the weekly KPI report as a standing job: he pulls the numbers from the tools where they live, builds the report, and delivers it on the schedule you set. Viktor is an AI employee who lives in Slack and Microsoft Teams and connects to 9,800+ tools, most through one-click OAuth; teams can also start in the web app at app.viktor.com.

Take an e-commerce stack. A plain-language request covers the whole job: “Every Monday at 8am, pull last week’s orders and revenue from Shopify, ad spend from Google Ads and Meta Ads, and payouts from Stripe. Calculate blended CAC and return on ad spend against our targets, mark anything outside the amber band, and post the summary in #ops with a link to the full report.” Viktor sets that up as a scheduled task and runs it every week. Before handing it over, check how he connects to your tools →

The report itself can take whatever form readers already use:

• Doc kept current at a link: Viktor writes the report from live data and keeps it updated at the same link, with access control.
• Spreadsheet or deck: An Excel file with working formulas, a PowerPoint deck for the monthly review, or a PDF for the board pack.
• Channel post: A bottom-line summary in Slack or Teams, with the exceptions listed first.

He follows documented definitions as instructions. Give him the definition cards from Step 3 and he calculates each KPI the documented way; you can add a weekly check of Shopify revenue against Stripe payouts to the same request, with any gap listed for an owner to review.

If the report has a structural hole, such as twenty KPIs with no targets, he can flag it and propose a shorter set with thresholds before building it.

Handing over an existing report takes one recording. Screen-record yourself building it, narrating as you go, and Viktor turns the recording into a written skill your team can open and correct. If the job repeats, he proposes a scheduled task that stays paused until someone approves it.

Sensitive actions wait for an approval card with Approve and Reject buttons, and admins can mark any tool as needing approval or forbidden.

Cost stays visible: the Activity view shows credit use by person and task, each scheduled task shows the time it saved and its credit cost, and spend limits cap the total. Shared workspace credits and current plans cover the details.

Hampton handed reporting to Viktor. In 44 days he connected 24 tools, took over reporting, built 12 dashboards and took on 26 recurring jobs per week, and Hampton avoided $440K in planned hires, according to Hampton’s customer story. Hand over your Monday KPI report and start free with up to $100 in credits, no credit card →

FAQ

A useful KPI report pairs a focused set of measures with consistent definitions, a review cadence and owned actions.

How many KPIs should a KPI report include?

Five to seven KPIs per executive report is the range Domo recommends, and Klipfolio suggests 3 to 7 per audience. APQC recommends 5 to 15 strategic KPIs for leadership review. Treat these as practitioner guidance, and cut any KPI that has stopped prompting decisions.

How often should a KPI report be updated?

Update it at the speed of the decisions it supports. Frontline operations often review daily, team leads weekly, leadership monthly and the board quarterly. The data can refresh more often than the meeting; Power BI Pro, for example, allows 8 scheduled refreshes a day.

Should I use a dashboard or a snapshot report?

Use a live dashboard for monitoring and a snapshot for review meetings. A snapshot freezes the numbers so everyone discusses the same figures, and a dashboard lets owners spot changes between meetings. PwC’s board guidance pairs a written summary with dashboards in an appendix.

How do I set a KPI formula and target?

Write the formula with its numerator, denominator, filters, time window and single source system, then record it on a definition card with an owner. Set the target from your objectives, your historical baseline and available resources, check it against an external benchmark where one exists, and document the red/amber/green bands and the reasoning.

How do I present a KPI report so stakeholders act on it?

Put the bottom line in the first sentence, show only the exceptions in detail, and give each one a cause, an owner and a due date. Use the same KPI set and layout every period, so readers spend their time on what changed. Close each review by confirming actions and owners.

Pick the one report your team rebuilds by hand every week and hand it over first. Try Viktor on that report free with up to $100 in credits, no credit card →