Key takeaways
- Automate the logistics around an employee — provisioning, document collection, checklist chasing, reminders, recurring people reporting — and leave every decision about an employee with a named human.
- Never let a screening, performance or termination outcome fall out of an automated process. GDPR Article 22 gives that person a right to human intervention, so design the gate in rather than bolting one on later.
- Decide your retention rules before you design the automation. The EEOC requires personnel and employment records, including every application form whether or not the applicant was hired, to be kept at least a year, and payroll records three years under the ADEA.
- Map the work as joiners, movers and leavers. The three families differ in frequency, variability and where the irreversible step sits, so they do not deserve the same amount of automation.
- If a lane fails the readiness rubric — no written trigger, unlisted exceptions, no single owner — that is a documentation problem, and automating it only makes it faster to get wrong.
Which HR work is a good automation candidate, and which is not
The test is not how tedious a task is. It is whether the step produces an outcome for one named individual. Provisioning a laptop does not. Declining an application does.
| HR work | Automate? | Why |
|---|---|---|
| Account, licence and equipment provisioning | Yes | Defined entirely by the role, and a mistake shows up on day one. |
| Document collection: contract signature, bank and tax details, policy acknowledgements, right-to-work evidence where required | Yes | A fixed list against a deadline. The work is tracking who owes what. |
| Checklist orchestration across manager, IT and payroll, and recurring people reporting: headcount, probation dates falling due, expiring certifications | Yes | Waiting, reminding and re-querying. None of it decides anything. |
| Screening and selection: sifting applications, ranking or rejecting candidates | No | Each output is a decision about a named person, and how you use applicant information is itself regulated. |
| Performance ratings, pay, promotion, termination and redundancy selection | No | Legal consequences for an individual, and the reasoning is the artefact you will be asked for later. |
The employee lifecycle as three process families: joining, changing role, leaving
Most HR teams already carry this map as joiners, movers and leavers. It is worth drawing properly, because the three families differ in how often they run, how much they vary, and where the irreversible step sits.
| Lifecycle moment | What starts it | Frequency and variability | Where the approval sits |
|---|---|---|---|
| Joining | A signed contract | Frequent and repetitive; the variants (role, location, contract type) are few and listable | Anything sent to the starter or filed as their record. The hiring decision happened upstream. |
| Changing role | An approved promotion, transfer or pay change | Occasional and highly variable; the exceptions matter more than the happy path | The pay and title change, and any access grant that widens what the person can see. |
| Leaving | A resignation or agreed end date | Rare per person, high consequence, time-critical | Final pay and the leaver record. Access removal can run as code if each step leaves evidence. |
The joiner lane, codified, looks like this.
- 01A signed contract landsTriggerOne specific event starts the lane. If yours starts when somebody remembers, fix that first.
- 02Fit the checklist to this particular starterAI judgmentWhich equipment bundle, which policy pack, which local requirement. The step that genuinely varies, and the one to narrow as the variants become known.
- 03Provision against the role, then chase the open itemsCodeAccounts, licences and equipment follow from role and location. Document requests, manager and payroll tasks, reminders and escalation are schedule work.
- 04Approve anything that reaches the person or their fileHuman approvalThe contract pack, the payroll record, the welcome message. Permanent by design, not a phase that ends once the process is trusted.
A decision about a person keeps a named human on the hook
GDPR Article 22 gives a person the right not to be subject to a decision based solely on automated processing where it carries legal or similarly significant effects, and, where such processing is permitted, the right to human intervention, to express a view and to contest the outcome. Hiring, pay and termination sit squarely there.
That asks for more than a person clicking approve: a screen showing a recommendation and a green button is a rubber stamp. Article 14 of the EU AI Act requires high-risk systems to be designed for effective human oversight: competence and authority for the overseer, and a design that counters over-reliance on the output. So show the reviewer the evidence rather than a score, make disagreeing as cheap as agreeing, and record who decided. In our own product these are the steps an operator pins during the walk-through, so the gate survives into the codified process. The approval patterns guide tiers the rest.
Employment records are a retention obligation, not a filing preference
Under EEOC recordkeeping requirements, employers must keep all personnel and employment records — including every application form, whether or not the applicant was hired — for one year, and two years at educational institutions and state and local government employers. Once a charge is filed, the related records must be kept until final disposition, and payroll records carry a three-year requirement under the ADEA. Your own jurisdiction adds to that list, never shortens it.
So a tidy-up job that deletes stale applicant records, or a sync that overwrites a field without keeping the previous value, is a problem you discover when somebody asks for the file. Decide the retention rule first, then make the automation leave a record of itself: what ran, on which inputs, what a human approved, and when. all-agents records every run and keeps it replayable for that reason.
A readiness rubric for handing one HR lane over
Score one lane — usually the joiner lane — against these five signals before automating it.
| Signal | Not yet | Ready to hand over |
|---|---|---|
| Written trigger | It starts when someone remembers | A specific event starts it: a signed contract, an approved change, a confirmed end date |
| Listed exceptions | Nobody can say what differs for a contractor, a rehire or an international starter | Each variant is written down, with what changes and who handles it |
| Single owner | HR, IT and payroll each own a slice; nobody owns the lane | One named person can say what a correct run looks like |
| Record trail | The evidence that a step happened lives in a sent folder | Every run leaves a durable record of what happened and who approved |
| Decision boundary | The lane ends in a judgment about the person | The lane ends in a task completed; judgments sit outside it, as gates with a named approver |
Two or more “not yet” scores and no tool will help, ours included. Write the lane down first: the procedure guide and the editable templates cost nothing.
Limitations and when not to use this
- This page is educational. It is not employment or legal advice, and not a compliance review of your process. Obligations are jurisdictional: the EEOC guidance cited here is United States federal, GDPR applies where your processing falls in scope, and local law and collective agreements add more. Take advice before changing how people are employed.
- The scope is the operational lanes around employment. It says nothing useful about hiring quality, compensation design or org design.
- Systems that score, rank or profile people are out of scope. Those raise different questions — bias testing, notification, contestability — that this page does not answer.
- Do not automate a lane if you hire a handful of people a year, or while the policy behind it is being rewritten. A checklist and a calendar reminder are cheaper, and survive the rewrite.
Sources
- Recordkeeping Requirements — U.S. Equal Employment Opportunity Commission Accessed 24 July 2026
- Art. 22 GDPR — Automated individual decision-making — GDPR Accessed 24 July 2026
- Background Checks: What Employers Need to Know — U.S. Equal Employment Opportunity Commission Accessed 24 July 2026
- Article 14: Human oversight — EU Artificial Intelligence Act Accessed 24 July 2026
Cost your joiner process first
Work out what one lifecycle lane costs you in hours today, before deciding whether it is worth pinning down.
Cost your joiner process firstUli Prantz
Builds and operates all-agents
Uli Prantz builds all-agents, the process-automation platform this site documents. He writes about the operational side of automating recurring business work: where deterministic code beats model judgment, where it does not, and where a human still has to approve.