An Employee Performance Review Template for Small Businesses
A practical worksheet for a retrospective review period — role expectations, specific evidence, employee reflection, manager support, development goals, and agreed actions. Includes a blank template and a worked example you can adapt.
Employee Performance Review Template for Small Businesses
HR Co-Pilot Resource • Reviewed: October 17, 2026 • A review conversation worksheet, not a rating, disciplinary, or legal process.
What a performance review is — and what it isn't
A performance review is a structured conversation that looks back over a defined period of work — a quarter or a year — and measures it against the role expectations and goals agreed at the start. It brings together specific evidence, the employee's own reflection, the context that shaped the work, and a plan for what comes next.
A good review is a two-way conversation, not a verdict. It works best when both people prepare, when the discussion stays tied to real examples, and when it ends with agreed actions and a follow-up date. Choose a review schedule that fits the role and your organization, and check any applicable agreements or requirements before setting it. This template does not set a mandatory review frequency or record-retention period.
This is a static public resource, not an app feature. There are no data-entry fields, no storage, and no tracking. You can select the worksheet text on screen and copy it, or use your browser print options. It does not calculate ratings, run appraisals, or make employment decisions, and it is not a performance improvement plan, disciplinary, or termination process.
- 1.Start with the role expectations and period goals.
- 2.Gather specific evidence before the conversation.
- 3.Copy the blank worksheet into your own document.
- 4.Agree on actions, owners, and a follow-up date.
For broader management context, the U.S. Office of Personnel Management describes a performance management cycle built around employee involvement in setting goals, ongoing feedback, and development. That guidance is written for the federal workforce — it is federal workforce management guidance, not a private-employer mandate — but the principles of involving employees in goals, giving ongoing feedback, and supporting development are useful for any team. State and local requirements vary where relevant; this template is general information, not legal advice.
Source: OPM Performance Management CycleBuild your own review
Work through these sections together. The text below is selectable — copy it into your own document. There are no input fields and nothing is stored. Adapt the sections to your role and company context.
Review basics
Identify the review period, the people involved, and the role being reviewed.
Employee name
[Employee name]
The person being reviewed.
Role / title
[Role or job title]
The role expectations this review is measured against.
Reviewer
[Manager or reviewer name]
The person leading the review.
Review period
[Start date – end date]
The window of work this review covers.
Review date
[YYYY-MM-DD]
When the review conversation happens.
Role expectations
Restate the expectations for the role so the review is measured against them.
Core responsibilities
[The main duties the role is accountable for]
What the role is expected to do day to day.
Goals for this period
[Goals agreed at the start of the period]
The specific outcomes the employee and manager agreed on.
How success was defined
[What 'meeting' and 'exceeding' looked like for each goal]
The standard the work is measured against.
Evidence & accomplishments
Capture specific, observable work from the period — not impressions.
Key accomplishments
[Specific work delivered this period]
Concrete outputs, projects, or milestones reached.
Evidence / examples
[Where to see the work — deliverables, metrics, feedback]
Point to real examples rather than general statements.
Goals met
[Which period goals were met, and how]
Map accomplishments back to the agreed goals.
Goals not yet met
[Which goals are incomplete, and why]
Be honest about gaps and the reasons behind them.
Employee reflection
Let the employee share their own view of the period first.
What went well
[What the employee is proud of this period]
The employee's own view of their strengths.
What was hard
[Obstacles, context, or blockers the employee faced]
Challenges and the circumstances around them.
What they want next
[What the employee wants to learn or take on]
Growth, stretch work, or new responsibilities.
Challenges & context
Note anything that affected the work so the review is fair.
Context that affected the work
[Changes in scope, team, tools, or priorities this period]
Factors outside the employee's control that shaped outcomes.
Support needed
[What would help the employee do their best work]
Resources, clarity, or access the employee is asking for.
Manager support
Record what the manager will do to help the employee succeed.
What the manager will provide
[Support, resources, or access the manager commits to]
Concrete help the manager owns.
Feedback to the employee
[Specific, forward-looking feedback tied to behavior]
Keep it concrete and tied to the work, not a score.
Feedback from the employee
[What the employee needs more or less of from the manager]
Two-way feedback, captured honestly.
Development goals
Agree on what the employee will grow toward next.
Next-period goals
[Goals for the upcoming review period]
Specific outcomes to work toward.
Skills to grow
[Skills or areas the employee wants to develop]
Where the employee wants to stretch.
How progress will be seen
[What will show that growth is happening]
The evidence both people will look for.
Agreed actions & follow-up
Close the loop with specific owners and a check-in date.
Actions agreed
[Each action from this review]
Every decision written down.
Owner
[Who owns each action]
One accountable owner per action.
Follow-up date
[When to check on progress]
A date to revisit these actions.
Notes reviewed / acknowledgment (optional)
[Names of who reviewed the notes and any corrections or differing views]
Record who reviewed the notes and any corrections or differing views; acknowledgment need not imply agreement.
A worked example for a fictional customer support specialist
This is a made-up example to show how the sections fit together — it is not a real customer or a case study, and it contains no ratings or performance verdict. Adapt it to your own role and context.
Review basics
Employee name
Fictional employee — customer support specialist
Role / title
Customer Support Specialist
Reviewer
Support Team Lead
Review period
April 1 – September 30, 2026
Review date
2026-10-17
Role expectations
Core responsibilities
Respond to customer tickets, maintain the help-center articles, and escalate product bugs to engineering.
Goals for this period
Reduce average first-response time, publish five new help-center articles, and complete the advanced product training.
How success was defined
First-response time under the team target, five articles live and reviewed, and training marked complete.
Evidence & accomplishments
Key accomplishments
Published six help-center articles (one above goal), completed advanced product training, and took on weekly ticket-triage rotation.
Evidence / examples
Article links in the knowledge base, training certificate on file, and triage log showing consistent weekly coverage.
Goals met
Help-center articles and training goals met.
Goals not yet met
First-response time improved but stayed above target during a two-week staffing gap; not yet consistently under target.
Employee reflection
What went well
Employee felt the help-center work was their most satisfying contribution this period.
What was hard
The staffing gap pushed response times up and felt outside their control; they asked for clearer coverage handoffs.
What they want next
Employee wants to start co-owning the help-center content calendar.
Challenges & context
Context that affected the work
Two teammates were out for part of the period, which increased ticket volume per person.
Support needed
A documented coverage handoff process and a backup for triage rotation.
Manager support
What the manager will provide
Draft a coverage handoff checklist with the team and add a named triage backup before the next period.
Feedback to the employee
Manager appreciated the employee stepping into triage during the gap and the quality of the help-center articles.
Feedback from the employee
Employee asked for earlier notice when coverage changes so they can plan their week.
Development goals
Next-period goals
Bring first-response time consistently under target with the new coverage process, and co-own the help-center content calendar.
Skills to grow
Content planning and prioritizing tickets during high-volume stretches.
How progress will be seen
Weekly response-time reports and a monthly content calendar the employee drafts.
Agreed actions & follow-up
Actions agreed
Manager drafts the coverage handoff checklist; employee drafts the first content calendar; both review response time weekly.
Owner
Manager — coverage checklist. Employee — content calendar. Both — weekly response-time review.
Follow-up date
2026-11-17 — review coverage process and first calendar draft.
Notes reviewed / acknowledgment (optional)
Notes reviewed on 2026-10-17 by the employee and the Support Team Lead; no corrections requested.
In this fictional example, the review captured concrete evidence (articles published, training completed, response-time trends), noted context outside the employee's control (a staffing gap), and ended with agreed actions and owners. No performance rating was assigned.
How to prepare for a useful review
A review is only as useful as the preparation behind it. These steps help both people come ready.
Before the review, write down the core responsibilities and the goals agreed at the start of the period. The review measures the work against those expectations — not against a vague sense of how the year went.
Collect concrete examples from the period: deliverables, metrics, and feedback from others. Specific evidence makes the conversation fairer and more useful than impressions alone.
Ask the employee to share their own view of the period before the meeting. Their reflection often surfaces context and goals the manager would otherwise miss.
A review works best as a two-way discussion about the work, the support behind it, and what comes next. It is not a disciplinary decision, a performance improvement plan, or a termination process.
End with specific actions, an owner for each, and a date to check back. A review without follow-through tends to fade between cycles.
This template is for routine performance conversations. It is not a performance improvement plan, disciplinary process, or termination decision. Route those concerns through your company's applicable process and, where appropriate, qualified counsel. This guidance is general information, not legal advice.
The AI HR assistant can help you talk through review questions and draft a starting worksheet using your company context, and the document generator can help draft related manager materials. You and the employee still lead the conversation and decide what to include. HR Co-Pilot does not automatically generate ratings, run appraisals, or make employment decisions.
Related resources
Pair reviews with recurring one-on-ones and new-hire planning.
Performance review questions
Common questions about using this template. Have a software question? Talk to our team.
HR clarity to your team today.
Get your HR tools and resources backed by industry-standard practices and procedures, supercharged by AI.