Translating Vague Client Photo Feedback Into Real Edits

Why "Make It Pop" Doesn't Mean Anything to a Retoucher

A retoucher reading "make it pop" has to pick a lane: more contrast, more saturation, sharper local contrast, a warmer white balance, a tighter crop, or some combination. Any of those is a defensible guess. Only one of them is what the client had in mind, and the client usually can't tell you which until they see the wrong one.

Run the arithmetic on a single delivery: say 12 photos go out, and 3 come back with a note like "make it pop" and nothing else. If the retoucher gets one of those three right on the first pass and guesses wrong on the other two, that's 2 extra rounds — and if a round takes even a single day to turn around, that's 2 extra days added to a delivery that should have shipped on schedule, not because anyone was slow but because two guesses had to be made and corrected. Multiply that across a busy month of shoots and the guessing is where the schedule actually slips, not the editing itself.

Most photographers already sense this and still don't push back on a vague note, because asking a follow-up question can feel like telling the client their feedback wasn't good enough. It isn't a criticism of the client to ask which direction "pop" means — it's the same question a good waiter asks when someone orders "something light," and it saves both people from a dish that gets sent back. The photographers who ask the follow-up question up front are not the ones who seem difficult; they're the ones who ship on schedule.

The fix isn't asking clients to learn retouching vocabulary. It's translating what they said into something specific enough that nobody has to guess.

The Vague Feedback Translation Table

These are the phrases that show up in almost every round of vague client feedback, what they usually turn out to mean once you dig one question deeper, and the question that gets you there faster next time.

None of these translations are guaranteed right for every client — they're the most common read on each phrase, not a rule. The point of the table is to give you a first guess worth asking about, instead of a first guess worth editing.

Turn Feedback Into a Multiple-Choice Question, Not an Essay Prompt

"What do you think?" invites a vague answer because it doesn't constrain the response. A client who isn't a photographer will describe a feeling before they'll describe a technical change, because feeling is the only vocabulary they have. The way around that is to ask questions with a small number of concrete answers, so the client is choosing rather than composing.

The same logic applies to picking between frames from a sequence — asking a client to rank three similar shots produces a decision faster than asking them to describe what's wrong with the one you sent.

Anchor the Note to the Photo, Not the Email

Even a well-translated note loses precision the moment it's separated from the image it's about. "Warmer, especially her skin" attached to the wrong photo in a 40-image gallery, or pasted into an email three replies deep, is right back to being a guess by the time someone acts on it. A note is only as useful as its anchor: which photo, and which part of that photo.

This is the same principle behind anchoring feedback to a specific part of the frame rather than the image as a whole — we go deeper into what that looks like in practice in retouching feedback that lands on the right pixel. Translating the language and anchoring the location solve two different halves of the same guessing problem.

What the Retoucher Actually Sees in Photoshop

Translate the feedback and anchor it to the right spot on the frame, and there's still one place the whole thing can go generic again: the handoff to whoever opens the file. A note rewritten as "warmer, especially her skin, see attached reference" is only as useful as the version that actually reaches the retoucher — not a summary of it relayed through a second email.

Appruva's Photoshop panel keeps the translated note attached to the frame itself instead of routed through a separate thread. Notes appear inside the panel numbered to match the badges the client saw on the review link, arriving live over a WebSocket where the network allows it and falling back to a 45-second poll where it doesn't — the retoucher is reading the client's actual words, at the moment the file is open, not a paraphrase written by whoever forwarded the email. When a note carries a reference image — the "match this skin tone" case — that image opens beside the document as its own file, so color can be sampled from it directly rather than eyeballed from a thumbnail. We cover that part in more detail in attaching reference images to retouching notes.

None of this replaces the translation work above — a panel that delivers "make it pop" faithfully still delivers a phrase nobody can act on. It just means the translating only has to happen once, by whoever talked to the client, instead of being redone by whoever opens the file next.

Prevent the Vague Note, and Give Clients a Template for the Next One

The cheapest place to fix vague feedback is before the client ever writes it. A delivery message that just says "here's your gallery, let me know what you think" is an open-ended essay prompt by default. One that sets the format up front — point at what you'd change, describe a direction, attach a reference if you have one — heads off the vague note before it's typed.

This matters more on shoots with more than one decision-maker. A couple approving wedding portraits, a marketing team approving brand photography, or an agency relaying notes from an end client all multiply the chance that "make it pop" gets typed by whoever is least sure how to describe what they want, then repeated by everyone after them because it's the only language on the thread. Setting the format once, in the delivery message, heads off the copy-paste version of the same vague note from three different people. Send something like this alongside the gallery link:

1. Point at the photo, not the gallery. Which frame, specifically.
2. Point at the area, not the whole image. A face, a corner, a color.
3. Describe the direction, not just the feeling. Warmer or cooler, brighter or darker, more or less — not just "off."
4. Attach a reference if you have one. A screenshot, a link, a photo from another gallery — anything closer to specific than a word.
5. Say what should stay the same. "Don't touch the background" prevents a retoucher from over-correcting somewhere the client was already happy.

None of this requires the client to learn retouching terms. It just gives the vague feeling somewhere concrete to land before it turns into a wasted round, and it's worth sending the same five lines every time rather than rewriting them per client — the value is in the client seeing the same format on every project, not in how it's worded.