KPI Template: The Four-Question Worksheet for Every Department
A free KPI template every department can copy: one row per KPI, with the question it answers, a baseline, a target, one owner and a review date.
A KPI template is only useful if it forces the decisions that most KPI lists skip: where the number stands today, where it should be and by when, and which one person owns it. The worksheet below does that in seven columns, one row per KPI, and it ties every row back to one of four plain questions about your strategy: Where are we now? Where are we going? What could affect us? What must we deliver?
Copy it, give one copy to each department head, and ask for five to seven rows back. Below the blank template you will find what goes in each column, two departments filled in as a worked example, a one-KPI definition card for the measures that need more detail, and the checks to run before anyone signs off.
The KPI template
One table per department. Five to seven rows. Every cell filled in before the year starts.
Department: ____________ Head of department: ____________ Financial year: ________
| # | KPI | Which question it answers | Baseline (value and date) | Target (value and date) | Owner | How measured | Review cadence |
|---|---|---|---|---|---|---|---|
| 1 | |||||||
| 2 | |||||||
| 3 | |||||||
| 4 | |||||||
| 5 | |||||||
| 6 | |||||||
| 7 |
The table pastes cleanly into a spreadsheet or a document. Keep it to one page per department. If a department's sheet runs to a second page, it has too many KPIs.
What goes in each column
KPI. The name of the number, written so that two people would calculate the same figure. "Customer satisfaction" is too loose. "Share of delivery surveys scoring 4 or 5 out of 5" is a KPI.
Which question it answers. One of the four:
- Where are we now? Rows that exist because you cannot yet measure something the strategy depends on. The KPI is usually "start measuring it", with a target date for having a reliable baseline.
- Where are we going? Rows that track progress toward a priority. Most of the sheet lives here.
- What could affect us? Guard rows that warn you early about a known risk: a competitor, a supplier, a staffing problem.
- What must we deliver? Rows that protect a commitment you have already made, to customers, the board, a lender or a regulator.
If you cannot pick a question for a row, the row is probably an activity count rather than a KPI. Cut it or rewrite it.
Baseline (value and date). Where the number stands today, and the period it was measured over. "88%, last six months" is a baseline; "about 90%" is not. A baseline that is an estimate is fine as long as the cell says so.
Target (value and date). Where the number should be, and when. Write the target with the baseline in front of you. If the jump looks unreasonable, it probably is. For how to set targets that move from a real starting point, see leading and lagging indicators.
Owner. One named person. Not "Sales", not "the leadership team", not two names with a slash between them. The owner reports on the number and explains it when it slips. Why a single name matters is covered in accountability in the workplace.
How measured. The system the number comes from and how it is calculated. If the honest answer is "an analyst builds it by hand", write that down. It tells you how often you will actually see it.
Review cadence. How often the owner looks at it and how often the leadership team does. Fast-moving numbers weekly, most numbers monthly, everything at the quarterly review.
A worked example: two departments, filled in
The example below uses Harbor Supply, the fictional 200-person regional distributor of plumbing and heating parts from our guide on how to create KPIs. It is an example, and every figure is illustrative. Its strategy is to grow from $60 million to $75 million in three years by winning more of each contractor's spend, while holding gross margin at 22% and raising on-time-in-full delivery from 88% to 96%.
Sales
| # | KPI | Which question it answers | Baseline | Target | Owner | How measured | Review cadence |
|---|---|---|---|---|---|---|---|
| 1 | Revenue from the top 300 accounts | Where are we going? | $33.6M, last financial year | $37.5M, this financial year | Sales Director | Sales ledger, accounts tagged top 300 | Monthly |
| 2 | Top 300 accounts with a recorded share-of-wallet estimate | Where are we now? | 40 of 300, today | 300 of 300, end of quarter 2 | Key Accounts Manager | Account review form in the CRM | Monthly |
| 3 | Average share of wallet, top 300 | Where are we going? | ~35% (estimate from 40 reviews) | 38%, year-end | Key Accounts Manager | Account reviews, updated twice a year | Quarterly |
| 4 | Quotes converted to orders within 7 days | Where are we going? | 46%, last 6 months | 55%, year-end | Inside Sales Lead | CRM quote and order dates | Weekly |
| 5 | Gross margin on top 300 accounts | What must we deliver? | 21.1%, last financial year | 21% or better, every month | Sales Director | Finance margin report by account | Monthly |
| 6 | Revenue from the 40 accounts nearest the new competitor branch | What could affect us? | $6.2M, last financial year | $6.2M or more, year-end | North Branch Manager | Sales ledger, named account list | Monthly |
Notice what is not on the list: calls made, visits logged, emails sent. Those are useful for a branch manager to watch, but none of them answers one of the four questions directly. Row 2 is a "start measuring" row; once every top account has an estimate, it retires and row 3 becomes reliable.
Customer service
| # | KPI | Which question it answers | Baseline | Target | Owner | How measured | Review cadence |
|---|---|---|---|---|---|---|---|
| 1 | Calls per 100 orders | Where are we going? | 18, last 6 months | 12, year-end | Customer Service Manager | Phone system call count ÷ orders shipped | Monthly |
| 2 | Issues resolved on the first call | Where are we going? | 71%, last 6 months | 80%, year-end | Customer Service Manager | Ticket system, closed with one contact | Weekly |
| 3 | Delivery complaints per 1,000 orders | What must we deliver? | 9, last 6 months | 5 or fewer, year-end | Service Team Lead | Ticket category "delivery" ÷ orders | Monthly |
| 4 | Delivery surveys scoring 4 or 5 out of 5 | Where are we going? | 78%, last quarter | 85%, year-end | Customer Service Manager | Post-delivery text survey | Monthly |
| 5 | Callbacks made within 2 hours | What must we deliver? | 64%, last quarter | 90%, end of quarter 2 | Service Team Lead | Ticket timestamps | Weekly |
| 6 | Credit notes issued for service errors | What could affect us? | $210K, last financial year | $120K or less, this year | Customer Service Manager | Finance credit note codes | Monthly |
Row 1 is the interesting one. Most calls to Harbor Supply's service desk are about late deliveries, so the number only falls if operations fixes the delivery problem. It connects customer service to the company's reliability priority without giving it a KPI it cannot influence at all.
For starting rows in other functions, KPI examples by department has five to seven per department, each with the paired measure that stops it being gamed.
The KPI definition template: one card per KPI
The worksheet is the summary. Some KPIs need more detail than a row can hold, usually the ones where a disagreement about the definition would change the number. For those, add a definition card:
| Field | Example: Delivery complaints per 1,000 orders |
|---|---|
| Name | Delivery complaints per 1,000 orders |
| Why it matters | Protects the next-day delivery promise to customers |
| Which question it answers | What must we deliver? |
| Definition | Tickets logged with category "delivery" (late, short, damaged or wrong item), divided by orders shipped in the same month, times 1,000 |
| Excludes | Complaints about price or product quality |
| Data source | Ticket system; order count from the warehouse system |
| Baseline | 9 per 1,000, average of the last 6 months |
| Target | 5 or fewer per 1,000 by year-end |
| Owner | Service Team Lead |
| Paired with | Callbacks within 2 hours (so complaints are not discouraged or left unlogged) |
| Review cadence | Monthly by the owner; quarterly by the leadership team |
The "Excludes" and "Paired with" lines prevent most of the arguments that happen later in the year. Write them down while everyone agrees.
Five checks before a department signs its sheet off
- Five to seven rows. Fewer than five measures one part of a job that has several. More than seven, and the department will quietly choose which three to care about.
- Every row has a question. And the sheet as a whole touches at least three of the four. A sheet with no "What could affect us?" rows has not thought about its risks.
- No empty baseline cells. If a baseline is unknown, the KPI becomes "start measuring it" with a date. A target without a baseline is a guess.
- One name per owner cell. Owners can share the work. They cannot share the accountability.
- It survives a read across. Put every department's sheet side by side before the year starts and look for rows that pull against each other, such as purchasing cutting stock while operations needs availability. Settle each conflict now, by agreeing which one gives way or adding a measure that keeps both honest.
Common mistakes with KPI templates
Filling it in alone. A head of department who writes the sheet the night before the planning meeting produces a sheet nobody else has agreed to. Fill it in with the people who will be measured by it.
Copying the company number down. If every department's first row is "company revenue", the template has been used as a form, not a worksheet. Each row should be something that department can move.
Leaving the review cadence blank. Without it, the sheet gets read once in January and again at the annual review, when it is too late to change anything.
Never retiring a row. Some KPIs finish their job, like row 2 in the sales example. Retire them at the quarterly review and replace them, rather than letting the sheet grow to twelve rows.
Frequently asked questions
What should a KPI template include?
At minimum: the KPI's name, the priority or question it serves, a baseline with its date, a target with its date, one named owner, how the number is measured and how often it is reviewed. Without the baseline and the owner, a template is just a list of numbers somebody would like to improve.
How many KPIs should each department have on its template?
Five to seven. That leaves room for one or two outcome measures, two or three early measures that predict them, and one guard measure that stops the outcome being hit the wrong way. If a department needs more, some of its rows probably belong to a team below it.
Should the KPI template be a spreadsheet or a document?
Whichever your leadership team will actually open. A spreadsheet makes it easier to update baselines and track progress; a one-page document is easier to read in a planning meeting. The columns matter more than the format.
Who should fill in a department's KPI template?
The head of department, with the people who will be measured by it, after the leadership team has answered the four questions at company level. A department sheet written before the company priorities exist tends to describe what the department already does rather than what the strategy needs from it.
Build it live, on your own strategy
Measure What Moves takes your strategy through the four plain questions with you: where are we now, where are we going, what could affect us, what must we deliver. AI drafts the KPIs as you go; you sign off every line. Free for CEOs and managing directors.
Register freeKeep reading
Accountability in the Workplace Starts With One Owner per KPI
Accountability in the workplace is a structure, not a trait: one named owner per KPI, contributors around them, and a review that asks the owner first.
How to Create KPIs From the Strategy You Already Have
How to create KPIs from your existing strategy: four plain questions, 5–7 KPIs per department, and a baseline, target and owner for every one.
Leading and Lagging Indicators: Baselines and Targets That Mean Something
Leading and lagging indicators explained with worked examples: how to pair them, set a KPI baseline, and derive a target that is more than a guess.