Compliance Radar · Practitioner Spotlight · September 2026

Practitioner Spotlight
Compliance works when ownership survives the handoff.
Matt Triola, Human Resources Executive at Zelis, shares a practical framework for keeping human judgment, named ownership, and durable follow-through inside automated HR and compliance processes.
September’s Compliance Radar focused on the ownership gaps that appear after a policy is written, a system is automated, or an initial approval is complete. Matt Triola’s responses return to the same operational test: can another person see what needs to happen, who owns it, and how exceptions are handled?
“Automation can complete tasks, but it doesn't eliminate accountability.”
This draft accompanies September’s Compliance Radar.
IN CONVERSATION
Before a manager changes an employee’s status because of a health-related concern, what ownership or escalation checkpoint should be in place?
The first checkpoint should be HR review before any employment-status decision is made. Managers should not independently decide that someone can no longer perform their job because of a medical concern.
HR needs to separate what we know from what we assume. What are the actual job requirements, what limitation has been communicated, and do we have objective information supporting the concern?
Before termination or removal from a role, HR should make sure the organization has considered any required interactive process, accommodation, leave, or other protections that may apply.
When an emerging AI rule affects HR technology, how do you decide what to inventory now, what to monitor, and what not to overstate?
I generally separate things into three buckets: what we need to act on now, what we need to understand, and what we need to monitor.
First, I would inventory where AI is already being used: recruiting, screening, performance management, compensation, workforce planning, employee relations, etc.
Then determine who owns each tool, what decisions it influences, what data it uses, and whether there is human oversight.
For proposed legislation, I would avoid immediately telling the organization, "The law now requires this." Instead, communicate clearly that this is developing and here is what we are doing to prepare.
Preparation usually has value even if a proposal changes. Knowing where AI exists, who owns it, and how decisions are made is good governance regardless of the final legislation.
STAY UP TO DATE
Get the Compliance Radar and Practitioner Spotlight in your inbox.
One practical monthly briefing for HR and compliance leaders, plus conversations with practitioners doing the work.
Where do organizations lose ownership after the initial approval, and what makes follow-through more durable?
The biggest risk is assuming that because something was compliant on day one, it will remain compliant indefinitely.
Every important process should have a named owner, not simply a department. Someone should know, "This is mine to review."
I like recurring checkpoints—quarterly, semiannually, or annually depending on the risk, with a simple question: Has anything changed that would affect the original approval?
Technology can create the reminder, but somebody still has to be accountable for reviewing the information and taking action.
How can an HR team introduce a new compliance check without creating a process that depends on one person remembering it?
Build the requirement into an existing workflow or system whenever possible rather than creating a completely separate manual process.
Establish three things from the beginning: an owner, a backup owner, and a documented escalation path.
Automate reminders where possible, but also have some type of reporting or audit mechanism so leadership can tell whether the check is actually happening.
My test would be: If the person who normally handles this went on vacation for three weeks, would the process still work? If the answer is no, the process is too fragile.
What is one question more leaders should ask before they call a process compliant or automated?
Organizations sometimes focus so much on whether a process is automated that they forget about the exceptions.
Automation can complete tasks, but it doesn't eliminate accountability. Someone still needs to understand the output, monitor exceptions, and decide when human judgment is required.
Similarly, being compliant today doesn't necessarily mean the organization has built a sustainable compliance process.
PRACTICAL TAKEAWAYS
What leaders can put into practice
- Put HR review and a named decision owner before a manager changes an employee’s status over a health-related concern.
- Inventory where AI influences people decisions, identify the owner and the human oversight, and describe emerging rules accurately.
- Assign an owner, backup owner, and escalation path to recurring compliance checks.
- Use automation to create reminders and visibility, but keep a person accountable for exceptions and action.