Every HR platform now ships AI. Almost none of it is load-bearing.
It arrived as a release note rather than a decision, which is why so little of it can be defended now. This is what the register holds on the people function: 58 vendors, 1,120 customer claims, and the 288 of those an employer has confirmed.
Recruiting carries the claims. Payroll carries the deployments.
Talent acquisition attracts three times the claims of payroll and administration, and confirms them at two thirds the rate.
Register edition 2026.4 · compiled 18 Oct 2026
Why HR looks further ahead than it is
No function has more AI switched on and less evidence that it changed anything. That is not a failure of ambition. It is what happens when the technology arrives as a feature of something you already bought.
The suite did the buying
In most of the register, AI entered the people function as a release note rather than a decision. It was bundled into the HR platform, the recruiting system or the payroll engine. Nobody chose it, nobody scoped it, and nobody set a number it was supposed to move, which is why so little of it can be defended twelve months later.
There is almost never a baseline
Ask an employer what time to hire, case handling time or query deflection looked like before the tool went in and most cannot say. Without that number the deployment can be neither proven nor killed, so it survives unexamined. This is the single most common reason an HR claim cannot be confirmed past a contract.
Deployment stops at the jurisdiction boundary
An HR deployment that works in one country meets a different works council, a different data regime and a different employment code in the next one. The pattern across the register is a system live in one or two markets and stalled everywhere else, and the constraint is legal and procedural rather than technical.
The decisions are contestable by design
A people decision can be appealed, grieved or litigated in a way a demand forecast cannot. Employers that moved fastest treated the record of reasoning, the human override and the named owner of each decision as build requirements from the first week, not as a compliance review at the end.
Eight categories, and they are not moving at the same speed
Vendor counts, claims captured, and how many of those claims an employer has confirmed. Absence of confirmation is as much a finding as its presence.
| Category | Vendors | Claims | Confirmed | Deepest stage established |
|---|---|---|---|---|
| Talent acquisition and screening | 16 | 341 | 94 | Full deployment |
| HR service delivery and case management | 11 | 206 | 71 | Full deployment |
| Payroll and workforce administration | 7 | 128 | 52 | Full deployment |
| Learning and skills | 12 | 174 | 38 | Partial deployment |
| Performance and talent management | 9 | 118 | 21 | Partial deployment |
| Workforce planning and analytics | 8 | 86 | 9 | Partial deployment |
| Employee listening and sentiment | 6 | 52 | 3 | Yet to start |
| Agentic HR operations | 10 | 15 | 0 | Yet to start |
Read the first row against the third. Talent acquisition draws more vendors and more claims than any other category in the function, and confirms them at a lower rate than payroll and administration, which almost nobody puts on a conference agenda. Attention and evidence are pointing in opposite directions here.
Two ways to engage us, and two things included with either
Everything rests on the same register. We do not introduce you to vendors, take referral fees, or accept sponsorship from anyone selling into the people function.
Expert guidance
A standing line to the people who maintain the register. Bring a shortlist, a suite renewal, a proposal on the table, or an AI program that has stopped moving.
- Inquiry calls and written responses inside 48 hours
- Shortlist reviews and proposal reads before you sign
- Bought as sessions, not seats, with register access included
Executive workshops
Your own decision, worked through by the people who have to own it, against a picture of the HR market drawn from the register rather than from vendor material.
- The HR leadership team, a sub-function, or the management layer
- Our maturity assessment, frameworks and canvas, brought to the room
- Moves chosen, owners named and a written record in five working days
Category review
Commissioned. Every vendor in an HR category, every claim across them, and where the working deployments sit. Published like any other determination.
Register access
Included with guidance. Search every HR vendor and claim, filter by stage and currency, export the data, and get alerted when a determination lands or lapses.
What 1,120 HR claims look like when you follow them through
Every number below is a count from the register, not a survey, an estimate or a projection. Quote them with the edition and date attached.
Eleven per cent of HR claims are confirmed running at full scale
Each step is the subset of the one above it that survived the next layer of evidence.
Confirmation runs opposite to where HR spends its attention
Share of captured claims that an employer has confirmed.
Where the fifty use cases actually sit
Stage mix within each of the six groups.
The sequence most HR teams get backwards
Where each horizon sits in time, and how much confirmed evidence stands behind it today.
Fifty HR AI use cases we track
Six groups, fifty use cases, and against each one the stage the register can currently confirm. Live means a confirmed full deployment exists somewhere. Getting started means partial deployments exist. The third label is our forecast, and we mark it as one.
Counts and stages are drawn from register edition 2026.4, compiled 18 October 2026. A use case marked 2027 to 2028 has no confirmed full deployment anywhere in the register today. In the people function the remaining constraint is more often legal and procedural than technical, which is why the third group is smaller here than in most industries and moves more slowly when it does move.
Where HR actually sits, sub-function by sub-function
Each cell is the number of confirmed deployments the register holds at that stage for that sub-function. Read across a row to see how far it has got. Read down a column to see how thin the right-hand side still is.
Hiring, service and payroll carry the confirmed deployments. The work HR talks about most, learning and performance, is still concentrated on the left, which means claims rather than deployments.
Fifty-one claimed against seven at full deployment. More content has been generated than has ever been completed, and almost nobody is measuring the difference.
Not one confirmed deployment at full scale anywhere in the register. Sentiment is the easiest thing in HR to demonstrate and the hardest to put weight on.
What actually stops HR deployments, in the order it stops them
Drawn from the enquiries behind confirmed and unconfirmed claims, and sequenced against the Forum's own readiness gates. Regulation is on this list. It is not at the top of it.
No measurement baseline
The employer cannot say what the number was before. Time to hire, case handling time, completion rate, query deflection. Without a baseline the deployment can be neither proven nor killed, so it stays switched on and unexamined.
The process lives in the manager, not the system
HR process truth sits in local custom and in people's heads far more than in the platform. The deployment automates the documented version and meets the real one on contact.
Jurisdiction, not regulation
It is rarely a rule that forbids the deployment. It is that the rule is different in the next country, and the works council, the data regime and the notice requirements all have to be cleared again before the same system can cross the border.
No named blame path
When an AI-assisted people decision is challenged, somebody has to answer for it. Where that person has not been named in advance, the function quietly keeps a human in every loop and the business case disappears.
What we have put out on HR
Everything below is free to read and draws on the same register. None of it is sponsored, and no vendor saw any of it before publication.
The machine in the people function
How AI is actually being deployed across HR in mid-market and enterprise, globally and in India, and what is holding weight.
October 2026 Deployment StudyScreening agents in volume hiring
Twenty-two claimed deployments taken to the employers named in them. Twelve confirmed, six overstated, four unanswered.
September 2026 Research briefingReadiness gates for people systems
The five gates an HR use case has to clear before it is worth deploying, condensed for a leadership team.
August 2026Bring us the HR decision in front of you
A shortlist, a suite renewal with AI modules attached, or a program that stopped moving. We will tell you what the register can answer, what it cannot, and which of our services fits. If none of them does, we will say that.
What HR leaders ask about this page
From the register. Every claim is captured from a vendor's own published material, and the confirmed ones have been taken to the employer named in them and answered under anonymity. Counts are as at the compilation date on the page, not estimates, projections or survey responses.
Switched on is not the same as deployed. The register counts a claim as confirmed at full deployment only when the employer states the capability carries the work across the population it was bought for. A module enabled in a tenant and used by a pilot group sits at a lower stage, and in this function that is where most of it sits.
Because no claim in that category has yet been confirmed by the employer named in it. Ten vendors are selling agentic HR operations and fifteen customer claims exist, all at Level 1. That may change next quarter. It has not changed yet, and we would rather print a zero than imply otherwise.
No. It means no vendor has published a claim that has been confirmed at that stage. Employers that built it on their own platform are not in the register, because the register is a record of vendor claims rather than a census of the function. Internal builds are a real gap in this view and we say so rather than pretending otherwise.
We do not audit a vendor's model and we do not certify anything as fair. What the register records is whether a deployment exists, at what depth, and what the employer said about it. Where an employer told us a deployment is subject to independent bias testing or a jurisdictional audit requirement, that is recorded on the entry as a stated fact, attributed to them and dated.
It carries an edition number and a compilation date, and it is rebuilt every quarter. Individual determinations underneath it carry their own dates and lapse to unconfirmed after twelve months, which is why the counts move down as well as up.
Yes, and it is the only part of this page that is. In the people function we place a use case there when the constraint is legal, procedural or evidentiary rather than technical, which is a slower kind of constraint to clear. We revise the group each edition. Everything in the first two groups is a record of what has happened, not a view about what will.
Either we have not opened a record on them yet or they sit outside the five technology categories we cover. Request them and we will open a record, capture every customer claim on their site and publish it. That is free and usually complete inside ten working days.
Yes. A shortlist check takes the vendors in front of you and runs every claim each of them makes in your category through the method, with the determinations and the full log returned to you and published to the register like any other.
Before the next HR technology decision goes to committee
Check what the register holds on the vendors in front of you, commission a category review, or bring the decision into a room with your own leadership team.