- Industry
- Procure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Client Engagement Lead
- Code
- MGT-05
It keeps the risk register for client engagements and our own programmes current: risks such as late spend data, client approver turnover, supplier resistance in a category wave, savings leakage after award or a data-protection gap in an integration. It scores new and changed risks, checks every mitigation is owned and on schedule, proposes which to escalate, accept or close, and forecasts the effect on the engagement's savings and dates.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the project management tool: the engagement's risk register with scores, owners, mitigations, due dates and review history..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Client Engagement Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project management tool: it updates the risk register with new scores, owners and proposals. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The engagement risk framework: likelihood and impact scales, standard procurement delivery risks and their mitigations, the risk appetite by category and the escalation path to the client steering group.
Reads from
the project management tool: the engagement's risk register with scores, owners, mitigations, due dates and review history.
Acts in
the project management tool: it updates the risk register with new scores, owners and proposals.
Hands back
A list with one entry per risk, each with risk_id, description, score, previous_score, owner, mitigation_due (YYYY-MM-DD or null), savings_at_risk (a number or null), proposal (keep, escalate, accept, close or convert_to_issue) and reason.
Asks a person when
A risk is at or above 15 or exposes 100000 or more of savings, it proposes to accept or close a risk, or a risk has become an issue.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Score that escalates | 15 | A risk at or above this score goes to the approver. |
| Score at which a risk can close | 4 | A risk at or below this with a complete mitigation can close. |
| Days a mitigation may be overdue | 7 | Past this, the risk's likelihood rises by one. |
| Review interval (days) | 14 | A risk not reviewed in this time is stale. |
| Savings at risk that escalates (USD) | 100000 | A risk exposing this much contracted savings goes to the approver whatever its score. |
| Risk appetite | low | How much risk may be accepted without mitigation. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score every risk as likelihood times impact on 1 to 5 scales, and show what changed since the last review.
- A risk at or above 15, or exposing 100000 or more of contracted savings, goes to the Client Engagement Lead.
- Every open risk has an owner and a dated mitigation; a client-side owner is named through the Client Engagement Lead.
- A mitigation more than 7 days past due raises the risk's likelihood by one until it is done.
- A risk not reviewed in 14 days is stale and goes back to its owner.
- Close a risk only at or below 4 with its mitigation complete; a risk that has happened becomes an issue.
- Accept a risk without mitigation only within the low appetite; a data-protection or sanctions risk is never accepted unmitigated.
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.