Plan a month you can actually produce
Enter a niche, choose one or more platforms, set the total number of posts per week, and pick a start date. The generator creates a thirty-day plan with rotating prompts. It does not promise that these are the best days to post or that a particular sequence will improve reach. The useful output is a dated starting document you can edit around your real capacity, business priorities, and available material.
Frequency is shared across your selected platforms. Choosing three posts per week and three platforms does not mean nine weekly posts. Each row is one post for one destination. Read the platform column before exporting so you know how the total workload has been distributed. If you need several versions of one idea, add that production work to your own plan instead of assuming a row includes unlimited adaptations.
How the calendar is calculated
The date range includes the start date and the following twenty-nine days. Event count is your weekly frequency multiplied by thirty, divided by seven, and rounded to the nearest whole number. The tool then distributes those events evenly across the range. For event index i, starting at zero, its day offset is the whole-number part of i multiplied by thirty divided by the event count.
The platform rotates through your selected list. Content prompts rotate through Teach, Show, Answer, Compare, and Reflect. Your niche is inserted into each prompt as a topic. That is the entire generation mechanism. There is no hidden trend feed, audience model, account analysis, or external writing service. The prompts are intentionally broad enough for you to turn them into specific useful pieces.
The controls accept one to fourteen total posts per week and a niche of up to eighty characters. Missing platforms, an empty niche, or an invalid date produce an error rather than a partial calendar. Your choices remain in the browser. Downloads create local files; they do not connect a calendar account or grant publishing permissions.
Three worked examples
Example 1: Three posts per week
With three posts per week, the tool calculates 3 × 30 ÷ 7, or approximately 12.86, and rounds to thirteen events. Select Instagram and LinkedIn and the destinations alternate through those thirteen rows. One receives seven rows and the other six because the total is odd. That is a mechanical allocation, not a recommendation that the first destination deserves more effort. You can reorder or edit the exported plan to reflect your actual priorities.
Example 2: One post each day on average
Seven posts per week gives 7 × 30 ÷ 7, exactly thirty events. The day offsets become zero through twenty-nine, so there is one event each day. Select five platforms and each receives six rows. The five content types also rotate six times. This balanced arithmetic does not establish that your production workload is balanced: a short text post and an edited video may require very different effort. Add production time as a separate planning column.
Example 3: Two daily slots across a month boundary
Fourteen posts per week produces sixty events. The day offset formula assigns two events to each of the thirty dates. If your start date is January 25, the plan continues across the end of January into February. The calendar uses date arithmetic rather than adding numbers to the displayed day string. Both events on a date are all-day planning entries; the tool does not choose two publication times or imply that the destinations should be posted simultaneously.
Read prompts as assignments, not finished captions
“Explain one useful idea about small business design” needs a specific subject before it is ready for production. Replace it with something concrete, such as explaining how to prepare a readable price list. A Show prompt might become a walkthrough of an actual process you can document. An Answer prompt should answer a real question rather than inventing audience demand.
Review the sequence for repetition. The generator varies the prompt type, not the factual substance of your niche. If several rows would produce the same lesson, change the topic or remove a row. A smaller plan you can complete is more useful than a mathematically full calendar with no clear reason for each item.
What the two exports contain
The CSV contains date, platform, content type, and prompt columns. It quotes fields consistently and protects values that could be interpreted as spreadsheet formulas. That protection can add an initial apostrophe to a risky value; it is a safety measure, not part of the intended caption. Keep the planning spreadsheet separate from a polished publication draft.
The ICS export creates all-day events with stable identifiers and an end date on the following day. The following-day end is intentional for this format. Calendar data conventions should be checked against the specification when integrating with another system. [VERIFY: IETF — RFC 5545, DATE values, DTEND, escaping, and content-line folding — https://www.rfc-editor.org/rfc/rfc5545] Import into a test calendar first and inspect a few dates before importing a large plan into a shared calendar.
The most common mistake: counting rows instead of capacity
Thirteen rows can still be too much work if each requires filming, approvals, graphics, and several revisions. Add a production owner, draft deadline, approval deadline, and asset status to your spreadsheet. This is a recommended workflow, not a feature the generator secretly manages. The exported plan cannot remind a colleague to approve an asset unless you set that up in your own calendar or project system.
What the generator deliberately does not do
It does not publish, schedule social-platform posts, retrieve holidays, calculate audience time zones, or identify trending topics. It cannot check whether your planned material is original, accurate, or appropriately disclosed. It also does not store the calendar after you leave the page, so export a copy if you want to keep it.
Use the caption truncation previewer when a prompt becomes actual text and the export settings advisor when the asset is ready for preparation. If a client is paying for the plan, the brand-deal pricing guide helps separate the number of deliverables from revision, licensing, and approval obligations.
Questions you might have
Is posts per week per platform or in total?
In total across all selected platforms. Each row is one planned post assigned to one destination.
Will it publish or schedule the posts?
No. It produces a planning document and local downloads. It has no platform connection or publishing permissions.
Why are there thirteen rows for three posts per week?
The tool rounds 3 × 30 ÷ 7 to thirteen events, then spreads them across the thirty-day range.
Does it pick the best posting times?
No. Calendar entries are all-day planning prompts, not audience-derived timing recommendations.
Why does an exported event end on the next date?
The ICS uses an exclusive following-day end for all-day entries. [VERIFY: IETF — RFC 5545, DTSTART and DTEND — https://www.rfc-editor.org/rfc/rfc5545]
Will my plan still be here after I leave?
The tool does not persist the plan. Download the CSV or ICS if you want to keep it and review imports in a test calendar first.