Before you build a business awards reporting dashboard, agree the measures

What decisions should this dashboard help us make?

Agree the choices the dashboard must change, rather than starting with the activity the team can count. The first decisions are whether to renew a category, which second scheme to enter, and whether spending should move to another channel. Measures without a decision role can wait.

Use the decision test shown below: a measure earns space only when it could alter a renewal, an entry or a spend choice. For example, a metric that cannot affect whether to renew a category does not belong in the first version. The measurement and reporting guide also frames reporting as a decision cycle, not a monthly pack.

Where should each measure come from?

Give each measure one named origin, one accountable person and a refresh date. Entry counts belong in the judging platform, cost figures in finance, and coverage figures with PR.

Naming the source system and owner lets a reader trace what was counted and who can explain it when a result is challenged.

External context can help explain movement in the programme figures. The Office for National Statistics publishes data on economic output and productivity that can help explain why entry volumes changed in a quarter. This context can distinguish a market shift from a campaign failure, without replacing the programme figures.

If the scheme includes resilience categories, business continuity standards from BSI show the evidence judges expect, which can shape what the team tracks. For travel-facing categories, use passports, travel and living abroad as the reference entrants cite, and flag rule changes that affect eligibility.

Which measures belong in the first version?

Start with eight measures or fewer, and include only figures connected to a decision. For an England-based programme, the candidate set below covers entry completion, cost, category outcomes, coverage, retention, enquiries and delivery time. It is a starting set, not an instruction to use every line.

Definitions matter more than the number of rows. If two people define win rate differently, they can argue over the figure instead of using it. The quality checklist and article on key metrics explain why clear definitions and sources make results comparable.

How often should the figures update, and who can see them?

Set an update schedule and a visibility rule for each measure before building a view. Entry and cost figures can update weekly during the entry window; coverage and enquiry data can update monthly; slower-moving items belong in the quarterly review. Match the schedule to when a decision needs the figure.

Put a cut-off date on every dashboard view so readers know which period the numbers cover. Without a date, a figure can appear current when it is not. Record the date beside the view, and use the same reporting boundary when comparing one period with another.

Match access to the decision being made. Finance can see cost lines, judging can see category performance, and the board can see the summary. The access control should follow those roles, rather than giving every reader every detail by default.

How can I compare a spreadsheet, a tool and a custom build?

Compare a spreadsheet, an off-the-shelf tool and a custom build against the same criteria. Score each option from one to five for every row, then give more weight to criteria that matter most. This keeps the choice tied to the decisions and evidence the programme needs.

For example, a team paying £400 a month for a platform that scores well on decision fit but poorly on definition stability is buying speed, not evidence. That is a conscious trade, not automatically a mistake. Use the score to make the compromise visible before committing to a supplier or build.

Who should own the dashboard, and when should definitions change?

Name the person accountable for the awards programme as the dashboard owner, even if an analyst builds the views. Ownership means defending definitions when they are challenged. Review those definitions once a year before the entry window opens, because changing one mid-cycle breaks comparability.

Show entry-fee revenue only when the fee itself is a decision variable, such as setting next-year prices. Otherwise, track cost per entry and leave revenue to the finance pack. If readers cannot summarise the dashboard in three sentences, it is too long; add measures only when a decision calls for one.

What should I do first?

Before buying a licence or booking developer time, write down the decisions, assign a source and owner to every measure, and compare the build options against the rubric. That sequence makes missing definitions visible before the team invests in a reporting tool.