AI for HR teams: five workflows to build first, and where a person must approve

Where should an HR team start?

Start where the work repeats, the rules are written down and a mistake can be caught before it reaches anyone. Most HR functions already have that work in volume, and it is where newer team members spend much of their time.

That matters for who benefits. In a study of 5,172 customer-support agents, an AI assistant raised issues resolved per hour by 15%, and newer, less experienced staff gained most (Brynjolfsson, Li and Raymond, Quarterly Journal of Economics, 2025). An HR officer in their first year, answering policy questions against a manual they are still learning, is in a similar position: the assistant carries the knowledge, and the officer applies judgment.

But gains come from changing the workflow, not from adding a tool to it. Among organisations getting most from AI, 3 in 4 fundamentally redesigned workflows, against 1 in 4 of the rest (McKinsey, The state of AI in 2026; Indicative). For HR, that means deciding for each workflow what the AI produces, what source it uses, and who approves before anything leaves the team.

What are the five workflows to build first?

1. Policy questions on leave, allowances and transfers. An assistant grounded in the current HR policy manual drafts replies and cites the clause it used, so the officer can check it in seconds. The source must have an owner: if the manual is out of date, so are the answers.
2. Job descriptions. Drafted from the organisation's grading framework, competency model and an approved template, then reviewed by the hiring manager and HR.
3. Interview guides. Structured questions and scoring criteria drawn from the job description, the same for every candidate for a role. The AI writes the guide; it does not score the interview.
4. Onboarding packs. Role-specific first-week plans, policy summaries and contact lists assembled from existing material, checked before they go to the new joiner.
5. Employee survey analysis. Grouping free-text comments into themes, with counts and representative quotes, for HR to interpret. Results are reported at group level, never used to identify or judge an individual.

Each of these is frequent, follows written rules, and produces something a person reviews before it takes effect. A wrong draft costs minutes, not a career.

Where does the Delegation Ladder stop in HR?

The Delegation Ladder, Cader Group's framework for AI authority, sets four levels of AI authority (Assist, Draft, Advise, Delegate) and tests each idea on whether a mistake would be recoverable or binding. In HR, the second test does most of the work.

Decisions about an individual are binding. Hiring, shortlisting, pay, promotion, performance ratings and discipline affect a person's livelihood and rights, and a wrong decision is hard to undo once made. So:

• Assist and Draft suit most HR work: finding policy answers, drafting documents, summarising feedback. A named person signs before anything reaches an employee or candidate.
• Advise on individuals, such as ranking candidates or flagging performance risk, needs recorded past outcomes to test against, bias checks and a person making every call. Most HR teams are not there yet, and should not start there.
• Delegate has almost no place in decisions about people. It fits only recoverable internal steps, such as routing a request to the right officer.

The line in practice: AI can prepare the material a decision-maker uses, but it does not make the decision about a person.

What about data privacy and bias?

HR holds the most sensitive data in most organisations, and staff are already putting company information into public tools. In a 47-country study, 48% of employees said they had uploaded company information into public AI tools (University of Melbourne and KPMG, 2025; Indicative). In HR, that can mean salary data, medical leave or performance reviews.

Four rules cover most of the risk:

• Approved tools only for anything containing employee or candidate data, ideally models that run in your own environment.
• Removing a name is not anonymising. Employee numbers, roles and dates still identify people.
• Check outputs for bias before use: job descriptions for exclusionary wording, interview guides for questions unrelated to the role, survey themes for groups whose comments are missing.
• Keep an audit trail of which source the AI used and who approved the output.

How does an HR team move from using AI to building with it?

In two steps. AI for HR (1–2 days) gets the whole team using AI on its own workflows, on the tools the organisation has approved, and ends with tested workflows, each with a human-approval point. Discovery comes first, so the exercises use the team's real policies and requests. This is the difference between capability and awareness, discussed in our note on why AI training should build capability.

AI for HR: Advanced (4 days) follows, for teams already using AI. The same team builds agents on its own processes across four depths: knowledge assistants, multi-agent workflows, agent controls and governance, and automation and integration. It ends with a function build, a governance checklist and a rollout plan with named owners.

Measure where your own team stands: take the free Readiness Snapshot →