How to organize client communication without losing feedback

A client requests a change through WhatsApp. Their director replies by email with the opposite instruction. Somebody approves the work in Thursday's meeting, but on Friday another stakeholder asks to restore an older version.

This is not simply “poor communication.” It is a system with no clear place for decisions.

For an agency or freelancer, two-way communication is not about replying constantly. Both sides need to ask questions, understand the answer, and close decisions without losing context.

Separate conversation from decisions

A call is useful for exploration. Chat is useful for quick questions. Neither should be the only record of approval.

After an important conversation, leave a short project note:

Agreed on 14 May: keep headline B, remove photograph 3, and deliver the vertical version on Friday. Approver: Laura, client.

You do not need a transcript. Record what changes, who decided, and what happens next.

Name one person who consolidates feedback

When five stakeholders review directly, the designer ends up negotiating contradictions. Ask the client to appoint one person to collect comments.

That does not silence other stakeholders. It gives the creative team one coherent instruction.

For example:

• Leadership comments on strategy.
• Legal reviews claims and rights.
• Product verifies facts.
• The marketing lead consolidates the response.
• The agency executes one prioritized list.

If nobody can own that role, make coordination an explicit part of the scope and budget.

Request feedback that can be executed

“Make it stronger” is not an instruction. Each comment needs four elements:

1. Where the problem occurs.
2. Which objective it fails.
3. What change is requested.
4. Whether it blocks delivery.

For video: “00:24, the product appears too late; show it before the benefit. Blocks approval.”

For design: “Version B, second block; legal has not approved the claim. Replace it with the brief copy.”

Agree on channels before starting

Set simple kickoff rules:

• Quick questions can use chat.
• Source material goes into the project.
• Comments belong on the reviewed version.
• Approvals are recorded.
• Urgent requests require an owner and a newly agreed date.

The exact tool matters less than consistency. If feedback lives in four places, no software can know which message is authoritative.

Put a deadline on feedback

A delivery cannot remain “waiting for client” forever. Set a review window, such as two business days. When feedback arrives late, the delivery date moves.

State the consequence in advance:

The review will be ready Tuesday. We need consolidated comments by Thursday at 2 p.m. Later feedback will require a new delivery date based on availability.

This is not a threat. It protects the agency schedule and makes waiting visible as part of the timeline.

Close every round

A review round ends when comments are consolidated, corrections are separated from new requests, one person can approve, the reviewed version has a name and date, and the next action has an owner.

Keep versions, comments, and approvals with the work, then store final masters in a shared asset library. A conversation becomes useful history instead of disappearing messages.

Good client communication does not mean being available every hour. It means anybody can answer three questions: what was decided, who approved it, and what happens next.