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 Data Protection Officer
Scheduling is documented as a working surface: a visual calendar with content categories, CSV uploads and a bulk post editor, evergreen resharing with expiry dates, Reels, Stories and Shorts, per-category UTM parameters, and best-time suggestions drawn from the account's own historical performance. When a post fails, the documented behaviour is a fallback to a mobile reminder rather than a surfaced platform error with one-click recovery, so this sits below the top band. 1 4 7 9 8 1