Support rep performance review template
A structured quarterly or half-yearly performance review for a support rep — evidence gathering, a support-specific competency rubric, metrics read as context rather than verdict, and forward goals — for managers who want a review that holds up instead of one that runs on last month's memory.
A performance review is the periodic, on-the-record conversation — usually quarterly or twice a year — where a support rep and their manager step back from the queue to agree on how the last stretch went and what the next one should look like. It is not the weekly coaching 1:1, and it is not the day a rep first hears bad news. If anything here is a surprise, the coaching that should have happened week to week didn't.
Done badly, reviews are theatre: only 14% of employees strongly agree the reviews they receive inspire them to improve, and just 29% think they are even fair (Gallup). Done well, a review is one honest read of the evidence plus a clear plan. This template is built to get you there. Replace everything in [brackets] before you use it.
Ground rules
- No surprises. Every theme here should have come up in a 1:1 already. A review summarizes; it doesn't ambush.
- Evidence over memory. Bring specific tickets, calls, and moments — not a general impression of the last three weeks. Most of us can't reliably recall behavior from more than a couple of months ago, so the review defaults to whatever happened recently unless you fight it with notes.
- Metrics are context, not the verdict. Numbers open questions; they don't close them. A rep with great CSAT who cherry-picks easy tickets is not your best rep.
- Two-way. The rep self-assesses first and does at least half the talking.
- Forward-looking. The point isn't the grade. It's the two or three things that change next quarter.
Cadence and roles
| Field | Value |
|---|---|
| Rep | [name] |
| Manager | [name] |
| Role / level | [e.g. Support Specialist II] |
| Review period | [Q_ / date range] |
| Cadence | [quarterly / twice-yearly] |
| Date of conversation | [date] |
Before the review
Manager prep (do this with the tickets open)
- Pulled the rep's numbers for the full period, not just the last few weeks (see the metrics table)
- Read
[8–12]of their interactions — a spread, including hard and routine ones, not only the flagged failures or the wins - Collected
[2–3]specific strengths, each tied to a named ticket/call/chat - Collected
[1–2]specific growth areas, each tied to a named example — one theme, not a list of ten small things - Checked whether last review's goals actually happened
- Gathered peer / cross-team input if this role touches Tier 2, escalations, or mentoring
[optional] - Read the rep's self-assessment before drafting my ratings, and noted where we disagree
Rep self-assessment (rep fills this in first)
- What I'm proudest of this period, with an example:
[...] - Where I want to get better:
[...] - What got in my way — tools, process, staffing, unclear scope:
[...] - How last period's goals went, honestly:
[...] - What I want next: skills, ticket types, a channel, a step toward
[role]:[...]
The rating scale
Use one scale for every competency. Anchor it in behavior so two managers would land in the same place.
| Rating | Means |
|---|---|
| 1 — Developing | Not yet meeting the bar for the role; needs structured support and a clear plan |
| 2 — Solid | Consistently meets the bar for the role; reliable, no concerns |
| 3 — Strong | Regularly exceeds the bar; a step above peers at level |
| 4 — Exceptional | Sets the standard others learn from; operating beyond the role |
Most solid reps sit at 2. That is a good outcome, not a disappointment — resist the drift where 2 quietly reads as "below average."
Competency rubric
Score each against your role's expectations. The middle column is the "Solid (2)" bar; adjust wording to your product and stack.
| Competency | What "Solid" looks like | Rating [1–4] | Evidence (ticket/example) |
|---|---|---|---|
| Resolution quality & accuracy | Solves the actual problem, correctly, without avoidable back-and-forth | [ ] | [#____] |
| Customer experience | Clear, human, low-effort replies; matches the customer's state; de-escalates | [ ] | [#____] |
| Productivity & reliability | Carries a fair share of volume for the role; meets SLAs; schedule-dependable | [ ] | [#____] |
| Judgment & escalation | Knows their limits; escalates the right things with clean, complete handoffs | [ ] | [#____] |
| Knowledge contribution | Fixes/creates KB articles and macros; captures answers so others reuse them | [ ] | [#____] |
| Collaboration & team | Helps in swarms, answers peers, onboards newer reps, shares what they learn | [ ] | [#____] |
| Ownership & growth | Follows through, seeks feedback, acts on it, drives their own development | [ ] | [#____] |
Metrics as context
Bring the numbers, then read them against the norm — and against how they might be gamed. A number that looks great in isolation can hide the real story.
| Metric | This rep | Team / role norm | Read it as |
|---|---|---|---|
| QA score | [__%] | [__%] | Quality, if your rubric predicts real outcomes |
| CSAT | [__%] | [__%] | Signal, not proof — check response rate and who bothers to answer |
| Reopen rate | [__%] | [__%] | The customer's verdict on "resolved" — low is good |
| Tickets / volume | [__] | [__] | Effort — but only alongside difficulty and mix, or it rewards cherry-picking |
| Handle / resolution time | [__] | [__] | A budgeting number, not a quality one; fast + wrong is worse than slow + right |
| SLA / schedule adherence | [__%] | [__%] | Reliability |
- For any metric that's an outlier, I've asked why before I've judged — mix, difficulty, a broken tool, or a genuine skill gap
The conversation (45–60 min)
| # | Segment | Time | Who leads |
|---|---|---|---|
| 1 | Rep walks their self-assessment | 10 min | Rep |
| 2 | Strengths — specific, with examples | 10 min | Manager |
| 3 | Growth areas — one theme, with examples | 10 min | Manager |
| 4 | Ratings & metrics, where you agree and don't | 10 min | Both |
| 5 | Goals for next period | 10 min | Both |
| 6 | Career / development & anything on the rep's mind | 10 min | Rep |
- Opened with the rep's own read, not mine
- Named strengths as concretely as growth areas (praise deserves a ticket number too)
- Let disagreement stand where we genuinely disagree, and recorded it
- Didn't defend the company reflexively when the rep raised a real blocker
Goals for next period
Two or three, no more. Each specific, measurable, and mostly within the rep's control.
- Goal 1:
[what, how you'll both know it happened, by when] - Goal 2:
[...] - Goal 3 (optional):
[...] - Support the rep needs from me to hit these:
[coaching, a rotation, a tool, protected time]
Development and career
- Where this rep wants to go next:
[deeper IC specialty / Tier 2 / lead / analyst / adjacent team] - The gap between here and there, in one or two skills:
[...] - One concrete step this period toward it:
[...]
Summary and sign-off
- Overall:
[one honest paragraph — no hedging, no surprises] - Overall rating (if your process requires one):
[1–4] - Rep has seen this in full and added their comments:
[...] - Manager sign-off:
[name / date] - Rep sign-off (acknowledges, need not agree):
[name / date] - Next review scheduled:
[date]
Mistakes that hollow out a review
- Saving up bad news for review day. If it's new here, your 1:1s failed. Fix that, not the wording.
- Letting the last month stand in for the whole period. Notes beat memory; without them the review just rates recent luck.
- Treating one metric as the verdict. Every support number can be gamed. Read them together, and ask why.
- Rating everyone a 3 to avoid hard conversations. Inflation makes the scale meaningless and cheats your real top performers.
- All grade, no plan. A rep should leave knowing the two things that change next quarter, not just a number.
- Confusing a below-bar quarter with a below-bar person. Ask what got in the way before you conclude it's them.
Continue exploring