Approving, requesting revisions & feedback

How owners review work, leave per-strategy feedback, and reject vs request a revision.

This page is for reviewers — workspace owners (and platform admins) whose job is to read submitted campaigns and either approve them or send them back with feedback. If you're a member submitting work, you want Submit a strategy for approval instead.

Who reviews
Workspace owners (and platform admins)
Where reviews happen
Sidebar → Approvals (the inbox)
Two outcomes
Approve · Request revision (with feedback)
Notifications
Submitter is emailed on both outcomes

Approval isn't a rubber stamp. The reviewer's job is to confirm the AI-generated strategy is on-brand, on-brief, and ready for the intended audience — and to provide specific feedback if not.

The reviewer's inbox

Where pending campaigns appear

When a campaign is submitted, an item appears in your Approvals inbox (sidebar — the count badge tells you how many are waiting). The item shows:

  • The campaign name, objective, and the company it belongs to.
  • Who submitted it and when.
  • Every strategy run in the campaign at submission time.
  • The submitter's note (if they left one).

Click in and you can read each strategy in full, exactly as the submitter sees it.

How to review

Reading the work

For each strategy run, read for:

  • Brand fit — does it sound like the brand? Use the right words? Avoid banned ones?
  • Strategic soundness — does the logic hold? Does the recommended approach actually serve the campaign objective?
  • Specificity — does it commit to real audiences, real channels, real numbers — or hedge into vagueness?
  • Factual accuracy — any claims that need a citation or a sanity check?

Two outcomes

Approve, or request a revision

  1. 1

    Approve

    Click Approve. The campaign flips to Approved. The submitter gets an email immediately. The campaign is now ready to bulk-export every strategy run as a PDF from the campaign journey.

  2. 2

    Request revision

    Click Request revision. You're prompted for feedback — required, not optional. Two layers:

    • Top-level reviewer comment — applies to the campaign as a whole.
    • Per-strategy-run feedback — leave a note on specific strategy runs that need work, so the submitter knows exactly what to regenerate.

    Save. The campaign flips to Revision requested and the submitter is emailed with your feedback inline.

If a revision comes back

The submitter regenerates and re-submits. A new approval cycle is created — the previous one stays as history. Your inbox shows the new submission as a fresh item; the campaign's approval history shows every cycle the work has been through. Useful for auditing what changed between v1 and v3.

Roles

Only workspace owners and platform admins can approve or request revisions. Members and viewers see read-only versions of the inbox. The reviewer cannot approve their own submissions — even a workspace owner who's also the submitter needs someone else to sign off (or they need to wear both hats explicitly).

Related: Submit a strategy for approval and How campaigns, strategies & approvals link up.