Why changes after approval need a rule of their own
Approval is a decision about one version of the work: a reviewer read that copy, those images, that offer and that audience, and agreed that together they met the standard. The work keeps moving after it. The requester asks for a different headline, the commercial team moves the introductory price, a channel specialist trims the copy to fit a placement, a senior colleague sees the final version for the first time and wants the image swapped. Each request is reasonable, and each one turns the approved version into a new one that nobody has looked at.
Without a rule, a team can slide into one of two habits. In the first, every change goes back through every review, so a corrected comma waits in the same queue as a new price claim, reviewers stop reading closely and the people making changes learn to make them quietly. In the second, nothing goes back once the work has been approved, and the approval stops describing what customers see. The tutorial on auditing marketing approvals grades a review held on a different version from the one that ran as a serious gap for exactly this reason: on paper the work was approved, and in practice the part that changed was not.
The site already states the rule in several places, each for its own kind of work. The creative approval SOP sends any later change back through the steps that change affects. The campaign workflow guide sends a change to a signed briefA short document telling the people making creative work what it must achieve, for whom, with which message and within which limits. back to the people who signed it. The claims library tutorial treats a changed word in an approved claim as a new claim. This guide turns those rules into one set for all the team's work, so that "does this need to go back?" gets the same answer whoever asks.
What counts as a change, stage by stage
A change is anything that would make the work differ from what someone signed or approved, whether the brief or the version on the approval record. That includes the obvious edits to words and images, and also the ones that do not look like edits: a different audience, a new landing page, a moved start date, a larger budget, a translation that rewords a line, or an asset an ad platform generates or enhances on the team's behalf. What a change needs depends first on where the work is in its route.
| Stage | Examples of a change | What it goes back to |
|---|---|---|
| Brief signed, build not started | A new objective, audience, offer, channel, budget or success measure | The signatures on the brief; the request is scoped again |
| During build | Anything outside what the signed brief describes | The brief first; the build then carries on |
| Approved, not yet live | Edited copy, a swapped image, a new price, a different audience or destination | The approver, plus the reviews whose scope the change touches, held on the new version |
| Live | Edits to the ad, email, page or post; audiences or money beyond the limits agreed at handover | The same reviews, or the limits written at handover |
| Changed by someone else | Platform enhancements, a partner's copy, a local translation, an updated template | Treated as a change to the approved work and tested the same way |
Work done inside the signed brief during build is the build, not a change. The line is crossed when the work stops matching what someone signed or approved. When the requester changes the request after work has started, the service levels tutorial resets the clock or scopes the request again, so the promised turnaround is not quietly absorbed by the team.
The last row is easy to miss. A platform that adds generated headlines or expands an image has changed the approved ad as surely as a colleague editing it, and the tutorial on reviewing AI enhancements in ad accounts finds those settings and decides on each one. A translation that shifts a claim's meaning has changed the claim, which is why the tutorial on checking localised copy you cannot read has every claim, price and offer translated back and read again before sign-off.
Which review a change reopens
Unless the team's own written procedure says otherwise, every change goes back at least to the person who approved the work; the question is which other reviews it reopens. The approval matrixA table that says which reviews each type of marketing work needs, such as legal, brand or budget, and who gives each, matched to the risk of the work. in the approvals and compliance guide answers that, because each of its rows is triggered by something observable in the work. Run the matrix's triggers on the change, as the intake form ran them on the original request. A change that adds a new claim, alters an approved one, or adds or alters a price or promotion, a testimonial, a regulated product, a new page or template, spend above the approved budget or material produced with AI tools reopens that row's review, for the changed element on the new version. New audiences, data sources and contact channels are triggers in their own right: the data protection lead checks them against the organisation's consent records and policy. And because the matrix sends all public-facing work to the brand or creative lead, a new or reworded line that stays inside the guidelines still goes to brand.
The matrix was written for new work, so some changes need a rule it does not hold.
| The change | Where it goes | Why it needs its own rule |
|---|---|---|
| A small fix: a typo, a resize or crop, a broken link pointed back at the approved destination | The original approver, through the fast lane, with only the changed check repeated; a resize or crop of an asset that carries a claim, price, offer or endorsement, or concerns a regulated product, keeps its compliance check unless the written procedure says otherwise | Nothing a specialist decided has changed, but the version has |
| A typo inside a price, statistic or claim | The reviewer who approved that price or claim | Correcting it changes what the claim says |
| A swap to another approved variant, or to an asset approved for the same use | The original approver, with the rights checked in the library for the date it will appear | Each asset passed review, but not this combination |
| Headlines or images the ad platform generates or enhances | A decision on each setting, as the AI enhancements tutorial sets out, and the claims row for anything they assert | The team did not make the change, and the approved ad changed all the same |
| Wording changed in localisation | A back-translation of every claim, price and offer, read before sign-off | The approver may not be able to see the shift in meaning |
| Approved material reworked with AI tools | The editor, plus any row the result triggers | Generated material can introduce claims nobody wrote |
| Work a customer or partner approved | That customer for any change; that partner when the offer, the creative or the form changes | Their approval covered only the version they saw |
Two principles keep this proportionate. Review the change, not the whole piece: the reviewer whose scope it touches checks the changed element on the new version, and checks the change cannot affect are not repeated, which is how the creative approval SOP already answers the question for creative. And judge a change by what it does, not by how big it looks: altering one figure in a price looks like a small edit but makes an entirely new price.
Changes to claims need particular care. The approvals guide records a core principle that it says advertising rules in most markets share, pointing to the UK's Advertising Standards Authority for the codes and rulings that apply there and to the US Federal Trade Commission for its business guidance on advertising: marketing must not mislead, and a claim has to be capable of substantiationThe evidence a business holds, before a claim is published, that the claim is true; advertising rules in most markets expect claims to be capable of it. before it goes out. A changed claim therefore goes back with its evidence attached, and once approved the new wording becomes an entry of its own in the claims libraryA record of every marketing claim in its exact approved wording, with the evidence behind it, the conditions and markets it is approved for and the approver.; where the old wording should no longer be used, its entry is marked as retired so that builders stop copying it. Price claims are different: the claims library tutorial notes that they usually go through promotion review rather than the library, so a changed price goes to the reviewers the matrix names and is recorded on the work item as a new version. None of this is legal advice; what a claim needs in your market is for your own legal advisers to say.
Small fixes
A small fix still makes a new version, and that version still goes back to the person who approved the work. What keeps it quick is that, apart from the compliance check on a resize or crop noted below, no specialist review reopens: the approver confirms the fix through the fast lane with only the changed check repeated. The fast laneA written, shorter approval route for low-risk, repeatable or urgent work, such as replies or posts from approved templates; anything risky leaves the lane. here is the shorter route already written down for low-risk work, so a fix follows its rules rather than a new exception. The creative approval SOP repeats only the changed checks for a quick copy fix to a live ad, and the error procedure described below sends a correction through the fast lane, adding the compliance reviewer where the correction touches a claim or a price. Fixes of this kind are spelling and punctuation that change no meaning, claim, number or name; a resize or crop for another placement that leaves what the asset shows and says unchanged, made on a new version rather than by the channel owner, though an asset that carries a claim, a price, an offer or an endorsement, or concerns a regulated product, keeps its compliance check unless the team's written procedure says a pure resize may skip it; a swap to another approved asset whose rights still run on the date it will appear, as the asset libraryThe single home for approved marketing files, holding one current copy of each with its version, rights, expiry, alternative text and usage notes. records them; a broken link pointed back at the approved destination; and a scheduled date moved within the campaign window where nothing in the work refers to the date.
A list of fixes that skip even the approver's confirmation applies only where the team's own written procedure says so explicitly, the same condition the creative approval SOP sets for skipping the compliance check on a resize. The handover after launch is one such written list, and media money has another: the tutorial on managing a media plan while it runs writes down before launch which moves a planner may make alone and which go to the budget holder, and the guide to setting spending authority shows how to write the delegation behind those moves with finance, which sets the limits. Anything not written down goes to the approver. When a visible problem stood for days because the monitor did not know the limits written at handover, or no limits had been written, the diagnosis of live campaign problems found too late shows how to tell that cause from the other ways a live problem goes unseen.
Some approvals are stricter, and the stricter rule wins. A customer who approved a case study sees every later change, however small, before it is published. A partner in a joint campaign approves again whatever carries its name when the offer, the creative or the form changes, which is why the co-marketing launch checklist is run again after a late change. Copy that changes once a web page is being built goes back to its approver under the procedure for publishing a web page. And under the email campaign send procedure, an email's final test goes back to its approver whenever anything in it changes, because that approver signs off both the finished email and the people it will go to.
The distinction between one-way and two-way doors helps decide how far the work is held back while a fix is confirmed. Work that is easy to undo, such as a scheduled post or a running ad, can stay at its approved version until the approver confirms the fix. Work that reaches customers beyond recall gets no second chance: printed material and a sent email are impossible to reverse once out, which the framework treats as the mark of a one-way door, so nothing goes to print or to the list until the approver has seen the final version with the fix in it.
Who may ask for a change and who decides
A change request should travel the same way as the original work: on the work item, saying what should change, why, and on which version. Requests made in chat or at the end of a meeting can reach the build without anyone deciding them. The decisions that follow a request belong to different people.
| Decision | Accountable | Consulted | Informed |
|---|---|---|---|
| Accept the change at all: does the work still serve the signed brief? | The campaign owner | The requester | The builders |
| Does the changed element pass? | The reviewer whose scope the change touches, or the original approver for a small fix | The campaign owner | The other reviewers |
| Does the launch date move to make room for the review? | The campaign owner | The requester and the reviewer | Channel owners |
| May the live campaign change beyond the limits set at handover? | The campaign owner | The person monitoring it and the reviewer the change touches | The requester |
The RACI matrix is the method behind the table, with a single accountable role on each row, so that a change does not wait while two people each assume the other will decide. Seniority does not change the route: a senior stakeholder asks for a change like anyone else, the campaign owner decides whether it is accepted, and the reviewer whose scope it touches still decides whether it passes. A reviewer asking for changes outside their own scope is making suggestions, as the creative approval procedure treats them, and a reviewer who reopens their own approval records it like any other change.
Changes after launch
Launch hands the work to the person who monitors it, and the handover names what that person may change without going back through approval. Those limits are a written list of the kind described under small fixes, agreed before launch, and can include pausing ads that are not working, as the procedure for pausing underperforming ads sets out, and moving money within the limits the media plan set. Everything else follows the reviews above, and some cases have owners of their own.
- Edits to live copy and images become a new version that goes through the reviews the edit touches and is released from the library, never typed into the ad platform.
- Errors in live work are contained first through the procedure for responding to errors in live ads and pages. The correction is itself a change: it takes the fast lane through review rather than skipping it, and it is approved by someone other than whoever made the error.
- Published web content follows the house rules in updating and correcting published content, which separates a slip fixed quietly from an update, an open correction and a withdrawal. An open correctionA correction made visibly: the error is fixed, a dated note says what was wrong and what is right, and the correction follows the mistake to where it was seen. to approved content is still a change, so its new version goes back to an approver like any other.
- A claim that stops holding or a licence that ends is not an edit but a removal, and withdrawing an asset from every channel finds every copy before it is taken down.
- Changes to systems rather than to the work, such as tags, tracking and automated journeys, follow those systems' own change rules, which the automation governance guide sets out for live workflows.
Late changes before launch and during a freeze
Changes that arrive in the last days before launch put the rule under pressure: the launch date is close, the reviewer may have moved on, and the quickest route can be the edit nobody sees. When a late change reopens a review, the campaign owner has four honest choices: get the review done in time, move the launch date, launch the approved version and release the change as a second version once it has passed, or drop it. Launching the unreviewed change is not one of them.
Knowing from the team's own records how long each kind of review takes lets the campaign owner make that choice early rather than on the day. The launch check is where the rule holds. Run by someone other than the builder, as the workflow guide asks, it compares what is about to go live with the latest version on the work item's record, approved or confirmed as a small fix, and stops anything that matches neither; the campaign launch QA checklist sends a creative failure found at that point back through the approval chain rather than into a quick fix in the platform.
Late changes that keep arriving have causes further upstream. The diagnosis of campaigns that keep launching late traces work that returns for changes after review to build starting before the brief was signed, and the diagnosis of legal rejections finds the same cause behind a review held on an earlier version than the one about to go live, routing a later edit to a claim to the legal reviewer as well as to the brief's signatories.
Around a peak, a change freezeA set period around a peak when changes that are hard to reverse are stopped while routine, reversible work continues through an agreed route. holds back changes to systems that would be difficult to undo and lets everyday work continue through its normal route. Changes to the work itself still follow this guide during the freeze; a change the freeze covers but the business cannot wait for goes through the exceptions route in the tutorial on planning a change freeze.
Recording each change
A change is finished when the record says what changed, who decided and which version went live. The audit trailThe record, attached to the work item, of what was reviewed, which version, who reviewed it, when, what they decided and the evidence relied on. on the work item is the natural home, because it already holds the original approvals next to the work.
| What to record | Where it lives | Why it matters later |
|---|---|---|
| The request: what, why, which version and who asked | The work item | Shows the change was decided rather than slipped in |
| The decision to accept or decline, and by whom | The work item | Answers the question of who wanted it |
| The new version label, with the superseded version marked, not deleted | The asset library and the file name, as the creative approval SOP sets out | Only the current version is released |
| Which reviewer approved or confirmed which element of which version | The approval record on the work item | The approval audit compares it with what ran |
| A changed or replaced claim, other than a price | The claims library entry | Builders copy the approved wording instead of reusing old work |
| A change that moves the numbers, such as a new landing page or start date | The measurement change log | Analysts can explain a step in the data |
A broadband provider sorts its late changes (illustrative)
Quobarnel Broadband sorts its late change requests
Quobarnel Broadband, an invented regional broadband provider, launched a full-fibre package on paid social, search, a landing page and an email to existing customers. The previous quarter's approval audit had found 3 of 40 sampled live items that differed from their approved versions, one of them an ad whose price was edited in the platform.
This time the creative was approved by brand, the price and contract terms by legal and the commercial owner, and the email's audience by the data protection lead 12 working days before launch. In the last 6 working days, 11 change requests arrived. The campaign owner moved each onto the work item and sorted it against the approval matrix. Four were typos, resizes of images carrying no claim, price, offer or endorsement, and a corrected link, made on new versions and confirmed by the original approvers through the fast lane with only the changed checks repeated. Two swapped hero images for other approved images in the library with rights running to the end of the year, and brand confirmed each swap the same way. Two repeated earlier requests and were closed.
The commercial team asked to add people who had registered interest in full fibre on the website to the customer email. A new audience is a trigger in the matrix, so among the specialist reviews the request reopened only the data protection lead's review of the audience; the lead checked the added contacts against the consent records and policy and approved version 4 of the send within 2 working days. Sales asked to add "the fastest broadband in the region", for which no evidence was on file, so the campaign owner declined it for launch and sent it to the claims route. On launch morning a director asked for a new headline with no claim in it; the campaign owner accepted it, and brand approved it within the hour.
The email was treated as a one-way door: after the audience change, its approver signed off the final test and the new segment count again before the send. After launch, the person monitoring the campaign paused 2 weak ads within the limits set at handover and, on the campaign owner's decision recorded on the work item, switched off headlines the ad platform had generated from the landing page. The next quarter's audit sampled 40 live items and found none that differed from its approved version.
Common mistakes
- Treating approval as permission to keep editing. Approval covers one version. Every later edit is a new version, and the record should show what happened to it.
- Sending every change back through every review. Reviewers drown in trivia and people stop asking. Send small fixes to the approver and reopen a specialist review only where the change touches its scope.
- Editing approved copy in the ad platform. The change leaves no approval behind it. Make a new version and release it from the library.
- Rewording an approved claim slightly. A changed word is a new claim. Take the wording from the library or send the new wording, with its evidence, for review.
- Changing work a customer or partner approved without asking them. Their approval covered the version they saw. Send every change back to a customer, and any change to the offer, the creative or the form back to a partner.
- No limits written at handover. The person monitoring a live campaign then changes nothing, or anything. Write down what they may change without fresh approval.
- Forgetting changes the team did not make. Platform enhancements, partners' copies, translations and updated templates change approved work too.
- Deleting the old version. When someone asks what ran, the superseded version is the answer. Mark it, keep it.
- Deciding legal questions in the team. Whether a changed claim or offer is acceptable is for the reviewer and your legal advisers; this guide only routes the change to them. The governance hub shows how this sits beside approvals, audits and the freeze.
