Publishing & calendar
How this is scored
Scheduling across networks: per-network formatting, the calendar as a working surface, bulk operations, and what happens when a post fails.
0 — No publishing or scheduling; the product is a listening, analytics or inbox tool only.
3 — Posts scheduled to several networks from one composer, with a list or calendar of what is planned.
5 — A content calendar with scheduling across the main networks, per-network text and media variants, drafts, and post previews.
8 — Bulk upload or CSV import, queue or evergreen scheduling, best-time suggestions, link shortening with UTM tags, stories, reels or shorts where the API allows, and failure notifications with a retry.
10 — Publishing is dependable at volume: hundreds of scheduled items across many accounts without collision, best-time recommendations from the account's own history, and every failure surfaced with the platform error and a one-click recovery.
The Brand Governance Officer
Bulk operations are the documented story: up to 500 posts via CSV or a single API request, recycle mode for evergreen queues, optimal-time scheduling, and a drag-and-drop calendar with post previews and follow-up comments. Failures are surfaced with stated causes and a manual publish or reschedule path, and a post left unapproved by its scheduled date is marked failed rather than sent. We found no public information on link shortening with UTM tags or stories and reels support, which keeps this short of the dependable-at-volume tier. 4 5 6 10 13 1