How many people actually work here

The headcount says 351 and the building says more. Twenty-seven contingent workers are in the tenant, on teams, in meetings, and in no delivered headcount, because All Active Employees excludes them by design. This report counts the workforce, not the payroll.

RuleCount the worker, carry the type: one workforce number that splits into employees and contingent on demand, from one model.

Neverpresent a headcount as the workforce. The delivered employee count excludes contingent workers by design, and the gap is who staffs half your projects.

Capacity planning, seat counts, and security reviews need the whole workforce. Payroll needs the employees. Two questions, two counts, one model.

◆ The two populationsone workforce, two very different contracts.

May 2026	Workers
Employees, on payroll	351
Contingent workers	27
The workforce, contingent share 7.1%	378

The 351 is the same population every headcount page counts and payroll pays. The 27 are in the tenant with positions and managers, and in no delivered employee report. Which number answers the question depends entirely on the question. Sample values are illustrative, never client data.

◆ The contingent 27, split twicewhere they are, and what they are.

Department	Contingent
Sales	8
Technology Delivery	14
Support	5
Contingent workers	27

Engagement type	Contingent
Independent contractor	15
Agency supplied	9
Consultant, firm engaged	3
Contingent workers	27

Technology Delivery runs a third of its capacity through people who appear in no employee report, which is exactly where undercounted workforces bite: seat planning, security reviews, and the org chart the auditor asks for.

◆ The conversion pathcontractor today, employee next quarter.

People convert between the types, contractor to employee being the common road, and a model that stores two separate people for one person breaks every tenure and history question at the conversion date. The Worker object is the superset for exactly this reason: model the person once, carry the type as a dated attribute, and a conversion reads as one career, not a rehire.

◆ The owned answerone dimension, the type as an attribute.

The worker dimension carries every work relationship with the type flagged and dated, so the workforce view, the payroll view, and the conversion history are three filters on one table. The dimension and its facts are drawn on the Core HR star, and the model page is the reference.

Use case

Problem

Contingent workers staff real teams but appear in no delivered employee report, so seat counts, capacity plans, and security reviews all run on an undercount nobody chose on purpose.

What we build

One worker dimension carrying every work relationship with the type as a dated attribute, so workforce, payroll, and conversion views are filters on one table.

What you get

The real count and the payroll count side by side, contingent split by department and engagement type, and conversions that read as one career instead of two people.

Does your headcount match your building?

We build the one-worker model where the workforce and the payroll are two filters, not two systems.

Talk to us

Terms on this page

Core HR: The workforce module this report belongs to; the worker dimension lives there.
contingent worker: A contractor, agency, or consulting worker: in the tenant, not on payroll.
workforce: Everyone doing the work: employees plus contingent.
engagement type: How a contingent worker is engaged: independent, agency, firm.
conversion: A type change for one person, commonly contractor to employee.
worker superset: The object covering both types; one person, one row, a dated type.
excluded by design: Delivered employee reports omit contingent on purpose; a choice to know about.