Work & focus

Conflicting Client Feedback: Get a Clear Decision Before Revising

Published by OneCell

Before revising the part that has conflicting client feedback, check whether the comments address the same passage in the same version. Separate changes that can work together from unclear requests and instructions that cannot both be followed. Ask the client to resolve the specific choice through their existing approval process. Other clear, authorized edits can still continue when they do not depend on that choice.

Start with the comments you have. You do not need a new review tool or a meeting for every difference of opinion.

Check the version and the exact passage

Open the draft each reviewer saw. Compare version names, page references or timecodes before deciding that two people disagree. A note about an earlier draft may already have been addressed; a general comment may concern a different section.

Then ask: Could one revision satisfy both requests? “Keep the anecdote” and “shorten the introduction” may be compatible if another part of the introduction can be trimmed. They become a different question if the client has specified a length that cannot accommodate the full anecdote. Clarify that requirement before choosing what to remove.

“Remove this anecdote entirely” and “keep this same anecdote in full,” applied to the same target version, require a decision. Splitting the difference would not satisfy either instruction.

Sort one set of comments before changing the draft

Consider a fictional freelance audio editor working on version 2 of an episode. The client’s usual contact is gathering notes from several reviewers. Four comments arrive:

  • “At 01:10–01:40, remove the opening anecdote entirely.”

  • “At 01:10–01:40, keep the opening anecdote in full.”

  • “Correct the guest’s name at 00:15.”

  • “Make it more energetic.”

The editor checks all four against version 2 and sorts the work:

  • A genuine conflict: the first two notes refer to the exact same anecdote. Keep the choice between retaining and removing it pending; neither the latest message nor a guessed hierarchy of job titles establishes the agreed direction by itself.

  • A clear independent correction: the name appears outside the disputed passage. In this example, the client has confirmed the correct name, supplied an approved replacement recording, and authorized that correction. The editor can make it without deciding what happens to the anecdote.

  • An unclear request: “more energetic” does not identify the section or the change. Ask whether the concern is pace, music, delivery or something else, and which passage needs attention.

This produces three different next actions: request a choice, make the independent correction, and clarify the vague note. Putting all four comments in one place helps you compare them, but does not by itself resolve the contradiction.

Ask for a choice the client can answer

Send the incompatible directions together to the contact already coordinating the review. Identify the source version and passage, state what cannot coexist, and ask how the final direction will be confirmed. Include the agreed purpose of the passage when that context helps the choice.

For the fictional episode, an original message could say:

In version 2, the notes for 01:10–01:40 ask both to remove the anecdote entirely and to keep it in full. Which direction should I use for the next version? Could you confirm how that choice will be agreed with the reviewers? I can make the approved name correction separately while this is being decided.

Use the client’s actual process. Their contact may be able to confirm the choice, or may need to take it back to other people. Ask when this is unclear rather than assuming that the person collecting comments can settle every decision.

Atlassian’s guidance on decision roles separates contributing input from responsibility for the final decision. That distinction is useful here without requiring your client to adopt a new framework or appoint exactly one approver.

Keep useful independent work moving

Before continuing an edit, check whether it depends on the unresolved choice. The approved name correction can proceed in this example because the editor has the right material and permission, and it sits outside the disputed section. If a correction instead falls inside material that may be removed, check whether doing it now would be useful.

Clarify the energetic note separately: Which section feels too flat, and is the change you want about the pace, music or delivery? Once the request is clear, check it against the existing brief and any other comments before revising.

Keep references tied to the draft the reviewers saw. If an early edit shifts later timecodes, retain “version 2, 01:10–01:40” with the original comment so everyone can still locate the disputed passage.

Keep the confirmed direction with its version

When the client’s process produces a decision, restate the result in the existing review thread. For example: For version 3, keep the full anecdote from version 2 at 01:10–01:40; the introduction will be shortened elsewhere, as confirmed. Use that wording only if those are the choices actually agreed.

Check the revised draft against that direction before marking the comments resolved. An unanswered message is still a pending choice; a new batch of comments is not automatically a final decision.

If waiting for that choice starts to affect delivery, use the separate guide on late client feedback and project deadlines to check the scheduling question.