Department enablement · People operations

Less HR administration, with every employment decision and sensitive case left to people

If your HR operations team answers the same policy questions and runs the same onboarding paperwork every week, you can commission a bounded pilot on that administrative work only. I build an approved policy-information workflow, a data minimisation checklist and a human escalation map with your team. The pilot never screens candidates, rates performance or makes any employment decision.

This is a good fit if…

  • Your HR inbox fills with the same questions about leave, expenses, benefits enrolment and policies that are already written down.
  • Onboarding administration (checklists, reminders, equipment and access requests) is tracked by hand across several systems.
  • Staff are already pasting HR questions into public AI tools because the official route is slow.
  • You want AI help for administration and a written line that keeps employment decisions and sensitive cases with people.

Look elsewhere if…

  • You want AI to screen CVs, rank candidates, rate performance, select for redundancy or set pay. I do not build or coach those uses.
  • You need employment-law, immigration or benefits advice. That stays with your advisers.
  • Your recurring workflow is reconciliation between operational systems. Use AI enablement for operations teams instead.

What you get

Approved policy-information workflow, data minimisation checklist and human escalation map

  • A policy-information workflow that answers employee questions only from approved, current policy documents, with the source shown.
  • A data minimisation checklist covering what staff information may enter which tool, and what never may.
  • A human escalation map that routes sensitive topics straight to a named HR person instead of an AI answer.
  • One onboarding administration workflow with AI-drafted checklists and reminders, reviewed by HR.
  • Baseline and pilot measures of routine-query volume handled from approved sources and escalation accuracy.

How it runs

  1. 01

    Scope the administrative work

    We list the recurring HR administration tasks and agree, in writing, which are in scope and which are excluded because they involve decisions about people.

  2. 02

    Data and policy review

    With your data protection lead, we write the minimisation checklist and identify which policy documents are approved, current and owned.

  3. 03

    Pilot with HR operations

    The HR team runs the policy-information workflow and one onboarding workflow, reviewing outputs and logging every escalation.

  4. 04

    Measure, hand over and decide

    We compare against the baseline, the HR operations owner takes over the workflows and checklist, and you decide whether to extend.

What needs to be in place

  • An HR operations owner, and your data protection lead or DPO involved from the start.
  • Current, approved versions of the policies in scope, each with an owner.
  • An approved AI tool for internal HR information, configured under your data policy.
  • Written agreement that employment decisions are out of scope.

Not included

  • Recruitment screening, candidate ranking, interview scoring or any hiring decision.
  • Performance ratings, disciplinary outcomes, redundancy selection, promotion or pay decisions.
  • Employee monitoring, sentiment scoring or profiling of individuals.
  • Processing health, grievance or other special-category information in AI tools.
  • Legal, immigration, tax or benefits advice.

The line this pilot draws

People operations teams carry a lot of administration. Employees ask how much leave they have left, how to claim an expense, when benefits enrolment closes, what the parental leave policy says. New joiners need equipment, accounts, contracts countersigned and induction booked. All of it is necessary, much of it is repetitive, and most of the answers already exist in a policy document somewhere.

AI can help with that. It must not be allowed to drift into decisions about people. Screening candidates, scoring interviews, rating performance, choosing who is made redundant: these are decisions with legal, ethical and human consequences, and in several jurisdictions they are regulated as high-risk uses of AI. This pilot is limited to administrative support only, and that boundary is written into the scope before work starts.

What the work involves

Approved policy information. We identify the policies that generate the most questions and confirm that each has a current, approved version and an owner. The assistant answers employee questions only from those documents and always shows the source section. If the policy does not cover the question, it says so and points to HR rather than guessing.

Data minimisation. With your data protection lead, we write a checklist: which categories of staff information may enter which tool, which never may (health, grievances, disciplinary records, anything special-category), how long anything is retained, and how the tool is configured. The policy workflow is designed to need no personal records at all.

Human escalation. We map the topics that always go to a person, who receives them and how quickly. The assistant recognises those topics and routes rather than answers.

One onboarding workflow. Using information HR already holds, the assistant drafts the joiner checklist, reminders and access requests for HR to review and send. It does not decide anything about the joiner.

This follows the principle I have published as the Substrate Pattern: decide in advance what an AI system can touch and where a person must approve, and enforce it in the design rather than by asking people to be careful.

The signature deliverable

You end with an approved policy-information workflow, a data minimisation checklist and a human escalation map. Illustrative example of an escalation map extract:

TopicAssistant behaviourRouted to
Leave balance or policy wordingAnswer from approved policy, show sourceNot routed
Health, sickness or reasonable adjustmentsNo answer; give HR contactNamed HR adviser
Grievance, bullying or discriminationNo answer; give confidential routeHR business partner
Pay dispute or individual contract termsNo answer; give HR contactPayroll / HR adviser
Question not covered by any policySay so; no guessed answerHR inbox

Illustrative example. Topics and routes are set with your HR team and data protection lead.

How acceptance is judged

The HR operations owner accepts the pilot against measures agreed at the start: the share of routine policy questions answered from an approved source with the correct section, the number of sensitive queries correctly escalated (and any that were not), HR inbox time spent on routine questions, and onboarding checklist completion on time. Any escalation miss is reviewed the same week. The adoption measure is whether employees use the policy route instead of emailing HR or turning to public tools.

Ownership and handover

HR owns the policy library, the checklist and the escalation map. Policy owners keep their documents current; the assistant follows them. Your data protection lead keeps approval of the tool configuration. The handover note explains how to add a policy, change an escalation route and review the log.

Boundaries

If you are looking for AI to make or support decisions about candidates or employees, this is not that engagement and I will not scope one. For the wider picture of AI use across business teams, see practical AI enablement for business teams. For an employee-facing knowledge assistant that serves customers rather than staff, see AI enablement for customer support.

Questions buyers ask

Why won't you help with CV screening?

Because it is a decision about a person, not administration. Automated screening carries real risk of unfair outcomes and is regulated or treated as high-risk in several jurisdictions. This pilot is deliberately limited to administrative work where a wrong answer is easy to spot and correct, and where people keep every decision.

What happens when an employee asks something sensitive?

The escalation map lists those topics: health, grievances, discrimination, pay disputes, wellbeing, anything about a specific person's case. The assistant does not attempt an answer; it tells the employee who to contact and routes the query to a named HR person.

How do you stop staff data leaking into AI tools?

The data minimisation checklist says what may enter which tool. The policy workflow needs policy documents, not personal records, so most of the pilot uses no individual data at all. Your data protection lead approves the checklist and the tool configuration before staff use them.

What if a policy answer is wrong?

Answers come only from approved documents and show the source, so an employee or HR can check them. Wrong answers in the pilot are logged and usually trace to an outdated or ambiguous policy, which the policy owner then fixes. HR remains the authority, not the assistant.

Related engagements

Department enablement · Operations

Operations teams

Our team repeatedly reconciles information between systems. How can we change this workflow without losing exception handling?

You get:Process map, reviewed reconciliation pilot and exception-handling runbook

Department enablement · Finance

Finance teams

We want faster management reporting, but every number and source still needs review. What can safely be piloted?

You get:Source-linked reporting workflow, reconciliation checks and reviewer sign-off steps

Department enablement · Customer support

Customer support

Can our support team use knowledge assistants while preserving access controls, current answers and escalation to people?

You get:Permissioned support-assistance pilot, answer-quality sample and escalation playbook

Department enablement · Client service

Client-service teams

How can consultants prepare research and client deliverables faster without mixing client data or publishing unsupported advice?

You get:Client-separated research workflow, evidence ledger and partner review checklist

Department enablement · Marketing

Marketing teams

We need faster research and content preparation without weakening editorial ownership. What should the workflow include?

You get:Research provenance template, editorial review gates and campaign workflow pilot

Department enablement · Product

Product teams

Can AI help us synthesize interviews and prepare requirements without treating generated opinions as customer evidence?

You get:Source-linked discovery synthesis, evidence labels and reviewed requirements workflow

Further reading

Scope a workflow pilot

A short, non-confidential description is enough to start. I read every brief personally and reply within two business days, including when the answer is that I am not the right fit.

Step 1 of 2 · The basics