A recruitment dashboard should help a team decide where to investigate and what to improve. It should not make a small number of applications look more conclusive than they are. Start with a few measures you can define and maintain accurately.

Use aggregate process information where possible. Restrict access to candidate-level records and avoid collecting personal data simply because a dashboard could display it.

Define the stages before counting

Agree what counts as an application received, an application reviewed, an interview completed, an offer made and an offer accepted. If different colleagues use the same label differently, the numbers will be difficult to interpret.

Record how withdrawn applications, duplicate submissions and cancelled vacancies are handled. Keep the definition consistent across the reporting period and note any change. A clear definition is more valuable than an elaborate chart built from inconsistent records.

Start with a small set of measures

Stage volume shows how many applications reached each point. Stage conversion compares the number progressing with the relevant number considered at the previous stage. Stage time shows how long applications wait or take to move through the process.

For example, if 12 of 40 reviewed applications progress to interview, the observed review-to-interview conversion is 30%. This is an illustrative calculation, not a benchmark or target. It does not tell you whether the job description was accurate, the screening was fair or the eventual hire was successful.

Use the right denominator and cohort

Do not divide this week’s interviews by this week’s new applications if the interviews came from applications received earlier. Decide whether the report follows a group of applications over time or measures activity within a period, then label it accordingly.

A small vacancy may produce large percentage changes when only one or two records move stages. Show the counts alongside percentages and avoid treating a change as a trend without sufficient context.

Investigate waiting time

If applications remain unreviewed, ask whether ownership, workload or an unclear criterion is causing delay. If interviews are completed but decisions stall, examine the debrief and approval process.

Use the recruiter handover checklist to make next actions visible. A dashboard can reveal a queue; it cannot resolve an unclear decision owner by itself.

Combine numbers with process questions

A low offer-acceptance count may have several explanations: package differences, timing, role changes or a small sample. Review documented feedback and confirmed facts rather than assigning a cause from the chart alone.

Choose one improvement, name its owner and review the effect after a suitable period. Avoid using a dashboard to rank individual candidates or reward application volume without considering relevance and fairness.

OpenDoor’s employer workspace helps organise applications and stages. Use only reporting data you can actually access and verify; a custom metric plan does not imply that every chart described here is a built-in product feature.