Agency operating guide
Resolve Conflicting Client Stakeholder Feedback
Do not make the delivery team guess which client comment wins. Turn the conflict into one visible, client-owned decision first.
The short answer
Collect every comment, but do not treat every comment as an instruction. Group the feedback, identify direct conflicts, separate scope changes from revisions, and ask one named client decision owner to choose before the agency edits the work.
The agency can explain tradeoffs and recommend a route. It should not quietly resolve the client's internal authority conflict through production choices.
Classify the feedback before acting
| Feedback type | Agency action | Who decides |
|---|---|---|
| Clear correction | Fix the error | Agency within the approved brief |
| Preference | Record it and compare with the agreed objective | Named client decision owner |
| Direct conflict | Show the incompatible instructions together | Named client decision owner |
| New requirement | Assess scope, timing, and cost impact | Commercial owner plus client decision owner |
| Open question | Request the missing context | Person with the relevant knowledge or authority |
The feedback resolution record
Deliverable and version: Agreed objective: Decision owner: Feedback received from: Comments everyone agrees on: Comments that conflict: Why the comments cannot both be implemented: Agency recommendation and tradeoff: Scope, cost, or date impact: Decision needed: Decision deadline: What pauses until the decision arrives:
Link the record to the reviewed version. A decision about version three should not later be applied to version four without checking what changed.
The five-step resolution workflow
1. Consolidate without flattening
Put all comments in one place. Preserve who said what when authority or context matters.
2. Mark the conflict precisely
“The feedback is mixed” is not specific enough. Write the incompatible instructions beside each other.
3. Explain the tradeoff
Show how each route affects the agreed objective, scope, timing, accessibility, compliance, or another material constraint.
4. Ask one owner for a decision
Invite useful input from several stakeholders, but require one authoritative answer or an agreed client forum.
5. Confirm before revising
Send the selected route, affected work, owner, and date back in writing. Then begin the revision.
Worked example
A brand director asks for a shorter homepage. The sales leader asks for three additional proof sections. Both comments apply to the same draft.
Conflict: Reduce page length vs add three proof sections. Agreed objective: Help qualified buyers understand the service and request a call. Agency recommendation: Keep one proof section on the homepage and move the two detailed examples to linked case studies. Tradeoff: The homepage remains focused, while buyers can inspect deeper proof without losing it. Decision owner: Client marketing lead. Decision needed by: Wednesday at 3pm. Pause condition: Layout revision starts after the route is confirmed.
The agency has not avoided judgment. It has made a recommendation while leaving the final internal priority with the client owner.
When the client has no decision owner
Ask the client to name one for this deliverable or convene a short decision call with the people who must agree. If neither happens, record the unresolved conflict and pause the affected revision.
Do not choose the loudest stakeholder, the most senior person copied on email, or the last comment received unless the client has assigned that authority.
Related Qubit resources
Sources and operating boundary
This workflow supports client communication and delivery control. It does not override the contract, regulated approval process, brand governance, or qualified professional authority.