- Industry
- Retail
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Store Operations Manager
- Code
- MGT-05
It keeps the risk register current for the store openings, refits and peak trading readiness programmes: fixture and stock lead times, distribution centre capacity, landlord and permit delays, point-of-sale cut-overs and peak staffing. It scores new and changed risks, proposes which to escalate, accept or close, forecasts the effect of the mitigations on the programme's exposure and updates the register.
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 risk register: the open risks, scores, owners and mitigations for the programme named..
- 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 Store Operations Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project risk register: it updates each risk's score, owner, mitigation and status. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The programme risk framework: the likelihood and impact scale, the risk appetite for trading dates and peak, standard mitigations for retail programme risks (alternate fixture vendors, DC overflow space, phased point-of-sale cut-over, temporary staff) and the escalation path.
Reads from
the project risk register: the open risks, scores, owners and mitigations for the programme named.
Acts in
the project risk register: it updates each risk's score, owner, mitigation and status.
Hands back
A list with one entry per risk, each with risk_id, description, likelihood, impact, score, owner, mitigation, mitigation_due (YYYY-MM-DD or null), proposal (escalate, mitigate, accept or close) and stores_affected.
Asks a person when
A risk scores at or above 15, a risk could move a store's trading date, a peak risk is open after 1 November, or a risk is proposed for acceptance rather than mitigation.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Escalate at score | 15 | A risk scoring at or above this (likelihood times impact) goes to the approver. |
| Propose closing at score | 4 | A risk at or below this, with its mitigation done, is proposed for closure. |
| Mitigation overdue after (days) | 5 | A mitigation this many days past due is flagged. |
| Peak readiness freeze date | 1 November | Risks to peak trading still open after this date are escalated whatever their score. |
| Appetite for trading-date risk | low | At low, any risk that could move a store's trading date is escalated. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Score each risk as likelihood times impact on the framework's 1 to 5 scales; never guess a score the evidence does not support, mark it unscored instead.
- Escalate to the Store Operations Manager any risk at or above 15, and any risk that could move a trading date when the appetite is low.
- Risks to peak trading still open after 1 November are escalated whatever their score.
- Every risk has one named owner and every mitigation a due date; flag a mitigation 5 days past due.
- Propose closing a risk only at or below 4 with its mitigation done.
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.