01
Separate the record from each interpretation
A fictional freelancer receives separate review messages from a marketing lead, an owner, and an operations manager. One asks for a warmer design, another asks for a more minimal design, and the third approves the current direction.
The problem is not merely tone. The freelancer lacks one authorized, actionable decision and risks doing work that another stakeholder immediately reverses.
Documented facts
- Three stakeholders sent different instructions during the same review round.
- The project record names one client approver and calls for one consolidated response.
- The freelancer has not implemented the conflicting directions.
What the freelancer believes
- Proceeding without clarification will create avoidable rework and consume the agreed review round.
- The comments need concrete examples and a single priority decision.
What the client believes
- Each stakeholder is trying to improve the result from a legitimate business perspective.
- The freelancer may be expected to interpret the comments and recommend a solution.
What remains unknown
- Which person has final authority for this decision and whether that authority changed.
- What ‘warmer’ and ‘minimal’ mean in observable terms.
- Whether the desired direction remains within the approved objective and revision allowance.
02
Consider both perspectives without assuming fault
Different concerns can be reasonable at the same time. Neither list proves a disputed fact; it shows what a workable response must address.
Freelancer perspective
Practical concerns from the freelancer’s side
- Summarize the conflict neutrally, explain why one decision is needed, and ask the recorded approver to consolidate.
- Offer a recommendation when useful, but distinguish professional advice from client approval authority.
Client perspective
Practical concerns from the client’s side
- Resolve internal differences before directing production work and explain the business priority behind the choice.
- Use examples and one consolidated response so the freelancer can act and the review record stays coherent.
03
Check these records before deciding what happened
Start with the material both parties can inspect. Preserve original messages and files; work from copies when adding notes.
- The named approver, stakeholder roles, review channel, and consolidated-feedback requirement.
- The current approved direction and the exact conflicting comments.
- Concrete examples or observable changes behind broad adjectives.
- The decision deadline and schedule effect of waiting or revising.
- Whether the requested direction changes scope, acceptance criteria, or earlier approval.
04
Choose the smallest proportionate next step
These steps are possibilities, not a required legal sequence. Adapt them to the actual risk, agreement, platform, and communication record.
Summarize without choosing sides
Put the conflicting instructions next to each other and identify the decision they require.
Ask the approver to consolidate
Request one prioritized response through the agreed channel by a practical date.
Restate the decision
Confirm the chosen direction, examples, affected items, review-round status, and schedule effect.
Resume bounded work
Implement only the clarified direction and preserve unrelated approved work where possible.
05
Adapt a neutral, answerable message
Replace every bracketed detail and verify the record before sending. Do not turn the example into a threat or claim a consequence you have not checked.
06
Know when the situation needs qualified help
Most contradictory feedback is a project-governance issue. Get qualified help if the communications involve harassment, discrimination, coercion, confidential information sent to unauthorized people, or a material contractual dispute that cannot be resolved through the named approval process.
Get qualified help promptly when there is
- a threat to anyone’s physical safety or credible harassment or discrimination concerns;
- suspected crime, fraud, unauthorized account access, or a material exposure of personal or confidential data;
- a large potential loss, an imminent filing or response deadline, or a demand that depends on jurisdiction-specific rights; and
- a platform restriction, court order, insurance requirement, or other process with a deadline you cannot confidently interpret.
07
Use Lucy only after removing sensitive details
Lucy can group compatible comments, surface conflicts, and draft clarification questions after names and confidential details are removed. Following this link opens the ordinary blank tool. It does not load this example, transmit content, or make an AI request until you choose to submit the tool form.
Organize redacted feedback into one decision →
Read how Lucy handles a request before submitting real project material.
Keep going
Continue from the actual record
Client guide
Consolidate project feedback
See how a named approver can turn stakeholder comments into one usable response.
Agreement record
Statement of Work outline
Define approver authority, feedback rounds, dependencies, and the change process.
Worked example
See Harbor Street provide inputs and feedback
Follow one consolidated review path before a later scope decision.
Related situation
Missing client information
Use a dependency record when the project lacks a required decision or input.