You send a draft, receive a helpful comment by email, then discover another request in a message thread. A third person is reviewing an older attachment. By the time the feedback reaches production, nobody is certain what needs to change.
A clear client feedback process gives those comments a home and a decision path. Your virtual assistant can organise the review, clarify missing details and hand over a usable revision list, while the people responsible for the work retain the right decisions.
Tell reviewers what this round is for
Different review rounds need different questions. An early concept review may focus on direction and audience. A final proof may focus on factual accuracy, links and approved details. Asking for every possible opinion at every stage makes small revisions turn into a fresh project.
Include the objective, deliverable, version, review deadline and the decisions you need. Link to your original campaign brief so comments can be assessed against the purpose of the work.
Choose one current review location
Use a shared document, project task or approved review tool your client can actually access. Name the current version clearly and stop distributing multiple editable copies. A polished tool is not helpful if reviewers cannot find the right file.
Your VA can gather comments received elsewhere into the review record, preserving who said what. They should flag that the comments have been collected rather than silently treating every informal message as a production instruction.
Ask for feedback that explains the problem
Useful feedback identifies the location, problem and desired outcome. Instead of asking someone to make a page more exciting, explain that a visitor cannot tell which service suits them and point to the section causing confusion.
An illustrative feedback note might read: “In the second service section, explain whether the onboarding call is included. New enquiries keep asking this question.” That gives the delivery team something concrete to solve.
Which page, paragraph or visual needs attention?
What is inaccurate, unclear or inconsistent?
Who is affected by the issue?
Is there approved wording or evidence to use?
What does the reviewer need to decide?
Resolve contradictions before production resumes
If one reviewer wants a shorter introduction and another wants extra detail in the same space, put both requests beside each other. Ask the authorised decision-maker to choose the outcome or explain how to reconcile them.
Your VA can make the conflict easy to assess, but should not invent a compromise that changes the client's intended message. Keep unanswered decisions visible in the handover, with an owner and due date.
Separate corrections from changes in direction
A wrong date is a correction. A request to change the audience, offer or deliverable may change the work required. Compare new requests with the agreed brief and route changes in scope to the appropriate person before committing time or making promises.
Keep the language straightforward: “This request changes the original deliverable. Please confirm the updated scope and timing before we proceed.” Your VA can prepare that summary without negotiating terms they are not authorised to approve.
Return a revision record with the next version
List the agreed changes, their status and any open questions. Check that each implemented change appears in the actual new version. Do not mark a request complete because somebody said they would handle it.
Ask the authorised reviewer to approve the exact version for the stated next step, such as production handover or scheduled publication. General praise does not necessarily answer that question. Store the decision with the work so the team can find it later.
Keep the review manageable
A feedback process does not need to become a new administrative burden. Begin with one current file, one consolidated decision list and one clear next step. Use your VA's weekly report to surface decisions that are blocking delivery.
VAmazing helps established Australian businesses coordinate marketing projects, implementation and the systems behind them. Get in touch if useful work keeps stalling between the first draft and the final decision.