Reviews and approvals

A review bundle groups drafts behind a shareable review link. Use it for a campaign, a weekly content batch, or a client review round.

1. Prepare the drafts

Create posts with --action draft, then list the drafts for the relevant accounts:

simplified posts:list-drafts --accounts "ACCOUNT_ID"

Copy the draft IDs you want reviewed. Use draft identifiers, not scheduled-post or account IDs. See social publishing for creation and editing examples.

2. Create a bundle

simplified review-bundle:create \
  --title "Autumn launch — first review" \
  --description "Please review the captions and visuals before we schedule." \
  --draft-ids "DRAFT_ID_1,DRAFT_ID_2"

Read the response and save the bundle ID and linkToReview. Share that link with the reviewers through your usual review process. Creating a bundle does not send the link to them automatically.

You can also create an empty bundle by omitting --draft-ids, then add content as it becomes ready.

3. Add more drafts

simplified review-bundle:add-drafts \
  --bundle-id "BUNDLE_ID" \
  --draft-ids "DRAFT_ID_3,DRAFT_ID_4"

Adding drafts is idempotent: IDs already in the bundle are skipped rather than creating duplicate entries.

4. Make revisions

Use the feedback to update the relevant drafts:

simplified posts:update-draft \
  --draft-id "DRAFT_ID_1" \
  --content "The revised launch caption."

Check the revised content in Simplified and complete the review there. The CLI exposes bundle creation and adding drafts; it does not provide commands for recording a reviewer’s approval or querying a bundle’s approval status.

5. Move approved content into the publishing plan

Finish scheduling the reviewed drafts in Simplified, or use the social publishing commands for your approved payloads. Creating a new scheduled post from approved copy creates a separate post; it does not convert or delete the original draft. Keep your review and publishing records aligned to avoid scheduling the same content twice.