What is regulatory change management?

Regulatory change management is the process by which a regulated firm identifies new or amended rules, works out how they affect its business, assigns owners, changes its policies, processes and controls, and evidences that the change was made on time. Once AI agents do regulated work, it also includes updating each affected agent and recertifying it.

Why does regulatory change matter once agents act?

A new rule used to land in a policy document, a training session and a process change. Staff read the update and adapted. An agent does not read the circular. It follows its brief, its sources and its bounds. If those are not changed, the agent keeps working to the old rule, consistently and at scale, after the effective date.

That makes agents both a risk and a help. A rule change that affects 20 processes may affect a dozen agents, each needing a brief update, new sources and fresh evidence that it behaves correctly under the new rule. Agents can also do much of the reading, which is why we say that for agents in regulatory change, the reading is not the work: the work is deciding what changes and making it.

How does the process work in practice?

Most programmes follow five stages:

1. Identify: watch regulators' publications and consultations. An agent can track regulatory change and summarise each item.
2. Assess: decide whether and how the change applies, using a regulatory change impact assessment.
3. Plan: assign an owner and a deadline for each required change.
4. Implement: update policies, processes, systems, training and agents.
5. Evidence: record what changed, when and who approved it, in a regulatory change log.

An example from a consumer lender

Take a consumer lender facing a revised rule on how arrears must be communicated. The tracking agent flags the final text and drafts a summary with the changed requirements. Compliance assesses it and finds three affected processes. One is run by a collections agent that drafts arrears letters.

The impact assessment lists that agent explicitly: its letter templates, its source policy and its escalation rules must change. The process owner approves a new brief; the agent is replayed against past cases with the new rule applied; it is recertified before the effective date. Until then, it keeps working under its old certificate, and anything it drafts that the new rule would affect is held for a person.

How is regulatory change management different from horizon scanning?

Horizon scanning is the first stage only: watching for what is coming, including consultations and speeches that may never become rules. It produces awareness.

Regulatory change management carries an item from awareness to evidenced implementation. Horizon scanning can be done well by an agent largely on its own, at read depth. Change management needs owners, decisions and sign-offs at every step, and its output is changed controls, not a newsletter. Firms that confuse the two end up well informed and non-compliant.

Which terms sit next to regulatory change management?

• Impact assessment: the analysis of what a specific change means for the firm.
• Effective date: when a rule starts to apply, which sets the deadline for agents too.
• Compliance agents work in the second line, never as the last word, including on change.

Where Pryme fits

In Pryme, a rule change that alters an agent's brief or sources is a change to that capability, so its certificate no longer covers the new behaviour. The agent is replayed in Attest against cases that reflect the new rule before it acts under it, and the record shows which version of the brief applied on any date.