Write the business or creative outcome in one sentence. Name the audience and the problem the month's work should help them solve. Choose your content themes from that purpose, rather than filling a grid with unrelated ideas.
Buffer's planning guide starts with goals, audience, content pillars and channels before choosing a posting cadence. Use those as planning inputs, then set your own manageable frequency. More dates do not automatically produce better work.
Give each recurring series a channel, theme and owner. A weekly answer to a customer question might sit beside a fortnightly project story and a month-end reflection. Decide what makes each series useful before expanding its dates.
This desk turns the cadence you enter into actual dates with rrule. It supports selected weekdays, intervals and positive or negative month days. A monthly day 31 is skipped in months without that date; day −1 means the last calendar day. Exclude dates deliberately when the regular pattern does not fit.
Write the complete copy or brief for each planned occurrence. Point to the asset, name the reviewer and keep the review note beside the post. A date with an empty brief is still an idea. A checkbox is a declared decision, not proof that another person approved it.
Asana's template organizes platforms, creative assets and schedule, with shared work and review. That is a useful reminder to track the work behind the date. Before publishing, check facts, permissions, accessibility and the channel's actual composer in the system you use.
The desk below prepares a portable plan. These documented products serve different parts of the work; the summaries are based on official pages reviewed October 5, 2026, without a signed-in trial.
Buffer / Publishing
Buffer describes a calendar with channel views, drafts and scheduling. Its current calendar page distinguishes account-free draft planning from scheduling, which requires an account and a connected channel. Use the actual publishing workflow when dates need to become scheduled posts; check the permissions and supported post format.
Asana's social calendar template brings channel, asset and schedule fields into team work, alongside assignment and review. It helps manage the making of a post. A task's date and status are separate from confirmation that the post was published on a social channel.
Storyflow's current page describes a canvas with content pillars, post briefs, references and AI-assisted arrangement. It explicitly says it does not schedule, publish or measure posts on social platforms. Current standalone access is paid early access, with a Free plan announced for later in 2026; check current pricing before choosing.
Expand the recurrence you enter, keep per-date briefs and exclude exceptions. The calendar download contains separate all-day planning events for this reviewed month. It does not schedule posts, set a best posting time, send invitations or claim that content was published.
Choose a month and add a recurring series, or load the example.
Ready here means the entered brief, asset reference and reviewer are nonempty and the author declared approval. The tool does not inspect the asset or authenticate a reviewer. Dates are all-day planning dates, with no time-zone conversion. Source JSON preserves excluded and out-of-month detail records; reviewed exports label those records separately. Inputs stay in browser memory; refresh clears them.
A worked month, with room to change.
The example is an original demonstration, not a recommended universal cadence. For October 2026, an education series on Mondays and Thursdays creates nine dates. Excluding October 12 leaves eight. A separate last-day reflection adds October 31, producing nine planning slots in total. Only October 1 has a complete declared review in the example; eight remaining slots still need their own briefs and decisions.
To adapt it, change the month, anchor and weekdays. Open each occurrence and write its own copy and asset reference. If a launch or absence changes a date, exclude the original slot with a note. Keep an out-of-month detail record until you decide where it belongs; moving the month does not erase the source text.
At handoff, export the reviewed plan, then enter appropriate times, destinations and channel settings in your publishing system. Review the actual post preview and delivery state there. This desk's calendar events are reminders for planning, not evidence of publishing.
Does the calendar file publish my posts?
No. It creates all-day planning events for the reviewed month. Publishing still requires your chosen channel or scheduling workflow.
What happens to a monthly date that does not exist?
A cadence for day 31 skips months without day 31. A negative day counts backward from month end: −1 means the final calendar day.
Does a ready label prove the client approved the post?
No. It reflects filled brief, asset and reviewer fields plus the author's declared approval. No reviewer identity, asset contents or external approval is verified.
Method: original planning guidance, official product documentation and an independently tested recurrence desk. Calendar format: RFC 5545. See library and privacy notes.
