PRINCE2 7 Foundation · Study lesson 29
Is initiation worth considering?
Spend just enough effort to judge whether detailed preparation is justified.
10 minute study lesson · Processes · Original learning material
What you will understand
- Explain the decision supported by Starting up a project.
- Distinguish a mandate, project brief and initiation stage plan.
- Recognise how early appointments and previous lessons shape the proposal.
The idea
An enthusiastic suggestion should not immediately become a fully funded delivery commitment. Starting up a project provides a short, proportionate check that a sensible proposal exists and that initiation can be organised. It is pre-project work. The aim is to avoid spending heavily on detailed preparation for an idea that lacks ownership, a credible purpose or a workable approach.
A project mandate is the trigger from the commissioning organisation. It may arrive as a formal instruction, a business request or another suitable expression of need. Its detail can vary considerably. Treat it as the reason to examine a possible project, not as proof that every delivery activity has already been authorised. Clarify what outcome is sought, the constraints and who can speak for the business.
Appoint an executive and a project manager so that business accountability and preparation of the proposal have clear owners. Design and appoint the project management team in a way that represents business, user and supplier interests. Starting up is not a substitute for knowing who can make the initiation decision. A small project can combine compatible responsibilities, but important accountability must remain explicit.
Seek useful experience before choosing the approach. A previous project might reveal difficult approvals, scarce skills or an adoption problem that a technical plan would miss. Capture relevant lessons and decide how to apply them. Select an approach to delivering the project that fits its context: for example, buying a configurable service instead of developing software. The approach affects costs, risks, people and the next planning effort.
Prepare an outline business case and assemble the project brief. The outline case gives enough reasoning to consider whether further investment is sensible; it is developed in more detail during initiation. The brief brings the proposal together, including the project definition, chosen approach and management team arrangements. Early clarity about the intended project product and its acceptance helps prevent initiation from planning an ambiguous destination.
Plan the initiation stage itself: what preparation is needed, who will do it, how long it should take and what it should cost. The project manager submits this initiation stage plan with the brief for the board’s decision through Directing a project. Approval permits initiation, not unlimited delivery. A refusal can be a successful outcome of good governance when it prevents a weak proposal consuming further resources.
Starting up prepares a decision
| Input or output | Purpose |
|---|---|
| Project mandate | Provides the initial reason and authority to investigate. |
| Project brief | Builds a concise basis for considering the proposed project. |
| Outline business case | Tests the early investment reasoning. |
| Initiation stage plan | Explains the work and resources needed to establish the foundations. |
| Board authorisation | Allows initiation to proceed; it is not automatic full-project approval. |
An original fictional example
Fictional case: a community repair booking service
A charity’s trustees ask whether volunteers could use an online system to book repair appointments. One trustee initially suggests commissioning a custom application before anyone has checked demand or safeguarding requirements.
The decision
The appointed executive and project manager clarify the need, consult volunteers, examine an existing service option and create a brief with an outline business case. They request a two-week initiation stage to investigate feasibility and prepare the management foundations.
Why it makes sense
The mandate triggered evaluation. The brief explains the proposed project; the initiation stage plan controls the next limited investment. Neither is a purchase order for the complete service.
A common confusion
The mistaken idea: Starting up a project produces the fully developed management baseline for delivery.
The distinction: Starting up prepares a credible proposal and a plan for initiation; initiation develops the detailed foundations.
First decide whether preparation is worthwhile; then establish how the project will be managed.
Points to remember
- Starting up is pre-project and is triggered by a project mandate.
- The project brief includes the outline business reasoning and proposed approach.
- The board authorises initiation; the project manager prepares its supporting information.
Your takeaway
Starting up turns a request into a reasoned proposal. Use early ownership, relevant lessons and an initiation stage plan to support a controlled decision about further preparation.
This independently written explanation is supplementary study material. It is not official examination content. Read about our content and its limitations.