Accounting Firm KPI Dashboard: Set It Up in an Afternoon

Why most firm dashboards fail

Firm dashboards fail for two reasons: too many numbers, and numbers compiled by hand. A twenty-tile dashboard is a report nobody reads, and a dashboard that requires someone's Friday afternoon to update stops being updated the first busy week — which is precisely when it was needed.

The fix is structural, not motivational: fewer numbers, each pulled automatically from where the work is already tracked, each owned by a person who has to say something about it once a week.

Pick five numbers, not twenty-five

A number earns a dashboard tile by passing three tests: it changes week to week, one named person owns it, and a bad value has an obvious next action. Anything that fails a test is reporting, not a KPI — interesting quarterly, useless Monday morning.

Five is not arbitrary modesty. Five numbers can all be discussed in fifteen minutes; twelve cannot, so twelve get skimmed, and a skimmed dashboard trains the team that none of it matters.

The five that earn their place

For most Canadian firms the working set is: overdue deadlines, deadlines due within seven days, open tasks per team member, recurring revenue booked, and engagements sent but not yet signed. Between them they cover risk, capacity, money and pipeline — the four questions a partner actually asks.

• Overdue deadlines — should be zero; anything else is the day's first conversation
• Due within seven days — the coming week's real workload
• Open tasks per team member — capacity and imbalance in one view
• Recurring revenue booked — the base the firm stands on
• Engagements awaiting signature — unpriced work about to start, or revenue about to stall

Prefer leading indicators over lagging ones

Deadlines due within seven days is a leading indicator — it flags trouble while it is still preventable. Revenue is lagging: by the time it moves, the cause is months old. A dashboard weighted toward lagging numbers is a rear-view mirror bolted where the windshield should be.

The SLA framing makes leading indicators legible at a glance: green for comfortably ahead, amber inside seven days, red at due or overdue. One shared rule, applied everywhere, means nobody has to interpret a colour twice.

Pull the data from where the work already lives

Every hand-compiled tile dies in busy season, so each number must come from the system where the work is tracked — deadlines from the reminder feed, workload from task assignments, revenue from service pricing. If a number has no system of record, fix that before charting it.

This is the afternoon's actual work in SpidNums: the Dashboard already computes KPI cards, a 'Needs attention' list and a recurring-revenue chart from the Client CRM, Services catalogue and Task Master, and team workload is computed live from client and task assignments. Setup is confirming services, cadences and assignments are recorded — the tiles follow from the data.

The fifteen-minute weekly review

A dashboard nobody discusses is decoration, so fix a fifteen-minute weekly slot — Monday morning works — where each number's owner says three sentences: where it stands, why it moved, what they are doing about it. The ritual, not the dashboard, is what changes behaviour.

Keep the meeting to the numbers. The moment it becomes a general status meeting, it grows to an hour and the dashboard goes back to being furniture.

Retire numbers that stop changing decisions

Review the dashboard itself twice a year and retire any number that has not changed a decision since the last review. A tile that is always green is a solved problem and can graduate to a quarterly report; its slot belongs to whatever the firm is currently getting wrong.

Add replacements one at a time. A dashboard that changes wholesale resets everyone's fluency; one that evolves a tile at a time keeps Monday's fifteen minutes at fifteen.