← Selected work

Case 02 / Govern

Payroll / HR
Control Lab

Where should systems, rules, AI and Human judgment each operate in payroll work?

Independent controlled simulationNot an employer deployment

Payroll is highly structured—but structured does not mean risk-free.

Hours, rates, overtime rules, deductions, eligibility, and system configurations can all be automated. Yet a system can execute its instructions perfectly and still produce the wrong business outcome.

That led to a broader question:

When payroll work is redesigned around automation and AI, where should automation authority stop?

Major Drilling America

This question came from operating experience, not from an AI exercise.

At Major Drilling America, I supported the ADP → Dayforce transition, including parallel validation, testing/UAT, employee and timekeeping data review, payroll reconciliation, exception correction, and go-live readiness.

During reconciliation, I identified an overtime configuration discrepancy before payroll release.

≈ $4,400Incorrect / excess pay prevented before release

The system was not failing to calculate.

It was calculating according to a configuration that would have produced the wrong business result.

That distinction became the starting point for this independent lab.

Real payroll contains different kinds of work.

A simple automation model assumes:

Input Calculation Payment

Rules
What should happen under known conditions?
Systems
How should authorized transactions be processed?
Exceptions
Where do expected and actual results disagree?
Investigation
Why did they disagree?
Judgment
What does the evidence actually support?
Authority
Who is allowed to change the result?

Processing work and decision authority are not the same thing.

Allocate work by capability—and by authority.

I separated the workflow according to what each participant is actually good at—and what authority it should hold.

RulesDeterministic control
  • Calculate
  • Compare
  • Validate required conditions
  • Apply thresholds
  • Flag defined exceptions

Same authorized inputs should produce the same result.

SystemsControlled execution
  • Store authorized data
  • Execute configured calculations
  • Maintain workflow state
  • Record transactions and changes
  • Enforce permissions

The system executes authority. It should not invent it.

AIInvestigation capacity
  • Compare records across sources
  • Surface anomalies
  • Identify patterns
  • Generate possible explanations
  • Expose contradictory evidence
  • Prepare information for review

AI can make investigation faster. Its explanation is a hypothesis—not authorization.

HumanJudgment & authority
  • Evaluate evidence
  • Resolve material ambiguity
  • Approve corrections
  • Interpret policy where necessary
  • Determine escalation
  • Authorize overrides
  • Own the consequence

Human attention should be concentrated where judgment actually matters.

The Human role should not be moving information between systems simply because the systems cannot communicate.

Human attention should be concentrated where judgment actually matters.

Detection explanation authorization

Detection
Something appears inconsistent.Rules, systems, or AI may identify it.
Explanation
Why might it have happened?AI may investigate and propose possibilities.
Authorization
What should actually change?Where employee or financial consequences are material, the appropriate Human authority decides.

A detected anomaly is not automatically an error.

A plausible explanation is not automatically true.

And neither grants authority to alter payroll.

Two paths. Different control needs.

Normal path

  1. Authorized data
  2. Deterministic validation
  3. System processing
  4. Reconciliation
  5. Release

When evidence agrees and the transaction remains within defined authority, adding Human relay can create work without adding control.

Exception path

  1. Exception detected
  2. Evidence assembled
  3. AI-assisted investigation where useful
  4. Human judgment
  5. Authorized action / escalation / no action
  6. Evidence retained

AI belongs inside the investigation path. It does not hold release authority.

Control the failure, not just the process.

Correct calculation / wrong configuration

A system faithfully executes an incorrect rule.

Control: Reconciliation and independent expected-result checks.

Plausible explanation / insufficient evidence

AI proposes a convincing explanation for a discrepancy.

Control: Separate hypothesis from verified evidence.

Correct detection / unauthorized correction

An anomaly is correctly identified, but an automated correction exceeds its authority.

Control: Material changes require defined approval authority.

Human present / no meaningful oversight

A Human clicks “approve” after AI has already framed the issue, selected the evidence, and recommended the action.

Control: The reviewer must have sufficient evidence, understandable reasoning, and real ability to reject or escalate.

Human-in-the-loop does not automatically mean meaningful Human oversight.

End in an evidence state—not an AI confidence score.

Exceptions should end in an evidence state—not simply an AI confidence score.

Pass
Evidence supports the proposed conclusion or action within defined authority.
Fail
Evidence contradicts the conclusion or a required control was not satisfied.
Unknown
Evidence is insufficient to justify a conclusion.

Sometimes UNKNOWN is the correct controlled result.

The appropriate response may be additional evidence, Human review, or escalation.

Reduce Human relay. Preserve Human judgment.

A common Human-in-the-loop model:

Automation does the work Human checks it

That can leave people performing routine review, transferring information, or rubber-stamping machine recommendations.

The lab produced a more deliberate allocation:

Rules
Handle deterministic logic.
Systems
Execute authorized transactions.
AI
Expand investigation capacity.
Evidence
Constrain conclusions.
Humans
Own material judgment, escalation, and authority.

Reduce unnecessary Human relay.Preserve meaningful Human judgment.

Independent controlled simulation.
Not an employer deployment.

Real payroll and HRIS operating experience informed the problem and control assumptions.

The AI-enabled work-design model itself is independent work.

It has not been deployed at Major Drilling America or represented as an employer AI transformation.

Model developed
Current state
Control logic defined
Current state
Employer deployment
Not claimed

Technology changes work. Decision rights must change deliberately.

This case started with payroll, but the underlying problem is broader:

When technology becomes more capable, how should work and decision rights change around it?

The answer is not to automate everything possible and add a Human approval button at the end.

  • Calculation from judgment
  • Detection from explanation
  • Explanation from authorization
  • Human presence from meaningful oversight
  • Technical capability from decision rights

Automate the deterministic.Accelerate the investigative.Preserve Human authority where consequences become material.

AI can change who—or what—does the work.

It does not eliminate the need to decide who owns the consequence.

Two evidence categories. Kept separate.

Real operating evidence

01

ADP → Dayforce Transition

Parallel validation, UAT/testing, reconciliation, exceptions, and go-live support.

Evidence retained / not publicly displayed
02

Payroll Control Exception

Overtime configuration discrepancy identified before release; approximately $4,400 incorrect/excess pay prevented.

Evidence retained / not publicly displayed

Independent lab evidence

03

Work Allocation Model

Rules / Systems / AI / Human authority boundaries.

Evidence retained / not publicly displayed
04

Exception Decision Model

Detection → Investigation → Evidence → Judgment → Authorized action.

Evidence retained / not publicly displayed
05

Evidence State Model

PASS / FAIL / UNKNOWN.

Evidence retained / not publicly displayed