Headcount and FTE Are Different Denominators

A board asks whether the organization is becoming more productive. Finance brings an employee-cost ratio. HR brings headcount. Procurement brings contractor expenditure. Operations brings project capacity. Each number may be internally correct, yet the combined presentation can support a conclusion that none of the underlying systems actually establishes. Headcount and FTE only help once each denominator is defined.

The difficulty is the denominator. Who counts as part of the workforce, over which period, and for which decision? An employee can be present in headcount but contribute less than a full-time schedule. A contractor can be essential to production while being absent from employee FTE. A person with two assignments can also appear twice in operational systems. A software agent can perform tasks without becoming a person or an employment relationship.

These distinctions become more consequential as enterprises combine acquisitions, contingent labor and AI. A credible workforce report must preserve them before it attempts to summarize them. Our guide to workforce analytics software lists what to check in a tool.

What a real multinational disclosure reveals

Shell’s 2025 annual report provides a useful example of explicit boundaries. It reports 85,000 employees at year end, comprising 72,000 outside portfolio companies and 13,000 in portfolio companies. Its employee overview, however, excludes contractors. The report also distinguishes year-end headcount from average employee numbers and notes differences in the treatment of secondments. These are reporting choices that readers must understand before comparing figures. They are therefore not discrepancies to eliminate by forcing every table to match. Shell, Annual Report and Accounts 2025, pp. 114–115 and 398–399

The managerial implication extends beyond energy. For example, an acquisition can enlarge the reporting perimeter without equivalent organic hiring. Similarly, a divestment can reduce recorded employment without showing a productivity improvement. A change in contractor classification can alter the apparent workforce mix without changing the people doing the work. A chart that omits those explanations therefore invites executives to mistake accounting boundaries for operating performance.

Start the review by asking what changed in the population, then what changed within that population. Reversing that order makes an attractive trend line more persuasive than the evidence warrants.

Keep headcount, employment, and FTE separate

The Global Reporting Initiative separates employees in Disclosure 2-7 from non-employees whose work the organization controls in Disclosure 2-8. It asks organizations to explain their counting method and whether figures represent a period end or an average. Both disclosures also allow headcount or FTE approaches with the relevant methodology. A claim that contractors can never be measured in FTE would therefore be incorrect. GRI 2: General Disclosures 2021

For internal management, a clear convention is to report employee FTE separately from external-worker capacity. That convention makes employee capacity intelligible, yet it does not make contractors disappear. If external FTE is calculated, label it separately and disclose the basis. If reliable hours are unavailable, report external headcount and the missing capacity measure instead of assigning every contractor a value of one.

The following distinctions should remain visible in a leadership report:

The ILO’s work on converting employment to full-time equivalents illustrates the broader measurement issue: counts of employed people and measures adjusted for working time are different statistical objects. Its national-statistics methodology should not be imported uncritically into a company’s contractual FTE calculation. ILO, Employment Satellite Account

Do not use FTE as a synonym for productive work

An FTE measure normalizes hours according to a declared rule. However, it does not establish whether a team has the right skills, whether its work creates value, or whether time is available for a new project. For instance, two departments with equal FTE may have different shift patterns, leave commitments, specialist responsibilities and service obligations.

Executives should therefore resist using a headcount-to-FTE gap as evidence of inefficiency. Part-time arrangements, for example, may be deliberate and productive. Training, regulated supervision and resilience coverage may require capacity that is not immediately billable. A contractor-heavy team may reflect a temporary installation program rather than a permanent sourcing strategy.

The useful question is whether the capacity measure matches the decision. Budget planning needs contractual commitments and cost. Delivery planning, by contrast, needs relevant availability and skill. Safety planning needs qualified coverage. A monthly organization report can connect these conversations, but it should not claim to replace their distinct operating measures.

The boundary must include the people who deliver the work

Research on workforce ecosystems makes the organizational problem concrete. In a 2023 Brookings paper, David Kiron, Elizabeth Altman and Christoph Riedl describe firms relying on employees and external contributors together. Their historical Novartis example reports approximately 100,000 employees and more than 50,000 external contributors. Those are figures cited in that research, not a statement of Novartis’s current workforce. Kiron, Altman and Riedl, 2023

A contractor excluded from the employee total can still require an accountable sponsor, current access, an end date and a route to the appropriate expert. Procurement may hold the commercial agreement while the business controls daily assignments. Neither system alone necessarily answers who should approve a change in responsibility.

This is where a common people view has operational value. It should connect the individual to the relevant engagement and accountable owner without erasing the distinction between an employee, an agency worker and a supplier contact. Inclusion in a directory should not silently grant employee privileges, access to confidential material or a permanent place in the reporting hierarchy.

The workforce-ecosystem framework discussed by Altman and colleagues identifies leadership, integration, technology and management practices as related parts of coordination. A dashboard is only one of those parts. MIT Sloan, 2023

Reconcile headcount and FTE movements before interpreting trends

A useful monthly review begins with an opening population and ends with a closing population. Between them, joins and departures explain changes in people. Transfers alter the distribution between units without automatically changing the enterprise total. Acquisitions, divestments, classification changes and corrected records need their own explanations.

Run that reconciliation separately for headcount and employee FTE. A person moving from a full-time to a part-time schedule can reduce FTE without reducing headcount. An external consultant becoming an employee can increase employee headcount while leaving total people unchanged. A transferred employee may appear in two regional extracts during a handover; a stable identity and effective dates are needed to prevent double counting.

Unresolved records deserve an explicit place in the report. If some employees lack reliable working-time data, show the coverage of FTE alongside the value. Do not convert unknown capacity into either zero or a full-time assumption without explanation. The same discipline applies to missing contract classifications and stale contractor end dates.

These controls make comparisons less dramatic but more useful. Leaders can then distinguish a real change in capacity from a late data correction, and an operating shift from a revised reporting boundary.

Put headcount and FTE definitions into the operating process

Agree a short measurement contract before automating the report. It should define the people included, the observation date, the employee classification source, the hours convention, treatment of concurrent assignments and the owner of unresolved exceptions. Keep a version history so that a methodological change does not rewrite the apparent past without explanation.

Assign responsibilities across functions. HR should own employment classification and organizational relationships within its authority. Procurement should maintain engagement and supplier information. Finance should approve the cost and reporting conventions it uses. Business sponsors should confirm continuing operational need. IT should reconcile identities and access without inferring employment status from an enabled account alone.

A small cross-functional review of exceptions is often more valuable than another dashboard tab. Examine records that affect decisions: people counted twice, contractors without sponsors, missing FTE inputs, unexpected departures and inconsistent effective dates. Record the resolution in the authoritative process so that the next report benefits from the correction.

Where TeamConnect AI and TeamJML AI fit

TeamConnect AI provides a consolidated organization view across people, departments, offices and organizational dimensions. Organization Insights can present people and employee FTE separately, with classification and observation context. In that convention, external workers remain people in scope but are excluded from the employee FTE measure. That is a declared product reporting choice, not a universal rule about FTE.

TeamJML AI connects approved joiners, movers, and leavers to the lifecycle work that keeps the underlying view current. A title or department change should not manufacture an access task; work follows a verified entitlement difference. Together, the products support the reporting process described here. The Shell and Novartis material is public evidence of the management problem, not a claim that either company uses Cubeet.

The board should receive a number it can question intelligently: who is included, which capacity is measured, what changed and what remains unknown. Agreement on those questions is the foundation of a credible productivity discussion. A more precise chart cannot compensate for an undefined workforce.