How to review a risk policy with AI

Compare two versions, trace each change to a clause and give the policy owner a short list of decisions to make.

Before circulating a revised risk policy, check who would have to act differently on Monday. Start by tracing changed requirements to their source clauses.

I’d use AI to prepare the comparison and surface questions for the policy owner. The review still needs the version in force, the proposed draft, and the approval or delegation schedule. Record the dates and file versions first. The Orange Book gives a useful reference for assigning risk roles and setting a clear process. HM Treasury, The Orange Book

Freeze the versions you are comparing

Use documents the organisation has cleared for the tool. Record the effective date of the signed version and the revision date of the working draft. Include the appendices that name the people who can act or set approval limits. Give each file an identifier the reviewer can follow.

If the signed policy is a scan, check the text extraction against the page images before comparing clauses. Approval limits, references and the words must and may deserve extra attention. NIST describes confidently stated errors as a generative AI risk. NIST, Generative Artificial Intelligence Profile

Give each material change a row

Ask for a short table that identifies the clause in both versions, the proposed change, who has to act and the decision you need. Let the comparison show when the draft adds or removes a requirement. Ask it to flag reordered clauses for a person to resolve.

ClauseChange to checkReview decision
4.2Moves sign-off to OperationsConfirm delegated authority
5.1Removes the deputy contactName a back-up approver
7.3Changes weekly review to monthlyAgree timing and escalation

These sample rows show the shape of a review. In your copy, include the source page for each version and a short excerpt for any material claim.

Check the policy against related documents

Follow the cross-references to the delegation schedule, the risk appetite statement or the relevant operating procedure. If the policy introduces a new approval role, check whether that role can use the required system and whether a deputy has the same authority.

In the sample above, moving sign-off to Operations and removing the deputy contact could leave the approval dependent on one person. Ask who can act when that person is away. Bring the answer back to the policy owner before rolling out the change.

Prepare the decision sheet

Try it
Compare the approved risk policy, proposed draft and delegation schedule provided. Create a row per material change with the source clause and page for both versions, the effect on daily work, the person or role affected and the decision the owner must make. Mark unresolved cross-references and any conflict with delegated authority. Give the reviewer a separate list of missing documents or ambiguities.

Sample the model’s output against both versions, with particular attention to changed owners, thresholds and time limits. Record corrections. Give the policy owner a decision sheet that names the proposed approver, the affected procedure and the training or system change required. Route interpretations of legal obligations to the organisation’s qualified reviewer.

Check what changes on Monday

Ask the process owner to take one case from the old procedure and explain how they would handle it under the new draft. If they cannot find who approves it or when it escalates, hand that question back to the policy owner. Close the review with the final approved wording and the implementation owner.

Sources