Balanced Scorecard
Run a four-perspective balanced scorecard — financial, customer, internal process and learning measures with direction-aware attainment, RAG status, a balance check and a board-ready report. Nothing is uploaded.
Version 1.0.0 · Updated Aug 6, 2026
Overview
Frequently asked questions
How does the Balanced Scorecard licence work?
It is a one-time purchase for a downloadable tool — no subscription. You buy it once and the file is yours to keep and use.
Can I try the Balanced Scorecard before buying?
Yes. Use the Try online button for a fully interactive demo with sample data already loaded — nothing to install and nothing is saved.
Does my data stay private?
Yes. The tool is a single HTML file that runs entirely on your computer and makes no network requests, so nothing you enter is ever uploaded or shared.
Do I need Excel or any other software?
No. It replaces the spreadsheet template entirely: open the file in your browser (Chrome, Edge, Firefox or Safari) on Windows, Mac, Linux or a tablet, and start working.
How to use Balanced Scorecard
The complete in-tool guidance, reproduced here so you can read it before you download.
What this tool does
CM8-232 is a working balanced scorecard. The balanced scorecard is the strategy measurement framework developed by Robert Kaplan and David Norton in the early 1990s, built on one observation: financial results alone tell you where you have been, not where you are going. You record one reading per measure per period — the measure, its actual, its target and who owns it — and the tool works out direction-aware attainment, flags each measure red, amber or green, draws the four-perspective picture, tracks the trajectory across periods and prints a report fit for a board pack or a management review.
Everything runs inside this single file. There is no account, no upload and no network request of any kind, so your margins, customer scores and strategic targets never leave the computer you are using.
The four perspectives
The scorecard forces you to answer four questions at once, because answering only one lets the others quietly rot:
- Financial — how do we look to the people who own the business? Revenue, margin, cash conversion, recurring revenue share. These are the results of everything else.
- Customer — how do we look to the people who pay us? On-time delivery, satisfaction, retention, complaints. Customers experience your business months before the accounts do.
- Internal process — what must we excel at for customers to see what they see? Yield, turnaround times, error rates — the handful of processes your promises depend on.
- Learning & growth — can we keep improving? Skills coverage, training, improvement activity, systems capability. This is where next year's internal-process performance is being built, or not.
The order is a causal chain read upwards: capable people improve processes, better processes deliver for customers, satisfied customers deliver the financial results. A business that manages only the top of the chain is steering by the wake.
Objectives, measures, targets, initiatives
The discipline most scorecards skip is that these are four different things, and every row here carries all four:
- An objective is what the strategy says you must achieve — "grow recurring revenue". It is a sentence, not a number.
- A measure is how you will know — "recurring revenue share %". If you cannot name a measure, the objective is a slogan.
- A target is the value that counts as success this period. A measure without a target is a dashboard ornament: interesting, never actionable.
- An initiative is what you are doing to move it — the project, the programme, the change. A red measure with no initiative behind it is a fact being observed, not a problem being worked.
The commentary field completes the row: one or two sentences on what moved and why, written when the reading is entered, while the reason is still known. Six months later the commentary is the only part anyone wishes had been filled in.
Choosing measures
Aim for two to four measures per perspective — eight to sixteen in total. A scorecard with forty measures is a data warehouse with opinions; nobody can hold it in their head, so nobody does.
Mix leading and lagging indicators deliberately. Financial measures lag — they report decisions made months ago. Learning measures lead — cross-training done this month shows up in yield next quarter and in margin the quarter after. If every measure on your scorecard is lagging, the scorecard can only describe the past; the learning and internal perspectives are where the leading indicators live, which is exactly why they are the perspectives that get dropped first.
Prefer measures that already exist in the business over measures that need a new collection exercise, and prefer a slightly crude measure someone owns over a precise one nobody does. Name one owner per measure — the person the review asks "what happened and what are you doing?"
Direction-aware attainment
Measures point in different directions — revenue up is good, quote turnaround down is good — so a naive actual-over-target ratio would reward the wrong movement half the time. The tool computes attainment according to the direction you set:
Higher is better: attainment = actual ÷ target × 100 Lower is better: attainment = target ÷ actual × 100
Either way, 100 means exactly on target and more is better. A quote turnaround of 5 days against a 4-day target scores 4 ÷ 5 × 100 = 80 — the same shortfall reads the same way whichever direction the measure points.
Two honesty rules apply. First, the arithmetic breaks near zero: a "lower is better" target of zero, or an actual of zero, makes the division meaningless, so the tool shows — rather than a confident nonsense number, and it will not save a zero target at all. Set the smallest meaningful target instead. Second, displayed attainment is capped at 200, so one measure that doubled its target cannot visually drown seven that missed theirs — a cap, not a correction, and the reading itself is always shown alongside.
Each measure then reads as On target (attainment 100 or better), Watch (below 100 but at or above the amber threshold — 90 by default, adjustable in Settings) or Off target (below the threshold).
Running the monthly review
Enter the readings before the meeting, not during it, and use month-end dates so periods line up. Then spend the meeting on two things only:
- The reds. For each Off-target measure: is the initiative behind it actually running? Has anything changed since last month? If the same measure is red three months running with the same initiative, the initiative is not working and the review should say so.
- The trajectory. The strategy-trajectory chart averages the perspective averages, so a perspective with two measures counts the same as one with six. Is the line rising? Is one perspective persistently the floor? The weakest-perspective tile names it.
Do not read every number aloud — that is what the printed scorecard table is for. A review that walks through sixteen measures one by one runs long and decides nothing; a review that argues about the three reds and the direction of the line earns its hour. The movement table shows what changed since last period, with each measure's commentary beside it, so "why did that move?" is answered before it is asked.
The balance warning
The balance tile checks the thing the scorecard exists to protect: that all four perspectives are actually being measured. A scorecard with nine financial measures and one learning measure is not a balanced scorecard — it is a finance pack wearing a costume, and it will drift exactly the way finance packs drift: toward this quarter at the expense of the ones after it.
The tile names any perspective with no measures in the latest period, and flags perspectives carrying only one — a single measure is a single point of failure, gameable and fragile. Two to four per perspective is the working range. If a perspective is empty because you genuinely cannot think of a measure for it, that is a finding about the strategy, not about the tool.
Cascading to teams
One scorecard per level, linked by logic rather than by copying. The company scorecard's internal-process measure — first-pass yield, say — becomes a team scorecard's financial-equivalent objective; the team then chooses its own process and learning measures that drive it. A useful test at every level: can the people being measured actually move the measure? A shop-floor team measured on group operating margin can do nothing but watch it.
Practically: keep one file per scorecard. Export each as its own .json, and let each team own its readings. Resist the urge to roll every team's measures into one giant register — the whole point of cascading is that each level reviews a scorecard it can hold in its head.
FAQ
How often should readings be entered? Monthly is the working rhythm for most measures; quarterly for slow-moving ones such as staff surveys. Use the month-end date either way, and enter a reading even when the number has not moved — a flat line is information, a gap is a mystery.
What if a measure has no sensible target? Then it is context, not a scorecard measure. Track it elsewhere. Every row here needs a target because attainment is the whole engine.
Percentages, days, scores — can they really share one chart? Yes, because the charts compare attainment, not raw values. 94.2% against a 95% target and 8.3 against a target of 8 both become attainment figures on the same 100-point scale. The unit label keeps the underlying reading readable.
Should targets change during the year? Rarely, and openly. A target quietly lowered to turn a red green defeats the instrument. If the world genuinely changed, change the target and say so in the commentary.
Is a scorecard the same as a KPI dashboard? No. A dashboard shows numbers someone chose to display. A scorecard derives its measures from strategic objectives across all four perspectives, gives each a target and an owner, and exists to force a monthly conversation. The discipline, not the charts, is the difference.
Saving your work
Readings, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window, a second machine or a clean-up tool that clears site data will not have it.
Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the readings for spreadsheet work. Reset asks twice, then erases everything this tool has stored. There is no undo. A scorecard states your strategy and your shortfalls in one page — treat exports as confidential.
Accuracy & disclaimer
The arithmetic here is deliberately simple and the tool does it faithfully — but a scorecard reports the strategy you chose to measure, nothing more. It cannot tell whether the objectives are the right ones, whether a target is ambitious or soft, whether a measure is being gamed, or whether the readings entered are accurate. Attainment percentages from different measures are comparable as progress-against-target, not as statements that the targets themselves were equally demanding.
Where the attainment division is meaningless — zero targets, zero actuals — the tool shows "—" rather than pretend, and caps displayed attainment at 200 so an outlier cannot distort the picture. This is a management reporting and review aid, not financial, strategic or investment advice, and a printed scorecard is not a substitute for the conversation it is meant to start.
Related tools
Project cash month by month and know your runway under different scenarios.
Build a scored SWOT analysis — strengths, weaknesses, opportunities and threats ranked by impact and likelihood, turned into TOWS actions with owners and review dates, printed as a strategy-ready report. Nothing is uploaded.
OKR Planner
Plan and track OKRs — objectives with measurable key results, weekly confidence check-ins, progress that treats stretch goals differently from commitments, and a print-ready quarterly review. Nothing is uploaded.