DocumentProject management plan
Doc IDPC-PMP-003
Version1.0
StatusApproved
OwnerProject manager
ClassificationPublic
1.0 APPROACH

AI is a powerful tool. It is not a project manager.

Handing every decision to AI is a plan to fail. Projects succeed on judgement, context and accountability, so AI does the heavy work and people keep those.

2.0 ROLES & RESPONSIBILITIES

Who does what

Every engagement runs on a defined responsibility matrix. AI agents do the work they do well; a qualified person is always accountable.

2.1 RACI matrix
ActivityAI agentsProject managerClient / sponsor
Draft plans, registers and project documentsRAI
Build schedules, site trackers and calculationsRAI
Capture daily and hourly updates from the channels connected to the projectRAC
Generate stakeholder reports on demandRAI
Track status, changes and open itemsRAI
Technical and safety judgement—AC
Decide scope, approach and prioritiesCAC
Approve stakeholder reports—AI
Approve the charter, baselines, gates and network changes—RA
RResponsible: does the workAAccountable: approvesCConsultedIInformed
3.0 GOVERNANCE

Built-in human gates

The work cannot move forward until a person acts at each of these points.

3.1 Human gates
GateWhat happensWho acts
ConfirmA person checks every draft, assumption and proposal before it is used.Project manager
ProvideNames, budgets, dates and site facts come from people. AI never makes them up.Project team and stakeholders
GuidanceDirection and trade-offs are decided by people. AI only recommends.Project manager
Sign-offThe charter, baselines, phase gates and network changes need approval from the authority, recorded by a person.Sponsor or client

Stage gates

InitiateCharter drafted
Gate 1Charter approved by the sponsor
PlanScope, schedule, cost
Gate 2Baselines approved
Execute & monitorChanges through change control
Gate 3Deliverables accepted
CloseHandover and lessons learned
4.0 TAILORING

As simple or as detailed as you need

Not every project needs every document. We tailor the process and paperwork to your project's size, risk and priorities, and adjust them as it changes.

4.1 Tailoring levels
LevelSuitsTypical documents
LightSmall, low-risk jobsA one-page project brief, a simple schedule, a risk list and short progress updates
StandardMost rolloutsAdds a stakeholder register, a change log, a communications plan and regular status reports
FullLarge, high-risk or regulated programsComplete PMBOK®-aligned planning, baselines, phase gates and formal change control

These are starting points, not boxes. You choose what to keep, add or drop.

5.0 REPORTING

Reports that fit the reader

Each stakeholder gets what they need, when they need it.

5.1 · RegularPer audience

Tailored to each stakeholder

Sponsors receive a one-page view of progress, cost, risks and the decisions needed from them. Engineers and contractors receive the site-level detail. Everyone gets the report they will actually read.

5.2 · Any timeOn demand

On demand, from live project feeds

AI compiles daily and hourly feeds from the channels connected to your project, such as chats, email, site updates and meeting notes, so a current report can be produced whenever it is needed, not just at month end.

The project manager reviews and approves every report before release.

6.0 DELIVERY APPROACH

Fits the way your project runs

Predictive, adaptive or hybrid: the project manager chooses per workstream. AI can recommend one, but never picks it.

6.1 Delivery approaches
ApproachHow it runsTypical use
PredictivePlan-driven: baselines, phase gates and formal change controlInfrastructure rollouts and builds
AdaptiveAgile methods such as Scrum: a prioritised backlog and short sprintsSoftware, integration and configuration work
HybridBoth, side by side, chosen per workstreamFor example, the network build runs plan-driven while configuration is delivered in iterations

Scrum, with the same discipline

For software, integration and configuration work we run Agile, usually Scrum: a prioritised backlog, short sprints, daily stand-ups, sprint reviews and retrospectives. Our tools keep the backlog, sprint plans and records up to date; the product owner and the team make the calls.

PRODUCT BACKLOG SPRINT BACKLOG DAILY STAND-UP INCREMENT SPRINT REVIEW RETROSPECTIVE SPRINT 1–4 WEEKS a person sets the order accepted by a person
7.0 NEXT STEP

Planning a project?

Tell us about your rollout, build, upgrade or migration. We can walk you through how we run a project, with AI doing the heavy lifting and people making the decisions, and give you an honest assessment of whether we are the right fit.

[email protected]
Document history
VersionDateChangeApproved by
1.0Oct 2026IssuedProject manager