Free template · Operations
Performance review template for a program / senior project manager
A ready-to-use, section-by-section template with the competencies that matter for a program / senior 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 program / senior project manager this period, and your overall verdict. Lead with the headline.
Example phrasing
“Ran the 14-month platform-migration program across four engineering teams, $1.4M budget, two C-level sponsors. Delivered against re-baselined plan with documented benefit tracking. Mentored two junior PMs through their first program-level work.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: program-level variance against re-baselined plan, benefits realised vs business case, interdependency-driven escalation count.
- Evidence for: multi-project program planning and orchestration.
- Evidence for: interdependency and resource management.
- Evidence for: executive-level stakeholder management.
- Evidence for: risk and issue management across projects.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic program / senior 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 program / senior project manager review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- multi-project program planning and orchestration
- interdependency and resource management
- executive-level stakeholder management
- risk and issue management across projects
- PMO process and methodology stewardship
- mentorship of project managers
- program-level budget and benefit tracking
Before you write
Program managers run the work that's too big or interdependent for one project manager. They orchestrate multiple PMs, manage executive stakeholders, and hold the through-line on benefits / outcomes across the program. Strong program managers run programs that finish with both the deliverables AND the people intact. Weak program managers ship the deliverables but burn out the teams.
Evidence to gather
Strong reviews for a program / senior 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.
- program-level variance against re-baselined plan
- benefits realised vs business case
- interdependency-driven escalation count
- executive-sponsor satisfaction signal
- PMs mentored through specific program phases
- PMO process improvements adopted across the function
Where to find the evidence
Work products a program / senior project manager produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- program charter and benefits case
- interdependency map across projects
- executive steering deck and minutes
- program-level RAID register
- re-baselining proposal documentation
- PMO methodology contributions (templates, playbooks)
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Ran the 14-month platform-migration program across four engineering teams, $1.4M budget, two C-level sponsors. Delivered against re-baselined plan with documented benefit tracking. Mentored two junior PMs through their first program-level work.”
Weak — vague, unevidenced, generic
“Strong senior PM.”
Phrases to never use
Stock filler that AI-written program / senior project manager reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “strong senior PM”
- “trusted by executives”
- “drives large programs to success”
- “exceptional program leader”
- “consistently delivers complex work”
- “calm under pressure”
- “rallies the team”
Don’t invent these specifics
The details an AI tends to fabricate for program / senior 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 program budgets not in input
- named programs or initiatives the PM ran
- specific re-baseline counts or outcomes
- named C-level sponsors or steering members
- particular PMO methodology adoption claims
- specific benefit-realisation percentages
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 program / senior project manager. Two reviews free, no card.
Try Crestento free