Praise as padding
A compliment used only to soften criticism is spotted quickly, and the reader starts discounting your praise. Say what worked because it worked, and be as specific about it as about the problems.
Let’s write an email!
Type a few lines about what you need to say, or paste your notes. Replying to someone? Open Details above and paste their email.
Feedback by email has a disadvantage compared with a conversation: the reader cannot ask what you meant, and they cannot see your face while reading the difficult part. So written feedback has to be more specific than spoken feedback, not less. Every point should say where the issue is, what effect it has, and what would fix it.
That applies to praise as much as criticism. Great job tells the person you were pleased but not what to repeat. The regional breakdown is exactly what the board asked for tells them which choice was right. Specific praise is useful information; vague praise is a pleasantry that makes the criticism that follows feel like the real message.
Describe the work, what worked, what did not and why, and what you want changed by when. From that the email writer produces the note itself plus three subject options, in whichever tone and length you pick. It works from your points, so if your notes are vague the email will be too; name the page, the slide or the figure in your brief.
Say what you reviewed, then name one thing that worked and why. For each problem, point to where it is, describe the effect on the reader or the result, and suggest what to do instead. Keep to about three points. End with a deadline if there is one and an offer to talk it through, since written criticism can land harder than you intend.
A real run of the Email Writer with the Feedback purpose, printed unedited.
Give feedback to a junior colleague on their first draft of the Q3 sales report. The charts are clear and the regional breakdown is exactly what the board asked for. But the executive summary is two pages and the recommendation only appears on page three; and three figures in the summary do not match the appendix table. Ask for a half-page summary with the recommendation first, and the figures reconciled, by Wednesday. Offer to go through it together.
Purpose Feedback, tone Professional, standard length. No recipient or sender name was given in Details, so the greeting and sign-off are the tool's defaults.
Thank you for submitting the first draft of the Q3 sales report. The charts are clear and the regional breakdown matches the board’s request, which provides a solid foundation.
The executive summary, however, extends to two pages and places the recommendation only on page three, making it harder for executives to locate the key takeaway. Additionally, three figures cited in the summary do not align with the data in the appendix table, which could cause confusion.
Please revise the summary to a half‑page, position the recommendation at the beginning, and reconcile the mismatched figures. I would appreciate having the updated version by Wednesday. Let me know a convenient time, and we can review the changes together.
Best regards
Generated by the Email Writer on 18 September 2026 and printed here unedited. Every date, name and number came from the brief; a draft is meant to be read and edited before it is sent. The draft has no greeting because the brief gave no name; adding the colleague's name in Details puts one in.
The Center for Creative Leadership's Situation-Behavior-Impact model is one of the most widely used frames for feedback: describe the specific situation, the observable behaviour, and its impact, without judging the person. CCL says the approach reduces the anxiety of the giver and the defensiveness of the receiver. It translates well to email, where the situation is usually a piece of work.
| Element | In a work email | Example |
|---|---|---|
| Situation | The document, meeting or task, precisely | In the executive summary of the Q3 report draft |
| Behaviour | What is actually there, observably | the recommendation first appears on page three |
| Impact | What that does to the reader or the result | so the board will read two pages before learning what we propose |
| Next step | The change you are asking for, with a date | Could you cut it to half a page, recommendation first, by Wednesday? |
CCL's extended version adds intent: asking what the person was trying to do. In an email that can be a genuine question, such as Were you keeping the detail up front for a reason? It invites a reply rather than compliance.
A draft usually has more problems than are worth mentioning. Pick the ones that most affect the outcome and rank them. Three is a practical ceiling for one email; more than that, and the person will fix the easy ones and miss the important one.
If there are many small issues of the same kind (typos, inconsistent headings, date formats), group them into a single point and offer a marked-up copy rather than listing each in the email.
If the work needs rebuilding rather than editing, say so plainly and suggest a conversation. Twelve separate notes on a draft that needs a different structure waste both people's time.
Most unhelpful feedback is not harsh; it is general. These rewrites show the difference that location and effect make.
| Vague | Specific and actionable |
|---|---|
| The intro is too long. | The first two paragraphs repeat the brief, so the new finding starts on page two. Could it start in line one? |
| Nice slides. | Slide 4 works well: one chart, one sentence, and the number the client cares about in large type. |
| The tone is off. | The reply to the customer says unfortunately three times, which reads as reluctance. One apology, then the refund date. |
| Needs more data. | The claim that churn fell has no figure. Add the before and after rates and the period. |
| Good effort. | The research is thorough; the problem is the order. Lead with the answer and put the method in an appendix. |
Professional suits most feedback between colleagues. Friendly helps with a junior colleague or someone new to the task, where the aim is to build confidence as well as fix the work. Empathetic is right when the feedback is hard to hear, for example on work someone has invested a lot in. Concise suits a colleague who asked for quick notes before a deadline.
Upward feedback, to your manager, reads best framed around a shared goal: The client may stop at slide 3 because the price is not until slide 9; would it help to move it? Feedback to a supplier can be more direct, since it is part of a commercial relationship, but the same rules of location and effect apply.
Avoid Confident and Persuasive. Feedback is an offer of information, and pressing it hard tends to produce defence rather than change.
Written feedback is good for specific, fixable points on a piece of work. It is poor for anything about behaviour, performance or relationships, where tone of voice and the chance to respond matter. If the feedback could affect someone's job, or if you would be uncomfortable reading it about yourself with no chance to reply, talk first and use the email to record what you agreed.
Timing matters too. Feedback sent late on a Friday about work due Monday lands badly whatever the wording. Send it when the person has time to act on it.
A compliment used only to soften criticism is spotted quickly, and the reader starts discounting your praise. Say what worked because it worked, and be as specific about it as about the problems.
The table is confusing is your reaction. The table has no units, so readers cannot tell thousands from millions is feedback. Add the consequence every time.
An email that lists issues but never says what to do next leaves the person guessing which to fix and by when. End with the change and the date.
Words like careless or sloppy describe character, not work. Point to the three figures that do not match and let the facts carry the message.
Start with something that genuinely worked, described as specifically as the problems, because it tells the person what to keep. Do not invent a positive to soften the rest; readers recognise the pattern and discount it. If little worked, begin with what the piece is trying to achieve instead.
Around three. Rank them by how much they affect the outcome and put the most important first. Group small repeated issues into a single point with a marked-up copy attached. If you have many substantial issues, the work probably needs a conversation rather than a list.
Writing works well for specific points on a document, slide deck or design, because the person can refer back to it. Behaviour, performance and anything sensitive are better discussed in person, with an email afterwards summarising what was agreed.
Keep it about the work and a shared goal, such as the client, the deadline or the team's workload. Be specific, suggest an alternative, and phrase it as an option rather than a correction. Professional tone and Short length usually suit. If it is about how they manage you, raise it in a conversation.
Name the piece of work and say it is feedback, for example Notes on the Q3 report draft or Feedback on Thursday's pitch deck. That tells the recipient what the email contains and lets them find it again when they sit down to revise.
It can help you phrase specific observations clearly, but a formal review usually follows your employer's process and forms, and often needs a meeting. Use it to draft individual points with situation, behaviour and effect, then put them into the format your organisation requires.
Written and checked by the AI Writing Assistant team. Last reviewed . Sources: Center for Creative Leadership: Closing the gap between intent and impact (SBI and SBII).
Each page opens the writer with that purpose already selected, shows a real draft the tool returned from a one-line brief, and explains what that kind of email has to do. The purpose menu above the brief covers all sixteen.