· 9 min
A social media content plan that survives the month
How to build a content plan that lasts past week two — rubrics, cadence, a two-week buffer of finished posts, and eight places to find ideas.
Most content plans die in week two. Not because they were badly made, but because they were made as a list of topics — and a list of topics has no answer to “what goes out on Thursday if the client still hasn’t sent the photos”. Below is a way to build a plan that survives those Thursdays, plus a template you can take and fill in today.
A plan is a schedule, not a topic list
A topic list says what you would like to write about. A plan says what goes out, when, and in which channel — and what happens if it doesn’t. One question tells them apart: using your plan, can you say how many posts are finished and ready to publish right now? If you can’t, you have a list.
A working plan answers four questions:
- which rubrics you run, and what each one is for;
- how many posts per week, and on which days;
- how many finished posts are sitting in reserve;
- who approves, and within what deadline.
The fourth is the one that gets skipped, and it is the one that decides your real publication dates. More on that below.
Step 1. Define your rubrics
A rubric is a recurring post type with a clear job. Not “useful stuff”, but “a breakdown of a mistake we saw at a client”. Not “about us”, but “how we actually do this”. The more specific the wording, the less time each next instalment takes to invent.
For most projects five or six rubrics work, split roughly like this:
- two selling — what you sell, to whom, and why it costs what it costs;
- two useful — answers to the questions people ask before buying;
- one human — people, process, behind the scenes;
- one reactive — industry news, replies to comments, whatever just happened.
More than six and half of them will run out of material. Fewer than four and the feed gets monotonous by week three.
Step 2. Set cadence and slots
Cadence is chosen by what you can sustain for three months, not by what you would like. Three posts a week that always go out beat seven that go out every other time.
A slot is a day and time locked to a rubric. Slots turn the daily “what do we post today” into “what fills Tuesday”, which has a default answer.
Cadence differs by platform and doesn’t transfer between channels. A follow-based Telegram channel takes three posts a week comfortably, while a recommendation feed tolerates a daily remark — as the Threads breakdown shows. How a slot turns into a published post is in Telegram auto-publishing setup.
The monthly template
Take this table and fill it in for your project. One channel, one table; with several channels the rubric rows usually match while the slots drift apart.
| Slot | Rubric | Week 1 | Week 2 | Week 3 | Week 4 |
|---|---|---|---|---|---|
| Mon 10:00 | Useful | ||||
| Wed 12:00 | Selling | ||||
| Fri 18:00 | Human | ||||
| Floating | Reactive |
Three filling rules that save the most time:
- Fill the slots first, invent the topics second. An empty cell is a request for an idea, not a reason to move the publication.
- The reactive rubric gets no fixed day. It gets a weekly quota: one post per week, day chosen as things happen.
- Fill the last week only halfway. Leave room for whatever the month brings.
What belongs in a cell
A filled cell is a small task, not a topic. Five fields are enough:
- the point — one sentence the reader should walk away with;
- format — text, carousel, video, poll;
- media — what is needed and from whom;
- draft deadline — the date the text is finished by;
- owner — one person, not a department.
The test: someone other than the person who invented the cell should be able to write the post from it. If they can’t, the cell holds a reminder, not a task.
What a filled week looks like
Say the client is a food delivery service, one Telegram channel, three posts a week.
| Slot | Rubric | The point | Media | Draft by |
|---|---|---|---|---|
| Mon 10:00 | Useful | Why orders take longer in the rain, and what to do about it | none | Wed, prior week |
| Wed 12:00 | Selling | A subscription beats three separate orders a week — the maths | screenshot | Thu, prior week |
| Fri 18:00 | Human | A courier’s day, first shift to last | 4 photos, from client | Fri, prior week |
Note the last column: drafts are finished a week before publication, and the photos were requested from the client earlier still. That offset is what makes a plan executable — not willpower on Friday evening.
Step 3. Eight places to find ideas
Ideas don’t run out because there are few of them. They run out because you look for them at the moment a post is due. Collect them continuously instead — these sources produce the most material.
- Questions asked in DMs and comments. The most underrated source: these are literally your audience’s queries, phrased in their own words.
- The sales team’s inbox. Objections repeat, and every repeating objection is a post — sometimes a whole rubric.
- Support tickets. A frequent question means an explanation is missing somewhere.
- Clients’ mistakes. People read a breakdown of someone else’s mistake more willingly than an instruction on doing it right.
- Internal documents. A checklist, a policy, an onboarding guide — almost a finished post that only needs human language.
- Comments under competitors’ posts. Not the competitors’ ideas — the comments: that’s where you see what people felt was missing.
- Seasonality and the industry calendar. Trade shows, reporting periods, season openings — all predictable, all schedulable months ahead.
- Your own analytics. A post that worked is worth rewriting from another angle a quarter later. That isn’t a repeat, it’s a second attempt at something that landed.
Put all of it in one place, with dates. Otherwise in a month you won’t remember why you wrote down “ask about the warehouse”.
Step 4. The buffer: a two-week rule
The buffer is finished, approved posts held in reserve. It is the single thing that separates a plan from a list of promises.
The working rule: at the start of the week you should have as many finished posts as the next two weeks will consume. The copywriter gets sick, the client goes away, the shoot falls through — the feed doesn’t notice.
Building the buffer hurts once: for two weeks you write double. After that it sustains itself, because you are permanently working two weeks ahead.
Step 5. Put approval into the plan
The publication date is not the date the post was written. Approval lives in between, and if it isn’t in the plan, the plan lies about your dates.
The minimum workable scheme:
- the post is ready five working days before publication;
- the client responds within two working days;
- one round of edits, a second only for substantive objections;
- no answer in time means either the agreed version goes out or the post moves to the next slot — and that rule is written down in advance, not argued about on the day.
How to agree on this with a client and what to put in writing: client content approval.
Three mistakes that break a plan
Planning from inspiration. “Next week we’ll do a big breakdown” is not a plan item — it has no size, no deadline and no owner. A plan item reads: “Wed 12:00, breakdown of the delivery mix-up, text by Monday, photos from the client, owner Ira.”
Scheduling a post where the material doesn’t exist yet. A slot that needs a video, with no shoot booked, is already a missed post — you just find out on the day. Material first, slot second.
Treating approval as instant. The most expensive one, because it moves a week rather than a post: the client answers three days late and the next three posts slide along behind. Hence the rule in step five — five working days is not paranoia, it’s the average length of the thread.
When there is more than one client
A plan for one client lives in a spreadsheet. A plan for five doesn’t, and here is why.
Each client has their own time zone. “Tuesday 10:00” in a shared sheet means different things for projects in different regions, and you discover the mistake after publishing.
Each has their own channels and cadence. A shared sheet either bloats past readability or erases the differences.
Each has their own approval cycle. One answers within the hour, another in three days; planning them identically doesn’t work.
Which gives a simple organisational rule: a separate workspace per client — its own channels, its own content plan, its own notes and its own approval link. That is how workspaces are built in Sonaco: a calendar with weekly and monthly views, drag-and-drop rescheduling, recurring posts and notes, tags and folders — all in that client’s time zone, not the browser’s.
How to tell the plan is working
A plan has two checks, both run once a month.
Consistency. Compare posts planned with posts published. Not “roughly the same”, but as a number: planned 12, published 9 — that’s 75%, and the three missing ones deserve an explanation. If you are consistently below 80%, the problem isn’t discipline, it’s cadence: the plan is too big and should be cut rather than enforced.
Engagement per rubric. Track ERR — reactions, shares and replies over views — but per rubric, not for the feed as a whole. An average ERR advises nothing. ERR per rubric says plainly: this one is read, this one needs replacing.
Look at the trend, not a single month. Three weeks down in a row is a signal; one weak post is noise.
A checklist before the month starts
Run it in the last week of the previous month — it takes half an hour.
- rubrics are written down, each with a stated job;
- slots are assigned, and the reactive rubric has a quota rather than a day;
- the four-week grid is filled, the last week only halfway;
- finished posts cover the next two weeks;
- approval deadlines are agreed with the client and written down;
- recurring publications are set up as recurring, not copied by hand;
- the month’s ideas are collected in one place and sorted into rubrics.
If any line is unchecked, the month starts by catching up. It is usually the fourth.