Performance Review Template, Employee Performance Review Examples, and Review Phrases
A copy-ready performance review template you can run this quarter, a filled-in example so the level of detail is concrete, phrase banks organized by rating, the self-evaluation form that goes out first, and the documentation habits that keep a review defensible.
In one answer
A performance review template should capture the review period and reviewer, three to five goals from the last period with an outcome against each, ratings on the competencies the role actually requires, specific strengths with evidence, specific areas to improve with evidence, goals for the next period, an employee comment section, and signatures from both parties. Send the self-evaluation a week ahead, write the review from documented examples rather than memory, and deliver it in a conversation rather than a document drop.
Human approval on every send · 14-day money-back guarantee
Try it on a real task
Routing slip · Officeagent
Status: Ready
Action requested
Pick a task above and press RUN IT. Officeagent handles it end to end; you approve the send.
Reading page /
☐ Approve · nothing sends without you
In the product you edit the draft right here; the agent learns your correction.
Officeagent drafted, you approved, it executed.
Sample data · Officeagent always waits for your approval before anything is sent
What a performance review is for, and the one rule that matters
A performance review does three jobs at once: it tells an employee where they stand, it creates the written record behind pay, promotion and (sometimes) termination decisions, and it sets what the next period is supposed to produce. Most reviews do the first job badly and the second job accidentally.
The rule that fixes most of it: nothing in the review should be new information. If an employee learns in the annual review that their handoffs have been sloppy since March, the failure is not theirs. Feedback that waits nine months is not feedback, it is an ambush, and it is also the version that reads worst if the record is ever examined. The review is a summary of conversations that already happened, not a substitute for them.
The practical consequence is that a review is written from notes, not from memory. Recency bias is real and well documented: without notes, a manager writes an assessment of the last six weeks and calls it a year. Keep a running file per person with dated entries, three lines each, whenever something notable happens in either direction. Ten minutes a month makes review week take an hour instead of a day, and it is the difference between "communication could be better" and "the March migration slipped four days because status was not shared until the Thursday."
The performance review template
Copy this into a document or form. It works for an annual, semi-annual or quarterly cycle; only the goal horizon changes.
PERFORMANCE REVIEW
Employee: [name] · Role: [title] · Department: [dept]
Reviewer: [name, title] · Review period: [start] to [end] · Date: [date]
1. GOALS FROM LAST PERIOD
For each goal: the goal as it was written · the outcome · met / partially met / not met · context (what helped or got in the way)
2. COMPETENCY RATINGS
Rate each on the scale below, and write one line of evidence under every rating. A rating without an example is an opinion.
Quality of work · Productivity and reliability · Communication · Collaboration · Problem solving and initiative · Role-specific skills [list the two or three that actually matter for this job] · Leadership (managers only)
3. STRENGTHS
Two or three, each with a specific example and, where possible, the effect it had on someone else's work.
4. AREAS FOR DEVELOPMENT
One or two, each with a specific example, the impact, and what "better" would look like concretely. Not a list of five.
5. GOALS FOR NEXT PERIOD
Three to five. Each one: what will be true, how it will be measured, by when, and what support is needed from the company.
6. OVERALL RATING
[scale value] with a two to three sentence summary in plain language.
7. EMPLOYEE COMMENTS
Left blank for the employee to complete after the conversation. Do not fill this in for them.
8. SIGNATURES
Employee: [signature] [date] (signing acknowledges receipt and discussion, not agreement).
Reviewer: [signature] [date] · Next-level reviewer: [signature] [date]
Two notes on the form itself. Keep the competency list short and role-relevant: a generic ten-competency grid produces ten mediocre ratings, while four that genuinely describe the job produce four useful ones. And keep section 7 genuinely open. An employee comment box that everyone leaves blank usually means the conversation was not one.
A filled-in performance review example
Here is section 3 and section 4 completed for a mid-level operations hire, so the level of specificity is unambiguous.
Strengths. "Owns problems end to end. When the vendor portal outage hit in April, D. did not escalate and wait; she pulled the last export, rebuilt the reconciliation in a sheet, and had the payment run out on the normal day. Two people downstream never knew there was an incident." · "Is the person others check their numbers with. Three colleagues independently mentioned bringing work to D. for review before sending it, which is a reliability signal you cannot self-report."
Areas for development. "Status communication on longer projects. On the Q1 migration, the four-day slip was known internally on the Tuesday and shared on the Friday. Nothing went wrong as a result, but two people spent Wednesday and Thursday planning against a date that had already moved. Concretely: for any project over two weeks, post a three-line status every Friday, and flag a slipped date the day it slips rather than when the plan is fixed."
Notice what those do. Each one names a specific incident with a date, states the actual effect on other people, and, in the development case, describes exactly what different behavior looks like. Compare that to "great team player" and "needs to work on communication", which are the two most common sentences in performance reviews and carry no information at all. An employee cannot act on the second version and, if the review ever matters legally, neither can anyone else.
Performance review phrases that are actually specific
Phrase banks have a bad reputation because most of them supply the vague sentences above. These are worth using differently: treat each one as a sentence stem you finish with your own evidence. The stem gives you the structure; the specifics are the review.
Exceeds expectations. "Took ownership of [problem] without being asked, and the result was [measurable effect]." · "Raised the standard for [process]: since [month], [specific improvement]." · "Handled [difficult situation] in a way that protected [client/colleague/deadline], specifically by [action]." · "Became the person the team goes to for [skill], which is visible in [evidence]."
Meets expectations. "Delivered [deliverable] on schedule across the period, including [example under pressure]." · "Consistently accurate on [work type]: [error rate or specific evidence]." · "Responds to [colleagues/clients] within [timeframe], which keeps [downstream process] moving."
Needs improvement. "On [project], [specific event] meant [specific impact on someone else]. Going forward, [concrete different behavior]." · "[Work type] has required rework [frequency]: for example, [instance]. The target is [standard], and the first step is [action]." · "Deadlines on [work] moved [number] times this period without advance notice. The expectation is that a slipped date is flagged the day it is known."
Two phrases to retire entirely. "Great attitude" tells an employee nothing they can repeat and is a common vehicle for bias, since it rewards agreeableness rather than output. "Needs to be more proactive" is the least actionable sentence in management: name the one situation where you wanted a different move, and describe the move.
Rating scales, self-evaluations, and the calibration problem
On scales, use five points or three, and label them in words rather than numbers alone. A five-point scale (does not meet, partially meets, meets, exceeds, outstanding) gives room to distinguish solid from exceptional. A three-point scale (below, meets, above) is faster and harder to game, and it stops the drift where every rating clusters at four. What you should not do is use a five-point scale and then rate everyone a four, which is what happens when ratings are attached to pay without a calibration step.
Calibration is the part small companies skip and then regret. Before ratings are final, have the managers sit together and compare: is a "meets" from one manager the same bar as a "meets" from another? Ten minutes per employee across a small team is enough, and it is the only defense against one lenient manager's team getting all the raises.
On self-evaluations, send them a week ahead, not at the meeting. Ask three or four open questions rather than the same competency grid: what are you proudest of this period, what did not go the way you wanted, what do you want to be doing more of, and what do you need from me. Read the answers before you write your draft. When an employee names their own development area first, the conversation stops being adversarial, and it happens more often than managers expect.
- Three or five points, labeled in words, used across the whole range
- Calibrate ratings across managers before anything is final
- Self-evaluation goes out a week ahead, with open questions
- Read the self-evaluation before drafting your own review
- Separate the pay conversation from the development conversation by a couple of weeks
Documentation, timing, and running the cycle without it eating a month
The review is also a record, and records get read at the worst possible moment. Two habits keep yours useful. First, write to the facts: dated incidents, observable behavior, and effects on work, never personality or protected characteristics. Second, keep the reviews consistent with everything else on file. A record showing three years of "exceeds expectations" followed by a termination for performance is the single most common documentation problem in small companies, and it is created by managers inflating ratings to avoid a hard conversation. Rate honestly in the moment and the record takes care of itself. Where a review supports a formal decision, the linked policies in your employee handbook should say the same thing the review says.
On timing: annual reviews are the norm and are too infrequent on their own. The version that works for a small business is a light quarterly check-in against goals, a full documented review once or twice a year, and a monthly one-to-one where feedback happens in real time. If you only do one thing, do the one-to-ones, because they are what make the annual review contain no surprises.
The administrative weight of a review cycle is genuinely heavy for a small office: scheduling every pairing, sending self-evaluations a week ahead, chasing the four people who have not submitted, collecting manager drafts, booking the conversations, filing signed forms, and setting reminders for the goals agreed in each one. None of that requires judgment, and all of it requires somebody. Officeagent runs that layer: it sends the forms, chases the stragglers, books the meetings, and files the signed reviews where they belong, while the goals from each review become tracked items with owners and due dates instead of a line in a document nobody opens until next year. Every message and filing waits on a human approval, which is the right control on anything in a personnel file.
Performance review sections, what goes in each, and the common mistake
| Section | What belongs in it | Common mistake |
|---|---|---|
| Goals from last period | Each goal as written, the outcome, met status, and context | Reviewing goals nobody wrote down at the start |
| Competency ratings | Four to six role-relevant competencies, each with a line of evidence | A ten-competency generic grid rated entirely fours |
| Strengths | Two or three, each with a dated example and its effect on others | "Great team player" with no evidence |
| Areas for development | One or two, with the incident, the impact, and what better looks like | Five items, none of which get acted on |
| Next period goals | Three to five, measurable, dated, with the support needed named | Aspirations with no measure or deadline |
| Overall rating | A scale value plus two or three sentences in plain language | Inflated ratings that contradict later decisions |
| Employee comments | Left genuinely open for the employee after the conversation | Filled in by the manager, or always blank |
| Signatures | Both parties, acknowledging receipt and discussion | Treating the signature as agreement with the content |
Pricing
Assistant $149/mo · Office $399/mo · Enterprise from $1,500/mo
Office covers the whole team, up to 10 people, with the follow-up engine and CRM sync. Full limits on the AI assistant pricing page.
Questions on this
What should be included in a performance review?
A performance review should include the review period and reviewer, the goals from the last period with an outcome against each, ratings on four to six role-relevant competencies with an example under each, two or three specific strengths, one or two development areas with evidence and a concrete target, three to five goals for the next period, an open employee comment section, and signatures from both parties.
How do you write a performance review for an employee?
Start from your dated notes rather than memory, read the employee's self-evaluation first, and write every rating with a specific example under it. Name two or three strengths and no more than two development areas, each with the incident, its effect on other people, and what different looks like. Then set three to five measurable goals for the next period and deliver it as a conversation, not a document.
What are good performance review phrases?
The useful ones are sentence stems you finish with evidence: "took ownership of [problem] without being asked, and the result was [effect]", "on [project], [event] meant [impact]; going forward, [concrete behavior]". Avoid "great attitude" and "needs to be more proactive", which give an employee nothing to repeat or change and are common vehicles for bias.
How often should performance reviews be done?
A full documented review once or twice a year, a lighter check-in against goals each quarter, and a monthly one-to-one where feedback happens in real time. The annual review alone is too infrequent to change behavior. The test of the cadence is simple: if anything in the annual review is news to the employee, the check-ins are not happening.
What rating scale should I use for performance reviews?
Use three points (below, meets, above) or five (does not meet, partially meets, meets, exceeds, outstanding), labeled in words rather than numbers alone. Whichever you pick, use the whole range and calibrate across managers before ratings are final, since the usual failure is a five-point scale where almost everyone is rated a four.
Should employees see the performance review before the meeting?
Send the self-evaluation a week ahead and read it before drafting your review, but hand over the completed review at the start of the conversation rather than days before. Sending it early turns the meeting into a defense of a document. The exception is a lengthy written review, where giving the employee ten minutes to read it in the room before you talk works well.
Does a signed performance review mean the employee agrees with it?
No. A signature on a performance review acknowledges that the employee received the review and discussed it, not that they accept its content, and the form should say so in that line. If an employee disagrees, the right response is to ask them to record their disagreement in the employee comments section, which keeps both positions in the same record.
Also on the routing slip
Your office admin, off your plate by Monday
Connect your calendar, inbox and drive. Officeagent drafts the work, you hit approve, and the busywork leaves your desk for good.
14-day money-back guarantee · Cancel anytime