PRINCE2 7 Foundation · Study lesson 31
Agree the management foundations
Create a shared baseline for deciding, delivering and assessing the project.
11 minute study lesson · Processes · Original learning material
What you will understand
- Explain how initiation develops the proposal into a management baseline.
- Recognise the purpose and contents of project initiation documentation.
- Distinguish preparing management arrangements from authorising delivery.
The idea
Once initiation is authorised, the team needs more than enthusiasm and an outline idea. Initiating a project develops a shared understanding of what will be delivered, why it is worthwhile and how it will be governed. This work takes place during the initiation stage. It gives the board a reasoned basis for deciding whether to commit to the project.
Refine the business case using the better information available. Relate expected benefits and dis-benefits to costs, timescales, risks and the chosen approach. Clarify who will own benefits and how they will be assessed, including reviews after delivery where appropriate. The business case remains a live decision tool. Completing it during initiation does not guarantee that the investment will remain justified at every later boundary.
Develop the project plan at a useful overall level, with products, dependencies, resources and significant decision points. Avoid pretending that every distant activity is known precisely. The current management stage needs sufficient detail for control, while later work can be progressively refined. Product descriptions and acceptance arrangements help connect planning with quality, so a schedule represents useful delivery rather than just a sequence of busy people.
Agree how key management topics will be handled and tailored to the context. Arrangements include managing risks, issues, quality, communication, change adoption, commercial relationships, sustainability, and digital information and data where relevant. An approach explains responsibilities, procedures and information needs. It is different from a register that records individual risks or issues. Proportionate arrangements can be concise and linked to existing organisational systems.
Establish project controls: reporting intervals, management stages, tolerances, escalation routes and decision responsibilities. Make information ownership and access clear. Set up the records needed to manage work and capture lessons. Record the reasons for tailoring so that the team understands why the arrangements fit its size, uncertainty and delivery method. Tailoring should strengthen usable control rather than quietly remove an uncomfortable responsibility.
Assemble the project initiation documentation, often called the PID. Think of it as the coherent set of information defining the project and its management basis, not necessarily one large document. It draws together the project definition, case, plan, roles, management approaches and controls. The project manager prepares it for the board’s authorisation decision. The initiation stage boundary also prepares the next stage information needed to proceed under clear authority.
Initiation makes control possible
| Foundation | What becomes clearer |
|---|---|
| Business case and project plan | The investment and how products will be delivered. |
| Roles and responsibilities | Who makes decisions and who undertakes work. |
| Management approaches | How people, quality, risk, issues and other concerns will be managed. |
| Project controls | How progress, tolerances and escalation will operate. |
| Project initiation documentation | Brings together the agreed management foundations. |
An original fictional example
Fictional case: a mobile library route
A council has authorised initiation for a mobile library service. Residents want reliable visits, the transport supplier needs maintenance windows, and the sponsor wants evidence that isolated households will use the service.
The decision
The manager develops the case, project plan and acceptance measures, agrees management approaches and reporting, and assembles the PID with clear links to the underlying records. The board then assesses the request to authorise the project.
Why it makes sense
Initiation makes delivery and governance understandable before substantial commitment. A collection of files is useful only when its responsibilities, targets and decision routes form a coherent baseline.
A common confusion
The mistaken idea: The PID is a static form whose completion itself authorises the project.
The distinction: The PID establishes the management basis; the board must separately decide whether to authorise the project.
Preparing the case and control arrangements is different from granting authority.
Points to remember
- Initiation develops the business case, project plan, management approaches and controls.
- PID means a coherent set of project initiation documentation, not a prescribed binder.
- The board’s project authorisation follows assessment of the initiation evidence.
Your takeaway
Initiation makes the proposal governable. Build a coherent baseline of value, products, responsibilities and controls, then seek the board’s decision about committing to delivery.
This independently written explanation is supplementary study material. It is not official examination content. Read about our content and its limitations.