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 CSV import, queue-style slot filling with evergreen horizons up to a full year, per-network captions, a drag-and-drop calendar and grid planner, and a rejection alert with one-click retry plus a refresh-connection fix put scheduling in dependable territory. We found no public information on link shortening with UTM rules or previews matching each network's actual rendering, which is what separates the solid from the top band. 1 3 4 10 11