UAE · ENBook a demo
Insure AIManagementDecision-maker

Risk Tracking Agent

Keeps project risks and mitigations current.

Risk Tracking AgentProject Delivery
Industry
Insure AI
Department
Management
Team
Project Delivery
Kind
Decision-maker
Approver
Compliance Officer
Code
MGT-05

It keeps the risk registers of the insurer's projects current, scoring new and changed risks on likelihood and impact and tagging those that touch conduct, data protection, solvency reporting or operational resilience. It checks every mitigation is owned and on schedule, proposes which risks to escalate, accept or close, forecasts the effect on exposure and updates the register.

How it works

7 steps, and a person signs off before step 7.

  1. 01Looks it up

    Finds the record the request is about in the project risk register: the current risks, scores, owners and mitigations for the project named..

  2. 02Reads the request

    Works out what is being asked and what a complete answer needs.

  3. 03Checks the facts

    Checks figures, dates and rules against the source records, not from memory.

  4. 04Forecasts, when it decides

    Projects what each option will cost or return before it recommends one.

  5. 05Works it through

    Prepares the draft, match, recommendation or reply, with its sources.

  6. 06Asks a person

    Hands the work to Compliance Officer with its reasoning before anything goes out.

  7. 07Acts

    Once approved, it acts in the project risk register: it updates each risk's score, status and mitigation and records the escalations. and records what was done.

What it works with

Your knowledge, your systems, your people.

Knows

The enterprise risk framework: the likelihood and impact scale, risk appetite statements for conduct, solvency, data and operational resilience, the escalation route to the risk committee, and the rule for when a project risk becomes a reportable incident.

Reads from

the project risk register: the current risks, scores, owners and mitigations for the project named.

Acts in

the project risk register: it updates each risk's score, status and mitigation and records the escalations.

Hands back

A list with one entry per risk, each with risk_id, description, category, likelihood, impact, score, owner, mitigation_status (on_track, late or none), proposal (escalate, mitigate, accept or close) and reason.

Asks a person when

A risk scores at or above 15, a conduct or data risk is proposed for acceptance, a risk has materialised, or a risk is proposed for closing.

ApproverCompliance Officer

Settings

Your limits, set by your managers.

SettingDefaultWhat it controls
Score that goes to the risk committee15A risk scoring at or above this (likelihood x impact) is escalated.
Score below which a risk may close4A risk below this with its mitigation done is proposed for closing.
Mitigation overdue after (days)7A mitigation this late is flagged.
Appetite for conduct and data risksnoneHow much conduct, customer-harm and data protection risk may be accepted.
Every risk needs an ownerOnWhen on, a risk with no named owner is returned, not scored.

Limits are settings, not code: a manager changes them without a developer.

Rules it always follows

  • Score each risk as likelihood times impact; at or above 15 it goes to the Compliance Officer for the risk committee.
  • With none appetite, a conduct, customer-harm or data protection risk is never accepted beyond that appetite; it is mitigated or escalated.
  • A materialised risk that harmed policyholders or exposed health data is reported as an incident to the Compliance Officer the same day.
  • Flag a mitigation more than 7 days late.
  • Propose closing a risk only when its score is below 4 and its mitigation is done.
  • When on is true, return any risk with no owner.

See the Risk Tracking Agent agent on your own work.

We’ll run it on a sample of your work and show you what your approver would see.

Risk Tracking Agent · Insure AI | Basinwright Industries