assess.one – AI-powered business operations platform

Workflow Template

Social Media Content Approval Workflow

Manages submission and review of social media posts: requester submits copy, channel, audience and creative assets; a brand reviewer checks content, optionally routes regulated claims to compliance review, then decides to approve (capturing schedule date and handing off for publishing), request changes (returned to requester for revision), or reject (closed with reason). Requester is notified on approval or return for changes.

Social posts stall when approvals happen over email, Slack, and spreadsheets, and regulated claims slip through without a compliance check. This workflow manages the full path from content submission through brand review, optional compliance review, and final decision — approve, request changes, or reject. Marketing requesters, brand reviewers, and compliance teams each work from the same record, so nothing gets lost between handoffs.

Business Outcomes

  • Reduces time spent chasing approval status across email and chat
  • Helps cut the risk of regulated claims going out without compliance sign-off
  • Speeds up the requester revision cycle with automatic notifications
  • Creates a clear audit trail of who approved what and when
  • Shortens the gap between approval and scheduled publishing

Workflow Steps

Steps

  1. 1
    Create Post Request Recordcreate record

    Registers the submitted post as a record for review.

  2. 2
    Set Status: Submittedupdate record

    Marks the post as submitted and awaiting brand review.

  3. 3
    Brand Reviewcreate task

    Brand reviewer checks the content, notes regulated claims, and records a decision.

  4. 4
    Set Status: In Brand Reviewupdate record

    Updates status to reflect the post is under brand review.

  5. 5
    Route on Regulated Claims

    Sends posts with regulated claims to compliance review before the brand decision is finalised.

    makes_regulated_claims: "true"→Set Status: In Compliance Review
    Default→Record Brand Review Decision
  6. 6
    Set Status: In Compliance Reviewupdate record

    Updates status while compliance reviews the regulated claims.

  7. 7
    Compliance Reviewcreate task

    Compliance reviewer checks regulated claims for accuracy and legal compliance.

  8. 8
    Persist Compliance Notesupdate record

    Saves compliance outcome and notes to the record.

  9. 9
    Route on Compliance Outcome

    If compliance requires changes, the post is returned to the requester instead of proceeding to brand decision.

    compliance_outcome: "Cleared"→Record Brand Review Decision
    compliance_outcome: "Needs Changes"→Set Status: Changes Requested
    Default→Record Brand Review Decision
  10. 10
    Record Brand Review Decisioncreate task

    Brand reviewer records the final decision: approved, changes requested, or rejected.

  11. 11
    Persist Decision Fieldsupdate record

    Saves the review decision, scheduled date, and rejection reason to the record.

  12. 12
    Route on Review Decision

    Routes the post to publishing handoff, back to the requester for revision, or to closure as rejected.

    review_decision: "Approved"→Set Status: Approved
    review_decision: "Changes Requested"→Set Status: Changes Requested
    review_decision: "Rejected"→Set Status: Rejected
    Default→End
  13. 13
    Set Status: Approvedupdate record

    Marks the post as approved and ready for scheduling handoff.

  14. 14
    Notify Requester: Approvedsend email

    Emails the requester confirming approval and the scheduled publish date.

  15. 15
    Set Status: Scheduled / Hand Off for Publishingupdate record

    Marks the post as scheduled and hands it off to the publishing process.

  16. 16
    Set Status: Changes Requestedupdate record

    Marks the post as returned to the requester for revision.

  17. 17
    Notify Requester: Changes Requestedsend email

    Emails the requester with review notes (and compliance notes if applicable) and asks them to revise and resubmit.

  18. 18
    Restart for Revisionrestart from step

    Restarts the workflow at brand review so the revised post can be re-reviewed.

  19. 19
    Set Status: Rejectedupdate record

    Closes the post as rejected with the recorded reason.

Fields

  • Requester Name*
  • Requester Email*
  • Post Copy*
  • Channel*
  • Target Audience*
  • Creative Assets
  • +8 more fields

Forms

Social Media Post Submission

7 fields

Data Views

All Post Requests

channel, audience, post_status, review_decision +1 more

Dashboard Widgets

Post Approval PipelinePosts by StatusPost Request Summary

Recommended integrations

Setup the following integrations to extend workflow capability.

  • Send email in the workflow

    AWS SES logoAWS SES
social media approvalsocial media content approvalpost approvalcontent workflowsocial media workflow

Similar Workflows

marketing content approvaldesign approvalcampaign approval

Similar Categories

marketing

FAQs

How do I set up this approval workflow for my team?

Publish the template in assess.one and it's live immediately — there's no setup project or waiting period. You can start submitting post requests right away and adjust steps, roles, and notifications as your team gets used to the process.

How long does it take to get this running?

Publishing the template takes minutes. Once it's live, your team can submit their first post request and start running approvals the same day, no separate implementation phase needed.

Can we customise the approval steps or add extra reviewers?

Yes. You can edit steps, add or remove reviewer roles, and change routing logic directly inside assess.one. This includes adjusting when compliance review triggers or adding an extra sign-off stage if your brand needs it.

Who needs access to this workflow?

At minimum you need requesters who submit posts, brand reviewers who check content, and a compliance reviewer for regulated claims. Access and permissions for each role are configured inside assess.one, so people only see the steps relevant to them.

How does the compliance routing decision work?

When a brand reviewer flags a post as containing regulated claims, the workflow automatically routes it to compliance review before it can move forward. Compliance notes are recorded on the record, and the outcome determines whether the post returns to brand review or continues toward approval.

What happens when a reviewer requests changes?

The post status updates to 'Changes Requested', the requester is notified automatically, and the request restarts for revision. This keeps the post moving without needing a separate follow-up email or manual reminder.

What happens after a post is approved?

Once approved, the reviewer captures a schedule date and the status changes to 'Scheduled / Hand Off for Publishing'. The requester is notified of the approval, and the record is ready to hand off to whoever manages publishing.

Can we track why a post was rejected?

Yes. Rejections require a reason, which is captured and persisted on the record before it's closed. This gives you a searchable history of rejected posts and the reasoning behind each decision.

Do we need any other software to run this?

No. The entire workflow, including notifications, runs inside assess.one. Any email or Slack notifications are configured within the platform, not through separate integration work.

Ready to use this workflow?

Create a free account and customise this workflow for your business.

Social Media Content Approval Workflow | assess.one