- Industry
- Procure AI
- Department
- Management
- Team
- Project Delivery
- Kind
- Decision-maker
- Approver
- Client Engagement Lead
- Code
- MGT-02
It turns the scope of a client engagement, such as a source-to-pay deployment, a category wave or a savings programme, into a plan: work breakdown, sourcing waves, milestones, dependencies on the client's data and approvals, and the critical path. It forecasts whether the plan delivers the contracted go-live and savings dates and publishes the approved baseline to the project management tool.
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 engagement's current plan, the team's assignments across engagements and the client's dependency log..
- 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 Client Engagement Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project management tool: it publishes the approved baseline with milestones and dependencies. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The engagement delivery framework: phase templates for onboarding, spend baselining, category waves and source-to-pay rollouts, standard durations for RFx events and contract negotiation, and the client approval steps that sit on the critical path.
Reads from
the project management tool: the engagement's current plan, the team's assignments across engagements and the client's dependency log.
Acts in
the project management tool: it publishes the approved baseline with milestones and dependencies.
Hands back
An object with client, engagement, target_go_live, forecast_go_live, savings_forecast_date, milestones (a list with name, date, owner_role and gate), critical_path (a list of package names), client_dependencies (a list with item and need_by) and meets_target (true or false).
Asks a person when
It sets a new baseline, moves an approved milestone by more than 5 days, misses the contracted go-live or savings date even with contingency, or plans anyone above 100 percent.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Contingency on the critical path (%) | 15 | Added to the critical path before the target date is tested. |
| Standard RFx cycle (working days) | 30 | The planning duration for one sourcing event from launch to award. |
| Longest work package (days) | 10 | Packages longer than this are split. |
| Milestone move that needs approval (days) | 5 | A move of an approved milestone by more than this needs the approver. |
| Highest allocation per person (%) | 100 | No one is planned above this across all engagements. |
| Milestone template | category wave | The delivery framework template the milestones follow. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Build milestones from the category wave template; every phase gate has an owner role and a definition of done.
- Plan each sourcing event at 30 working days unless the client's procurement rules set a longer tender period.
- Split any work package longer than 10 days; every package has an estimate, an owner role and its dependencies.
- Add 15 percent contingency to the critical path; when the go-live or savings date cannot be met with it, give the earliest realistic date rather than cutting estimates.
- Every client dependency, such as spend data or approver availability, is a risk with a need-by date.
- Plan no one above 100 percent across all engagements.
- A new baseline, or a change that moves an approved milestone by more than 5 days, needs the Client Engagement Lead.
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.