Project Management Plan Template

What is a Project Management Plan?

A project management plan, usually shortened to PMP, is the primary document used to plan and control a project. It sets out how the project will be executed, delivered, monitored and controlled across its lifecycle. The project manager produces it during the planning stage and keeps it current through delivery.

A PMP is a governing document rather than a schedule. Cost, time and risk each get a section. The plan's real work is recording the decisions made before delivery starts: who holds authority, what the tolerances are, and how changes get approved.

Some organizations call it a project delivery plan or a PM plan. Where several related projects run together, the equivalent document is a program management plan.

Project Management Plan Format: What's Included in This Template

Eighteen sections and nine appendices, in Word, written for construction and capital works delivery.

The nine appendices hold the supporting plans:

• Stakeholder register
• Stakeholder and communications plan
• Change management plan
• Schedule management plan
• Cost management plan
• Quality management plan
• Risk management plan
• Project risk register
• Procurement plan

Several sections arrive part-written rather than empty. The purpose statement, the reporting cadence and the cost management process are already drafted. You edit established wording instead of facing a blank page.

How to Write a Project Management Plan Using This Template

Work through the sections in order. Each one depends on decisions made in the one before it, and governance comes early because it sets how much rigor everything after it needs.

Complete Document Control before circulating a draft. A plan with no version number and no named approver carries no authority.

1. Fill in Document Control and the project details table with the project number, client organization and the full project management team
2. Write the project summary covering charter, background, scope and objectives, stating plainly what is in and out of scope
3. Set the project classification, then map the team structure and the project governance reporting lines
4. Complete the benefits table with a baseline measure, a target measure and a target date for each benefit, verified by the project sponsor
5. Set the meeting and reporting cadence, including who prepares the monthly project report and how many days ahead of the meeting it circulates
6. Record the budget allocation, the cash flow forecast and the contingency figure in the cost management plan
7. State the tolerances requiring sponsor approval before work proceeds, covering extensions of time and variations
8. Write the four delivery strategies for design, construction, commissioning and handover, and closure, then attach each supporting plan as an appendix

Refresh the table of contents before you issue it. Page numbers do not update on their own once sections change length.

Project Management Plan Example

Here is the same template completed for a council aquatic centre redevelopment.

Three things make this example work. The charter is one sentence carrying a contract value and a completion date. The scope section states what is out as well as what is in, which is what prevents an argument later about the cafe fit-out.

The background justifies the decision with evidence: two failed condition audits, a feasibility study, and the date Council endorsed replacement.

Note the footer. Rev 3 and the date sit on every page, so nobody has to open the document to know which version they are holding.

Common Mistakes in a Project Management Plan

Most weak plans fail the same few ways and the two biggest are benefits written without measures and tolerances left unstated.

Watch for these when you review a draft:

• Benefits with no numbers. "Improved reporting" with no baseline, no target and no date is an intention, not a benefit
• Unstated tolerances. Without them, every change escalates to the sponsor or none of them do
• Duplicated appendices. Repeating supporting plans in the body doubles the page count and guarantees the two versions disagree within a month
• Silent exclusions. Scope that lists what is in and says nothing about what is out
• No named approver. A version number without a signature makes the plan a draft, whatever the cover says

The larger failure is a plan written once and never reopened. A document that has not moved since the planning stage records what people expected rather than describing how the project is being run.