Use Grow → Content to review a saved brief, a channel output, or a social variant before it moves toward delivery. A useful review checks the message, facts, audience, destination, and requested next step—not just whether the copy reads well.
Each brief, output, and variant has its own approval. Approving the brief does not approve all of its outputs, and approving a social output does not approve every account variant. Approval records the saved revision you reviewed; it does not publish or schedule the content.
Find the work and confirm your role
Open Content and choose All content if you want to review across channels. Use More filters → Awaiting my review to find work assigned to you, or filter Editorial stage to Needs review for a broader view. Check the channel, planning horizon, and other filters if the list looks empty. See Planning content across channels for view and filter controls.
Open the item and check who owns the work and which outputs need review. The brief and individual outputs can have their own Owner ID and Reviewer IDs. These fields use admin user IDs; reviewer lists are comma-separated. Ask your administrator for the correct identifiers instead of entering display names.
Reviewer assignment helps organize the work. It does not grant approval permission. Editing, approving, and scheduling are separate permissions, so someone may be able to review without being able to change the draft. Ask an administrator to check feature access when the required controls are missing.
Agree on the review scope: the shared idea, a specific channel output, or a particular social account's version. For example, approving a workshop announcement's brief confirms the message; the email invitation and each social variant still need their own checks.
Save and send the right version for review
Before submitting work, finish the edits and save each part with its own control:
- In Brief, select Save brief.
- In Deliverables, use Save output for the edited channel output.
- For edited social variants, use Save variant on each version.
Wait for the save result. Send for review and approval actions work with saved content; they do not save unfinished text in the editor for you.
To request review of the shared brief, select Send brief for review near the item heading. For an output or variant, select its Send for review button in Deliverables. Check that the relevant work is now at Needs review.
Set the reviewers before submitting so the work is assigned clearly. Sending one part for review does not submit every other part. If you started from a Brainstorm idea, accepting that idea is a separate decision; see Turning a saved idea into content.
A review button may disappear when that part is already awaiting review or approved. Check the displayed stage and approval state before trying to submit it again.
Review the brief, output, and destination
Start with the brief so you understand the purpose. Check Core thesis, Audience promise, Why now, Desired outcome, and CTA intent. Resolve contradictions or missing decisions before approving the wording built from them.
For each output you intend to approve, check:
- Message and audience: does this version deliver the promise in the brief, in language suited to its readers?
- Facts and evidence: are dates, prices, product details, names, and claims correct and current? Can a teammate find the supporting reference?
- Destination and next step: do the links, account choice, and call to action lead to the intended place?
- Channel fit: does the length, structure, and tone suit a blog, email, video, or social post?
- Completeness: are placeholders, unconfirmed promises, and unfinished instructions resolved?
For social content, inspect the copy and account details on each variant. Do not assume that a correct main draft means every variant uses the right link, date, or account.
If Strategy changed appears, review the strategy before proceeding. Keep snapshot records a decision to retain the saved strategy context. Rebase updates that context and can invalidate approvals. Use Keeping strategy plans current when the underlying plan needs attention.
If the output names another workspace as its owner and offers an Open … link, follow that link. After a handoff, the publishable content is edited and reviewed in its destination, such as Site → Blogs, Email → Campaigns, or Calendar. The Content snapshot is read-only for that copy, even though some coordination fields remain editable.
Approve the exact revision you checked
When the content is ready:
- Confirm that the latest edits have saved and that you have read that saved version.
- Choose the relevant control: Approve brief for the shared brief, Approve revision for a channel output, or Approve for a social variant.
- Wait for the success message, then check the approval state for that same part.
- Open Activity & review → Approval history and verify the target, revision, approver, time, and whether the approval is Current or Stale.
- Repeat only for the other outputs or variants you have actually reviewed.
An output shows Approval current when its approval is valid. Do not rely only on the item-level Approved label: the email, blog, and social variants can have different review states.
Moving a card on the Workflow board is not an approval action. Use the explicit approval control for the content you checked.
Approval does not complete scheduling, sending, or publishing. Those actions have their own permissions and readiness checks. A current approval also does not prove that a link works, an account is connected, or a destination has accepted the content; verify those details in the appropriate workflow.
Request clear changes and review the revision
For work at Needs review, use the Review note field next to the relevant review controls. Name the problem and the change needed. For example: “The email says the workshop starts at 10:00, but the approved event page says 10:30. Correct the time and check the social variants against the same page.”
Select Request brief changes for the brief, or Request changes for the output or variant. The button requires a non-empty note. Check the success message and the Needs changes stage on the affected part.
A change request removes the target's current approval. Make sure the owner has the feedback and knows which version needs work. Activity & review records the change-request event, but its activity list is not a full comment thread; keep detailed review discussion available to the person making the changes.
The author should make the correction, save the affected brief/output/variants separately, and send the revised work for review again. Recheck the changed facts wherever they appear. Correcting the email does not automatically correct a social variant.
If an author and reviewer are the same person, the controls still depend on their permissions. Agree on any second-person review your team requires; assigning a reviewer alone does not enforce that working arrangement.
Handle changed or stale approvals
Material edits can invalidate approval. Changes to a brief can also affect approvals for outputs still managed in Content. After saving, inspect the relevant output or variant again rather than assuming the earlier approval survived.
In Activity & review, expand Revisions to see the saved snapshot, change note, and changed fields. Approval history retains earlier decisions and marks invalidated approvals Stale, with a reason. Use that history to identify what needs another review.
The approval fails because the target changed. Someone saved a newer revision after you loaded it. Preserve any unsaved text, use Reload saved version, and review the new content before approving again. Do not retry blindly against a version you have not read.
A save leaves the output unapproved. Recheck its current revision and approval state. Saving can require a fresh review even when you expected a small administrative update. Finish related edits before recording the final approval.
Request changes is missing. The control is shown for work at Needs review and requires approval permission. Check the stage, your access, and whether the output is now owned by another workspace. For approved work needing correction, coordinate the edit with its owner and review the resulting revision.
Archived work cannot be approved. Restore the item and any archived output or variant you intend to use, then review it in its current context.
Protect from AI is enabled. This protects an output from batch AI replacement; it is not an approval and does not prevent ordinary human edits. Continue to check revision and approval state after changes.
A handed-off output changed elsewhere. Open its destination and review the actual publishable record. Returning to the Content brief and approving it again does not approve that destination's new copy.
Before handing work to the person scheduling or publishing, confirm exactly which saved outputs and variants are approved and identify anything still awaiting changes. Leave the remaining work visible rather than treating the whole item as finished.