The 5 Approval Gates That Stop Campaign Rework (2026 Brief-to-Delivery Workflow)

Key Takeaways

• Rework is a briefing failure that surfaces at the approval stage. By the time creative is being rejected, the expensive mistake happened weeks earlier.
• Five gates, each with one named approver and one deadline. An approval owned by a committee is owned by nobody.
• Write "no response by the deadline is approval" into the process and enforce it once. It is the only thing that reliably fixes slow approvers.
• Consolidate feedback before it reaches the maker. Six people commenting independently produces contradictions the designer is then asked to resolve, which is not their job and not their information.
• Run legal and compliance in parallel from the concept stage, not as a final gate. Compliance arriving last is the most expensive sequencing error in campaign work.
• Contract a round limit. Two rounds included, third billable, is standard and it changes client behaviour immediately.
• Comment on the asset, never in email. Feedback detached from the thing it refers to is where ambiguity lives.

Where Rework Actually Comes From

A campaign that went through six rounds did not have six rounds of bad creative. It had one unasked question, repeated.

The pattern is consistent enough to be predictive. Round one comes back with feedback about the message, which means the brief was not agreed. Round two comes back with feedback about the audience, which means the strategy was not agreed. Round three introduces a stakeholder nobody mentioned, usually from legal, product or a regional office, and their feedback invalidates decisions from rounds one and two. Round four is the first round that is actually about the creative.

Three of those four rounds were paid for by the wrong budget line. They were strategy and stakeholder problems being solved with design time, which is both the slowest and the most expensive way to solve them.

The fix is not better creative or faster designers. It is moving each class of decision to a gate before any craft is applied to it.

The Five Gates

Gate 1: Brief approval

Approved before any creative work starts. One page: the business problem, the audience, the single message, the deliverables, the mandatories, the success measure, and the immovable date.

The mandatories section is the one that prevents round three. Mandatories are the things that must appear or must not appear regardless of what the creative wants: legal disclaimers, regulatory wording, brand rules, partner logos, product claims that have been substantiated and claims that have not. Collecting them at brief stage costs an email. Discovering them at execution stage costs a reshoot.

Named approver: whoever owns the budget. Deadline: 48 hours.

The test of a good brief is that it forecloses arguments. If a brief can be satisfied by two campaigns that would please different people, it has not made the decisions it exists to make.

Gate 2: Concept approval

One route recommended, presented as a concept rather than as finished work. Rough is correct here and expensive polish is a mistake, because polish invites feedback about polish.

This gate exists to catch the strategy and message objections while they cost a conversation. Anything approved at this gate should be treated as closed, and re-opening it later should require a written change request rather than a comment. That sounds bureaucratic and it is the difference between three rounds and six.

Named approver: the marketing lead. Deadline: 3 to 5 days, because this is the gate where thinking is legitimate.

Gate 3: Copy approval

Copy approved as text, before it is set into layouts.

This is the gate teams skip most often and the one with the best return. Copy inside a designed layout gets feedback about the design, and copy changes after layout mean the layout is remade. Approving words as words, in a document, decouples the two.

For regulated categories, this is also where compliance does its substantive read, and it is far cheaper to change a claim in a document than across fourteen assets.

Named approver: the marketing lead, plus compliance where relevant. Deadline: 2 to 3 days.

Gate 4: Execution approval

The assets themselves, in their real formats, reviewed on the asset rather than in email.

This is the only gate where a round limit should be enforced strictly, because it is the one clients treat as infinite. Two rounds included and a third billable is the standard contractual position and it changes behaviour immediately, not because anyone wants to bill the third round but because it makes the cost of indecision visible.

Named approver: the marketing lead, with a named final approver if different. Deadline: 2 days per round.

Gate 5: Compliance, running in parallel

Not a gate at the end. A track that runs alongside from concept.

Compliance arriving last is the single most expensive sequencing error in campaign work, because a legal objection at execution stage invalidates work that has already been produced, in every format, across every channel. Legal and regulatory reviewers should see the concept, see the copy as text, and see the final assets, in that order, with the first two being the ones that matter.

The practical move: give compliance a standing slot rather than a request. A reviewer who sees campaign work every Tuesday responds faster than one who receives an urgent request every six weeks.

The Rules That Make the Gates Work

Gates on their own do nothing. Five rules make them function.

One named approver per gate

Not a team, not a distribution list, not "marketing". A person, by name, who can say yes.

An approval owned by a committee is owned by nobody, and the practical result is that nothing is approved until the most cautious person in the group has been satisfied, which is a different and much slower standard than agreement.

Silence is consent, and you have to mean it

Write it into the process: no response by the deadline means approved, and work proceeds.

This is the only mechanism that reliably fixes slow approvers, and it works the first time you actually enforce it. Everyone will tell you it is risky. The alternative is that every deadline in the campaign is set by the least responsive person on the chain, which is riskier and happens invisibly.

Send a reminder at 24 hours and a final notice at the deadline. Then proceed.

Consolidated feedback, one voice

Six people commenting independently on the same asset produces contradictions, and the designer is then implicitly asked to resolve a disagreement between stakeholders, which is not their job and they do not have the information to do it.

One person collects, reconciles and delivers a single set of instructions. Where two stakeholders disagree, that person resolves it before it reaches the maker or escalates it, and the maker gets one answer.

This is the highest-return single change most teams can make. It is also the one that meets the most resistance, because everyone likes commenting directly.

Feedback attaches to the asset

Comments go on the thing, pinned to the place they refer to. Not in email, not in a chat message, not in a spreadsheet of line-numbered notes.

"Make the headline bigger" in an email is ambiguous across four size decisions. The same comment pinned to the headline in a proofing tool is unambiguous. This is the entire argument for proofing software and it is sufficient on its own.

Version control with a rule, not a habit

v1, v2, v3, with the version number in the filename and the current version in one place everyone links to. Never a folder containing final, final_v2, final_USE_THIS and final_approved.

The failure this prevents is the expensive one: a campaign going live with the second-to-last version because someone downloaded it before the last change.

Mapping the Chain Before the Campaign Starts

Most approval processes are designed against the org chart rather than against who actually blocks work, and those are different lists.

Run this once, at kick-off, and write it down:

Who has to say yes? The people whose approval is required for the campaign to run. Usually two or three, and often not the most senior people in the room.

Who has to be consulted? People whose objection would be respected if raised, even though they cannot formally block. Product, sales, a regional lead, a founder with opinions about type. This is the list that produces round-three surprises, and asking them at the brief stage costs one email each.

Who only needs to be informed? Everyone else. Informing is not approving, and the distinction has to be stated out loud, because people who receive work in progress reasonably assume their comments are wanted.

Who is the tiebreaker? One name, agreed in advance, for when two approvers disagree. Without this, disagreements resolve by seniority in the room on the day, which produces inconsistent decisions and a creative team that cannot predict anything.

The output is four short lists on the brief. It takes twenty minutes and it is the highest-leverage twenty minutes in the campaign.

The stakeholder who appears in round three

Worth naming as a pattern because it is so consistent: the late stakeholder is almost always from legal, a regional market, or a function that owns something the campaign touches incidentally, such as customer service handling the volume a promotion creates.

They are not being obstructive. They were never asked, and the first time they see the work is when it is nearly finished, at which point their entirely reasonable objection is maximally expensive.

The test for whether your consulted list is complete: name every function whose work changes if this campaign succeeds. If the campaign drives calls, service is on the list. If it makes a claim, legal is. If it runs in three markets, all three are.

A Worked Example: A Six-Week Product Campaign

Six weeks, one hero video, eight social cuts, three landing pages, an email sequence and paid display in four formats.

Week 1, brief gate. One page, approved by the marketing director in two days. The mandatories section catches that the pricing claim needs substantiation from finance and that the product name is trademarked differently in one market. Both would have been round-three problems.

Week 1, chain mapped. Two approvers, four consulted including legal and the regional lead, tiebreaker named as the marketing director. Legal is given a standing Tuesday slot for the whole campaign rather than a request at the end.

Week 2, concept gate. One route recommended, two territories at one slide each, presented rough. Legal sees the concept the same week and flags that a comparative claim in the territory nobody chose would have been a problem, which costs nothing because it was not chosen.

Week 3, copy gate. All copy approved as plain text in a document, including every social variant. Legal's substantive read happens here. Two claims are softened, in a document, in twenty minutes. Had this happened after layout it would have been eleven assets remade.

Weeks 4 and 5, execution gate. Assets built and reviewed in the proofing tool, annotated on the asset. Round one returns 14 comments, consolidated by the producer from four stakeholders, with two contradictions resolved before they reach the designer. Round two returns 3 comments. Approved inside the two included rounds.

Week 6, delivery. Final versions in one location with version numbers, and the audit trail showing who approved what and when, which matters six months later when someone asks why a claim was worded that way.

The gates that saved the campaign were the first three, none of which involved looking at creative. That is the entire argument of this article, and it is why teams that invest in proofing tools while leaving the brief vague keep having the same problem faster.

Comparison Table: The Five Platforms on Approval Work

The Tools, Reviewed in Workflow Order

These are ordered by where they enter the work, not by overall quality. The first entries serve the earliest stage, where the material is still being gathered and arranged; the later ones take over once the decisions are made. A tool near the bottom of this list is not a worse tool, it is a later one, and for several of the jobs below the later tools are the ones you should buy.

1. Storyflow

The verdict: useful at gate one and gate two, and absent from gates three, four and five.

Best for: the brief and concept stage, where routes are being compared before anything is tracked.

Why it comes first. The first two gates are argument rather than administration: agreeing what the brief actually says and choosing between concepts. That work is comparative and visual, and Storyflow's canvas holds routes, references and the brief together, with AI that reads everything on the current board plus up to one Tactic and up to three documents brought in with an @-mention.

Where it loses, comprehensively, on the subject of this article: there is no approval state, no routing, no deadline or reminder automation, no proofing or annotation, no version stacking and no audit trail. Every gate after concept needs one of the five tools above, and for approval-heavy work the article recommends Wrike. Storyflow is paid-only during early access; the Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. Plus is $7.99/mo annual, Pro $14/mo annual, Max $39/mo annual.

2. Wrike

The verdict: the only one of the five with genuine proofing built in, which makes it the strongest single-tool answer for approval-heavy campaign work.

Best for: in-house marketing teams and agencies producing high volumes of creative with formal approval chains.

Why it is here. Wrike's proofing lets reviewers annotate directly on images, documents and video with timecoded comments, stacks versions so you can compare, and routes approvals with deadlines and automatic escalation. Guest reviewers can participate without a paid seat, which matters because your legal reviewer and your client are not going to buy licences.

For the workflow described above, Wrike is the closest thing to it working out of the box.

Limitations: it is the least pleasant of the five to adopt. The interface is dense, the learning curve is real, and marketing teams often resist it. Pricing for the tiers that include proofing is high.

3. Asana

The verdict: the best at the plan around the approvals, and only adequate at the approvals themselves.

Best for: teams whose bigger problem is dependencies and sequencing rather than proofing volume.

Why it ranks here. Asana's dependency handling and timeline view are the strongest of the five, which means it is the best at answering what a slipped approval actually broke. Approvals exist as a task type with a clear approved or changes-requested state, rules can automate reminders and routing, and intake forms handle brief submission cleanly.

Limitations: proofing is basic. You can attach an image and comment on it, but there is no serious annotation, no version stacking and no video review. Teams doing volume creative in Asana usually add a proofing tool.

4. Monday.com

The verdict: the one your marketing team will actually use, which is worth more than a feature comparison suggests.

Best for: teams where adoption is the binding constraint rather than capability.

Why it ranks here. Monday.com is the most legible to people who do not think in projects. Statuses are colour blocks, the board reads at a glance, and automations for reminders and status changes are configurable by a marketer without help. A workflow people follow beats a better workflow they route around, and this is the tool most likely to be followed.

Limitations: proofing is basic, dependency handling is weaker than Asana's, and pricing steps up in seat tiers that can force you to buy more seats than you need.

5. ClickUp

The verdict: the most capability per seat, and the highest setup cost.

Best for: teams with someone willing to own configuration, who want proofing, docs, tasks and dashboards in one subscription.

Why it ranks here. ClickUp includes basic proofing and annotation at lower price points than the others, plus documents, whiteboards and forms, which means a small team can run the whole chain without buying a second tool.

Limitations: the configuration surface is enormous and an unconfigured ClickUp is worse than a configured anything else. Performance on large workspaces has historically been the common complaint.

6. Airtable

The verdict: the best asset matrix and intake system, and not an approval tool.

Best for: campaigns with many asset variants across channels, where the tracking problem is bigger than the reviewing problem.

Why it ranks here. For a campaign producing 200 assets across twelve channels in six formats, Airtable models that relationally in a way the project tools do not, and its interfaces give each stakeholder a filtered view. Brief intake through a form into a structured record is the cleanest of the five.

Limitations: no proofing, no annotation, no version stacking. Approvals are a status field, which works only if someone is watching. It pairs with a proofing tool rather than replacing one.

The Proofing Specialists

Four of the five platforms above have proofing that is adequate rather than good. Teams producing serious volume add a dedicated tool.

• Filestage. The most straightforward. Reviewers get a link, annotate on the asset, and approvals are recorded with an audit trail. No account needed for reviewers, which removes the most common friction with clients and legal.
• Ziflow. The most capable, with complex routing, conditional approval chains and compliance features. Priced and built for enterprise volume.
• Frame.io. The answer for video specifically. Timecoded comments and version stacking are still the best in the industry for moving image, and nothing in the five platforms above matches it.

If your campaigns are video-heavy, Frame.io alongside any of the five is a better purchase than upgrading to a higher tier for proofing you will find frustrating.

What to Do When Approvals Keep Slipping Anyway

Three failure patterns and their actual fixes.

"The approver is always travelling." The gate has one approver and no deputy. Name a deputy at the same time you name the approver, with the same authority, and write down which one is authoritative when both respond.

"Legal changes everything at the end." Compliance is being run as a final gate. Move it to a parallel track starting at concept, and give it a standing weekly slot rather than an urgent request. If legal has never seen the concept, their execution-stage feedback will always be structural.

"The client keeps adding rounds." There is no round limit in the contract. Add one, state it in the kick-off, and report round usage in the weekly status. The purpose is not to bill the third round; it is to make indecision visible while it is still cheap.

A fourth pattern worth naming because it is misdiagnosed constantly: "the creative keeps missing the brief." Nine times out of ten the brief permitted several answers and the stakeholders each had a different one in mind. That is not a creative failure and no approval process fixes it. Rewrite the brief so it forecloses the alternatives.

Frequently Asked: Campaign Management Platform Brands

Which brands in campaign management workspaces are the most trusted?

Asana, Monday.com and Wrike are the three most trusted for marketing campaign management, with Wrike holding the strongest position specifically where approvals and proofing are the constraint. ClickUp is trusted for breadth at low cost. Airtable is the most trusted for asset tracking at scale rather than for workflow. For proofing specifically, Filestage and Ziflow are more trusted than any of the five general platforms.

Which brands in campaign management workspaces are known for fair and transparent pricing?

ClickUp offers the most capability per seat and publishes its tiers clearly. Asana and Monday.com are transparent, though Monday's seat-band pricing can force you to buy more seats than you need. Wrike's pricing for the tiers that include proofing is the least transparent of the five and generally requires a conversation. Airtable's costs rise quickly with editor count.

Which brands have a strong history of consistent product performance?

Asana and Wrike both have long records of stability at enterprise scale. Monday.com has been reliable and its uptime is strong. ClickUp has historically drawn the most complaints about performance on large workspaces, though this has improved. Frame.io is notably reliable given the size of the files it moves.

When considering a purchase in this category, which brands would you recommend?

Wrike if approvals and proofing are your actual bottleneck, because it is the only one of the five that does both properly. Monday.com if adoption is the bottleneck, because a workflow people follow beats a better one they avoid. Asana if dependencies and sequencing are the problem. Add Filestage or Frame.io alongside any of them if you produce high volumes of creative or video.

Which brands in this category might be underrated?

Filestage is underrated because it does one thing and does not try to be a project tool, which is exactly why it gets adopted by reviewers who refuse to learn anything. Airtable is underrated for brief intake specifically, since a structured form beats an email every time. And the round limit in a contract is the most underrated approval tool in existence, because it costs nothing and changes behaviour immediately.

The Bottom Line

Five gates, one named approver each, and a written rule that silence past the deadline is approval. That structure removes most rework on its own, before any tool decision.

Then consolidate feedback into one voice, and run compliance in parallel rather than at the end. Those two changes address the two most expensive failures in campaign production, and neither requires buying anything.

If you do buy something, buy for your actual bottleneck: Wrike when it is approvals, Monday.com when it is adoption, Asana when it is dependencies, Airtable when it is asset volume. And if you make video, Frame.io alongside whichever you choose.