Skip to content
Back to articles

Why Isn't AI Helping With HR Compliance Work?

November 6, 2026 8 min read
Share
Grey in-tray of charcoal folders with one orange folder pulled out, symbolizing why isn't AI helping with HR compliance work

The leave request sits in the queue for the third day running. Someone in HR is cross-referencing it against a state policy update, a collective bargaining agreement, and an exception granted to someone in a different department, because the AI system flagged it as "needs review" and offered no reasoning anyone trusts enough to act on alone. The license got approved last year. The adoption never did.

This piece is about why that keeps happening. The AI model is usually working as designed. The process around the decision was never rebuilt to let it help.

Why hasn't AI reduced the manual work in HR compliance decisions?

Most HR compliance decisions still require someone to weigh context, precedent and risk, and the process around them was never defined clearly enough for AI to take a share of it. The workflow does not route any part of the decision to AI, so the specialist still does all of it.

Most compliance cases in HR are not one thing. A leave request involves a federal rule, a state rule, a company policy, and sometimes a manager's informal precedent from two years ago that nobody wrote down. Before anyone asks AI to help, someone needs to have mapped which of those inputs are stable rules and which are judgment calls dressed up as rules.

That mapping work is unglamorous. It means sitting with HR specialists and asking what they check, in what order, and which parts they would never delegate even to a trusted colleague. Few organizations do this before buying. They buy, point AI at the case queue, and wonder why the specialists keep doing the work by hand.

This is where the AI Profitability Gap shows up in HR: licenses paid for, adoption flat, and a process underneath that was never redesigned to let AI carry any real share of the work.

Should AI be making leave or compliance determinations at all?

AI should narrow and prepare compliance determinations, and a named person should make them, because the risk of a fluent but wrong answer is highest where judgment and accountability matter most.

There is good evidence for that caution. In a preregistered experiment with 758 knowledge workers, run with Boston Consulting Group on realistic consulting tasks and published as a Harvard Business School working paper in September 2023, people using GPT-4 on tasks inside AI's capabilities completed more of them, faster and at higher quality. On a complex task chosen to sit outside those capabilities, they were 19% less likely to reach a correct solution than colleagues working without AI. The researchers called that uneven boundary a "jagged technological frontier." Compliance decisions, full of edge cases and institutional precedent, sit on the harder side of it.

Weak AI output in this context rarely looks weak. It reads fluently, cites a policy section and sounds confident. That is what makes it dangerous where someone has to own the outcome if a determination is challenged.

So the useful question for leaders is a set of questions, asked before AI goes near a case: what problem the work is solving, what kind of judgment it requires, where a person makes the biggest difference, where trust matters most, and who owns the outcome when something goes wrong.

Where the edge sits

The edge of AI's reliability in HR compliance moves. It depends on how well the policy is documented, how closely the case resembles earlier ones, and how much discretion the role has. Finding that edge in your own organization is groundwork, and it has to happen before AI is trusted with anything.

Why do HR teams still handle case-by-case decisions manually after rolling out AI?

Managers were never given the guardrails, training or permission they needed to trust AI's output, so they default to the slower method they know works. The license got distributed and the decision authority stayed where it was.

Managers need a credible story about why the organization adopted AI for this work and what a good outcome looks like. They need clear guardrails on where AI use is encouraged or restricted, and explicit permission to manage the transition rather than enforce it from above. Without those, a manager facing a borderline leave case will fall back on the manual process every time, because that is the one where they know who is accountable if it goes wrong.

Training on the software is not enough either. People need to understand how AI fits into the compliance workflow: where to use it, how to judge its output, which guardrails apply, and when a second person has to look.

A specialist who keeps doing the manual check is telling you something true about where trust has not been earned yet. Reading that signal is more useful than mandating faster adoption around it.

What does it take to redesign an HR process so AI helps with it?

Start by mapping the existing workflow honestly: which steps are repetitive, which require judgment, where the bottlenecks sit, and which parts nobody has examined in years. AI gets placed into that map afterwards.

The book makes the point directly: it is very difficult to redesign work that nobody has properly examined. If the organization has not worked out which parts of the compliance process are broken, where workarounds have crept in, and which tasks are repetitive and which need a person to weigh competing facts, AI creates more confusion than it resolves. Clean up the workflow first.

From there, the redesign has a clear shape. AI drafts the first-pass summary of a case and flags the applicable policies. A specialist reviews the summary against the parts of the case that need judgment. The final determination carries a named owner whether or not AI touched it. The specialist's job changes, with less repetitive drafting and more of the decision-making their expertise is for.

Leaders also need evidence that this is working, in terms people recognize. An early win here is specific: case turnaround drops, the backlog shrinks, or specialists spend less time on repetitive steps and more on the judgment calls. "We launched it" tells people nothing.

How do you know if the redesign is working or just adding another layer of process?

It is working when specialists choose to route more cases through the new workflow, and when the time saved shows up in turnaround and backlog figures. Usage numbers alone will not tell you that.

Watch the distance between what leadership reports and what specialists do when nobody is checking. If people complete the mandatory steps in the new process and then redo the judgment call by hand because they do not trust the AI-assisted version, the redesign has added a layer and changed nothing.

Another honest signal is whether managers can say, without hesitating, where AI is supposed to help in this workflow and where a person has to own the call. If that answer is fuzzy, the guardrails were never clear enough to build trust, and more training will not fix it.

What's the real cost of leaving this unresolved?

The license is the smaller cost. The larger one is the trust lost between HR leadership and the specialists who were told AI would help them and found it added a step.

That loss compounds. The next technology initiative lands on a team that has learned to treat new systems as extra work. Rebuilding that trust takes longer than building it would have the first time, and it starts the same way: mapping the workflow, naming where judgment has to stay with a person, and giving managers the backing to make the transition real. The Elephant in the Algorithm walks through this in more depth, including why the jagged frontier makes compliance work such a hard case for blanket automation.

If you already know this is where your adoption stalled and want a structured way to rebuild the process around the people accountable for the outcome, see how the AI Profit Partnership works. It ends in a plan for the path from case intake to determination that gives AI a bounded role and leaves specialists the judgment work that needs them.

Take it with you

Download this as a PDF

A clean, branded version to read offline or share with your team.

Frequently Asked Questions

Why does AI struggle with HR compliance decisions?

Compliance decisions combine overlapping rules, precedent and judgment calls that are often not written down. AI handles well-defined, pattern-based work reliably, but compliance cases often sit outside that zone, where fluent output can still be wrong and nobody has mapped which parts need a person's judgment.

How long does it take to redesign an HR compliance process for AI?

It depends on how well your current policies and precedents are documented, and how much discretion specialists use case by case. A process with clear written rules maps faster than one built on informal precedent. Map the workflow honestly before estimating anything.

Should we pause our AI compliance system while we redesign the process?

Narrow where it is trusted instead. Let AI draft case summaries and flag applicable policies while specialists keep the final judgment. That keeps it useful while the workflow is mapped and the guardrails are defined.

What should managers be told before they are expected to use AI for compliance cases?

Why the organization adopted AI for this work and what a good outcome looks like, where AI use is encouraged and where it is restricted, and that they have permission to raise concerns and use judgment. Without those, managers fall back on the manual process.

Is low AI adoption in HR compliance a training problem?

Rarely on its own. Training on the software helps less than understanding how AI fits the actual workflow: where to use it, how to judge its output, and when a person must review. Low adoption usually points to an undefined process.

Share
Newsletter

With People

The people side of making AI pay.

  • One story from the news about AI at work, read through our book, The Elephant in the Algorithm.
  • A few links worth your time, and sometimes a podcast conversation.
Privacy Policy