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 Analyst
CSV bulk scheduling with per-row captions, media, post type and first comment, queue and interval modes, and bulk edit of hundreds of scheduled items puts the publishing machinery above the baseline, alongside thread, poll and video scheduling. The permissions table names a URL shortener but we found no public information on UTM rules for it, on per-network previews, on stories or reels, or on failure notification and retry when a post misses. 2 3 8