Everything That Goes Into Building A Project Plan

Alexandra Cote

Written by

Alexandra Cote

Read Time

11 minutes

I don’t really need a project plan if I’ve already discussed all the details with my client. Right?


A well-built project plan outlines all the details you need for your project’s correct development. It acts like a map, making sure that you don’t miss anything that could derail your project or cancel it altogether.

The project planning stage and particularly the project plan are commonly part of the correct execution, monitoring, and closure of a project. Especially for larger or more complex ones.

Yet, not all teams create project plans for their more complex projects. While not always, the results of no project planning can be chaotic and might negatively impact your project unless you declutter your work progressively.

But that’s only if you jump straight into execution and forget to create a project plan. Or don’t want to do it because you don’t see its purpose or worse, think of project planning as a time-wasting activity.

For all teams who don’t skip project planning, the project will be detailed from the very beginning and most risks or changes that occur will be treated according to this plan.

To help you understand why having one is vital, I’ll show you exactly how you should create a project plan to get your project in order and reap its full benefits.

What Is A Project Plan?

First of all, we shouldn’t confuse the terms “project management plan” and “project plan”. Most people with no project management experience use the term “project plan” to refer to the schedule of the project. Even experienced project managers use “project plan” as a short version of “project management plan”.

Since the term “project plan” is indeed more common, I’m also going to use it alternatively throughout this article.

However, the correct term to refer to the formal document that details the project’s development remains “project management plan”. The PMI® PMBOK Guide only mentions and defines the project management plan.

According to the Lexicon of Project Management Terms, a project management plan is defined as follows: “The document that describes how the project will be executed, monitored and controlled, and closed.”

Briefly, a project plan tells you exactly how the team should approach a project during project execution, control, and closure. It shows what needs to be done, who should work on which task, how the in-office or remote team can communicate, what resources you’ll need, and what your budget and deadlines are.

If you’re a beginner without prior project management experience, think of the project plan as if it’s a map. It shows you exactly where you are, where you need to go, and what alternative paths you’ve got in case something goes wrong or you made a mistake.

Don’t confuse it with the project charter though. The latter doesn’t include all the activities that employees need to complete, nor provide details on how the project should be executed. Project charters are also short (around 3-5 pages) compared to lengthy project management plans which can sometimes exceed 100 pages.

Usually, the project manager creates the project plan only after gathering feedback from the team, clients, and other stakeholders. Written during the project planning stage, the whole process of writing the plan requires close attention and sometimes several days of work. This ensures that all aspects have been covered before going into project execution.

Most project management plans are written using a text editor and can then be printed, used, and later placed in an archive. But if you’d rather keep your data in the cloud, you can always go for project planning software. These will prevent loss of data and help you share updates and files automatically with your team.

The Project Plan’s Purpose

Having a plan before you start working on the actual tasks helps you organize your team’s activity, save time you’d otherwise spend on fixing misunderstandings, and reduce the costs you’d waste on useless resources.


Never rush the project plan’s creation. To make sure you haven’t missed anything, go into every single detail and review the plan as many times as necessary.

In fact, the purpose of this plan is to ensure that you have everything in order from the start. An accurate plan can prepare you to face any changes and risks that could arise, keep you within budget, identify bottlenecks, and prevent project delays.

As the main document of a project, there are several different benefits and usage situations for a project management plan:

Defines the project’s value proposition

The project plan tells stakeholders why you’re carrying out a project, what its purpose is, what problem it solves, and why they should sponsor it. This also helps the author of the plan when choosing a certain development path for the project. Having clear goals in mind eases the process of picking the right techniques, resources, tasks, and team members.

Develops upon what goes into the project

The project management plan should go into great detail on all tasks that the team needs to carry out and what resources they to execute them or any other task that might be needed whenever a change or risk event occurs. Project planning also shows stakeholders what the final deliverables (product or service) and their quality standards are.

Shows who’s responsible for each activity

Project planning helps you tell your team members who’s in charge of which task, what their responsibilities are, what resources they can use for a specific task, their time limits, and how they should conduct each task.


During project planning, your team can say approximately which tasks, resources, and how much time they’ll need to complete a specific part of the project. This is why their input is mandatory when building the project plan.

Sets your deadlines

It can show you exactly how much time a team member has to complete a task, what the project’s milestones are, and when you should deliver the final product or service.

Guides your budget

Having clear budget estimations from the project planning stage can help you avoid unanticipated costs that might postpone your project or cancel it altogether.


In case you do find yourself in this situation, you can ask your client for more money. Just make sure you’ve clearly stated the possibility of your initial budget not being enough in the original project plan.

The Elements Of A Project Plan

Any project management plan must and will (if created correctly) contain all the essential elements and secondary plans that go into the project management process. To see exactly what each step should include during project planning, check out our template below.


The elements below are the basic ones all project plans should include. In addition to these, you can choose to focus on other aspects too – depending on your company, team, client, and project.


This first part should include a brief description of the project, its purpose, and any objectives, needs, and goals that you’ll use to measure the project’s success. You can also include a list of deliverables as part of the introduction to clearly state what the targets of the project are.

Executive Summary

Use the project charter you’ve created before to find and summarize the information you can include in the project plan as well.


You can also include the list of stakeholders in the project plan. However, the 5th edition of the PMI® PMBOK Guide and Standards has introduced the Stakeholder Management Plan which can be added as a separate section to the project’s plan.

Integration Management Plan

The Integration Management Plan includes the detailed processes that go into managing a project until its completion: team roles and responsibilities, company organization and hierarchies, and other internal or external influencers.

Focus on managing and controlling changes, executing tasks, monitoring team activity, and closing the project.


While some include the Change Management Plan here, this can also be a separate section of the project management plan.

Scope Management Plan

For this section, use the scope you’ve mentioned in the project charter and detail it. Include the limits of the project, what your team can and can’t work on, and what should be avoided by all means.

A clearly stated scope will help your team understand the boundaries of the project and prevent any misunderstanding or mistakes.


You can also include here the Requirements Management Plan and your project’s Work Breakdown Structure (WBS) to write down all activities and their relationships.

Schedule Management Plan

The schedule is one of the most important elements you should set during project planning. List all time-related details in accordance to the project’s deliverables, due dates, milestones, and other determinant factors. Include all methods of schedule development, who’s in charge, what resources will be used, and how time reporting should be done.


You don’t have to plan your project’s schedule on paper. Use project management software or task management tools instead to schedule the duration of each task and make them available for the entire team. Or even better, tools for Gantt chart creation (pretty popular in the construction industry) to align planning with time management.

gantt chart for project plan - planning

Gantt Chart example in Paymo

Cost Management Plan

This section contains all the information on how a project’s budget will be managed and controlled including the methods used for cost management, who’s in charge of this, and how budget reporting can be done.

NOTE: if you need an automatic invoicing tool to create reports, estimates, and invoices and ensure timely payment, be sure to check out the best 6 simple invoicing software. Such an invoicing solution is good for small businesses and freelancers alike.

Quality Management Plan

This part of the plan focuses on ensuring the quality of the final product/service in a way that meets the client’s requirements.

State what the project’s quality standards and procedures are, the team members in charge of QA (Quality Assurance) and QC (Quality Control), what tools and techniques can be used, and how the quality of the project deliverables should be measured.


Include the standards and quality procedures for all deliverables right from the project planning phase to ensure the final result is accepted.

Human Resources Management Plan

Use this section of the plan to offer information on how the project team should be appointed, managed, and trained during the whole project development process. This includes needed resources, techniques to handle performance and productivity issues, and other tools or methods that can be used.


Include everything else that involves your team from team buildings to mentoring and other career development opportunities.

Communication Management Plan

Describe how you should manage team and stakeholder communication including methods and tools, team members responsible for handling communication, and any other relevant elements.

When creating your plan, focus on the information that can be shared, who can do this, which methods can be used, and when a piece of information should and shouldn’t be communicated with others.


Not having a plan for handling communications can cause confusion during the project’s phases and lead to misunderstandings that will require extra issue management.

Risk Management Plan

Describe how risks are going to be identified, analyzed, managed, monitored, controlled, and reported. During project planning, state who’ll be responsible for these steps, what the exact responsibilities are, and what tools or techniques can be used.


You can also plan for ongoing risk identification as the project progresses to ensure that no unrecognized risk can derail the project.

You’ve probably created these plans before starting to build your complete project plan. According to the PMBOK Guide, most of these secondary plans are usually made during the several different processes that precede the development of the project plan.

At the end of the plan add:

  • an Approvals section where stakeholder signatures are gathered
  • a Glossary to explain the terms you’ve used
  • an Attachments section to add any other notes or relevant documents that can guide the project development process
  • a Revision History section as well either at the beginning or end of the plan to keep track of any changes

Project Plan Template

Here’s a template for a project management plan you can use as a baseline. You can download it as a PDF file.

Instructions On Using This Template

Use the template as a reference to know where to add project-related information and what kinds of details you should include. You’ll find the explanations for each section written in an italicized font. Remove these indications when you’re creating your plan.

If you’ve chosen the Google Docs version, create a copy to gain editing rights on your own document. Also, make sure to refresh the Table of Contents after completing it with your own project’s particularities.

The way in which you structure your project’s plan depends on your own company’s organization, but the elements outlined in this template are the most often mentioned ones. Going over these in great detail can prevent you from bumping into a problem for which you won’t be able to find a solution.


While this template is only a few pages long, the complete project plan can have as many as 100 pages or more.

Steps To Building Your First Project Plan

I know the whole process of building such a detailed and complete document might look tedious, but follow the following systematic steps and you’ll get your first project management plan:

Ensure full comprehension of everything that goes into the project

Before you create any project document, make sure everyone has understood your client’s requirements, the project’s objectives, its limitations, what the deliverables should be, and what their quality standards are.

You’ll need to know exactly what the client’s expectations are before you write anything down. Hold a new project planning meeting with your clients to avoid any misunderstandings. Ask relevant questions, see what their preferences are, and try not to leave anything out.

Outline your project plan

After the client meeting, put together all your answers and project-related facts and create a rough plan. Consider all project phases and tasks team members have to complete in order for work to continue.

This step is your chance to think of how you’ll approach the project. Write every project detail that goes through your mind be it cost, time, resources, team, general assumptions, or others. You’ll then better organize this information and turn it into a full plan.


Outlining a rough project management plan can help you better organize your final one and keep all information consistent without any contradictory statements.

Write the complete project plan

Gather the plans you’ve already written and compile them to create your complete project management plan. This is often the lengthiest part of project planning as you’ll need to write and include at least everything we’ve mentioned in the elements section above.

Besides these, you can add any issue that concerns your specific project from Governance Reviews to Procurement Management, Information Management, Configuration Management, Acquisition Strategy, and so much more.

Review the project plan

Don’t send the plan for approval if you haven’t reviewed it. Check the project plan as often as needed until you and your team have no more misunderstandings or unclarities. This is why you should also involve your team in reviewing the project plan. Each person can be responsible for checking what goes in and out of the tasks they’ll be accountable for.


Although you’ll most likely make changes during project execution, make sure you don’t make any serious mistakes while planning the project.

Get approval

A project plan can’t be used unless it has been formally approved. Depending on your company’s size and structure, it will be the project manager, project sponsor, or manager who can give you the final go.

These people know exactly what they need to complete a project and what the limitations are, so they’re the perfect fit to judge a plan’s sustainability. Make a list with all the names of the people who approved the plan and the dates when they did this.


Keep all approval documents (written or received via email) obtained during project planning to prevent further disagreements.

Key Takeaways

  • Don’t start a project without having a project plan in place.
  • Don’t expect to finish project planning in one day. You’ll need to go through all secondary plans and then add them up to ensure there are no inconsistencies.
  • You might need to update the project plan as the project progresses. Whenever a change occurs to a secondary plan, you’ll need to modify that specific part of the project management plan and keep the changes consistent.
  • Always involve your team and client in project planning to prevent further misunderstandings.
  • There is no single template for the perfect project plan. You can thus tailor it to your own needs and focus on the aspects that matter the most for your project. But never leave out the essential aspects like team members, cost, time, resources, risks, and so on.
Building a project management plan is just one of the many responsibilities a project manager can have. Check out our full guide to them.

Found this article useful? Please spread the knowledge and share it with your teammates and followers.

Subscribe via email

Get monthly tips on how to successfully run projects and remain sane at the same time.

Thank you for subscribing!

Hmm, something went wrong... Please try again.