Free template · Operations
Performance review template for a project manager
A ready-to-use, section-by-section template with the competencies that matter for a project manager, role-specific example phrases, and a guard against the stock filler that makes most reviews read as generic. Copy the structure, fill in your evidence, or skip the writing entirely with Crestento.
The template
Four sections, in this order. Length should match the evidence you have — a thin section is honest; an invented paragraph is not.
Summary
One or two paragraphs setting the context: what was expected of project manager this period, and your overall verdict. Lead with the headline.
Example phrasing
“Delivered the ERP rollout on time and 4% under budget despite a mid-project vendor change, with weekly RAID logs flagging the swap two weeks before it became critical. Re-baselined cleanly with the steering committee.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: scope, schedule, budget variance against baseline (with context), re-baseline cycles and how cleanly they landed, risks raised in advance vs surfaced reactively.
- Evidence for: scope, schedule, and budget management.
- Evidence for: risk identification and mitigation (RAID discipline).
- Evidence for: stakeholder communication and steering management.
- Evidence for: cross-team coordination and dependency tracking.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic project manager criticism.
- One pattern observed across the period.
- One specific behaviour to develop.
- One concrete next step.
Goals for the Next Period
Two or three concrete goals. Each should name a specific behaviour change, a measurable target, and a deadline. Avoid vague aspirations.
Competencies to evaluate
The 7 competencies a strong project manager review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- scope, schedule, and budget management
- risk identification and mitigation (RAID discipline)
- stakeholder communication and steering management
- cross-team coordination and dependency tracking
- change-control and re-baselining discipline
- retrospective rigor and post-project learning
- documentation and status reporting
Before you write
Project outcomes are heavily shaped by context the PM doesn't control — vendor behaviour, executive-sponsor stability, engineering capacity. Strong PM work is preventive and invisible: the risk flagged eight weeks ahead, the scope-creep that didn't happen because change-control ran cleanly, the stakeholder conflict resolved at the working-group level. A review that anchors on shipped-or-not without reading the underlying craft will over-credit lucky PMs and under-credit strong ones running harder projects.
Evidence to gather
Strong reviews for a project manager cite evidence of these shapes. Only use a specific value (a percentage, a count, a dollar amount) if you actually have it — don’t invent a number to sound concrete.
- scope, schedule, budget variance against baseline (with context)
- re-baseline cycles and how cleanly they landed
- risks raised in advance vs surfaced reactively
- change-control request volume and disposition
- stakeholder NPS or steering-committee feedback
- retro-to-practice-change conversion (how many retros produced real changes)
Where to find the evidence
Work products a project manager produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- RAID log (Risks, Assumptions, Issues, Dependencies)
- project charter and statement of work
- weekly status reports
- steering-committee minutes and decks
- change-control request register
- post-project retrospective and lessons-learned doc
- Gantt / WBS / burn-down depending on methodology
- stakeholder map and communication plan
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Delivered the ERP rollout on time and 4% under budget despite a mid-project vendor change, with weekly RAID logs flagging the swap two weeks before it became critical. Re-baselined cleanly with the steering committee.”
Weak — vague, unevidenced, generic
“Strong PM, very organised.”
Phrases to never use
Stock filler that AI-written project manager reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “strong PM”
- “very organised”
- “great at managing projects”
- “drives projects to completion”
- “passionate about project management”
- “trusted to deliver”
- “consistent project delivery”
- “stays calm under pressure”
Don’t invent these specifics
The details an AI tends to fabricate for project managerreviews. If you don’t have the specific number, name, or date in your notes, leave it out — generic-but-honest beats specific-but- invented every time.
- specific budget or schedule variance percentages not in input
- named projects or programs the PM ran
- specific risks raised or escalations made not mentioned
- particular methodology adoption claims (PMP, PRINCE2, SAFe) not in input
- named steering-committee members or sponsors not mentioned
- specific retro outcomes or process changes not in input
- tool-specific work (Smartsheet, Asana, Jira) not referenced
Skip the template, generate the review
Drop your bullet points into Crestento and it produces the polished draft using this exact template structure, tuned for a project manager. Two reviews free, no card.
Try Crestento free