Headcount dashboards that score every seat


Podcast Overview


    What should be on a headcount scorecard?

    Most headcount dashboards answer one question: how many people do we have, and how many more did we plan for? It is a useful number. It is also the number every executive already knows.

    The questions leadership actually asks in a planning review are harder. Why did engineering hire three months late? Who is sitting on approvals? Did the roles we fought for in January ever get filled at the salary we budgeted? Which recruiter can take on the next five reqs?

    For most HR, Finance and Recruiting leaders, those answers live in a spreadsheet that was overwritten last week, an approval thread in someone's inbox, and a recruiter's memory. Nobody lost the data on purpose. It simply was never captured.

    That is changing. When headcount planning, approvals and recruiting run through one connected workflow, every action leaves a timestamped record. Put those records together and you get something new: a scorecard for every person and team in the process, not just a count of seats.

    Why this data was always lost?

    Headcount data has three natural enemies: the overwrite, the inbox and the hand-off.

    The overwrite. A hiring plan spreadsheet holds one value per cell. When a start date moves from March to June, March is gone. So is the salary you budgeted before the level changed. At year end you can report where the plan landed, but not how far it travelled to get there.

    The inbox. Approvals by email or chat leave no clock. You can find out who said yes, if you dig. You cannot easily find out that the request sat with one approver for nine days while the rest took less than one.

    The hand-off. Finance owns the budget, HR owns the role, Recruiting owns the search, and the ATS and HRIS each own a slice of the outcome. Every hand-off between them is a place where context falls on the floor. The offer that closed 8% over budget gets noticed in the HRIS three months later, if at all.

    A system built for headcount changes the default. Instead of storing only the current answer, it keeps:

    • The original plan, frozen the day a role is added, beside the current plan and the final outcome

    • Every change, with who made it, when, and the reason they gave

    • Every approval step, with when it was requested, when each approver responded, and what they said

    • Every hand-off, from approval to the ATS, from accepted offer to the HRIS record

    None of this asks anyone to do extra work. It is a by-product of doing the work in one place, and it is the raw material for scorecards.

    Two of these deserve a closer look, because they change the conversation the most.

    Approval cycle time is the metric most leaders have never seen. Every organization believes its approvals are fast. Measured, the picture usually splits: most approvers respond within a day, and one or two steps account for most of the waiting. That turns a vague complaint ("approvals are slow") into a specific fix.

    Plan vs. actual turns a budget into a story. When you hold the original plan, the current plan and the final outcome side by side, you can show not just that spend came in over, but where it drifted, when, and by whose decision.

    The approver scorecard is the one that surprises people. Approvers are rarely measured, because their work was invisible. Give a VP a monthly line that reads "average response: 4.6 days, team average: 1.2" and behavior changes without a single escalation.

    The hiring manager scorecard does something similar for planning quality. A manager whose roles are changed after the search has started is costing recruiting time, and the data now shows it.

    Three ways to use a scorecard: department, person, process

    The same data supports three kinds of evaluation. Picking the right one keeps the conversation fair.

    Evaluate a department

    Start with plan quality, not hiring speed. Compare each department's original plan to its final outcome. A department that hit its headcount number but pushed half its start dates back four months did not deliver its plan. It delivered a different, later plan, and the business absorbed the cost of the gap.

    Useful cuts: hires on time by department, slippage in months, compensation variance against the original plan, and change requests per approved role.

    Evaluate a person

    Score people on what they control. An approver controls response time. A recruiter controls offer timing on a role that stayed stable, but not on one whose level changed mid-search. A hiring manager controls how often their roles change after approval.

    This is where timestamped history matters most. Without it, a late hire is blamed on whoever touched it last, usually the recruiter. With it, you can see that the role waited three weeks for approval and was re-leveled during the search.

    Evaluate a process

    Some problems belong to no single person. If one approval step adds five days to every request, the step is the problem, not the approver. If backfills take twice as long to approve as new roles, the policy may be asking the wrong questions.

    Process scorecards look at averages by workflow and step rather than by name. They are the easiest to bring to an executive team, because they point at a fix rather than a culprit.

    How to use headcount scorecards in an executive meeting

    Executives remember the leader who explained what happened, not the one who reported it. Scorecards give you the evidence for that explanation. A simple structure turns them into a story:

    1. The plan. What we committed to in January, frozen as it was.

    2. The drift. Where reality moved away from it, in dates and dollars.

    3. The cause. Which decisions, steps or teams drove the drift, with timestamps behind each claim.

    4. The fix. One process change, with the metric that will show whether it worked.

    Here is the difference in practice. A typical update says: "We are 12 hires behind plan." A scorecard-backed update says: "We are 12 hires behind plan. Seven of them waited more than two weeks at one approval step, and four were re-leveled after the search began. Removing that step and freezing levels at approval would recover most of the gap next quarter."

    The second version does three things the first cannot. It shows command of the detail. It moves the discussion from blame to a decision. And it makes the person presenting it the obvious owner of the fix.

    That last point matters for the people giving these updates. HR, Finance and Recruiting leaders are often judged on outcomes they share with a dozen other people. Scorecards make your contribution visible, and they show you are the one who can see across the whole process. That is how a functional leader becomes a strategic one.

    What are headcount scorecard best practices?

    History can't be produced after the fact. The approval that took nine days last spring is gone unless something recorded it at the time. The best time to start building scorecards is a full planning cycle before you want to present them.

    Three steps get you started:

    • Freeze your starting plan. Whatever you approve at the start of the year, keep an untouched copy. It is the baseline every later metric depends on.

    • Put approvals on a clock. Move approvals out of email and chat and into a workflow that dates every request and response.

    • Connect the outcome. Link each approved role to its accepted offer in the ATS and its employee record in the HRIS, so plan vs. actual is a lookup and not a project.

    Teams that run headcount in a dedicated planning platform such as headcount365 get this history automatically, because every change, approval and hand-off is recorded as it happens. Whatever tools you use, the principle holds: a headcount dashboard is only as good as the history behind it. Capture the history, and the scorecards, for every seat at the table, follow.

    Headcount Scorecard FAQ

    Next
    Next

    Balancing Q4 Hiring Production and Annual Headcount Planning with Jeff Moore