Exceeds expectations
- Delivers reports that need no correction, with figures that tie back to the source every time.
- Catches own errors before submission, so work reaches the manager already checked.
- Sets a standard the juniors copy, from clean file naming to careful cross-checks.
- Handles the tricky cases with the same care as routine ones, not just the easy volume.
- Builds a small check into each task, so the same mistake does not slip through twice.
- Produces client-ready output first time, sparing reviewers a second and third round.
- Keeps quality steady under deadline pressure rather than trading accuracy for speed.
- Documents work clearly enough that anyone can pick it up without a walkthrough.
Meets expectations
- Produces accurate work that meets the standard with only minor, occasional corrections.
- Follows the checklist and format the team has agreed for the task.
- Checks own work before handing it over rather than relying on the reviewer.
- Keeps error rates low across a normal month's volume.
- Fixes feedback fully the first time rather than leaving the reviewer to re-flag it.
- Maintains quality on routine tasks even when the work is repetitive.
- Asks when a requirement is unclear instead of guessing and reworking later.
- Keeps files and records organised so work can be traced and reused.
Needs improvement
- Delivers fast but leaves small errors that the reviewer has to catch each time.
- Skips the self-check, so avoidable mistakes reach the manager.
- Quality drops under deadline pressure, with accuracy traded for speed.
- Handles routine cases well but is careless on the tricky ones that need most care.
- Repeats the same mistake across tasks rather than building a check to stop it.
- Fixes only the flagged error and misses similar ones nearby in the same file.
- Leaves work poorly documented, so others need a walkthrough to use it.
- Guesses at unclear requirements instead of asking, which leads to rework.
Self-review phrases
- I built a short self-check into each report, and corrections from my manager have dropped.
- I now hold my accuracy steady under deadline instead of trading it for speed.
- I want to give the tricky cases the same care as the routine ones.
- I ask when a requirement is unclear rather than guessing and reworking later.
- I fixed the file naming so juniors can find and reuse my work.
Tips for writing this feedback
- Judge quality on error rate and rework, not neatness alone. How often did the work come back, and why?
- Look at the hard cases. Anyone can be accurate on easy volume; care on tricky work is the real signal.
- Check whether mistakes recur. A person who builds a check to stop a repeat error is improving quality, not just fixing it.
- Weigh quality against speed fairly. Note whether accuracy holds under deadline, where the trade-off usually shows.
- Give a specific example of both strong and weak work, so the standard you mean is clear to the person.
Track goals and review cycles for every employee in ZeniaHR.
See it on your own data
A 30-minute demo on a video call. We set up your departments, shifts and leave rules and show attendance, leave and payroll running for your team. Free for your first 50 employees.
Book a free demoSee pricingFrequently asked questions
How do you measure quality of work in a review?
Measure it by accuracy and rework rather than appearance: how often work came back for correction, whether errors repeated, and whether the person self-checked before handing over. Pay special attention to difficult cases, since care there is a stronger signal than accuracy on easy, high-volume tasks. Use specific examples of both strong and weak output.
How do I address someone fast but careless?
Acknowledge the speed, then show its cost in rework and reviewer time. Point to specific errors that a self-check would have caught, and note if quality drops under deadline. Ask for one concrete habit, such as a short check built into each task, and agree how you will look at error rate next cycle.
Should quality and productivity be rated separately?
Yes. Productivity is about how much gets done; quality is about how well. A person can produce high volume riddled with errors, or flawless work at a slow pace. Rating them separately keeps the picture honest and stops fast, sloppy output from hiding behind numbers, or careful slow work from looking like underperformance.