How to batch a month of posts in one afternoon
Not a productivity theory. This is the order the work actually goes in, why each step comes where it does, and the specific places people lose the afternoon. It applies whatever tools you use.
Decide the shape of the month before you write a word
The hardest part of batching is not the writing, it is starting from nothing sixteen times. Deciding the shape first converts a blank page into a list of assignments, and an assignment is much easier to write than a post.
Pick a cadence you can actually sustain, three or four a week rather than daily, and then split those slots by kind: a few that teach something, a few that show the work, one or two that ask for something. You are not writing yet. You are filling in a grid of what-each-slot-is-for.
If you cannot fill the grid, the month is too ambitious. Cut the cadence now rather than discovering it in week three.
Write everything in one place, one row per post
A spreadsheet, a document, anything that holds all of it at once. The format matters less than the property: you can see the whole month while you write any part of it, which is what stops the fourth post repeating the second.
One row per post, and columns only for things that genuinely change between posts. A headline, the supporting line, a price or a date if the post has one, and the caption. A column you leave empty for eleven of sixteen rows is a column that should not exist.
Write all the words before you make anything look like anything. Switching between writing and designing is what turns four hours into two evenings, because each switch costs the context you had built up.
Separate the words from the design, once
The reason a month of posts feels like a month of work is that most people rebuild the design for every post. They open a design tool, duplicate last week’s file, replace the text, fix the bits that broke, export, repeat.
The alternative is deciding the layouts once. Three or four is plenty: something for a statement, something for a tip or a step, something for an offer. Each layout holds your fonts, colours and logo, and leaves holes where the words go. After that, a post is a row of values rather than a design job.
This is the step that makes the difference, and it is the one most often skipped, because it does not feel like producing anything.
Produce the images in one pass
With the words written and the layouts decided, making the images should be mechanical. Whatever you use, the goal is a single pass over the whole list rather than sixteen separate sittings.
Check the output as a set rather than one at a time. Seeing all sixteen together is how you notice that four of them say almost the same thing, or that one headline is twice the length of the others and looks wrong at small sizes.
This is the part PlanBatch was built for: the rows become finished branded images in one run, including multi-slide carousels from grouped rows. Plenty of teams do this step by hand instead, and the method works either way; it is just the longest part.
Schedule the set, then leave it alone
Put the whole month on the calendar in one go. Spreading it by hand, post by post, is another sixteen small decisions at the end of an afternoon when you have the least judgement left.
Check the first week closely, especially the first image on each platform, since that is where cropping surprises show up. Then genuinely leave it: the value of a batch is that the month runs without you, and re-litigating each post the night before gives that back.
Keep a little room. One or two unscheduled slots let you react to something without unpicking the plan.
Where afternoons actually go wrong
- Writing inside the scheduler. It forces one post at a time and pulls you into design mid-sentence.
- Designing before writing. A beautiful template with nothing to say is a slot you will fill badly at 6pm.
- Per-platform everything. The image can usually be shared across networks. Vary the caption, not the artwork.
- No column discipline. Fifteen columns where six would do turns a spreadsheet into its own project.
Common questions
How many posts should one batch cover?
A month is the usual unit, because it is long enough to be worth the setup and short enough that the plan is still relevant when you get to the end of it. Three or four posts a week for a month is twelve to sixteen rows, which is an afternoon's writing.
Do I need different copy for each platform?
Usually only for the caption, not the image. The same graphic works across Instagram, Facebook and LinkedIn; the wording around it often needs to change, because a LinkedIn audience and an Instagram audience expect different registers. Plan for one image and up to three captions.
What is the most common reason a batch never gets finished?
Writing directly into a scheduler. It forces you to think about one post at a time, and the moment a graphic needs making you leave the tool and lose the thread. Writing all the words first, in one place, is what makes the afternoon possible.
Is batching worse for engagement than posting spontaneously?
There is no evidence that a scheduled post performs worse than a manual one; the platforms stopped penalising third-party publishing years ago. What does hurt is a feed that goes quiet for three weeks because nobody had time, which is the outcome batching prevents.
How does PlanBatch fit into this?
It handles the step most tools leave to you: turning the rows into finished branded images, then scheduling them. The free plan covers 30 images and 10 rows per upload on 1 channel, which is enough to try a month before deciding anything.
If the image-making step is the one eating your afternoon, that is the part this product automates. The rest of the method is yours either way.