Managing Client Requests, Approvals, and Revisions Without Losing Context

A client emails feedback, a colleague adds changes in chat, and a new file arrives without a clear name. The team starts work without knowing which instructions to follow. Request management needs a clear record connecting the request, approval decision, and relevant version.

Anyone on the team should be able to see what changed, who approved it, and what happens next. Keep these details beside the task using team comments.

Turn a message into an actionable request

For the wider delivery process, use agency project management and recording decisions with tasks to keep each approval connected to the right output.“Change the design” is not enough. Identify the part, desired outcome, and version under review. Determine whether the change corrects an agreed requirement or adds new scope, since each affects the plan differently.

• The deliverable or file and its current version link.

• The requested change and its purpose.

• Consolidated feedback and conflicting points.

• The contributor and approver.

• The requested date and impact on other work.

Identify who consolidates feedback and approves

Several client stakeholders may contribute, but someone needs to consolidate feedback and resolve conflicts. Agree on an approver or clear approval process. Do not assume the latest message represents everyone.

Resolve conflicting opinions against the agreed goal and criteria. Contributors should not choose on behalf of decision makers. Silence is not approval.

Organize each review round

1. Send a specific version and explain what needs review.

2. Agree on a suitable feedback deadline.

3. Consolidate comments into one list and remove duplicates.

4. Resolve conflicts and ambiguity before execution.

5. Assess the impact on scope and timing.

6. Implement the agreed changes and return the version for verification and approval.

Record requests arriving after a round closes as new changes and discuss their impact. This keeps commitments clear while allowing the work to develop.

Example: reviewing campaign assets

A client reviewing three assets asks to change the main message, while a colleague asks to keep it. The project owner brings both comments to the approver before redesign starts. Once resolved, the owner records the decision with the version link and creates an execution task with acceptance criteria.

If the client adds a fourth asset outside the original scope, explain the design effort and delivery impact. Agree whether to accept, defer, or replace another asset. Do not silently add it to the team’s commitments.

Make the approved version easy to find

Use clear file names and one reference to the approved version. Add its link, approval date, and approver to the task. Avoid two files named “final” without explaining which is valid for delivery.

On the work board, distinguish execution, review, and completion using agreed definitions. This is an organizational method; it does not assume the platform offers a client portal, electronic signatures, or automatic approvals.

A short request template

Project… Deliverable and version… Requested change… Purpose… Decision owner… Contributor… Deadline… Change impact… Approval status…

Use the template when clarification is needed. Match detail to the impact and likelihood of misunderstanding, without turning every small comment into a lengthy process.

Frequently asked questions

How should we handle verbal feedback?

Write a summary of your understanding and ask for corrections, especially when scope or timing changes. Link it to the task so the contributor has the context.

Should we set a fixed number of revision rounds?

Follow the working agreement with the client. Clarify limits and change handling in advance. Refer to that agreement when expectations differ.

When is the task complete?

When agreed acceptance criteria are met and required approval is recorded. Finishing the revision alone does not establish acceptance.