How to turn vague client feedback into a clear, actionable revision list

"Can you just make it pop more?" "It's not quite right yet." "Let's workshop the hero section." Feedback like this is common, and it is almost impossible to act on directly. If you start editing based on a vague comment, you risk guessing wrong, doing the work twice, and burning a revision round on changes the client did not actually ask for. The fix is a short, repeatable step between receiving feedback and starting work: turning it into a numbered, specific list the client confirms before you touch anything.

Why vague feedback is a scope problem, not just a communication problem

Every item on a revision list is either in scope (covered by the agreed rounds) or extra (billable separately). You cannot sort vague feedback into those two buckets until it is specific. "Make it pop more" could mean a color change (five minutes) or a full layout redesign (a new project). Converting feedback into a list is not bureaucracy — it is the step that lets you apply your revision policy and your pricing correctly instead of guessing.

The three-step process

1. Acknowledge, don't interpret yet. Reply quickly to confirm you received the feedback, without committing to a specific fix. This buys you time to ask clarifying questions instead of starting work on a guess.

Thanks for the feedback on [deliverable] — I'll turn this into a quick list so we're both clear on exactly what's changing, then get started.

2. Convert it into a numbered list with your own interpretation spelled out. For each vague point, write what you think it means in concrete terms, and ask the client to confirm or correct it. This is the single most important step: it moves the guess from your head into writing, where it can be checked before any work happens.

Here's what I'm planning to change based on your notes — let me know if I've read any of these right:

1. "Make the header pop more" → increase the heading size and switch to the darker brand color (not a full redesign of the section)

2. "The flow feels off" → reorder sections 3 and 4 so pricing comes before FAQ

3. "Can we workshop the hero" → I'll send 2 quick variations of just the hero headline, not the full hero layout

If all three match what you meant, I'll get started today. If any are off, a quick note on which one will save us a round.

3. Get a one-line confirmation before starting. Even a plain "yes, that's it" from the client is worth waiting for. It converts the list from your assumption into something both sides agreed to, which is exactly the kind of record your approval log should hold.

Handling feedback from a call or voice note

Spoken feedback is often less precise than written feedback, because people describe impressions rather than specifics while talking. Use the same three steps, but add a short recap first (see our guide on putting verbal approvals in writing for the recap format), then build the numbered list from the recap, not from memory of the call days later.

When the client's answer is still vague

Sometimes the reply to your numbered list is just "yes to all" without really checking, or the client repeats the same vague phrase instead of confirming your interpretation. In that case, narrow the question further instead of starting work:

Just to make sure item 2 lands right — do you mean swap sections 3 and 4 entirely, or just move the pricing table above the FAQ while keeping everything else where it is? Either is a quick change, I just want to do the right one first time.

What this protects you from

Without a written list, a disagreement later sounds like "I asked you to fix the hero and you didn't." With a written list the client confirmed, it sounds like "you confirmed item 3 was just the two headline variations, which is what was delivered — a full hero redesign would be a new item." The second version is a fact you can point to, not an argument about who remembers the conversation correctly.

Make the list part of your normal workflow

Once a numbered-list reply becomes automatic, most feedback rounds get faster, not slower, because you stop doing work based on a guess and then redoing it. The Client Approval Log + 50 Client Messages pack includes a Revisions sheet to log exactly this (what was asked, your interpretation, whether it was confirmed, and whether it was in scope or extra), plus ready-to-paste messages for the acknowledgement and confirmation steps above.

Get the Client Approval Log + 50 Client Messages ($9)