Image
Workflow
Back office

Headcount and turnover reporting that builds itself

Every quarter someone rebuilds the headcount spreadsheet, and the turnover number changes depending on who built it. An agent produces the report from your HR records with definitions you wrote down, and a named person reviews it before anyone else sees it.

The short answer

Short answer

An agent produces headcount and turnover reports by reading your HR records on a schedule and applying definitions you wrote down: who counts as headcount, what counts as a hire, a departure, voluntary or not.

It hides any breakdown small enough to identify a person. A named person reviews each report before it goes to anyone else.

Today

Why does the turnover number change depending on who built it?

At quarter end, someone exports the employee list, filters it, counts, and pastes the result into a slide. Next quarter someone else does it slightly differently. Contractors are in one time and out the next. A person who moved teams counts as a departure in one version. The board sees a turnover number that nobody can explain, and the next question, which team, sends someone back into the spreadsheet for a day.

Who is this for?

An owner, finance lead or people lead who produces headcount numbers for budgets, board meetings or planning and rebuilds them each time. It suits companies with an HR system or payroll system that records start dates, end dates and roles. It does not interpret why people leave. That conversation belongs to the leadership team.

What changes when the report runs from written definitions?

Part of the reportRebuilt each quarterBuilt from written definitions
DefinitionsIn the builder's headWritten once, applied every time
The dataAn export, filtered by handRead from the HR record you authorize
BreakdownsWhatever someone has time to cutBy team, location or role, as you choose
Small groupsShown, even when one person is identifiableCombined or hidden below the size you set
Sign-offSent straight to the deckReviewed by a named person first

How it works, step by step

The definitions are yours. The agent applies them the same way every run and shows its working.

01

Write the definitions down

Before the first run, you write what each term means for your company: headcount, a hire, a departure, voluntary and involuntary as your records already code them, and how contractors and internal moves are treated.
02

Read the HR record

On the schedule you set, the agent reads start dates, end dates, roles, teams and departure codes from the HR or payroll system you authorize. Reading records to produce a report is a long-standing part of this work: O*NET notes that human resources assistants may prepare reports for employment records and furnish information to authorized persons.
03

Apply the definitions and count

It applies your definitions and produces headcount, hires and departures for the period, with the turnover calculation you specified. Each number links to the list of records behind it, visible to the reviewer only.
04

Protect small groups

Where a breakdown would show a group small enough to identify someone, it combines or hides that cell, using the minimum group size you set. NIST built its Privacy Framework to help organizations manage privacy risk, and the minimum group size is one practical control.
05

Human gate: a named person reviews before sharing

The draft report goes to the people lead or finance lead you named. They check it, ask questions, and approve it before it reaches the leadership team or the board. The agent sends it nowhere else. Approval gates sets out why that sign-off has one name.
06

Flag records that look wrong

It lists records that break the definitions, such as an end date before a start date or a departure with no code, for the record owner to fix. It does not fix them itself.
07

Keep each period's report

It files each approved report with the definitions used, so a number from last year can be explained this year.

Never with workforce data

What does the agent never do with workforce data?

Interpret departures

It counts. Why people left is a leadership conversation.

Expose individuals. Small groups are combined or hidden.

Change records

It flags problems for the record owner.

Share without approval

Every report waits for its reviewer.

Predict who will leave. No attrition scores, no flight-risk lists.

Where this fits

Workflow / Automate a Workflow

A recurring report from one data source is a single process, the shape of Tier 1, Automate a Workflow. Your definitions are what the readiness checklist will probe first. The same pattern of a report that runs itself on a schedule is described in recurring reports that spawn themselves, and a finance version is cash position reporting that builds itself. The rest of the library is at the use case library.

How does a headcount report differ from a payroll report?

QuestionPayroll reportHeadcount and turnover report
What it answersWhat did we pay, and to whom?How many people, and how is that changing?
Who reads itFinance and the payroll providerLeadership and the board
Privacy riskIndividual payIdentifying someone in a small group
What it depends onPay recordsYour written definitions
Tier 1 / Prove
How It Works

Questions, answered

Only if last year's report used the same definitions. The first run shows where your old reports differed, so you can decide whether to restate them or note the change.
AI Opportunity Audit · Headcount reporting

Stop rebuilding the headcount spreadsheet

Bring the last headcount slide and the spreadsheet behind it.