Client change routing turns a request into one authorized instruction that an account operator can execute. The agency should clarify the affected assets, destinations, timing, and approval before asking the provider to change scheduled or published work.
What information does a change request need?
Record the requester, campaign, affected asset version, account, requested change, deadline, and reason. Include the current state: not yet accepted, queued, or already published. A request to change the latest video is ambiguous when several files and destinations exist. The operator needs an exact reference and an authorized outcome, not a screenshot without context.
How should the agency assess the impact?
Check whether the request changes creative approval, rights, timing, destination, or the agreed service scope. Identify any already-published versions and linked campaign material. A small wording change may require a new approval, while a replacement video may affect scheduling and reporting. Share the impact before promising the client that every affected post can be changed immediately.
Who should send the final instruction?
Use a designated agency contact or an agreed request system that makes authority visible. Preserve client context, but give the provider a clear action rather than forwarding a long conversation. If client stakeholders disagree, the agency should resolve the conflict. The provider should not infer which person's message overrides the approved campaign record.
What closes the change request?
Close it when the requested action has been completed or a documented limitation has been accepted by the responsible agency contact. Record the affected URLs, new version, and remaining exceptions. An acknowledgement is not completion, and changing the source file does not prove that queued or published copies have also been replaced across the campaign.
What does the research help you decide?
Adobe 2025 Australian marketer survey reports: 48% struggled to meet demand; 46% spent over 40% of their time on administration, reviews and approvals. These findings concern Australian marketing teams, not all agencies. They explain why change coordination deserves an explicit owner rather than becoming unrecorded administrative work spread across the delivery team.
What would this look like in a real workflow?
The following is a hypothetical operating example, not a Conbersa customer result. A client asks to remove a discount from a video caption after some posts are live and others remain queued. The agency identifies both sets of destinations and approves the replacement wording. The provider updates what the platform permits and reports any posts requiring a different action. The agency then confirms the completed changes to the client using the actual delivery record rather than assuming a single edit propagated everywhere.
Use a record that someone outside the original conversation can act on:
| Record field | What to write down |
|---|---|
| Affected work | Asset version, account, scheduled or published state, and relevant URL. |
| Authorized action | Approved replacement instruction and the person who accepted its impact. |
| Completion | Executed change, timestamp, evidence, and any platform or access limitation. |
Keep routine changes and urgent removals distinguishable in the same system. Urgency should affect routing and escalation, not erase the need to identify the correct material. After repeated changes, review whether the campaign brief itself needs revision so operators are not maintaining an expanding collection of exceptions.
How does this connect to the wider workflow?
Continue with How Do You Keep One Client Approval From Blocking Other Campaigns and How Should Agencies Set White-Label Service Levels and Reporting Cadence for the related decisions. Keep the accepted instructions connected to the same campaign record. When scope, permission, or destination changes, the responsible team should be able to identify what must be reviewed and which publishing work is affected.
How Conbersa fits into the workflow
Keep the agency responsible for the client promise and name the provider responsibilities inside the delivery agreement. Conbersa offers managed account infrastructure for teams supplying content. Discuss platforms, account access, posting work, reporting needs, and escalation expectations before incorporating that service into a client retainer.