Skip to the main content.
Talk to an expert
Talk to an expert
Featured Offer
Ambitious 50 →
6 months of Hire and Engage free for businesses under 50 people.

Hey Compono!

A coach that actually gets you.

Get 10 minutes free, then $15 a month. Cancel anytime.

Get Started ≫
Free tools for HR leaders

Organisation
and planning performance review phrases

24 phrases across four rating bands, for managers, coaching conversations and self-evaluations. Filter, copy, print. Free, no sign-up.

Start with the rating band that matches the person, then pick the voice you are writing in. Copy a phrase, then change the specifics so it names the real project, the real quarter, the real thing that happened. A comment that could describe anyone is the thing you were trying to avoid.

How these were written, and the five steps to a review that holds up ↓
Rating:
Voice:
24 showing
Exceeds expectations

Plans that survive contact with reality, because the risks were named before they arrived.

Manager to employee

Sequenced [work] so the dependencies were cleared before anybody was blocked by them.

Manager to employee

Their plan is the one other people work from, without being asked to produce it.

Manager to employee

Worth having them plan across teams rather than within one. The dependencies between teams are where plans usually fail.

Coaching

Ready to own planning for a whole programme rather than a workstream.

Coaching

I mapped the dependencies on [work] before starting, which caught two that would have blocked us in the second month.

Self-evaluation
Meets expectations

Plans work realistically and adjusts when things change.

Manager to employee

Keeps their own priorities in order without needing them managed.

Manager to employee

Anticipates the obvious risks rather than only reacting to them.

Manager to employee

Plans their own work well. The next step is planning around other people, whose timelines you do not control.

Coaching

Worth writing down what could go wrong before you start. Ten minutes there saves most of the surprises.

Coaching

I started listing what could go wrong before each project rather than after, which has made the replanning much smaller.

Self-evaluation
Needs development

Work is planned in the order it arrived rather than the order it is needed.

Manager to employee

Dependencies on other people are identified once they have already caused a delay.

Manager to employee

Plans do not survive the first change, because there was no room in them.

Manager to employee

Before starting, write the three things that would stop this. Most of them can be cleared in advance for very little effort.

Coaching

Build slack into the plan deliberately. A plan with no room is a forecast of the best possible week.

Coaching

I plan in the order work arrives rather than what it depends on, and I discover the dependencies late.

Self-evaluation

My plans assume nothing goes wrong, which has not been true yet.

Self-evaluation
Unsatisfactory

Work has repeatedly been delivered late because dependencies were not identified, after this was raised in [month].

Manager to employee

No workable plan has been produced for [work] despite it being requested.

Manager to employee

For the next piece of work I need a written plan before it starts: sequence, dependencies, risks, dates. Reviewed in six weeks.

Coaching

If the work changes too fast for planning to be worth it, say so, because that is a real answer and it changes what I ask for.

Coaching

I have not planned work properly and it has cost other people time. I want an agreed planning step before work starts.

Self-evaluation
No phrases match those two filters together. Clear one of them.
How do you write about planning in a performance review?

Check whether the plan survived. A plan that assumed nothing would go wrong was a forecast of the best possible week.

How these were written

Written, not calculated. Each phrase names a situation, an observable behaviour and its effect on the work or the people around it. Bands run from exceeds expectations to unsatisfactory across three voices: a manager writing about somebody, a manager coaching, and a person writing their own self-evaluation.

Assumptions
  • Phrases are starting points. Drop in the real situation or the comment reads as filler.
  • The four bands assume a four-point scale. On a three or five-point cycle the band is a sorting device, not a score.
  • Written for Australian workplaces and Australian English.
  • Check the constraint before rating the person. Workload, authority, tooling and what happened to the last person who tried shape most of what gets written up as an individual failing.
  • Unsatisfactory-band comments assume a dated record already exists and the issue has been raised before.
Sources

What to do about it

Good phrasing rescues a review that was already done properly. It cannot rescue one where nobody wrote anything down until the week it was due.

1

Start from your notes, not from this list

Open what you recorded during the year, pick what really happened, then find the wording. The other order produces a fluent review that says nothing.

2

Name the situation in every comment

The real project, the real quarter, the real result. Only one person could have earned it.

3

Match the band to your evidence, not the conversation you want

A generous rating on somebody you privately consider a problem is how next year's difficult conversation ends up looking like it came from nowhere.

4

Pair every development comment with a support step

Training, a pilot, a pairing, a cadence. Criticism without a path forward produces defensiveness and reads badly to anyone reviewing the file later.

5
Where a tool helps

Read your reviews as a set

If the same competency is the gap across a function, that is a capability gap in how the team was built rather than a dozen development plans.

A plan with no room
is a forecast.

Compono Develop maps capability against what a role requires, so weak planning reads as a specific, teachable gap rather than a general complaint about organisation.

Step 5 asks what your reviews say together. That is very hard to answer from a folder of review documents and straightforward to answer from capability data.

See how it works
Compono Develop
4.7/5
rating across millions of learners

Common questions

What are examples of planning feedback?

Sequencing work so dependencies clear before anybody is blocked, naming the three things that could stop it, building slack in deliberately.

How do you help someone plan better?

Ask for the risks in writing before work starts. Ten minutes there prevents most of the replanning later.

Can I use these phrases word for word?

Yes, with the real work and dependencies named.

These phrases are starting points, not finished comments. Change the specifics so each one is true of the actual person and the actual situation, because a comment that could describe anyone is the thing you were trying to avoid. Review comments can later be read as evidence in an employment matter, so anything you take from the unsatisfactory band should match a dated record you already hold. Last reviewed July 2026.

Next step

HR Glossary

Competency framework

The bands above are competency ratings. This is what a competency framework is, and how the levels are meant to work.

Read the definition →Related tool

Headcount planning calculator

Reviews name the gap one person at a time. This one sizes it across the team.

Run it next →Buying

Requirements builder

Score the platforms you are looking at against the two risks, must-haves first.

Build the scorecard →Talk to us

Bring us your review cycle

A conversation about what your reviews are telling you as a set, not a demo script.

Talk to us →