Project Plan Template Pack (PMI Standard Word, Excel & PDF)

8 min read · Reviewed August 2026 by Dan Sunil Kumar

When to use it

• A charter has been signed and you now need the plan that turns it into dates and money.
• Your schedule lives in a tool nobody outside the team can open, so governance has no baseline.
• Dates keep slipping and nobody can say which tasks have float and which do not.
• A stage gate or PMO asks for a baselined plan before spend is released.
• You inherited a project with a task list but no scope boundary, cost plan or change process.

Every section, and what good looks like

1. Section 1

   Plan control (document)

   Project name, sponsor, project manager, version, baseline date and next review date.

   A version number that increments only on approved change, so everyone knows which copy is live.

2. Section 2

   Scope baseline (document)

   Objectives, in-scope and out-of-scope lists, acceptance criteria, and the WBS-to-work-package table.

   Every work package has an owner and an obvious acceptance route — someone can say yes or no to it.

3. Section 3

   Schedule summary (document)

   Six to eight governance dates, each labelled as a target or a commitment, plus the critical path note.

   Task-level detail stays in the worksheet; the document carries only the dates governance tracks.

4. Section 4

   Task rows (worksheet)

   ID, task, owner, duration in working days, predecessor IDs, start, calculated finish, total float and status.

   No task longer than about ten working days, so slippage shows up inside a single reporting cycle.

5. Section 5

   Float and critical flag (worksheet)

   Total float per task, with a formula that flags any zero-float row as critical.

   Float is re-derived after every change, not carried over from the first baseline.

6. Section 6

   Milestones tab (worksheet)

   Baseline date, forecast date and a calculated variance in days for each milestone.

   The baseline column is frozen; only the forecast column moves week to week.

7. Section 7

   Cost and resource plan (document)

   Budget, committed spend and tolerance per category, plus named resource assumptions with dates.

   Contingency is a line of its own rather than padding hidden inside estimates.

8. Section 8

   Accountability (document)

   Decision rights for sponsor, project manager, technical lead and business owner.

   Detailed task-level responsibility is delegated to the RACI matrix instead of duplicated here.

9. Section 9

   Change control and approval (document)

   What triggers a change request, the approval thresholds, and the signature block.

   Approved changes are re-baselined in the worksheet and the document version is incremented the same day.

A filled-in example

The first eight rows of the schedule worksheet, filled in for a planning phase, so you can see how duration, predecessors and float sit together before you baseline.

Mistakes that make a project plan stale by week three

• Starting with dates instead of scope, so the plan documents a wish rather than a commitment.
• One giant task called "build", which hides slippage until it is too late to recover.
• Never entering float, so every task looks equally urgent and the real critical path stays invisible.
• Overwriting the baseline column when dates move, which destroys the variance you need to report.
• No named owner per row — a team name means nobody is accountable for the date.
• Changing the schedule without a change request, so the document and the worksheet quietly disagree.
• Baselining once and never reviewing, until the plan is a historical document rather than a control.

Questions people ask

What is in this project plan template pack?

Two artifacts: a nine-section plan document in Word and PDF covering plan control, scope baseline, schedule summary, cost, accountability, RAID, communication, change control and sign-off; and an Excel schedule worksheet with a task schedule tab, a milestone baseline-versus-forecast tab and a how-to-use tab.

What is the difference between a project plan and a project schedule?

The plan answers what, why, how much and who, and changes only through approved change control. The schedule answers when and in what order, and is updated weekly. The pack keeps them as separate files for exactly that reason.

Is the schedule worksheet free to use commercially?

No. Both files follow the PMBOK Guide planning structure and ship inside the paid PM Delivery Toolkit. Once you buy the toolkit you can rename and reuse them on any project inside your organisation.

Does the worksheet calculate the critical path automatically?

It calculates finish dates from duration and flags any row with zero total float as critical. To derive early and late dates and float from scratch, paste your tasks into the free critical path calculator on this site and copy the float column back into the worksheet.

How long should a project plan be?

Around eight to ten pages for the document. If it is longer, detail that belongs in the schedule worksheet, the RAID log or the stakeholder register has been pasted into the plan instead of referenced from it.

How often should the plan and schedule be updated?

Update the schedule worksheet weekly and the milestone forecast column at the same time. Update the plan document only when an approved change request moves scope, cost or a committed date — then increment the version.

Read next

• Work Breakdown Structure and Scope Control
• The Critical Path Method, Worked Through
• Estimation That Survives Contact with Reality
• Total Float vs Free Float
• Change Control Without the Bureaucracy
• The Project Lifecycle, End to End

Other PMI-standard templates

Every one has the same walkthrough, worked example and PMI mapping, and every file ships inside the PM Delivery Toolkit.

• Project charter templateWord & PDF · Integration Management
• RACI matrix templateExcel, Word & PDF · Resource Management
• RAID log templateExcel, Word & PDF · Risk Management
• Stakeholder register templateExcel, Word & PDF · Stakeholder Management
• Project status report templateWord & PDF · Communications Management
• Lessons learned log templateWord & PDF · Integration Management

Keep going on the site

The hubs and tools that pair with this project plan pack.

• How to create a project planThe eight-step guide this pack was built for, question by question.
• Critical path calculatorEnter durations and dependencies to derive float, then paste it back into the worksheet.
• PM Delivery ToolkitEvery PMBOK-mapped template in one paid pack, with the walkthroughs.