A staffing total often arrives in an executive meeting with more authority than the work behind it deserves. The number is exact, the chart is familiar and the comparison with last month looks simple. Discussion moves quickly to whether the figure is too high or too low. I have learned to pause before that judgement. The more useful first question is what has been counted, at what date and for which decision. An answer that needs explanation may be more valuable than a clean number whose meaning everyone assumes.
In a communications business, several legitimate populations sit close together. There are direct employees, authorised positions, active recruitment requests, temporary assignments and people employed by installation partners. Each can matter to a different operating question. None should silently stand for all the others. A network leader may be asking whether work can be covered, finance may be examining an expense commitment and recruiting may be estimating its active workload. A single total cannot answer those questions merely because it is the most convenient figure available.
Count the thing the decision actually concerns
Our 2021 vacancy register illustrated the problem. It contained 164 entries and was presented as an account of open positions. Review found 92 current approved requirements, 48 obsolete requests and 24 duplicates. The original total had combined several administrative histories. It did not describe 164 distinct hiring decisions waiting to be executed. Operating and finance colleagues had been reacting to the same number while imagining different consequences. The first task was not to agree a planned reduction; it was to establish a population managers could recognise.
The correction required time and USD 210,000 of additional support and review. It was tempting to describe the result as a large saving because 72 entries left the active count. I opposed that interpretation. We had not removed 72 occupied jobs, and the records did not establish that their assumed salaries would otherwise have been spent. The defensible result was narrower: the company had a better account of its current hiring requirements. Whether to fill each requirement remained a separate decision about priorities, work and affordability.
One objection is that executives cannot revisit definitions every time they examine a report. That is reasonable. A reporting system should not force every meeting to begin from first principles. My answer is to establish the definition where the work is prepared and make material changes visible when they occur. The responsible owner should know what the total includes, which exclusions matter and where an unresolved issue remains. Executive attention can then focus on changes that alter the decision, rather than repeatedly discovering basic ambiguity after the chart has circulated.
This also changes how trends should be described. If a category is redefined, a downward movement may reflect the new boundary rather than an operating improvement. If acquired roles enter the population partway through the year, the comparison needs that context. A consistent-looking series is not necessarily a comparable one. I would rather show a break with an explanation than preserve a smooth line that invites the wrong conclusion. The reader should not have to infer a substantive change in meaning from a quiet footnote.
A common category can conceal an unresolved difference
The same issue appears after acquisitions, where a shared system encourages a shared classification. In 2024 we reviewed 126 acquired roles. Ninety-one had a supported match, 23 required a revised description and 12 stayed under separate review. A title and salary band could suggest equivalence without establishing it. The work involved decision scope, reporting relationships and responsibilities expected to continue. Those questions could not all be settled by the administrative team responsible for entering the result into the receiving system.
We accepted a ten-week extension and USD 280,000 of additional expense. The integration sponsor had wanted a single completion date, and I understood the value of reducing uncertainty. Yet describing all 126 mappings as complete would have hidden the twelve questions management still needed to answer. The category itself would then acquire authority: an employee or manager could reasonably assume that the new label represented an examined decision. Keeping the open cases visible was more useful than satisfying the reporting milestone with a conclusion the evidence did not support.
The opposite risk is indefinite review. A people function can make classification so elaborate that a transaction never reaches a workable operating state. I do not regard every difference as a reason to delay. The distinction is whether the unresolved point matters to the responsibilities, terms or decisions that the mapping is intended to support. Some differences can be documented without preventing progress. Others require the appropriate operating, transaction or employment decision. The review should make that distinction explicit, with an owner and a next step, rather than use complexity as a permanent shelter from choice.
Nor does an accurate mapping settle the employee’s experience of an acquisition. A role may be entered correctly while its holder remains uncertain about the future or dissatisfied with the process. The administrative record and the human account answer related but different questions. Management should listen to both without treating one as proof that the other is complete. This is another reason I resist a broad claim that personnel integration has succeeded solely because every required field in the new system is populated.
Make revision part of the account
Good workforce reporting needs a way to revise its own categories. Businesses change, responsibilities move and an old definition may stop being useful. The challenge is to make revision visible without making every earlier report appear careless. A definition can have been reasonable for its original purpose and inadequate for a new one. The reporting owner should explain what changed, why it matters and which comparisons remain valid. That explanation gives the organisation continuity of reasoning rather than merely continuity of format.
I also want the person affected by a record to have an appropriate route for raising a factual error. The route must respect privacy and the responsibilities of the relevant specialists, but it should not assume that the central system is right simply because it is central. Regional colleagues often understand a distinction that has disappeared in consolidation. Their account should be examined, not automatically accepted or dismissed. A useful process can correct the record while preserving who made the decision and the reason for the amendment.
My current review of 18 executive workforce indicators follows that approach. Eleven have a documented population, purpose and limitation; seven still need a clearer explanation before wider circulation. The incomplete seven are not evidence that measurement has failed. They identify work that needs doing before the figures receive greater authority. I want the executive team to know that status. A smaller set of well-explained measures can support better judgement than a comprehensive-looking dashboard whose readers cannot tell where the categories end and the assumptions begin.