People Analytics for Multi-Entity Groups: Attendance, Skills, and Career Health in One View

Multi-entity HR lives with a specific blindness: every subsidiary has an HR answer, and nobody has the group answer. Attendance runs in one company's spreadsheet, skills in another's training binder, headcount in a deck that is six weeks stale — so group decisions (where to staff, who to promote, which company has the retention problem) get made from anecdotes assembled over email. The org-wide visibility layer is not a luxury report; it is the difference between a group HR function and a federation of company clerks. One view across companies, departments, and teams — attendance with exceptions, skills with calibration status, career health with progression velocity — turns the monthly group HR meeting from storytelling into dashboard review, and turns decisions into queries.

The four lenses worth a monthly meeting #

• Attendance exceptions, not attendance totals: who is chronically late, which teams have the pattern, which sites hide it in averages.
• Skills coverage against org needs: for each critical skill, how many verified masters per company — the staffing risk map.
• Career health: progression velocity by department, level-tenure outliers, and employees stuck one evidence item from promotion.
• Request flow health: approval cycle times and backlog age — HR's own service levels, measured honestly.

The attendance lens deserves its rehabilitation, because attendance data is usually wasted on totals. Averages tell you nothing actionable; the exceptions view — chronic lateness by person, absence clusters by team, the department whose Friday absence rate is a quiet institutional joke — is where interventions live. Skills coverage is the strategic lens: when the group bids a project requiring six certified quantity surveyors, the coverage view shows that four exist in one subsidiary and none in the bidding one, weeks before the staffing crisis. And the request-flow lens is cultural: when approvals take three weeks, employees conclude the organization does not respect their time, and the data proving it is sitting in HR's own workflow timestamps.

The operating rhythm that makes analytics real is unglamorous: the same four lenses, the same monthly review, the same one-decision-per-lens discipline. Groups that install dashboards without the rhythm produce beautiful screenshots and unchanged decisions; groups that run the rhythm with even modest views produce compounding institutional knowledge — this department's absence pattern has appeared three quarters running, this skill gap has closed by two people since the training budget moved. Analytics is not the dashboard; it is the memory the organization builds by looking at the same honest numbers on a schedule.