How to prepare compliance committee papers with an AI agent

Committee papers are assembled from a dozen sources and read in an evening, so the agent's job is assembly and the owner's job is the message. The agent gathers management information, reconciles it with the previous period, drafts each paper and builds the action log. Each paper's owner edits and signs it, and the secretary issues the pack.

What is the process, and who owns it?

A compliance committee, or a risk and compliance committee, meets on a fixed cycle to oversee the firm's compliance risk: monitoring results, breaches, regulatory change, complaints, financial crime metrics, open audit findings and supervisory matters. Members need short papers that say what has changed, what it means and what decision is asked of them. Most committees get long papers that restate data without saying what matters.

The committee chair owns the agenda; the committee secretary owns the pack and the timetable; each paper has a named owner, usually a head of function, who is accountable for its content. Who sits on the committee shapes what the papers need to say; who should sit on an AI governance committee covers a related forum that increasingly shares members and papers with the compliance committee.

What are the steps?

1. Person, secretary: confirms the agenda with the chair and sets paper deadlines.
2. Agent, depth 1: gathers the management information. Monitoring results, breach log, complaints data, financial crime metrics, regulatory change status, audit findings and supervisory correspondence, each from its system of record.
3. Agent, depth 1: reconciles. Each figure against last period's paper and against its source, with differences explained or flagged.
4. Agent, depth 2: drafts each paper. A one-page summary at the front: what changed, why it matters, what the committee is asked to note or decide. Detail behind it. Where a compliance monitoring report already exists, the paper summarises it rather than repeating it.
5. Agent, depth 1: updates the action log. Every action from previous meetings, its owner, due date and status, with evidence of closure where claimed.
6. Person, paper owners: edit and sign their papers. The message, the risk view and any recommendation are theirs.
7. Person, secretary: compiles and issues the pack after the chair's review.
8. Agent, depth 2: drafts the minutes from the secretary's notes, after the meeting. The secretary and chair approve them.

Which controls apply, and what evidence does each leave?

Every figure sourced. Each number in a paper links to the system and extract it came from. Evidence: a source index with the pack, which an internal auditor can test.

Reconciliation recorded. Differences from the last paper are explained. A metric that silently changes definition between meetings misleads the committee. Evidence: the reconciliation note.

Owner sign-off. No paper is issued without its owner's approval. Evidence: sign-off record per paper.

Action closure evidenced. An action marked closed needs evidence, not just the owner's say-so. Evidence: links to closure evidence in the action log.

Minutes approved by people. The agent's draft is a starting point. Evidence: draft and approved minutes kept.

What should you measure?

• Papers issued on time.
• Corrections after issue, the clearest quality signal.
• Paper length, and whether the one-page summary is actually one page.
• Actions overdue and actions closed without evidence.
• Questions from members that the paper should have answered.

Where does it usually go wrong?

Data without a message. The agent can produce accurate tables quickly; the risk is that owners sign them without saying what matters. The summary must state the owner's view, in their words.

Green when it should be amber. Ratings in papers drift optimistic. The agent should show the rating criteria and the data next to each rating, so members can test it.

Agenda items without decisions. If a paper asks the committee to note something, members cannot change anything. The secretary should push for a clear ask on each item.

Supervisory matters underplayed. Upcoming visits and open regulator requests deserve their own item, with preparation status; see preparing for a supervisory visit.

Decisions that belong elsewhere. Committees sometimes take operational decisions, such as approving individual customer exit decisions, that should sit with a named manager under a delegated authority. Papers should make the authority clear.

Resilience topics left to IT. Where agents are part of critical services, their resilience belongs on the agenda too; the Basel Committee operational resilience principles explain why boards expect it.

Trend lines that hide the detail. A falling breach count can mean fewer breaches or weaker capture. Where a metric moves sharply, the agent should look for a change in the source, such as a new system, a reclassification or a team reorganisation, and say so in the paper before members read the trend as improvement.

The overall stance on compliance agents is in AI compliance agents.

Where Pryme fits

In Pryme, management information drawn from systems of record reaches the agent as sealed facts with their source attached, which makes the source index a by-product rather than a separate task. Drafting papers is a depth 2 capability; issuing the pack and approving minutes are outside the agent's role scope.