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 at 3am.
0 — One post to several networks at once with no per-network variation and no calendar.
3 — A calendar with scheduling and basic per-network text variants; failures are discovered by noticing the post never appeared.
5 — Per-network content, media and first-comment variants, drafts, a usable calendar with drag-and-drop, and failure notifications with a retry.
8 — Bulk upload and CSV import, evergreen or queue-based scheduling, link shortening with UTM rules, preview matching each network's actual rendering, and stories, reels or shorts supported where the API allows.
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 scheduling is the strong suit: a single CSV maps every row to a scheduled post with caption, media, post type and first comment, queues and intervals are supported, and hundreds of scheduled items can be updated, rescheduled or relabelled in bulk, with threads, polls and videos scheduled for X. But I found no public information on what happens when a post fails overnight — no failure notification, retry, per-network preview or best-time recommendation from the account's own history is evidenced. 3 2 1