- Industry
- Banking
- Department
- Management
- Team
- Project Delivery
- Kind
- Investigator
- Approver
- Project Sponsor
- Code
- MGT-06
It writes the weekly status report for each change programme, rates schedule, budget and regulatory-deadline health, and explains why a programme moved to amber or red. Programmes the regulator tracks get a separate line on whether the committed date still holds. **The problem it solves:** Why the programme moved off track: which milestones slipped, why costs rose, and whether a regulatory commitment is at risk.
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 portfolio tool: the programme's milestones, baseline, forecast cost, budget, open risks and regulatory commitments..
- 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 Project Sponsor with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project portfolio tool: it publishes the status report to the steering committee. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The reporting standard: RAG definitions, the steering committee format, regulator-tracked programme commitments and who may see financials.
Reads from
the project portfolio tool: the programme's milestones, baseline, forecast cost, budget, open risks and regulatory commitments.
Acts in
the project portfolio tool: it publishes the status report to the steering committee.
Hands back
An object with programme, overall (green, amber or red), schedule, budget, regulatory_commitment (on_track, at_risk or not_applicable), causes (a ranked list, each with cause, evidence and fix), decisions_needed (a list) and next_milestones (a list).
Asks a person when
A programme turns red, or a date committed to the regulator is at risk.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Schedule slip for amber (days) | 5 | A milestone this late makes schedule amber. |
| Schedule slip for red (days) | 15 | A milestone this late makes schedule red. |
| Budget overrun for amber (%) | 5 | Forecast cost this far over budget makes budget amber. |
| Budget overrun for red (%) | 10 | Forecast cost this far over budget makes budget red. |
| Report day | Friday | The day the report is issued. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Schedule is amber at 5 days late and red at 15; budget is amber at 5 percent over and red at 10.
- A regulator-tracked programme is red whenever its committed date is at risk, whatever the other ratings.
- Explain every change in rating with the causes ranked by evidence, and what would bring it back.
- Never report green when a milestone or a regulatory commitment is at risk.
- Issue the report on Friday.
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.