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
Scheduling reaches ten networks from one dashboard, backed by an evergreen content library with categories and weekly time slots, bulk import, story and video scheduling, and Edgar Links with UTM parameters. What I could not find is any failure notification with a retry, and the timing guidance in the analytics copy reads as generic advice rather than best-time recommendations — for a corporate account, how a failed publish is surfaced is the part I need documented before trusting the queue. 2 4 5 6