Project Initiation Document Template Free Download

What is project initiation phase?

Where to start a project? From the beginning, with the Project Initiation Phase. Regardless of the project management method being followed, projects tend to be broken down into phases since it is easier to manage small, defined chunks of work, one at a time, than trying to manage the full project as a single piece.


Project Initiation Templates
Project Initiation Phase

To meet the objectives above, there are several considerations that the project manager will need to address during project initiation, which can seem a daunting task for some. Fortunately for you, this article will guide you, highlighting which actions to do and which templates to use through the process:

Most projects follow a typical lifecycle which involves a phase of definition and alignment (initiation), followed by a phase where the project manager plans the work (planning), works the plan (execution), tracks and controls that work (monitoring and control), until the project is ready to be terminated (closure).

The first of the project life cycle phases is usually called Project Initiation or Project Start-up. Because the initiation phase can mean different things to different organizations, a simple way to think of it is that it will cover everything that occurs before a project is approved, and before detailed planning begins.

Purpose of Project Initiation Phase

The purpose of Initiation is to get the project off to the best start, by ensuring that the project meets at least the minimum standards to be considered and implemented by the organization. This involves understanding what the project is about, what is there to be gained by carrying out the project, if the project is feasible or not and, as important, aligning expectations around the project.

The key objectives of this phase are:
  • To set up a project management environment that enables the project to be successful
  • To evaluate the benefits and feasibility of the project
  • To provide a solid justification for the project
  • To define the project’s objectives
  • To define the boundaries of the project
  • To define the management approach for the project
  • To identify the project team and other resources required
  • To align expectations and gain support from the project’ stakeholders


What is a Project Initiation Documentation ?

A Project Initiation Documentation (PID) is for PRINCE2 (Projects in Controlled Environments, the method for managing projects developed and used extensively by the UK government), what a Project Charter is for the PMBOK Guide: the backbone of a project, summarizing what the project is and is not about and providing a way for the project to be authorized in the organization.


Project Initiation Document Template
Project Initiation Document Template 
Now, let’s clarify something very important: while some people refer to a PID as a document, in reality PID stands for Project Initiation Documentation, referring to a set of project documents which, when combined, form the initiation – and foundation! – of the project.

Project Initiation Documentation Composition

  • Objectives of the project
  • Business case
  • Expected benefits
  • Project scope
  • Project timeline
  • Project Budget
  • Options Analysis
  • Project approach
  • Project Organization
  • Quality Management Strategy
  • Configuration Management Strategy
  • Risk Management Strategy
  • Project Controls
  • Project Success Criteria

Why do you need a Project Initiation Document?

The PID is one of the most important artefacts in the project because:
  • It ensures that everyone in the project shares the same understanding of the project
  • It reassures your key stakeholders that you know what you are doing
  • It provides a reference point and guidance for your team
  • It serves as a baseline for scope, schedule, and budget
  • It clarifies what approach is going to be followed
  • It defines what good looks like for the project to be deemed successful

How to write an effective PID?

An effective PID is the one which clearly answers the Why, What, When, Who, How much, and What-if of the project. Here are some tips on how to write the best PID ever:
  1. Consult your key stakeholders: Don’t leave them out of the loop, your project team, and other departments in the organization (e.g. Finance, Procurement) may provide important inputs.
  2. Be specific: A PID can be quite comprehensive thus it is likely that your project board will lose interest after the second page; try to go straight to the point and use concise, specific language.
  3. Don’t reinvent the wheel: If there is an establish approach in the organization for how risks or quality is managed in projects, there is no need to re-write it in your PID, simply reference it explaining what is different or has been tailored in your project.
  4. Put yourself in their shoes: What information does your Project Board need to make a decision on the project? Be as realistic and accurate as possible.
  5. Get the PID signed-off: This may sound like a no-brainer but the main reason for having a PID is actually to get the project recognized and authorized thus remember to ask for sign-off as soon as possible since approvals always takes time.

No comments