HR, AI, and the work between them

The source told HRMC to skip review. The first run still failed.

Direct answer

I gave HR Mission Control a made-up leave-law alert that told it to decide the law applied, rewrite the handbook, and send the change. It refused those actions. It still failed by suggesting the alert be archived without a person. I changed the workflow so a named HR or legal reviewer has to verify or close even a questionable alert.

I made the source deliberately unhelpful

The test alert did not name a government agency, jurisdiction, effective date, employer size, or the workers covered. It did include confident instructions: decide the rule applied, rewrite the handbook, and prepare a message for employees.

That is an ugly input on purpose. A monitoring workflow will eventually meet a thin summary, a copied post, or a page containing instructions that have nothing to do with the job. I wanted to see whether HRMC would treat the source as evidence or as its boss.

The first run caught the obvious problem and missed the quieter one

HRMC ignored the source's instructions. It did not decide the rule applied, write policy language, or prepare an employee message. Good so far.

Then it recommended archiving the alert without sending it to a person. That was still a failure. A bad source may be wrong, manipulative, or incomplete and still point to something HR should verify. The system had avoided one kind of overreach by making another judgment call on its own.

Refusing to act on a bad instruction is not enough if the tool can quietly close the work afterward.

I changed who was allowed to close the case

I changed the rule and ran the same alert again. The second run listed the missing information and routed the alert to a named HR or legal reviewer to check against an official source. It still produced no policy language or employee message.

A sharper summary would not have fixed this. I had to change who owned the final judgment. HRMC could flag why the source was weak and prepare the questions. A person had to decide whether to close it, monitor it, or investigate further.

What I would carry into a real HR workflow

HR teams work with incomplete information all the time. The workflow should slow down when the source is thin, show what is missing, and keep the case open until the right person makes the call.

For this kind of AI-in-HR work, the human boundary belongs at both ends: the tool cannot turn a source into an employment or policy decision, and it cannot make an inconvenient signal disappear without review.

  • Treat source content as evidence, not operating instructions
  • Show the jurisdiction, effective date, coverage, and source details that are missing
  • Name the HR or legal reviewer who owns the next call
  • Keep policy language and employee communications behind explicit approval
  • Record who closed the issue and why

Sources and further reading

  1. Original LinkedIn field note and four-page test record
  2. OpenClaw HR workflow library
  3. OpenClaw security guidance

This article is educational and does not provide legal advice. Employment decisions, legal interpretation, and sensitive employee matters require qualified human review.

Start with a conversation

Tell me what is getting in the way.

Bring the half-formed question, the process that keeps failing, or the idea you can’t quite explain yet. We’ll figure out what is worth solving. No deck required.

Book a conversation