Reuse the types, not the sentences. Every post still needs your own facts. If a week is busy, skip a slot rather than publish a hollow one. If something time-critical happens (a ship, a sold-out dish, a deadline), that post replaces the planned one.
This is a starting pattern, not a rule, and not a promise that a calendar will grow an account.
A four-week rotation (about 3 posts a week)
Week 1Monday: a process or method. Wednesday: a concrete example from work (anonymised or fictional and labelled). Friday: a narrow question, or a short observation.
Week 2Monday: a definition or a distinction in your trade. Wednesday: a limit — what you do not do, or a constraint of the product. Friday: a ship, a restock, a deadline, or a useful reply turned into a post.
Week 3Monday: a lesson from something that went wrong. Wednesday: a checklist or anatomy (the parts of a brief, a session, a listing). Friday: a short thread if, and only if, you have a sequence.
Week 4Monday: a before-and-after of a brief, a page, or a process (with permission). Wednesday: a myth you still hear, corrected carefully. Friday: one clear, dated announcement if you have one; otherwise a process post you have not used yet.
Alongside the posts, keep a 15–20 minute reply window on the days you publish, in your audience’s time zone if you can. The calendar does not replace conversation.
Example posts, one for each type
Process (week 1, Monday) · example
For a copywriting job I do this, in order: a 45-minute kickoff and a written outline you approve; a first draft and one structured revision; final files in Docs and Markdown.
If legal needs a pass, we add it at the outline stage, not after the “final” draft.
Example from work (week 1, Wednesday) · example
Last month I rewrote a pricing page. The constraint was: no new screenshots, no invented case studies, and the three plans had to stay as they were.
Most of the work was putting the limits (seats, log retention, support hours) in the same order on every plan.
Narrow question (week 1, Friday) · example
For year-end, we ask for the pack eight weeks before the filing date. Some firms ask at four.
If you run this, which window do you use, and what actually arrives late?
Distinction (week 2, Monday) · example
A bank feed is useful, and it is not the same thing as a reviewed set of books.
Someone still has to match transfers and ask about the odd payments. That is the work, not the fact that the bank is connected.
A limit (week 2, Wednesday) · example
I do not offer unlimited revisions.
Unlimited sounds generous. It usually means the brief was never finished. I write “two rounds” in the statement of work, and a day rate after that.
A lesson from a failure (week 3, Monday) · example
Three projects that went wrong last year had the same first week: a kickoff call, no written brief, and “we will know it when we see it”.
I now send a one-page brief back for a yes before I open the file.
Myth, carefully (week 4, Wednesday) · example
“I can run my personal shopping through the company if I take it out later” is a sentence that causes mess.
What you may or may not put through a company depends on the rules and on your facts. Ask your accountant before you invent a method. This is general information, not advice on your books.
When to break the calendar · example
The mackerel is gone for today.
The soup and the schnitzel are still on. Kitchen until 14:30.
(This replaces Friday’s planned question. Fresh facts win.)
These are original example drafts, written for this page, for a fictional professional. They are not real posts from a real account, and they are not a promise of reach, clients or sales. Adapt the structure; replace every fact with one you can stand behind.
Batch the drafting if that helps: one hour on a Sunday to sketch the three posts, then a final pass on the day with any new fact. The free X Post Writer can turn each sketch into 10 tones. Do not fire all 10 into the week. Pick one per slot, and leave yourself room to be present.