Planning & Scheduling
Project Plan 2
MyPMP
QMS Template
Objectives
Scope
Approach
| Milestone | Owner | Due | Status |
|---|---|---|---|
βοΈ
Free to try β your work auto-saves in this browser.
Saving to the cloud (sync across devices) is a paid feature. Unlock Project Plan 2 for $1/mo, or get everything with membership ($9/mo or $99/yr).
πΊοΈ Planning & Scheduling
Auto-saved in your browser Β· β members can white-label & sync across devices
About the Project Plan 2 template
A Project Plan 2 is a second-iteration or refined project plan, typically produced after an initial baseline has been reviewed, approved, or revised to reflect changed scope, resourcing, or timelines. It consolidates the updated schedule, deliverables, and dependencies into a single working document so stakeholders track against the current agreed version rather than an outdated draft. Maintaining a versioned plan keeps execution aligned with reality and provides a clear audit trail of what changed and why.
It's part of My QMS, MyPMP's Quality Management System: fill it in online, personalize it with your name and logo, then export a clean, branded PDF. Your work auto-saves in your browser.
When to use a Project Plan 2
- βΈAfter a phase gate or stakeholder review triggers a revised baseline
- βΈWhen scope, budget, or milestones shift and the original plan is superseded
- βΈRolling from a high-level Plan 1 into a detailed delivery plan
- βΈOnboarding a new PM who needs the current source of truth
What a good Project Plan 2 includes
- βVersion number, revision date, and summary of changes from the prior plan
- βUpdated milestones, phases, and target dates
- βTask list with owners, durations, and dependencies
- βRevised resource allocation and budget figures
- βAssumptions, constraints, and current risks
- βApproval and sign-off record for the new baseline
What's inside this template
The interactive form above gives you:
ObjectivesScopeApproachA table of Milestone, Owner, Due, StatusRisks & dependencies
Tips & common mistakes
- π‘Log what changed between Plan 1 and Plan 2 so reviewers do not re-litigate settled decisions
- π‘Re-baseline formally rather than quietly editing dates, or your variance reporting becomes meaningless
- π‘Confirm dependencies still hold after a revision; a shifted milestone often breaks downstream tasks
How it works
- 1. Fill it in β type directly into the fields, tables and sections above.
- 2. Brand it β add your organization name and logo with the Branding button.
- 3. Export β print to PDF, or become a member to white-label and sync across devices.
FAQ
How does a Project Plan 2 differ from the first plan?οΌ
Plan 2 is the updated version created after review or change, carrying a new baseline, revised dates, and a documented record of what was altered since Plan 1.
When should I create a second version of my project plan?οΌ
Create one whenever an approved change, phase gate, or significant variance makes the original plan inaccurate as a guide for execution.
Should I keep the old project plan after making Plan 2?οΌ
Yes; retain the previous version for audit and variance analysis so you can compare planned versus revised commitments and justify the changes.
Make it yours β $9/mo or $99/yr
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membershipMore Planning & Scheduling templates