Skip to content
Overflow Sites Discuss a partnership

How Agencies Manage Client Revisions

A practical workflow for consolidating client feedback, separating corrections from new scope, and keeping a web production partner aligned.

💡
Key Takeaways
  • Collect and consolidate feedback before sending it to the production partner.
  • Separate defects against the approved brief from new requests or preference changes.
  • Confirm how changes affect schedule and cost before work continues.

Client feedback often arrives in several forms: comments in a design file, emails, chat messages, and meeting notes. Sending every comment directly to a production partner can create contradictions and leave unclear which request is approved. The agency’s project owner should turn feedback into one actionable, prioritized set of instructions.

Collect feedback in one place

Set a review window and tell stakeholders where to leave comments. Ask them to refer to a page, screen size, or specific element. Encourage observations about a user problem or business goal, not only personal preference. A note such as “the phone number is difficult to find on mobile” is more actionable than “make the page friendlier.”

When a client shares feedback in a call, record it and send a summary for confirmation. A written record prevents the agency and partner from remembering different decisions. Avoid asking the partner to interpret multiple uncoordinated comment threads.

Classify each request

Separate feedback into useful categories:

  • Defect: the delivered work does not meet an agreed requirement.
  • Clarification: the original brief did not specify the behavior or content.
  • New request: the client wants a page, feature, or change outside the agreed scope.
  • Preference change: the client wants to revise an earlier approved decision.
  • Dependency: the work is waiting for copy, assets, credentials, or an approval.

These categories help determine the next step. A defect should be checked against the acceptance criteria. A new feature may need an estimate. A preference change may involve rework. A dependency needs an owner and a date before the partner can proceed.

Consolidate before sending

The agency owner should remove duplicates, resolve contradictions, and prioritize issues. Each item should identify the URL or component, expected behavior, actual behavior, and desired change. Include screenshots when they clarify the issue. If one request conflicts with the approved design or another request, ask the client to choose before passing it on.

Use a single source of truth for the current feedback and mark which items are approved. When the partner completes a round, review the changes against the list and close items explicitly. Do not assume that an issue is resolved because a new preview is available.

Protect scope and schedule

Compare each request with the project brief and agreed revision process. If it is new work, explain the difference and ask the partner for the impact before promising a date to the client. Do not ask a partner to begin out-of-scope work while the agency is still deciding whether to charge for it. This creates confusion about approval and responsibility.

Likewise, do not label a legitimate defect as a scope change merely because it takes effort to correct. The acceptance criteria should guide that decision. If the original brief was ambiguous, the agency and partner should agree on a fair resolution and update the scope record.

Set a review cadence

Agree on who reviews each round, how quickly feedback will be returned, and what happens when a stakeholder misses a window. A predictable cadence gives the partner a workable queue and helps the agency communicate realistic expectations. If the client needs more time, update the schedule rather than implying that work can proceed without approval.

Keep a decision log

For each round, save the submitted comments, decisions, change approvals, and remaining issues. This gives the agency a record if priorities shift or a new stakeholder joins. It also makes future work easier because the team can see what was accepted and why.

Make feedback easy to act on

Ask reviewers to reference a page, section, and specific change instead of sending broad notes such as “make it pop.” When feedback conflicts, the agency should resolve the preference with the client before forwarding instructions to the implementer. Keep editorial corrections separate from new requirements, such as an added page or feature. The distinction matters because a change that sounds small can affect layout, testing, integrations, or launch timing. A shared decision log can capture the request, who approved it, the response, and any impact on agreed scope. It also helps the agency summarize what changed without asking the client to search through long email threads.

Explore the topic hub and these related guides:

For work involving WordPress, the official WordPress documentation is a useful reference for maintenance responsibilities and recovery planning.

Sources