Social Media Planner

The social planner is a publishing calendar with connected accounts behind it. You connect the client's channels once, then draft, schedule and publish from a single view instead of logging into each platform in turn. Everything that has been published, is queued or is waiting for approval sits on the same calendar, which is usually the first time a client has seen their own output laid out as a plan.

The mental model is one piece of content, many destinations, each with its own rules. A post is drafted once and then adapted per channel: different character limits, different image ratios, different link behavior, different tolerance for hashtags. The planner makes the adaptation easy to forget, which is why the per-channel preview matters more than the editor.

It is worth being clear about what the planner is not. It is a scheduling and publishing tool, not a social inbox and not an analytics suite. Comments and direct messages belong to the conversations module where those channels are connected, and the numbers it reports are whatever each platform's connection chooses to return.

Connected channels

• Facebook Pages and Groups, Instagram professional accounts, LinkedIn personal profiles and company pages, X, Google Business Profile, Pinterest, TikTok and YouTube where each platform's API permits publishing
• Multiple accounts per platform, grouped per location or per brand
• Which user in the account owns each connection, and the re-authorization reminders when a token expires
• Default channels selected for a new post, so the common case needs no thought

Composing a post

• A single draft adapted per channel, with per-channel text overrides rather than one shared caption
• Images, galleries, video and link previews, with aspect-ratio guidance per destination
• First comment, hashtag sets and mentions where the platform supports them through its API
• Link handling, including a branded short link and tracking parameters for attribution
• Per-channel preview, which is the only honest check that the post will look right
• Drafting and variation help from the AI content assistant, and image generation or selection from the media library

Scheduling

• Publish now, schedule for a specific date and time per channel, or add to a recurring queue of time slots
• A posting plan of weekly slots by channel, so content fills a cadence rather than being timed one post at a time
• Bulk creation by uploading a set of posts with their dates and captions
• Recurring and evergreen posts that republish on a defined cycle
• Timezone of the publishing calendar, set once for the account

Collaboration and governance

• Draft, pending approval, scheduled, published and failed states on the calendar
• An approval step so a client or manager signs off before anything goes out
• Internal notes on a post, and a change history of who edited what
• Per-user permissions covering who may publish versus who may only draft
• A media library of approved brand assets shared across posts

Reporting and reuse

• Published-post performance as each platform reports it: reach, impressions, engagement, clicks, follower change
• Comparison across channels in one view, with the caveat that each platform defines its metrics differently
• Export of the calendar as a content plan for the client
• Workflow connections, so a published post can be logged or a failure can raise an internal alert

1. Confirm the client's accounts are the right type before you connect anything. Instagram needs a professional account, Facebook publishing needs a Page with an admin, and a personal profile will not behave like a business one.
2. Have the client connect each channel themselves, logged in as the account owner, rather than using a staff member's personal login. A connection made through a departing employee's account dies with their access.
3. Record who owns each connection and when it will need re-authorizing. Token expiry is the most common cause of silent publishing failure.
4. Set the calendar timezone before scheduling a single post, and confirm it matches the audience rather than the agency.
5. Agree the cadence per channel with the client in plain terms: how many posts a week, on which days, roughly what time. Then build those as the recurring slots the queue fills.
6. Upload the approved brand assets to the media library first, so nobody is hunting for a logo at the point of posting.
7. Draft the first two weeks of content in one sitting. The planner's value is batch work; posting one at a time is no better than using the apps.
8. Adapt the caption per channel rather than publishing one text everywhere. Rewrite the opening line for each platform, and strip hashtags where they look amateur.
9. Check every image against the destination's aspect ratio, and look at the per-channel preview for each post rather than trusting the editor's layout.
10. Use a branded short link with tracking parameters for any link you post, so the traffic can be attributed back in reporting.
11. Turn on the approval step if the client wants sign-off, and agree how long they have to approve before a slot is skipped. An approval queue nobody clears stops the whole plan.
12. Set permissions so junior staff can draft but only a named person can publish, then verify by logging in as that junior user.
13. Publish one test post to the least sensitive channel and confirm it appears correctly on the platform itself, not just as published in the calendar.
14. Add a failure alert: a workflow or internal notification when a post fails, so a broken connection is noticed within hours rather than at the end of the month.
15. Agree who answers comments and messages, and where. If the channel is connected to the conversations inbox, say so; if it is not, the client needs to know they must still open the app.
16. Review performance monthly against the plan, not post by post, and be explicit with the client that each platform counts reach and engagement its own way.

The planner is the top of the funnel in most builds: it drives traffic to the pages, offers and booking links the other modules own. It pairs with the blog as the distribution arm of content, with funnels and forms as the destination, with reporting for the traffic it produced, and with the conversations inbox where a connected channel's messages can be answered beside every other channel.

Blog to social distribution

A blog article is published, and the planner schedules a set of posts drawn from it across the week (a quote, a statistic the client supplied, a question) each pointing at the article with a branded tracked link. Reporting then shows which channel actually sent readers, and the next month's plan weights that channel more heavily.

Offer launch across channels

A seasonal offer lives on a funnel page with a form and a booking widget. The planner carries a scheduled sequence of posts to the connected channels in the two weeks before it opens, with per-channel captions and the same tracked link. Form submissions tag the contact with the campaign, so the pipeline can show what the social effort produced rather than only what it reached.

Multi-location consistency

Each location has its own connected Page and Google Business Profile. A shared post is adapted per location with local detail and scheduled from one calendar, while a manager at each site approves their own version. The client gets consistent brand output without a head office writing every caption.

• Token expiry is the defining failure mode. Connections lapse when a password changes, an admin leaves, or the platform simply rotates its permissions, and posts then fail quietly. Check connections weekly.
• Each platform's API decides what is possible, not the planner. Stories, reels, carousels, first comments, tagging and some video formats are supported inconsistently and change without notice. If a format matters to the client, test it rather than promise it.
• Account type blocks publishing. Personal Instagram accounts, Pages without a proper admin, and profiles without the right business setup cannot be published to however correct the connection looks.
• One caption everywhere reads as lazy. The same text with the same hashtags on every channel is the clearest sign a business is scheduling rather than communicating.
• Aspect ratios crop ruthlessly. An image that looks right in the editor can lose a face or a logo on a platform that crops to square or portrait.
• A failed post usually fails silently. Nothing tells the client, and the calendar can show the slot as handled. Build an alert and check the platform itself periodically.
• The planner does not replace the apps. Comments, mentions, story replies, community management and most insights still live on the platform unless that channel is connected to the conversations inbox.
• Metrics are not comparable between platforms. Reach, impressions and engagement are defined differently by each, so a cross-channel chart is suggestive rather than authoritative.
• Approval queues stall the plan. If a client does not approve, the slot passes and nothing goes out. Agree a default, publish or skip, before the first lapse.
• Evergreen reposting ages badly. A recycled post about a past offer, an old price or a departed staff member reappears without anyone reading it again. Review the evergreen set quarterly.
• Scheduling is not a strategy. A full calendar of weak posts looks like activity and produces nothing. The plan should be judged on traffic and inquiries, not on slots filled.
• Deleting a post in the planner may not remove it from the platform. Once published, the post belongs to the channel; removing it there is a separate act.
• Link previews are cached by the platforms. Changing a page's title or image after posting often does not update the preview, and there is nothing the planner can do about it.
• Bulk uploads multiply mistakes. A wrong date column or a mismatched image set can queue weeks of bad content in one action. Review the calendar view after any bulk import.