Exceeds expectations
- Writes an email where the ask and the deadline sit in the first line, so nothing is missed.
- Turns a messy incident into a clear, dated note that anyone can act on without a call.
- Documents a process step by step, so a new joiner runs it without asking the author.
- Summarises a long thread into three decisions and their owners, ending the confusion.
- Writes to the reader, plain for a customer and precise for the finance team, without a wasted line.
- Keeps records so clear that a dispute months later is settled by reading the trail.
- Drafts a policy note in plain language, so shop-floor staff read it once and follow it.
- Proofs own writing, so messages go out without the typos that cause a second round.
Meets expectations
- Writes clear emails that state the point without a long wind-up.
- Keeps messages brief and to the point rather than rambling.
- Uses correct, simple language that the intended reader understands.
- Structures a report so the reader can find each part easily.
- Records decisions in writing so the team can refer back.
- Replies to written queries with a complete answer, not a partial one.
- Matches the tone to the reader, formal or friendly as needed.
- Checks a message for errors before sending it out.
Needs improvement
- Buries the main ask at the end of a long email, so readers miss it.
- Writes messages so brief that the reader has to ask for the missing detail.
- Sends unproofed notes with typos that cause a second round of questions.
- Documents work loosely, so others cannot follow it without a call.
- Uses jargon a customer will not understand in a customer-facing note.
- Leaves decisions only in conversation, so there is no record to refer back to.
- Writes long, rambling reports where the point is hard to find.
- Replies to only part of a written query, so a follow-up is always needed.
Self-review phrases
- I put the ask and the deadline in the first line of an email now.
- I summarise long threads into decisions and owners to end the confusion.
- I want to proof messages before sending so typos stop causing a second round.
- I document processes step by step so a new joiner can run them without me.
Tips for writing this feedback
- Judge written communication by whether the reader acted correctly from the message, not by length or vocabulary.
- Look for the ask up front, since a request buried at the end of a long email is often missed.
- Value clear documentation, because a process only in one person's head is a risk to the team.
- Separate written from verbal communication; a strong speaker may still write muddled emails, so rate each.
- Check tone for the reader, since the same facts need different wording for a customer and the finance team.
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 strong written communication review phrases?
Strong phrases show the reader acting correctly from the writing: an email with the ask and deadline in the first line, a messy incident turned into a clear dated note, or a long thread summarised into decisions and owners. They cover clarity, structure and records, not length or vocabulary. Avoid vague lines like writes well with no example.
How is written communication different from general communication?
Written communication is one channel: emails, reports, notes and documentation. General communication also covers speaking, listening and day-to-day updates. A person can present and talk well one to one yet write muddled emails, or write clearly while struggling in a live discussion. Rate the channel the role relies on most, and note where the two differ.
How do you give feedback on unclear writing?
Use a specific message and show the effect: an ask missed because it sat at the end, or a follow-up needed because the query was half answered. Suggest one concrete habit, such as leading with the request and deadline, or proofing before sending. Documentation gaps deserve their own note, since a process only in someone's head is a real risk.