By Prof. Hernan Huwyler, MBA CPA CAIO AI GRC Director · Academic Director, IE Law School
Published 19 · Last reviewed 19
- Compliance automation works only in order: clean, owned data first, then rules as code, continuous evidence, and governed AI agents.
- Seven use cases show the current practices, from regulatory change and DORA registers to GDPR requests and pharma deviations.
- Govern the automation itself: keep humans accountable for risk decisions, log everything, and pilot one process.
Every regulatory change, every control test, and every audit request costs a compliance team manual effort that grows faster than the team does. Analysts read new texts and map them to policies by hand. Control owners take screenshots that are stale the moment they are saved. Auditors sample a few dozen items and everyone hopes the rest looked the same. The business problem is not a shortage of dashboards. Assurance still depends on people moving information between systems, and people do that unevenly and late.
The practical answer today is to automate in four layers and to build them in order. First, fix the data that automation will read: a clean taxonomy of policies, risks, and controls, each with one named human owner. Second, express rules as code so a bad action is blocked before it happens instead of found at the next test. Third, collect evidence continuously into packages an auditor can re-perform. Fourth, add AI agents that draft and route work, with a named person approving anything that carries risk. Skipping a layer produces automated answers that are fast and wrong.
This article is for compliance officers, internal auditors, risk owners, and GRC platform owners who must show results this year. It starts with the problem and the value at stake, reviews the first-generation approaches most programs already run and where they stop, and then walks through seven use cases with their technical implications and implementation advice. It closes with how to govern the automation itself and a starting plan. Each section stands alone, so you can jump to the use case that matches your current backlog.





