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
The scheduler is real and the failure handling is unusually well documented: failed posts land in a failed/missed queue naming the board and the platform error, a red banner counts failures, and posts can be sent back to drafts and rescheduled, on top of bulk CSV upload, RSS-driven SmartPins and SmartSchedule queue spacing. What holds it down is the thin multi-network side: Facebook is reachable only as a single-photo cross-post of an Instagram post, and the vendor itself documents that an expired Facebook authorization lets that share silently fail with no notice in the app — exactly the kind of unreported failure a corporate account cannot afford. 2 3 6 7