Feedback
input
A reaction, preference, concern, or idea.
Feedback classification guide6 min readReviewed 2026-04-30
Not all feedback is a revision request.
Client feedback can be useful, vague, contradictory, strategic, or out of scope. Before acting on it, freelancers need to classify what the feedback actually asks them to do.
Revision request
action
A specific change to a specific deliverable.
Scope risk
new direction
Feedback can become new work if it changes the agreed outcome.
1
Treat feedback as raw material
Feedback is not automatically a task. It needs interpretation, prioritization, and sometimes a follow-up question.
Ask what specific deliverable or section the feedback affects.
Separate taste, strategy, correction, and new direction.
Confirm whether the client wants a change or is only thinking aloud.
Avoid starting production from vague comments.
2
Define an actionable revision request
A revision request should tell you what to change, where, why, and what outcome the client expects.
It names the deliverable or version.
It describes the requested change clearly.
It explains the reason or decision context.
It fits inside the agreed revision policy or becomes extra scope.
3
Protect against new direction disguised as feedback
A client may call something a revision even when it asks for a different concept, feature, audience, format, or deliverable.
Compare the request against the original brief.
Check whether approved work is being reopened.
Estimate impact before accepting a new direction.
Offer a paid change order or future phase when needed.
Feedback classification checklist
The affected deliverable is clear.
The requested change is specific.
The reason for the feedback is understood.
The request is classified as correction, revision, or new scope.
The revision round limit is checked.
Out-of-scope impact is approved before work starts.
Frequently asked questions
What if client feedback is vague?
Ask a clarifying question before revising. Vague feedback creates interpretation work and can easily become unnecessary rework.
Is subjective feedback always out of scope?
No. Subjective refinement can be included. A new concept, direction, or deliverable is more likely to be new scope.
How do I avoid sounding defensive?
Use neutral classification language: 'This looks like a new direction rather than a refinement of the approved version.'
EasyScope