Quantity of work performance review phrases
Volume is the easiest area to make objective, so the best phrases come with the target and the actual number. Below are 33 phrases sorted by rating, with self-evaluation versions, goals and a sample review you can adapt.
Lauren is a real coach. You're texting an AI trained on her coaching.
What good quantity of work looks like
Quantity of work is about output: how much someone gets done compared with what the role expects, and whether volume holds up without quality dropping. Reviewers look at throughput against targets and how the person handles a heavy load.
- Hits or beats volume targets
- Keeps output steady through busy periods
- Takes on more without dropping quality
- Says what they can take before taking it
- Finds ways to do more in the same time
Exceeds expectations
For work that sets the standard. Add the specific result after each phrase; that's what makes it believable.
- Consistently exceeds output targets; closed [number] [cases] this period against a goal of [number].
- Took on [extra responsibility] mid-year with no drop in their core output.
- Kept output steady through [busy season], when volume rose [number]%.
- Automated [task], freeing about [hours] a week for the team.
- Handles a heavier load than peers in the same role while keeping quality high.
- Manages a full queue without letting older items stall.
- Volunteers for overflow work when the team is behind.
- Turns around [deliverable] faster than the team standard, with no rise in errors.
Meets expectations
For solid, reliable work. "Meets expectations" is a good rating, so say that out loud in the conversation too.
- Completes the expected volume of work for the role.
- Meets output targets consistently.
- Handles a normal workload without falling behind.
- Keeps up during busy periods with support from the team.
- Balances volume and quality appropriately.
- Completes assigned tasks within expected time frames.
- Keeps their queue current and flags backlogs early.
- Takes on additional work when they have capacity.
Needs improvement
Pair each one with a specific example and a goal. A needs-improvement line without a next step reads as a verdict.
- Has produced below target for [period]: [number] against a goal of [number].
- Falls behind during busy periods and doesn't flag it until deadlines are at risk.
- Spends significant time on low-priority tasks while the core queue builds up.
- Lets older items in the queue stall; working oldest first would help.
- Produces noticeably less when working without regular check-ins.
- Takes on new requests without saying what will slip, so commitments are missed.
- Repeats manual steps that could be templated, which slows output.
- Varies a lot in output from week to week, which makes it hard for the team to plan.
Self-evaluation: strengths
First-person versions for your own review. Swap in your real projects and numbers.
- I closed [number] [cases] this year, [number]% above target.
- I kept up with [busy season] volume without overtime by batching similar tasks.
- I built a template for [task] that cut my time per [unit] in half.
- I took on [extra area] in [quarter] and kept my core numbers on track.
- I cleared a backlog of [number] items that had been sitting since [month].
Self-evaluation: where you're growing
Name the gap and what you're doing about it. Reviewers trust a self-evaluation that includes one honest growth area.
- My output dipped in [period]. I'm going to flag capacity problems earlier instead of trying to catch up quietly.
- I spend too long on small items. I want to timebox them.
- I'd like to automate more of the repetitive parts of my work.
- I need to say what will slip when I take on new requests.
Quantity of work goals for next period
Goals work when someone else could tell whether they happened.
- Hit [number] [units] a month, with a weekly check of progress against the target.
- Automate or template [task] by [date] to free [hours] a week.
- Flag any week the queue grows past [number] items, with a plan to clear it.
A sample review paragraph
Behavior, example, impact, then one growth area with a goal. Replace the brackets with specifics from the review period.
[Name] meets their output targets consistently and kept up during [busy season] with help from the team. Their template for [task] saved time for everyone. One area to build on: in busy weeks, the queue grows before anyone hears about it. Next quarter, the goal is to flag any week the backlog passes [number] items, with a plan to clear it.
How to say it in the review meeting
Bring the numbers and the target, then ask why before you judge. Low output is often a sign of unclear priorities, broken tools or constant interruptions.
If someone is far above target, check that quality and their own wellbeing are holding up. A pace that burns someone out isn't a win for anyone.
Talk it through with Lauren
The written review is half the job. Here's what it looks like to get the hardest line right by text, the night before.
one of my reps is way under target but works really hard. I don't know how to write it
hard-working and under target usually means something's in the way. worth finding out what before the review
where does her time actually go? any guess?
she builds every proposal from scratch. hours each
there's your goal. "You're at [number] against a target of [number]. I think custom proposals are eating your week. Let's build two templates together by the end of the month." it's a fix, not a scolding
Get a second read before you send it.
Text Lauren the situation and your draft. She'll help you make it specific and fair, and prep you for the conversation itself.
Hi Lauren! I'm writing a performance review and want help with the quantity of work section.
Lauren is a real coach. You're texting an AI trained on her coaching. Your first week is free. Cancel anytime from your account or by texting Lauren.
Frequently asked questions
How do you write about quantity of work fairly?
Compare against the role's target and the person's own trend, not the fastest person on the team. Note anything that affected volume, like a new system or a leave of absence.
What if someone has high output but lower quality?
Cover both in the same review: credit the volume, name the quality issue with an example, and set a goal that protects quality, such as a final check before handoff.
How do I talk about my workload in a self-evaluation?
Give your numbers against target, then explain what drove them. If you took on extra work, say what it was and what it cost, so your manager sees the full picture.