What should an HR dashboard show?

Headcount split by permanent and contract status, attendance and absenteeism, overtime hours and cost, compliance status per site, and cost per site normalised for fair comparison.

How do we compare plants fairly?

Only once every plant uses the same definitions for attendance, overtime and workforce categorisation. Without common definitions, cross-site comparisons reflect measurement differences rather than real performance gaps.

Can leadership see contractor and permanent headcount together?

Yes, and they should be shown both combined and separately — combined for total workforce cost, separated because the two categories carry different compliance and payroll implications.

Is the data real-time?

It should be, where attendance, compliance and payroll data feed the dashboard directly rather than being reassembled from spreadsheets at month-end.

Can it export for board review?

A dashboard intended for leadership use should support a summarised export format distinct from the operational plant-level view, rather than forcing manual rework before every board meeting.

Access is typically layered — plant HR sees full operational detail for their site, group HR and compliance see cross-site exceptions and trends, and leadership sees the summarised, cost- and risk-framed view.

← Back to blog

HR technology

HR Dashboard for Multi-Plant Manufacturing: What It Should Actually Show

August 28, 20267 min read

HR leadership reviewing a multi-plant workforce dashboard — replace with real dashboard or office photography before publishing

Summary

A multi-plant HR head does not need another headcount total — they need to see which sites have a problem before it becomes a crisis. Most HR dashboards fail at this because they show totals instead of exceptions, and compare sites without agreeing what the numbers actually mean.

A single-plant HR dashboard and a multi-plant one solve different problems. A single plant needs today's headcount and attendance. A multi-plant HR head needs to know, across every site, where something is going wrong — without visiting each site or waiting for a monthly report to say so.

Most HR dashboards get this wrong by showing totals rather than exceptions, and by comparing sites that are not actually measuring the same thing.

What belongs on a plant HR dashboard

Headcount — permanent and contract, broken out separately and combined. Attendance and absenteeism against plan. Overtime hours and cost. Compliance status — licence expiries, pending documentation, approaching statutory thresholds. Cost per site, normalised so plants of different sizes can be compared fairly. Together these answer the questions a plant HR head and a group HR head actually ask, rather than a generic set of employee metrics.

Why site comparison requires common definitions

Comparing "attendance rate" across plants only works if every plant calculates it the same way — same shift definitions, same treatment of contract versus permanent workers, same overtime cutoff. A dashboard that pulls numbers from different local systems without reconciling these definitions will show differences that are really just measurement artefacts, not real performance gaps.

Exception-first design

A dashboard that leads with totals asks the viewer to spot the problem themselves. A dashboard that leads with exceptions — the plant with an expiring licence, the site with an attendance drop, the contractor approaching a headcount cap — tells the viewer where to look first. For a group HR head covering many sites, this difference determines whether the dashboard gets opened daily or ignored until month-end.

Board-ready reporting

Leadership reporting needs a different view again: fewer numbers, framed around cost, compliance exposure and workforce trend rather than operational detail. A dashboard built only for plant-level operational use rarely translates cleanly into a board deck without manual rework — the export format matters as much as the data underneath it.

Live data vs month-end compilation

A dashboard rebuilt from spreadsheets at month-end shows where things stood weeks ago. A dashboard fed by live attendance, compliance and payroll data shows where things stand today — which is the difference between managing a problem and discovering one after it has already cost something.

Frequently asked questions

What should an HR dashboard show?: Headcount split by permanent and contract status, attendance and absenteeism, overtime hours and cost, compliance status per site, and cost per site normalised for fair comparison.
How do we compare plants fairly?: Only once every plant uses the same definitions for attendance, overtime and workforce categorisation. Without common definitions, cross-site comparisons reflect measurement differences rather than real performance gaps.
Can leadership see contractor and permanent headcount together?: Yes, and they should be shown both combined and separately — combined for total workforce cost, separated because the two categories carry different compliance and payroll implications.
Is the data real-time?: It should be, where attendance, compliance and payroll data feed the dashboard directly rather than being reassembled from spreadsheets at month-end.
Can it export for board review?: A dashboard intended for leadership use should support a summarised export format distinct from the operational plant-level view, rather than forcing manual rework before every board meeting.
Who sees what?: Access is typically layered — plant HR sees full operational detail for their site, group HR and compliance see cross-site exceptions and trends, and leadership sees the summarised, cost- and risk-framed view.