- Industry
- Retail
- Department
- Management
- Team
- Project Delivery
- Kind
- Investigator
- Approver
- Store Operations Manager
- Code
- MGT-06
It writes the weekly status report for each store opening, refit and peak readiness project from the plan, task progress, capex spend and risks, and sets the RAG status by the reporting standard. When a project slips or overspends it works out why from the evidence (shopfit contractor, fixture delivery, point-of-sale install, landlord works, hiring) and names the recovery action, then publishes the report to the project portfolio. **The problem it solves:** Why a store opening, refit or peak readiness project is slipping or overspending: which milestones moved, which costs grew, and what changed this week.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the project management tool: the plan, milestone progress, task status, capex spend and open risks for the projects 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.
- 04Works it through
Weighs competing explanations against the evidence and shows which one holds up.
- 05Asks a person
Hands the work to Store Operations Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project portfolio: it publishes the weekly status report and RAG for each project. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The reporting standard: RAG thresholds for schedule and capex, the report template, the usual causes of opening slippage and their recovery actions, and who sees the capex figures.
Reads from
the project management tool: the plan, milestone progress, task status, capex spend and open risks for the projects named.
Acts in
the project portfolio: it publishes the weekly status report and RAG for each project.
Hands back
A list with one entry per project, each with project_id, store_number, rag (green, amber or red), schedule_slip_days, capex_variance_percent, causes (a ranked list, each with cause, evidence and confidence), recovery_action, owner and next_milestone.
Asks a person when
A project turns red, a trading date is forecast to move, or a recovery action needs extra capex.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Amber at slip of (days) | 3 | A trading date forecast this many days late turns the project amber. |
| Red at slip of (days) | 10 | A trading date forecast this many days late turns the project red. |
| Amber at capex overrun (%) | 5 | Forecast capex this much over budget turns the project amber. |
| Red at capex overrun (%) | 10 | Forecast capex this much over budget turns the project red. |
| Report day | Friday | The day the weekly report is published. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Set RAG from the worse of schedule and capex: amber at 3 days or 5 percent over, red at 10 days or 10 percent over.
- For every amber or red project, weigh the competing causes (contractor, fixture delivery, point-of-sale install, landlord works, permits, hiring, stock allocation) and rank them by evidence in the plan and task history.
- Name one recovery action per slipping project, with its owner and the date it pulls back.
- Never turn a project green without the evidence that the slip or overrun is recovered.
- Capex figures go to the sponsor and steering group only; the store-facing version leaves them out.
See the Status Reporting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.