An HR dashboard should help a manager decide what to do next, not create another monthly reporting ritual. The best version keeps a short set of measures tied to hiring, capacity, cost, and employee experience. It also shows who owns the next check.
Start an HR dashboard with one decision
Do not begin by exporting every available field. Begin with a business question. A retail operations lead may need to know whether weekend coverage will hold. A growing software company may need to know whether critical roles can be filled before a product launch. The question sets the audience, the reporting rhythm, and the measures.
People metrics describe what happened. Analytics helps explain why it happened and what to test next. The CIPD people analytics factsheet makes the same distinction: data about people should solve a business problem, rather than sit unused in a report.
7 HR dashboard metrics that earn their place
1. Headcount versus plan
Show approved positions, active employees, open roles, and the difference from plan. Break it down by team only when a leader can act on the gap. A total headcount figure alone hides whether a customer support team is short while another team is overstaffed.
2. Vacancy rate in critical roles
Count open priority roles divided by approved priority roles. Mark the role group and the age of each vacancy. This keeps an executive view focused on operational exposure rather than a generic recruitment total.
3. Time to fill
Use the same start and end dates every time. A simple definition is offer acceptance date minus requisition approval date. Compare the current period with a baseline and split the view by priority role. A faster average can still mask a single role that has been open for months.
4. Voluntary attrition
Calculate voluntary exits divided by average headcount for the period. Add the team, tenure band, and role family only after checking whether the group is large enough to protect privacy. A rise is a signal to investigate, not proof of a cause.
5. Overtime hours and cost
Pair overtime with staffing gaps, absence, or peak periods. A dashboard that shows overtime without context can lead to the wrong fix. The useful question is whether recurring overtime covers a temporary surge or an unresolved capacity problem.
6. Absence rate
Use absence days divided by available workdays, then compare like with like. A logistics team with seasonal peaks should not be judged against an office team with a different schedule. Look for a change from the team’s own baseline first.
7. Internal fill rate
Calculate internal hires divided by all filled roles. This measure shows whether the organisation can move people into needed roles before going to the external market. It works best next to time to fill and voluntary attrition, because mobility, hiring speed, and retention affect one another.
Turn HR dashboard metrics into action rules
Every metric needs a threshold, an owner, and a follow-up date. Otherwise, a red indicator becomes wallpaper. Keep the threshold simple. For example, flag a critical vacancy after 45 days, then ask the hiring manager to confirm the hiring plan, interview capacity, and candidate pipeline within five business days.
Use a short note beside each measure: what changed, why it may have changed, and what will happen next. That note stops leaders from treating a correlation as a conclusion. It also creates a record for the next review.
A worked example: turning overtime into a staffing decision
A 120-person distribution team planned 19,200 work hours for a four-week period. It recorded 1,440 overtime hours. The overtime share was 1,440 ÷ 19,200 × 100 = 7.5%.
The dashboard also showed that 6 of 24 evening-shift positions were vacant and that absence rose from 2.8% to 4.1%. The right response is not to label the whole operation inefficient. The owner should first check whether the vacancies, absence pattern, and delivery demand overlap on the same shifts. If they do, the immediate action may be a temporary shift plan and a focused hiring plan. The next dashboard review can test whether overtime falls after those actions.
Keep the dashboard small and trustworthy
Set access by role. Avoid exposing employee-level details when an aggregated view answers the question. Explain what data is used, why it is used, and who can see it. This protects trust and makes the dashboard easier to maintain.
Start with seven measures or fewer. Add one only when someone can name the decision it will improve. Teams that need flexible views can build, share, and export module reports through a reporting workflow instead of rebuilding the same spreadsheet each month.
A good HR dashboard does not replace conversation. It gives that conversation a common starting point, then makes the next action visible.
