Project Manager Self-Evaluation Examples (Copy & Paste)
Project managers make other people's work land on time, which means your own wins are easy to overlook, including by you. A strong self-evaluation turns that invisible coordination into results a reviewer can see.
Below are 25 examples you can copy, grouped by what reviewers look for. Replace every [bracketed] value with your own numbers.
The formula behind every strong example
What you did
The action you personally took, not what the team did around you.
The measurable result
A number, a before-and-after, or a date. An honest estimate is fine.
Why it mattered
The effect on customers, revenue, the team, or a company goal.
Example: Delivered the CRM migration on schedule and 4% under budget (result) by re-sequencing dependencies across four teams (what I did), so sales could start the new quarter on the new system (why it mattered).
What reviewers look for in a project manager self-evaluation
| Area | The question behind it |
|---|---|
| Delivery and scope control | Did your projects land on time, on budget, and at the scope everyone agreed to? |
| Stakeholder communication | Did the right people know the right things early enough to act on them? |
| Risk and issue management | Did you see problems coming and keep them from becoming delays? |
| Process improvement | Is the team faster or calmer because of a change you made? |
| Leading without authority | Could people who don't report to you still rely on you to lead? |
25 self-evaluation examples for project managers
Delivery and scope control
- Delivered the [CRM migration] on schedule and [4]% under its $[X] budget while keeping all [12] committed requirements in scope.
- Brought a project that was [6] weeks behind back on track within one quarter by re-planning the critical path and cutting two low-value deliverables with sponsor sign-off.
- Ran [9] projects in parallel this year with an on-time delivery rate of [89]%, up from [70]% the year before.
- Introduced a change-request log that cut unplanned scope additions by [40]% across my portfolio.
- Closed out [3] projects with formal lessons-learned reviews, and [2] of the recommendations are now standard practice on the team.
Stakeholder communication
- Sent a one-page weekly status to [15] stakeholders that leadership now uses as the template for every project in the department.
- Aligned [4] department heads with conflicting priorities on a single launch date by running a trade-off workshop and documenting each decision.
- Held bi-weekly reviews with the executive sponsor, so no issue reached them for the first time as an escalation.
- Flagged a vendor delay [3] weeks early, giving the sales team time to reset customer expectations before any contract was affected.
- Rebuilt trust with a frustrated client by moving them to a weekly call and a shared action tracker; they renewed for another [12] months.
Risk and issue management
- Kept a live risk register for [project]; [5] of the [7] risks I identified were mitigated before they affected the timeline.
- Caught a compliance gap during planning that would have delayed go-live by an estimated [2] months.
- Prepared a contingency plan for our single-vendor dependency and used it when the vendor missed delivery in [month], losing only [3] days.
- Cleared a cross-team blocker in [2] days that had stalled the project for three weeks, by getting both managers into one decision meeting.
- Set early-warning thresholds for budget burn, which surfaced a $[X] overrun in time to renegotiate the contract.
Process improvement
- Standardized our project kickoff checklist, cutting average setup time from [3] weeks to [8] days.
- Moved the team from spreadsheets to [Asana], giving leadership real-time visibility and removing about [4] hours of manual reporting a week.
- Introduced a simple RACI for every project, and handoff questions in our team channel dropped by about half within a month.
- Wrote a project playbook that [6] new hires used to run their first project without shadowing.
- Cut our weekly status meeting from 60 to 25 minutes by moving updates into a written pre-read.
Leading without authority
- Led a cross-functional team of [11] people from [4] departments without direct authority and delivered the program on its original date.
- Mentored [2] junior project coordinators; one now runs projects independently.
- Kept the team steady through a [3]-month crunch by protecting focus time and rotating weekend coverage fairly.
- Ran blameless retrospectives after every milestone, and the team adopted [5] of its own improvement ideas.
- Stepped in as interim lead for [team] for [6] weeks during a manager vacancy without missing a deliverable.
Examples for a year that didn't go to plan
Most review forms ask about areas for growth. Name what happened, what you learned, and what you are changing.
- Two of my projects slipped this year, and in both cases I raised the risk too late. Next year I will review the risk register with sponsors every two weeks instead of monthly.
- I relied on email for critical decisions, and some got lost. I now confirm every decision in a shared decision log.
- I took on too many projects in Q[2], and quality slipped on [project]. I have agreed a maximum portfolio size with my manager.
- I want stronger financial skills, so I plan to complete [a budgeting course] and own the budget forecast on my next program.
- Delegating was hard for me this year. My goal is for each coordinator to own one workstream end to end.
Before and after: vague vs. specific
"I managed several projects and kept everyone updated."
"I delivered 7 of 8 projects on time and sent a weekly one-page update to 15 stakeholders, which leadership adopted as the department template."
Why it works: It says how many, how well, and what changed because of you.
"I'm good at handling risks."
"I identified 7 risks on the ERP rollout and mitigated 5 before they hit the schedule, including a compliance gap that would have delayed go-live by two months."
Why it works: A claim about yourself becomes evidence a reviewer can repeat in calibration.
"I improved our processes."
"I standardized our kickoff checklist, cutting project setup time from three weeks to eight days."
Why it works: A before-and-after number shows the size of the improvement.
Free project manager self-evaluation template
# [Your Name] — Self-Evaluation ([Review period])
Role: Project Manager · Team: [Team] · Manager: [Name]
## 1. Summary
The one or two results you most want your manager to remember.
## 2. Key accomplishments
Formula: what I did + the measurable result + why it mattered.
### Delivery and scope control
-
### Stakeholder communication
-
### Risk and issue management
-
### Process improvement
-
### Leading without authority
-
## 3. Areas for growth
- What didn't go to plan, what I learned, and what I'm changing:
## 4. Goals for next period
- Write down what you remember. WinStash does the rest.
Paste rough notes about your year, even half-remembered ones. WinStash turns them into review-ready accomplishments in the same format as the examples above. Then log a one-minute note each Friday, and next year's review writes itself.
- Weekly updates for your manager
- Brag sheet for your review
- STAR stories for interviews
Frequently Asked Questions
What should a project manager include in a self-evaluation?
Lead with delivery results: projects completed, on-time and on-budget rates, and scope you protected. Then add stakeholder outcomes, risks you caught early, process improvements, and how you led people you did not manage directly.
How do I write about projects that were delayed?
Explain what caused the delay, what you did to limit it, and what you changed afterward. Reviewers usually care more about how you handled a slip than about the slip itself.
How long should a project manager self-evaluation be?
Most review forms fit in one to two pages. Pick your three to five strongest accomplishments and give each a number and a result instead of listing every task.
What if I don't have exact numbers?
Use honest estimates and label them as estimates, such as "about 30%" or "roughly four hours a week." Your project tool, calendar, and old status reports hold most of the dates and counts you can verify.
How do I remember what I did all year?
Look back through status reports, sent email, calendar invites, and closed tickets. Next year, write a short note every Friday so the evidence is already collected when review season arrives.