Exceeds expectations
- Summarises client calls in writing the same day, so the team never works from memory or guesses.
- Explains a delayed shipment to an anxious customer in plain words, and the complaint closes without escalation.
- Runs the daily stand-up in under ten minutes, yet every person leaves knowing exactly what to do.
- Rephrases a tricky policy for shop-floor staff in Hindi and English, so nobody misreads the rule.
- Raises a risk to the reporting manager early, with the facts and two options, not just the problem.
- Writes handover notes before every leave, so the stand-in picks up the desk without a single follow-up call.
- Listens fully in review meetings, repeats back the ask to confirm, then delivers exactly what was agreed.
- Keeps three branch teams aligned on one WhatsApp thread, trimming long chains into short, dated updates.
Meets expectations
- Replies to internal emails within a working day and flags anything that needs more time.
- Shares project status in the weekly meeting clearly enough that the manager rarely asks for more.
- Uses simple language with customers and checks that they have understood before ending the call.
- Keeps the reporting manager informed of blockers rather than letting them surface at the deadline.
- Documents meeting decisions in the shared notes so the team can refer back later.
- Speaks up in team discussions with points that stay on the topic being decided.
- Answers colleague questions patiently and points them to the right person when unsure.
- Sends clear joining instructions to new hires, covering timing, documents and reporting desk.
Needs improvement
- Often shares updates only when asked, so the manager learns of delays late in the week.
- Long messages bury the main ask, and readers miss the deadline sitting in the last line.
- Tends to go quiet in meetings, then raises concerns privately after the decision is made.
- Could confirm understanding at the end of a call, as repeat queries suggest the message did not land.
- Sometimes replies to customers in a hurry, leaving the actual question half answered.
- Passes on instructions by word of mouth, so details change by the time they reach the last person.
- Would benefit from writing short handover notes before leave, to save the team follow-up calls.
- Interrupts colleagues before they finish, which makes quieter team members hold back their input.
Self-review phrases
- I now send a written recap after every client call, and repeat queries have dropped noticeably.
- I am learning to keep my emails to three short lines with the ask at the top.
- I want to speak up earlier in reviews instead of raising doubts after the decision.
- I check understanding before ending a support call, and fewer customers ring back the same day.
Tips for writing this feedback
- Judge communication by outcomes, not volume: did the listener act correctly, was the deadline met, did the query close without a second round?
- Give one concrete example per point. 'Unclear in meetings' helps nobody; name the meeting and what went missing.
- Separate the medium from the message. Someone strong on calls may still write muddled emails, so rate each channel.
- Watch for language and hierarchy. A team member may stay quiet with seniors present, not because they lack ideas.
- Balance speaking and listening. Note whether the person hears feedback and confirms it, not only how well they present.
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
What are good communication review phrases?
Good communication phrases describe a specific behaviour and its effect on work. Instead of 'communicates well', write what the person did and what changed, such as sending a written recap after each client call so the team stops working from memory. Keep each phrase to one observable action.
How do I write feedback for a quiet team member?
Focus on contribution, not personality. Note where their input reached the team, such as detailed handover notes or clear written updates, and where it did not, such as staying silent until after a decision. Suggest a concrete step, like sharing one point early in each review, rather than telling them to speak more.
Should communication be rated separately from teamwork?
Yes. A person can write clear reports yet struggle to listen in a group, or be a warm team player whose emails confuse readers. Rate communication on how clearly information moves to and from the person, and rate teamwork on how they work with others toward a shared goal.