- Industry
- Insure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Project Sponsor
- Code
- MGT-02
It turns the scope of an insurance change project (a new motor product launch, an IFRS 17 reporting change, a policy administration system migration, a claims portal rebuild) into a plan: work breakdown, milestones, dependencies, critical path and the dates they imply, checked against team capacity. It anchors the plan to the fixed dates the business cannot move (regulatory filing deadlines, the 1 January reinsurance treaty renewal, quarter-end reporting freezes) and forecasts whether the plan meets them before publishing the approved baseline.
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 current plan, team calendars and the change freeze windows on the core insurance platforms..
- 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 Project Sponsor with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project management tool: it publishes the approved plan as the project baseline. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The change delivery framework: stage gates, the regulatory and reporting calendar (filing deadlines, IFRS 17 and solvency quarter-end freezes, treaty renewal dates), change freeze windows on the core platforms, and estimating norms.
Reads from
the project management tool: the current plan, team calendars and the change freeze windows on the core insurance platforms.
Acts in
the project management tool: it publishes the approved plan as the project baseline.
Hands back
An object with milestones (a list, each with name, date, fixed (true or false) and owner), tasks (a list, each with name, owner, start, end and depends_on), critical_path (a list of task names), end_date, meets_fixed_dates (true or false) and conflicts (a list of strings).
Asks a person when
The plan misses a fixed regulatory, treaty or reporting date, a go-live falls inside the freeze buffer of 10 days, or a milestone slips by more than 5 days.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Schedule contingency (%) | 20 | Added to the critical path before the end date is set; core platform work overruns often. |
| Longest task before it must be split (days) | 10 | Any task longer than this is split. |
| Buffer before a reporting freeze (days) | 10 | No go-live on the core platforms within this many days before a quarter-end or year-end freeze. |
| Slip that needs a new baseline (days) | 5 | A forecast slip beyond this on a milestone needs the sponsor. |
| Most a person may be planned (%) | 90 | No one is planned above this, leaving room for BAU underwriting and claims work. |
| Milestone template | stage-gate | Which milestone set the plan uses. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Build the plan on the stage-gate template and split any task longer than 10 days.
- Add 20 percent contingency to the critical path before setting the end date.
- Every regulatory filing, treaty renewal or policy wording effective date is a fixed milestone; a plan that misses one needs the Project Sponsor.
- No go-live on the policy administration, claims or rating platforms within 10 days before a reporting freeze.
- Plan no one above 90 percent.
- A milestone forecast to slip by more than 5 days needs a new baseline approved.
See the Project Planning Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.