Performance Review Template for Managers + Examples (Written From Evidence)

A performance review template needs four parts: (1) competency ratings on a clear scale, (2) specific evidence behind each rating, (3) goals for next period, and (4) an overall summary. The copyable template and competency-by-competency examples are below. The hard part is not the form. It is filling it with specifics. A review that says "communicates well" is forgettable. "Led three incident retros and wrote the runbook the team now uses (logged March to May)" is defensible. Specifics require notes you kept during the year, not a memory test at the blank page. Below: the template, real examples, and how to close that evidence gap.

The performance review template

Copy this and fill it in per person. Keep the structure simple so every reviewer reads the scale the same way, and so each rating has a place to cite the dated moment behind it.

PERFORMANCE REVIEW · @[Name] · [Period]
Rating scale: 1 Below · 2 Developing · 3 Meets · 4 Exceeds · 5 Outstanding

COMPETENCY              RATING   EVIDENCE (dated, specific)
Impact / Results         [ ]
Technical / Craft        [ ]
Communication            [ ]
Collaboration            [ ]
Ownership / Reliability  [ ]
Growth this period       [ ]

KEY ACCOMPLISHMENTS (3-5, with impact)
-

DEVELOPMENT AREAS (behavior + path forward, not character)
-

GOALS · NEXT PERIOD (specific, measurable)
-

OVERALL SUMMARY
-

Each row earns its rating in the evidence column. If you cannot point to a dated moment for a score, that is a signal you are rating an impression, not a record. The fix is not to concentrate harder at the blank page. It is to have written things down while they were still true.

How to use it in five steps

1. Read the whole period first. Walk the calendar from the start of the cycle, not from last month. Early work counts as much as last week.
2. Rate each competency on the scale. Score impact, craft, communication, collaboration, ownership, and growth, one row at a time.
3. Attach two or three dated examples per rating. Name the project, the date, and the outcome in the evidence column.
4. Write development areas as behavior plus a path. Describe what happened and what changes next, not who the person "is."
5. Set measurable goals and a short summary. Close with goals you can check and a summary that matches the evidence above.

Want the evidence already gathered when review season starts? See how managers prep a full cycle from per-person notes.

Performance review examples by competency (vague vs specific)

The same achievement can read as a throwaway adjective or as defensible evidence. Each example below shows the before (vague, forgettable) and the after (dated, specific). Use them as patterns: swap in your person's real projects, dates, and numbers.

Impact and results

• Vague: "Delivered strong results."
  Specific: "Shipped the billing migration February to March with zero downtime and unblocked three teams; owned the rollback plan from start to finish."
• Vague: "Had a productive quarter."
  Specific: "Cut checkout latency from 1.4s to 380ms this half, which reduced cart abandonment by 22% in the A/B test."
• Vague: "Closed a lot of work."
  Specific: "Closed 14% more support tickets than the team target while holding CSAT at 4.7 out of 5 (Q2 to Q3)."
• Vague: "Helped move the roadmap forward."
  Specific: "Drove the search-relevance project to launch in May; click-through on results rose 11% in the first month."
• Vague: "Was reliable on delivery."
  Specific: "Hit 9 of 10 committed dates this period; the one slip (the October export feature) was flagged two weeks early with a revised plan."

Technical and craft

• Vague: "Writes good code."
  Specific: "Refactored the notification service in April; the new design cut on-call pages for that service from roughly 6 a week to under 1."
• Vague: "Solid technical skills."
  Specific: "Caught the data-leak bug in staging before the March release and added the regression test that now guards it, which saved an escalation."
• Vague: "Quality is fine."
  Specific: "Raised test coverage on the payments module from 41% to 78% over the half; review cycles on that module dropped noticeably."
• Vague: "Knows the system well."
  Specific: "Became the go-to for the sync engine this period; wrote the architecture doc the team now onboards new engineers with (June)."

Communication

• Vague: "Communicates well."
  Specific: "Ran three incident retros this half; the runbook she wrote is now the team standard (April)."
• Vague: "Keeps people informed."
  Specific: "Started weekly project summaries in February; two other teams said it cut their status pings to her."
• Vague: "Clear in meetings."
  Specific: "Rewrote the launch plan into a one-page brief that stakeholders actually read; the March launch had no last-minute scope surprises."
• Vague: "Good at documentation."
  Specific: "Rebuilt the onboarding docs after noticing new hires asked the same five questions; ramp time dropped from about 3 weeks to about 10 days."

Collaboration

• Vague: "Works well with others."
  Specific: "Paired with design weekly on the redesign instead of waiting for handoff; the team shipped two sprints early."
• Vague: "Helpful teammate."
  Specific: "Unblocked the data team during the April crunch without being asked, which kept the dashboard launch on date."
• Vague: "Mentors others."
  Specific: "Mentored a new teammate through their first on-call; they were running solo by week three."
• Vague: "Good in cross-team work."
  Specific: "Coordinated QA across three teams for the platform launch; ran daily syncs and a shared tracker, and we shipped on date with zero P1s."

Ownership and reliability

• Vague: "Takes ownership."
  Specific: "Owned the checkout domain solo this year (4 services, on-call lead) and kept it stable through two major launches."
• Vague: "Dependable."
  Specific: "Volunteered to own the messy data-cleanup project nobody wanted in Q3 and saw it through to done; reporting errors fell to near zero after."
• Vague: "Handles pressure."
  Specific: "During the June outage, posted status every 30 minutes and led the fix, then drove the retro that produced three shipped follow-ups."
• Vague: "Follows through."
  Specific: "Closed every action item from our 1:1s this period; the two that slipped, she flagged the same week with a new date."

Growth this period

• Vague: "Has grown a lot."
  Specific: "Moved from owning tasks to owning a workstream this half; ran the search project with light oversight from start to launch (Feb to May)."
• Vague: "Improving steadily."
  Specific: "Acted on the feedback to scope before committing; the last three projects landed on time after a rough Q1 on estimates."
• Vague: "Showing more leadership."
  Specific: "Stepped up to lead planning when I was out in April; the team kept the sprint realistic and hit it."

Development areas (behavior plus a path, not character)

• Vague: "Needs to be more reliable."
  Specific: "Missed 3 of 5 committed dates in Q3, mostly from late scoping. Next step: scope reviews before committing dates. Let's pair on the first two."
• Vague: "Should communicate better."
  Specific: "Twice this half, blockers surfaced in standup days after she hit them. Going forward, flag a blocker the day it appears. We will add a midweek checkpoint."
• Vague: "Quality needs work."
  Specific: "The last two PRs had test gaps caught in review, which added a cycle each. Next step: a self-review checklist before requesting review."
• Vague: "Too quiet in meetings."
  Specific: "In planning, strong ideas tend to stay in 1:1s and not reach the room. Next step: bring one estimate or risk to each planning session; I will make space for it."

Overall summary

• Vague: "Great year, keep it up."
  Specific: "Consistently exceeded on impact and craft this period; the growth area is estimation. Ready for stretch project ownership next half."
• Vague: "Solid year overall."
  Specific: "Met expectations across the board and exceeded on collaboration. With more reps owning scope decisions, on track to operate at the next level by year end."

Why the usual review goes vague (and how to fix it)

Almost every weak review fails the same handful of ways. None of them is a writing problem. They are evidence problems that show up at the blank page.

• The blank-page cram. Opening the form the night before forces you to reconstruct a year from memory in one sitting. What you get is the last six weeks with footnotes.
• Adjectives without evidence. "Strong communicator," "reliable," "needs polish." None of these can be checked or defended. Replace each with a dated moment.
• Recency bias. The most recent sprint feels like the whole year. A quiet spring of real work disappears, and one rough November drags down a strong cycle. Here is how to prep from the whole year instead.
• Character feedback instead of behavior. "He's disorganized" is a verdict on a person. "The deck wasn't ready Tuesday, so we lost 15 minutes" is feedback someone can act on. See more constructive feedback examples.
• Unmeasurable goals. "Be more proactive" cannot be reviewed next cycle. "Flag blockers the day they appear and bring one risk to each planning session" can.

The fix for every item above is the same: keep dated notes per person as the year goes, so the review is reading, not remembering.

Write the review from a year you already wrote down

A year of @person notes turns the blank review page into a writing task, not a memory test. The evidence is already there, dated, under each person's timeline. You type @Sarah, write one line when something lands, and tag it #delivery or #mentoring. Months later you search the name, the year is grouped and dated, and you pull the specifics straight into the template. Prep stops being recall and becomes reading.

The notes are private by default and account-scoped, and they are stored on secured infrastructure. You can export anytime. What is live today is the part this page depends on: web capture, @people timelines, #topic timelines, search, and export. That is enough to walk into a review with two or three dated examples per competency already in hand.

• ✓ Type @Sarah, write one line. The note files itself into Sarah's timeline. No folders, no "review-notes-v2-FINAL."
• ✓ Tag the competency. Add #delivery or #communication and the same note also lands in a topic timeline you can read at review time.
• ✓ Search the name at review time. The whole period comes back dated and grouped, so each rating cites a real moment.

Performance review FAQ

Keep going

• Recency bias in reviews: prep from the whole year. Why reviews drift toward the last six weeks, and the fix.
• Constructive feedback examples that stay specific. The situation-behavior-impact pattern for development areas.
• The 1:1 meeting notes template that builds on itself. Capture the moments that fill the review, week by week.
• Self-evaluation examples. The employee side of the same review, with examples by competency.
• Notivo for managers. A private, per-person memory for every report.