Processes
Processes as practical steps.
Plain-English process pages focused on what the project manager should check, decide, produce, and escalate.
Project initiation
Starting Up a Project
Turn a vague mandate into a decision-ready project start with clear outcome, sponsor accountability, and a practical go or no-go recommendation.
Use this when
- • A sponsor proposes work but the problem, scope edge, or decision rights are still unclear.
- • A project request arrives as a preferred solution instead of a defined outcome.
Open full process guidance
Project governance
Directing a Project
Run governance as a decision system so sponsors and boards can direct value, tolerance, and risk in time.
Use this when
- • Setting up governance cadence at initiation.
- • Preparing sponsor or board-level highlight reports.
Open full process guidance
Project planning
Initiating a Project
Build a practical project baseline that can be controlled, reported, and adapted without excessive bureaucracy.
Use this when
- • After startup approval to proceed into formal project control.
- • Before significant delivery spend or supplier mobilisation.
Open full process guidance
Project reporting
Controlling a Stage
Operate the stage week by week through work authorisation, progress control, RAID management, and timely exception escalation.
Use this when
- • Any live stage where delivery work is in progress.
- • Weekly control and sponsor reporting cycles.
Open full process guidance
Project delivery
Managing Product Delivery
Coordinate teams and suppliers through clear work packages, quality expectations, and acceptance evidence.
Use this when
- • Authorising work to internal teams or external suppliers.
- • Managing handoffs between delivery and project control.
Open full process guidance
Project boundary
Managing a Stage Boundary
Prepare the evidence and options needed for a confident continue, adjust, reset, or stop decision at stage end.
Use this when
- • Approaching end of stage.
- • Before major funding or continuation decisions.
Open full process guidance
Project closure
Closing a Project
Close with control: confirm acceptance, transfer ownership, document lessons, and protect post-project benefits follow-through.
Use this when
- • When planned delivery is complete.
- • When project direction changes to stop or hand over early.
Open full process guidance