Auto-saved in your browser Β· β members can white-label & sync across devices
About the Project Review template
A Project Review is a structured checkpoint that assesses whether a project is delivering against its scope, schedule, budget, and quality objectives, and captures what should change going forward. It gives sponsors and delivery teams a shared, evidence-based view of progress rather than optimistic status colours, and creates a documented trail of decisions and corrective actions.
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 Review
- βΈAt the end of a phase or stage gate before authorising the next tranche of work
- βΈDuring monthly or quarterly steering-committee cycles to validate RAG status and forecasts
- βΈWhen a project is drifting on cost, schedule, or quality and needs a formal reset
- βΈPost-implementation, to compare delivered benefits against the original business case
What a good Project Review includes
- βProject summary: objectives, sponsor, current phase, and reporting period
- βPerformance against baseline: schedule variance, budget/EAC, and scope changes
- βRAG status with a short narrative explaining each rating
- βOpen risks, issues, and decisions requiring escalation
- βMilestones achieved this period and those forecast next period
- βActions, owners, and due dates arising from the review
What's inside this template
The interactive form above gives you:
Tips & common mistakes
- π‘Back every RAG rating with a number or fact; a green status with no evidence hides problems until it is too late
- π‘Keep actions specific and ownedβreviews fail when they generate discussion but no accountable next steps
- π‘Compare against the approved baseline, not last month's forecast, so scope creep and slippage stay visible
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 often should a project review be held?οΌ
Most projects run a formal review at each phase or stage gate plus a lighter monthly or steering-cycle review; high-risk or fast-moving work may warrant more frequent checkpoints.
Who should attend a project review?οΌ
Typically the project manager, sponsor or steering committee, and key workstream leads; supplier or PMO representatives join when contract performance or portfolio alignment is on the agenda.
What is the difference between a project review and a lessons-learned session?οΌ
A review assesses live performance and decides corrective actions while the project is running, whereas a lessons-learned session looks back after delivery to capture insights for future projects.
Membership unlocks white-label export (remove the MyPMP footer), cloud sync across devices, plus all apps & ScheduleX.
See membership