Skip to main content
Approval is the step most often improvised under deadline, which is why it needs to be written down before the deadline. Follow the general workflow below. The two specialist reviews have their own pages: brand approval and legal review.
Fill in the tables below once, as a team. The rest of the page describes how the process runs regardless of who you put in them.

What needs approval

Not everything does. Approving everything is how approval becomes a rubber stamp, and how the things that genuinely need scrutiny get the same three seconds as a social caption. The pattern worth keeping: approve the thing that is new. Reusing cleared claims and approved assets inside an existing brief is production, not a new decision. The same logic covers the drafter: reviews attach to the work and its claims, not to who or what produced it, so AI-drafted work routes through exactly the reviews its human-drafted equivalent would, no more and no fewer.

Who approves what

A named backup matters more than it looks. A single approver with no backup means every holiday is a freeze.

The order

1

1. Approve the brief, not the output

The cheapest approval is on the brief, before anything is produced. A concept rejected at brief stage costs a conversation. The same concept rejected after production costs the production.
2

2. Produce

No approvals happen during production. If the brief changes mid-flight, the brief gets updated and re-approved, rather than the change being carried in someone’s memory.
3

3. Run the specialist reviews in parallel

Brand and legal review the same version at the same time. Running them in sequence doubles the wait for no benefit, since they check different things.
4

4. Consolidate feedback into one round

One point of contact collects every reviewer’s notes, resolves contradictions between them, and sends a single set back. Reviewers do not brief the producer directly. Collecting and collating is clerical and can be a builder’s; resolving a genuine contradiction between reviewers is the owner’s.
5

5. Final ship approval

One named person confirms the final version is the approved version. This is the step that catches the file that was revised after approval, and the version comparison itself is a check a builder runs better than memory does: the person confirms against the builder’s diff.

Revision rounds

Agree the number in the brief. Two rounds is a common default: one substantive, one for corrections. Rounds are consumed by feedback, not by time. Work that comes back with contradictory notes from three reviewers has not used a round; it has failed step 4.

When an approver doesn’t respond

Silence is the most common failure in any approval process, and it needs a stated answer rather than a norm people guess at. The turnaround clock is watched by a scheduled pass, not by memory: when it runs out, the escalation below fires. E.g. If a reviewer doesn’t respond within the turnaround above, the campaign owner escalates to the backup. If the backup doesn’t respond, brand and budget approvals default to approved and the campaign owner notes the exception on the brief. Legal review never defaults to approved.

What gets recorded

  • Who approved, and which version they approved.
  • The date.
  • Any condition attached to the approval.
  • Any exception taken, and why.
Record it on the brief in the relevant library, not in a message thread. The question “was this approved?” arrives months later, from someone who wasn’t there.

Exceptions

Urgent work still goes through the same reviews, compressed. What changes is the turnaround, not the list of reviewers. Skipping legal because something is urgent is the case that costs the most.
Type: process
Domains: approval, legal, brand
Provides: process:approval, approval-route
Uses: checklist-prelaunch, checklist-review, glossary, legal-triggers
Hands off to: process:brand-approval, process:legal-review
Triggers: “Does this need approval?” · “Who needs to sign off on this?” · “Send this for approval” · “The reviewer hasn’t responded” · “Record the approval”Asks, in order:
  1. What is it, and what’s new in it vs. already approved material? Options: approval-route. Skip when: asset and its brief are attached.
  2. Which version is the one that will ship? Options: your answer. Skip when: single version.
Output: Routing decision (which reviews, approver, backup, turnaround) from the team’s table; consolidated feedback round; approval record (who, version, date, conditions, exceptions) on the brief; escalation when turnaround lapses.

Get the complete Marketing OS

Subscribe to Snow Doughnut, our free weekly newsletter, and get the Notion workspace where you do the work: tasks, a marketing calendar, name generators, briefs, and more.

Have us run it for you

We implement this system, use it to help you grow and scale, then hand it all off to you when you’re ready.
Last modified on November 2, 2026