You need to tell someone their work isn't up to standard. Or that their approach isn't working. Or that the thing they're proud of needs significant changes.
In person, you can calibrate in real time. You can see their reaction, adjust your tone, and have a real conversation. Over email, none of that exists. Your words land without context, without nuance, without the ability to course-correct.
This is why feedback emails so often go wrong. But sometimes email is the right medium, maybe you're remote, maybe you need a record, maybe the feedback is detailed and they need time to process it. The key is doing it right.
When to Give Feedback Over Email (And When Not To)
Email works for:
- Detailed feedback on a document, design, or deliverable
- Written feedback they can reference later
- Situations where the person might need time to process
- Follow-up to a verbal conversation (putting it in writing)
Email doesn't work for:
- Major performance issues (have the conversation first)
- Emotionally charged situations
- Feedback that might be misinterpreted without tone cues
- The first time you're addressing a serious problem
When in doubt, have the conversation first and follow up with an email summary.
The Feedback Email Structure
1. Context and intent
Start by making clear that your goal is to help, not to criticize. One sentence.
2. What's working
Genuine acknowledgment of what's good. Not a hollow compliment before the "but." Something specific and true.
3. What needs to change
Be specific. "This needs work" is useless. "The intro section doesn't address the reader's main objection, which is price" is actionable.
4. Why it matters
Explain the impact. "If we ship the proposal like this, the client will have unanswered questions about ROI, which could stall the deal."
5. Suggested path forward
Don't just identify the problem. Suggest a direction for the fix.
Giving feedback on a team member's client proposal
“Hey Jordan, I took a look at the proposal. I have some concerns. I think it needs quite a bit of work. The structure is confusing and I'm not sure the client will understand what we're offering. Can you take another pass at it? Let me know if you have questions.”
“Hey Jordan, I went through the Acme proposal. The pricing breakdown on page 3 is really clear and the case study section is strong. Two things I'd adjust before we send: 1) The intro jumps into features without addressing their main concern, which is reducing onboarding time. I'd lead with the 40% time savings metric and then explain how. 2) The timeline on page 5 doesn't account for the API integration they mentioned in the call. Can you add 2 weeks for that? These changes should make it much more compelling. Happy to review the next version.”
The first email tells Jordan it's bad without telling them what to fix. The second identifies specific issues, explains why they matter, and suggests clear solutions.
Tone Rules for Feedback Emails
Use "I" language, not "you" language. "I noticed the timeline doesn't include the API work" lands better than "You forgot to include the API work."
Be specific, not general. "The presentation needs to be better" is demoralizing and unhelpful. "Slide 7 needs a clearer call to action" is something they can actually fix.
Separate the work from the person. You're critiquing the proposal, not the person. "The intro could be stronger" vs "You wrote a weak intro."
Don't soften to the point of vagueness. "Maybe possibly consider potentially adjusting the intro slightly if you think it makes sense?" No. Just say what needs to change.
Acknowledge effort. Even if the work needs significant revision, acknowledging the effort that went into it costs nothing and prevents defensiveness.
The Feedback Sandwich (And Why It Doesn't Work)
The classic "praise, critique, praise" sandwich is so well-known that people see through it. When you start with a compliment, they immediately brace for the "but."
Instead of a sandwich, try genuine specificity. If the pricing section is genuinely good, say so. Not because you're building up to criticism, but because accurate feedback includes what's working, not just what isn't.
Common Mistakes
Piling on. If there are 10 issues, pick the 3 most important ones. Too much feedback at once overwhelms and demoralizes.
Being passive-aggressive. "Per my last email..." or "As I mentioned before..." These phrases drip with frustration and put the person on the defensive.
CC'ing unnecessarily. Don't give feedback in front of others unless there's a good reason. Direct feedback should be direct.
Waiting too long. Feedback on work from three weeks ago feels like an ambush. Give feedback while the work is fresh.
Let ColdCheck Get the Tone Right
Feedback emails are emotionally loaded. You might be frustrated, which makes you too harsh. Or you might feel bad, which makes you too vague.
"Need to give Jordan feedback on the Acme proposal. Pricing section is good, case study is strong. But the intro doesn't address their onboarding concern, and the timeline is missing API integration work. Want to be direct but supportive."
ColdCheck writes feedback that's clear and constructive. Specific problems. Specific suggestions. No passive aggression. No vagueness. Just useful feedback that Jordan can act on.
Give feedback that lands
Describe what needs to change and why. Get clear, constructive feedback in your voice.
The Bottom Line
Good feedback is specific, actionable, and focused on the work, not the person. Acknowledge what's working. Be clear about what needs to change and why. Suggest a path forward. And deliver it while the work is still fresh.
Feedback over email requires extra care because tone is invisible. When in doubt, read your draft as if you were receiving it. If it would make you defensive, revise until it wouldn't.