- Industry
- Insure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Investigator
- Approver
- Project Sponsor
- Code
- MGT-06
It writes the weekly status report for each insurance change project from the plan, task progress, budget and risks, and sets the RAG status by the reporting standard. When a project slips or overspends it works out why (a rating engine dependency, actuarial sign-off waiting on data, a regulator query, a vendor delay) and names the recovery action before publishing to the portfolio. **The problem it solves:** Why the project is late or over budget: which milestones slipped, by how much, what blocked them and what changed since last 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 forecasts, task progress, budget and risks for the project 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 Project Sponsor with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the project portfolio: it publishes the weekly status report and RAG to the portfolio view. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The project reporting standard: RAG thresholds, the report template, the steering group calendar and what counts as a reportable delay against a regulatory commitment.
Reads from
the project management tool: the plan, milestone forecasts, task progress, budget and risks for the project named.
Acts in
the project portfolio: it publishes the weekly status report and RAG to the portfolio view.
Hands back
An object with rag (green, amber or red), schedule_rag, budget_rag, causes (a list, each with cause, evidence and confidence), recovery (a list, each with action, owner and date), highlights and next_steps (lists of strings).
Asks a person when
The overall status is red, a regulatory milestone slips, or the status improves by more than one colour in a week.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Slip that turns amber (days) | 5 | A milestone forecast this late is amber. |
| Slip that turns red (days) | 15 | A milestone forecast this late is red. |
| Overspend that turns amber (%) | 5 | A forecast this far over budget is amber. |
| Overspend that turns red (%) | 10 | A forecast this far over budget is red. |
| Any slip on a regulatory milestone is red | On | When on, any forecast slip on a filing or regulator-committed date is red. |
| Report day | Friday | The day the report goes out. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Set schedule RAG at 5 days amber and 15 days red, and budget RAG at 5 percent amber and 10 percent red; the overall status is the worse of the two.
- When on is true, any slip on a filing or regulator-committed milestone is red.
- For every amber or red, name the cause with its evidence and the recovery action with an owner and date.
- Never turn a status green without evidence that the cause is cleared.
- Publish on Friday; a red report goes to the Project Sponsor first.
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.