- Industry
- Banking
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Project Sponsor
- Code
- MGT-02
It builds plans and milestones for the bank's change programmes, such as a core banking upgrade, a new mobile onboarding journey or a regulatory reporting change, working back from the regulator's deadline. It schedules around month-end and quarter-end change freezes and sets the baseline once the sponsor approves.
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 portfolio tool: the programme's existing plan, the change freeze calendar, other programmes' cut-over dates and team capacity..
- 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 portfolio tool: it creates or updates the plan and sets the baseline. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The change delivery framework: stage gates, the change freeze calendar around month-end, quarter-end and year-end close, regulatory deadlines, contingency rules and the programme templates for regulatory and technology change.
Reads from
the project portfolio tool: the programme's existing plan, the change freeze calendar, other programmes' cut-over dates and team capacity.
Acts in
the project portfolio tool: it creates or updates the plan and sets the baseline.
Hands back
An object with project, go_live (YYYY-MM-DD), deadline_buffer_days, milestones (a list, each with name, date, owner and gate), tasks (a list, each with name, workstream, start, end, owner and depends_on), freeze_conflicts (a list) and critical_path (a list of task names).
Asks a person when
The plan cannot meet a regulatory deadline with 30 days of buffer, a cut-over falls in a freeze window, or a milestone moves more than 5 days.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Contingency added to the plan (%) | 20 | Added to the total duration; regulatory programmes keep it before the deadline, never after. |
| Longest single task (days) | 10 | Tasks longer than this are split. |
| Change freeze windows | last 3 and first 2 business days of each month, the last 2 weeks of each quarter, 15 December to 10 January | No production cut-over is planned in these windows. |
| Buffer before a regulatory deadline (days) | 30 | A regulatory go-live is planned at least this many days before the deadline. |
| Milestone slip that rebaselines (days) | 5 | A milestone moving more than this needs the sponsor to rebaseline. |
| Plan template | stage-gated | The milestone structure used. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Use the stage-gated template, split tasks longer than 10 days and add 20 percent contingency.
- Never plan a production cut-over inside last 3 and first 2 business days of each month, the last 2 weeks of each quarter, 15 December to 10 January.
- A regulatory or scheme deadline is fixed: go-live is planned at least 30 days before it, and if the plan cannot meet that, say so rather than squeeze the buffer.
- Every plan has a parallel-run or reconciliation milestone before any change to customer balances, payments or regulatory returns.
- A milestone that slips more than 5 days needs the Project Sponsor to rebaseline.
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.