Harsh or vague feedback needs structure: restate, clarify, revise inside limits, document.
11 min readPARSE steps
- Pause before reply
- Acknowledge ("I hear you want X clearer")
- Restate specific changes
- Scope check revision vs new direction
- Execute inside round limit
Vague feedback script
Thanks for the notes. To hit this right, can you confirm top 3 changes? For example: (a) shorter intro, (b) move CTA, (c) fix typo block on page 2. I will fold into round [1/2] and send v2 by [date].
Harsh but in-scope
I will apply these edits in round 2 by [date]. If direction shifts beyond our brief, I will send a quick change order so we stay aligned.
Abusive tone boundary
I am happy to fix the work. I need feedback on the deliverable, not personal comments. Let us keep notes professional so I can deliver my best.
You may end the contract if abuse continues.
Common mistakes
| Mistake | Fix |
|---|---|
| Matching anger | Restate facts |
| Unlimited redo | Cite round |
| Fixing without confirm | Email restate |
| Accepting insults | Boundary |
See revision limits.
How Salag helps
- Freelance Readiness Checker: revision terms upfront.
- Late Fee Calculator: if delays from feedback loops.
- Scam Pattern Detector: extreme disrespect patterns.
Move safer. Not faster.
In short
Hard feedback happens. Parse it: what do they want changed, is it in scope, which revision round is this?
Reply calm. Restate in writing. Fix inside limits. Abusive tone is a boundary issue, not a free redo pass.
Common questions
Hard feedback happens. Parse it: what do they want changed, is it in scope, which revision round is this? Reply calm. Restate in writing. Fix inside limits. Abusive tone is a boundary issue, not a free redo pass.
Breathe. Restate feedback in your words. Ask one clarifying question if vague. Do not reply angry in Slack.
Professional tone. Separate person from work. Use revision round rules.
Revision limits and feedback deadlines in scope prevent endless free edits.
If tone is abusive, set boundary on respectful communication. You can fire clients.
Pause, Acknowledge, Restate ask, Scope check, Execute inside round limit.
Personal insults, racist comments, or 10th "complete redo" without new scope.
Yes. Restate feedback in email creates paper trail for revisions.
Revision limits in agreement tools.
Feedback doc, Loom, version numbers, revision terms.
Five minutes to restate and confirm round.
Projects use round caps. Retainers need "one pass per deliverable" rule.
Send restate email anyway. Work only inside confirmed round.