Hear about the change before it becomes a finding.
Hendl's monitors watch the regulation you care about, agents map every change to your policies and live casework, and oversight runs on a record that's complete by construction — not assembled the week before the audit.
Compliance teams spend their judgement on paperwork.
Reading feeds, chasing attestations, sampling files, assembling evidence — the work that fills a compliance team's week is exactly the work agents should be doing.
From horizon to case file, one connected loop.
Monitors watch the horizon, agents translate change into policy and controls, and the same platform runs the casework those controls govern — so nothing falls between systems.
Standing watchers over your domains — legislation, regulators, ombudsmen and codes.
Each change read against your policies, controls and live casework, with the overlaps cited.
Policies and procedures versioned, mapped to obligations and pushed to the teams they govern.
Sign-offs requested, chased and logged — with the laggards visible.
Every first-line decision checkable against the policy version in force.
Implementation dates and reporting cycles tracked with escalating alerts.
Information requests and s.166-style reviews drafted from the record.
Any obligation, policy or case exports as a time-stamped, citable trail.
From the gazette to the front line, in days.
A monitor flags the change, agents assess the impact against your policies and live cases, and the updated procedure reaches the front line with the trail already written.
What compliance teams see.
Based on early deploymentsOversight that reads the record, not reconstructs it.
Because the casework runs on the same platform, the second line reviews what actually happened — every decision, policy version and exception, as it occurred.
Every change, assessment and sign-off time-stamped and exportable.
Every case decision tied to the policy version in force when it was made.
Assessments and rollouts carry a named owner — SM&CR-ready attribution.
Controls tested against every case, not a quarterly sample.
Every impact call cites the rule text and the policies it touches.
Second-line workspaces separated from the first line they oversee.
Questions compliance leaders ask.
Which sources can monitors watch?
Legislation, regulator publications, ombudsman decisions, codes of practice and consultation papers — you choose the domains, monitors watch them continuously.
Does impact assessment replace our judgement?
No. Agents read the change, find the overlaps and draft the assessment with citations — your team makes the call, and the call is logged under their name.
Can it oversee casework we run outside Hendl?
Best results come when the casework runs on Hendl, but agents can also review exported files from other systems against your policies.
How does this help in an audit or skilled-person review?
The record is the evidence — obligations, assessments, policy versions and case decisions export as one cited, time-stamped trail.
Stay ahead of the change. Prove it on demand.
Start with one regulatory domain — monitors and impact mapping running on your own obligations in weeks.