Skip to content

Agencies

Content operations for agencies: approval belongs to a version

“Approved!” in a comment thread, then two more rounds of changes, then the wrong file goes live and everyone points at the thread. We build content operations where every asset carries its brief and every version, approvals are tied to the exact version and the person who gave them, and nothing ships on an approval meant for something else.
Start a projectSee three review rounds ↓
C-22 · dental group · spring campaign bannerv2first layout, offer headlineClient: “Love it, approved.”v3headline changed after legal reviewInternal review: passedthe v2 approval doesn't carry to v3sent to the named approverApproved v3 · client marketing director✓ Released: v3approval and version on file

Approvals in threads, or approvals on versions

Approvals in threads

  1. 01Feedback across email, chat and the review tool
  2. 02“Final_v3_FINAL” in a shared drive
  3. 03An approval that meant an older version
  4. 04Nobody sure who on the client side can sign off

When something goes wrong, the argument is about what was approved, not how to fix it.

Approvals on versions

  1. 01Every asset with its brief, versions and feedback in one place
  2. 02Each decision tied to a version and a named approver
  3. 03Changes after approval go back for approval
  4. 04Only approved versions can be released

The record settles the question before anyone has to ask it.

Every asset carries its record

Client and briefC-22 · spring campaign briefwork never lands in the wrong client's folder
Every versionv1, v2, v3 with what changedanyone can see how it got here
Feedback, by versionlegal note on v2comments don't drift onto the wrong file
The approverclient marketing directorthe right person signs off, every time
The decisionapproved v3, with daterelease only from an approved version

Three review rounds, handled properly

Banner v3 changed after v2 was approved

  1. v2 approved

    by the client's marketing director

    done

  2. v3 created

    headline changed

    done

  3. Approval carried over

    approvals belong to one version

    not used

  4. v3 approval

    sent to the same approver

    with the approver

Nothing ships on an approval meant for a different file.

A good fit if approvals live in email threads

Good fit

  • Many assets in review at once, across several clients.
  • Clients have more than one person giving feedback.
  • A wrong version has gone live, or nearly did.

Not the right fit yet

  • One or two clients with a single decision-maker each.
  • You want AI content published without human review. We won't build that.

Related

End the “which version was approved?” argument

Show us how an asset goes from brief to live today. We'll show you the review flow we'd build around it.

Start a project