Manage Marketing Agency Scope Changes With a Written Change Request

A marketing engagement changes as teams learn. A campaign may need another landing page, an approved audience may expand, or sales may request a new asset. A written change request gives both sides a way to evaluate that work before it becomes an unplanned commitment. The useful output is an agreed decision about scope, cost, and delivery.

Compare the request with the signed scope

Start with the signed scope and its assumptions. Identify which deliverables, revision rounds, channels, and reporting tasks are included. A request to correct work that does not meet the agreed acceptance criteria belongs in normal delivery. A request for a different audience, additional format, or new integration may change the scope. Resolve that distinction before discussing an extra fee.

Keep the request short enough for people to use. Record the requested outcome, why it matters now, the existing deliverable it affects, and the person asking for it. Include a link to the relevant brief or ticket. Avoid accepting instructions scattered across meetings and chat messages without a shared record of what was decided.

The agency should return an impact estimate covering effort, fee, schedule, dependencies, and any displaced work. Where the work is uncertain, define a bounded discovery step rather than pretending the final estimate is exact. If a new landing page needs a client developer or a customer quote needs permission, make that dependency visible.

Estimate cost, timing, and approval needs

Consider a hypothetical request for five additional creative versions. The estimate should explain whether these are resizes of an approved concept or new concepts requiring copy, design, and review. Those choices have different implications. A client can then approve the work, reduce the number of versions, move the deadline, or exchange it for another planned task.

Name the person who can approve changes on each side. Keep financial authority and editorial feedback clear: a stakeholder may be able to review copy without authorizing a new fee. Set the approval path before urgent work arrives, and record the approved version of the request. A verbal agreement can be summarized immediately in the shared system for confirmation.

Define what happens while approval is pending. Work that depends on the change should have a visible status and owner. For genuinely urgent requests, agree a limited authorization with a spend cap, named tasks, and an expiration. Review that exception afterward so a temporary arrangement does not become a standing assumption about free capacity.

Record the decision and review repeat changes

Once approved, update the delivery plan and acceptance criteria. Keep the original request and decision history so an invoice can be reconciled later. Identify what counts as completion, who will review it, and whether a new milestone affects other campaign dates. Scope clarity is especially important when media spend, platform fees, and service fees are billed separately.

Use the engagement’s observable acceptance criteria as the starting point, and compare the change with the agreed schedule. The process should help both teams make a tradeoff while the work can still be adjusted. It is most effective when a small request has a small approval process and a material request receives the review it needs.

Review requests periodically for patterns. Repeated additions of the same task may indicate that the recurring scope needs an update. Frequent late changes may reveal an intake problem or missing stakeholder. Improve the plan based on that evidence, and keep the change process predictable enough that neither side needs to negotiate every minor correction.