Employee Review Form: What to Include, With Six Templates You Can Copy

A review form does two jobs. It makes managers write down something specific enough to be useful, and it makes the process consistent enough to defend. Most forms do neither, because they ask for ratings without asking for evidence.

This page covers what to put on an employee review form, which rating scale to use, six templates you can copy as they are, and the mistakes that turn a completed form into a filing exercise.

{{banner-1="/banner-page"}}

Employee review form, evaluation form, feedback form: which is which

The three names get used interchangeably and they are not the same document.

• An employee review form is filled in by a manager about one person, for a defined period, and it ends in a rating or a summary judgement. It goes on the record.
• An employee evaluation form means the same thing in practice. If there is a distinction, "evaluation" leans slightly more formal and more likely to include a scored competency matrix. Treat the two terms as synonyms and pick whichever one your company already says.
• An employee feedback form is different: it collects feedback in one direction or many, often anonymously, and it does not produce a rating. Use it for pulse feedback, upward feedback and post-project input — not for the performance record.

The rest of this page is about the first two. If you want a form that gathers opinions rather than one that records a judgement, the feedback form is the one you want.

What every employee review form needs

Eight components. Anything beyond these is usually there because someone added it once and nobody removed it.

1. Identification and period

Name, role, manager, department, and the exact period covered. The period matters more than it sounds: without it, the review drifts into whatever the manager remembers from the last month, which is the single most common source of unfair ratings.

2. The expectations being measured against

Either the role's stated responsibilities or the goals agreed at the start of the period, written on the form itself. A rating against expectations nobody wrote down is an opinion with a number attached.

3. Rating scale with defined levels

Each point on the scale needs a written description of what it looks like, not just a label. More on this below.

4. A comment box under every rating, not one at the end

This is the highest-leverage design choice on the form. A single comment box at the bottom gets one paragraph covering everything. A box under each rating gets evidence attached to each score, which is what makes the conversation specific and the record defensible.

5. Self-assessment, completed first

The employee fills in their section before the manager writes theirs, and the manager reads it before rating. This surfaces disagreement about facts before it becomes disagreement about judgement, and it frequently changes the rating.

6. Strengths and development areas, with examples

Two or three of each, each with a specific instance. "Communication could improve" is not usable. "The incident update on 14 March did not reach the support team until after customers had called" is.

7. Goals for the next period

Three at most, each with a measure and a date. If the form ends at the rating, the review has documented the past and changed nothing about the future.

8. Signatures, dates, and space for employee comment

Including a box the employee can use to disagree on the record. A form the employee cannot contest is a form they will contest elsewhere.

Rating scales: pick one and define it

Three options are in common use and the choice matters less than the definitions you write for each level.

Five-point scale

The default, and the right default. Five levels give enough range to separate strong from adequate without asking managers to make distinctions they cannot defend. Typical labels run from "does not meet expectations" to "consistently exceeds expectations", with "meets expectations" in the middle.

Write a one-line behavioural description of each level for the role. Without that, the scale measures manager temperament: some managers' 3 is other managers' 4, and calibration becomes impossible. The performance rating scale guide goes deeper on the trade-offs.

Ten-point scale

More granularity in theory, less reliability in practice. Two managers will not agree on the difference between a 6 and a 7, and nobody uses the bottom third. If you already have one, the practical fix is to group it into bands.

Behaviourally anchored rating scale

Each point on the scale carries a concrete example of observable behaviour for that competency. It produces the most consistent ratings of the three and takes the most work to build, because every competency needs its own anchors. Worth it if you are running reviews that feed promotion and pay decisions.

Two rules whichever you pick. Avoid an even number of points if you want people to be able to say "meets expectations" — forcing a choice either side of the middle produces noise rather than decisiveness. And do not change the scale between cycles unless you are prepared to lose the comparison.

{{banner-3="/banner-page"}}

Six employee review form templates

Copy these into whatever you already use. Each one is a complete form, not an outline.

1. Quarterly review form — the short one

Fifteen minutes to complete, for companies running reviews four times a year.

• Period covered, employee, manager.
• Goals set last quarter: each one, and whether it was met, partly met, or not met, with one line of why.
• Overall performance against expectations this quarter (five-point scale) plus two lines of evidence.
• One thing that went particularly well, with the specific instance.
• One thing to work on next quarter, with what support is needed.
• Three goals for next quarter, each with a measure and a date.
• Employee comment.

2. Annual review form — the full one

The formal record. Rate each competency separately with a comment box under each, rather than giving one overall score.

• Identification, period, and the role expectations being measured against.
• Quality of work — rating plus evidence.
• Productivity and delivery — rating plus evidence.
• Collaboration and communication — rating plus evidence.
• Initiative and ownership — rating plus evidence.
• Role-specific competencies, two or three, taken from the career framework.
• Goal outcomes for the year, one line each.
• Strengths, two or three with examples.
• Development areas, two or three with examples and a proposed action.
• Overall rating, and how it was reached.
• Goals and development plan for next year.
• Manager signature, employee signature, date, employee comment box.

3. Employee evaluation form — the scored competency version

Where an employee evaluation form differs from a general review form, this is usually how: a competency matrix scored line by line, with a weighted total. It suits roles with a written framework and companies that need ratings comparable across teams.

• Identification and period.
• Each competency listed as a row, with the level definition for this role written beside it.
• Score per competency on your defined scale, and a weighting if some matter more for the role.
• Evidence box per competency — mandatory, not optional.
• Self-evaluation score per competency, completed first and shown alongside the manager's.
• Calculated total, plus a statement of what the total means for this role.
• Gap analysis: which competencies sit below the level expected, and the plan for each.
• Calibration note: whether this score was reviewed against peers in the same role, and by whom.

The last line is what makes a scored form worth the extra work. Without calibration, a weighted total just makes an inconsistent judgement look precise. This guide to performance calibration covers how to compare ratings across managers.

4. Self-evaluation form

Given to the employee first, before the manager writes anything. Keep it short or you will get generic answers.

• What are you most proud of from this period, and why?
• Which of your goals did you meet, and which did you not? What got in the way?
• What part of your job do you find hardest, and what would help?
• What do you want to be better at in six months?
• What should your manager do differently to help you?
• Is there anything about this period you think your manager does not know about?

That last question earns its place more often than the rest combined.

5. 90-day review form for new hires

Short, and focused on whether the hire and the company are working out rather than on rating performance nobody has had time to demonstrate. There is a fuller version in the 90 day review template.

• Was the role as described? If not, how does it differ?
• Which parts of onboarding helped, and which were missing?
• What has the new hire delivered so far?
• What do they still need access to, training in, or clarity on?
• Manager assessment against the 30/60/90 plan set on day one.
• Confirmation of the outcome: continue, extend the probation period, or end it — with the reason written down.

6. Peer review form

Three questions per reviewer is the practical limit. More than that and the quality of the answers falls off, especially when one person is reviewing several colleagues. For a structured multi-rater version, see the 360 review template.

• What does this person do well that the team relies on? Give an example.
• What one thing would make working with them easier? Give an example.
• Where have you seen them grow since the last cycle?

Performance appraisal form: when you need the formal version

An employee appraisal form is a review form built to survive scrutiny — a promotion committee, a pay decision, or a dispute. The content is the same; the difference is rigour in three places.

• Every rating carries written evidence. No blank comment boxes, no exceptions. An unsupported rating is the first thing anyone reviewing the decision will attack.
• The standard is stated on the form. Not referenced elsewhere. Whoever reads it in two years should not have to go looking for what "meets expectations" meant for this role in this period.
• Calibration is recorded. Who reviewed the rating against peers, when, and whether it changed.

If the appraisal is going to support a pay or promotion decision, keep the pay conversation on a separate document and at a separate time. Merging them means the employee hears only the number, and the development half of the conversation is wasted.

How to fill one in without wasting the hour

1. Read the self-assessment before you rate anything. It will change at least one of your scores, and finding that out before the meeting is better than during it.
2. Collect evidence across the whole period, not the last month. Recency bias is the most reliable distortion in performance reviews. If you have no notes from months one to four, say so rather than guessing.
3. Write the evidence first, then pick the rating. Choosing the number first and justifying it afterwards produces a paragraph that argues rather than describes.
4. Name the behaviour, not the person. "The spec was missing the error cases, which cost a week" is actionable. "Careless" is a character judgement and will be heard as one.
5. Send the completed form before the meeting. Reading and reacting at the same time produces a defensive conversation. Twenty-four hours is enough.
6. Spend the meeting on next period, not last one. The form already documents the past. The conversation's job is what changes.

Adapting the form to the role

One form across every role is the most common shortcut and it produces the vaguest reviews. You do not need a separate form per job — you need the same structure with two or three rows that change.

• Keep constant: identification, period, expectations, scale, self-assessment, strengths and development areas, goals, signatures.
• Swap per role family: the competency rows. An engineer's rows might be code quality, system design and review turnaround; a salesperson's might be pipeline hygiene, discovery quality and forecast accuracy; a support agent's might be first-contact resolution, tone and escalation judgement.
• Swap per level: what each scale point means. "Meets expectations" for someone two years in is not the same behaviour as for someone eight years in, and if the form does not say so the rating drifts upward with tenure rather than with capability.

Write the role-specific rows once with the manager who runs that team, not centrally in HR. They will be more accurate and the manager will use them.

What to write in each box

The most common reason a completed form is useless is not the structure, it is the writing. Four patterns to apply.

Evidence before judgement

Start the sentence with what happened, then what it meant. "The migration ran two weeks late because the data audit was skipped, which pushed the customer deadline" tells you more than "planning needs improvement" and cannot be argued with the same way.

One instance is enough, but you need one

You are not building a case file. One specific example per point is the difference between a rating a person accepts and one they dispute. If you cannot find a single instance, the point is probably an impression rather than an observation, and it should not be on the form.

Say what better looks like

Every development point needs a next action, and it should be something the person could start on Monday. "Be more proactive" is not one. "Post a written update on the migration every Friday so the support team is not finding out from customers" is.

Write the same way about strengths

Strengths get the vaguest writing on most forms, which wastes the easiest part of the conversation. "Good team player" tells someone nothing they can repeat deliberately. "You unblocked two people on the API change without being asked, which is why it shipped on time" does.

Mistakes that make a review form useless

• One comment box at the end. Produces one paragraph and no evidence per rating.
• Ratings with no written level definitions. The scale then measures the manager, not the employee.
• A form nobody can disagree with. No employee comment box means disagreement goes somewhere you cannot see it.
• Too many competencies. Fifteen rows gets fifteen thoughtless scores. Six gets six considered ones.
• Rating personality traits. "Attitude" and "professionalism" cannot be evidenced and should not be scored.
• Copying the same form across every role. A form that fits an engineer and a salesperson equally well fits neither.
• No goals section, or goals with no measure. The review documents the past and changes nothing.
• Changing the form every cycle. You lose the comparison, which is most of the value in year two.

Legal and documentation basics

A completed review form is a record, and in a dispute it is often the main one. Three practical habits, which are not a substitute for advice from an employment lawyer in your jurisdiction — the rules on what you must document, how long you keep it, and what an employee can demand to see vary by country and by state, so get a professional to check your process before you rely on it.

• Write only what you could show the employee. Assume they will read every word, because they can.
• Keep the standard and the evidence on the same document as the rating, so the decision can be understood without context you no longer have.
• Record performance concerns when they happen rather than saving them for the annual form. A first-time concern raised in a review that triggers a consequence is difficult to defend.

Paper, spreadsheet, Google Forms, or software

A document template is the right answer below about twenty people. It costs nothing and you will change the form twice before you settle.

Spreadsheets and google form evaluation template setups are the common next step and they work, with two limits: collecting self-assessments and peer input means chasing people manually, and nothing carries forward, so each cycle starts from a blank file and last year's ratings are in a different document.

Dedicated performance appraisal software is worth it when the chasing becomes the job — usually somewhere between 30 and 80 people — or when you want this year's rating next to last year's without assembling it by hand. The other trigger is calibration: comparing ratings across managers is painful in a spreadsheet and straightforward in a tool.

If you want the full cycle rather than just the form, the performance review template covers the process around it.

Conclusion

Take the quarterly form above, add a comment box under every rating, and write a one-line definition of each level for the roles you are reviewing. That gets you most of the way, and it takes an afternoon.

Then leave it alone for a year. The comparison between this cycle and the next is worth more than any improvement you make to the form in between.

Effy AI builds the review forms, collects self-assessments and peer input in Slack, and keeps each cycle next to the last for teams without an HR operations function, with small business performance management for companies setting up their first cycle.

{{banner-7="/banner-page"}}