Content Batching: One Saturday, 6 Weeks of Posts. Here's How.

Last Saturday, I sat down at 9am with a cup of coffee, a 2,400-word blog post about remote work productivity, and a goal: batch 6 weeks of social content for a client before 3pm. I've done this dozens of times, but I've never written it up in detail. This is the full account, including the parts that didn't go smoothly.

The client is a mid-size HR software company. They publish one blog post per week and want consistent social presence across LinkedIn, X, TikTok, and a bi-weekly email newsletter. Before we implemented batching, their social content was an afterthought — published sporadically, formatted poorly for each platform, and not connected to their editorial calendar in any meaningful way.

Six months in, their LinkedIn reach is up 34% compared to the 6-month period before. That number isn't all batching, but batching is a big part of why the consistency improved.

Why Batching Felt Wrong at First

I want to address the mental barrier before I get into the tactical stuff, because I've seen it stop people from trying this.

When I first suggested content batching to this client's marketing lead, her response was: "But won't the posts feel dated? Like we're not actually in the conversation?" That's a real concern. Content that was written three weeks ago can feel disconnected from what's happening now.

Here's how I think about it: 80% of good social content is evergreen. A post about why async communication improves focus, or a LinkedIn post framing a key insight from a blog article about remote work, doesn't expire in three weeks. Maybe 20% of what you'd want to post is reactive or trending-dependent. You don't batch that 20%. You leave room for it.

My standard recommendation is to batch 80% of your calendar and leave 20% unscheduled for reactive content, breaking news in your industry, or things that come up organically. If something big happens in your space, you should absolutely drop a scheduled post and respond to it in real time. The batched content is the floor, not the ceiling.

Once that clicked for the marketing lead, the resistance went away.

The Setup: What I Had Going In

The source material for this batch session was a single 2,400-word blog post the client had published two weeks prior. The post was titled "Why Remote Work Productivity Isn't About Hours" and covered five research-backed frameworks for thinking about deep work, async communication, and measurable output over time-tracking.

I chose this post because: it had solid supporting data and real arguments, not just opinion; it was long enough to yield multiple distinct points; and the topic has long-term relevance (not just a trending story that would feel stale in three weeks).

My tools for the session:

• Reslice for generating the initial platform-specific drafts
• Notion for organizing the outputs and tracking what's scheduled for which week
• Buffer for scheduling the approved posts

I had a Notion template already set up for this client with columns for: platform, content, scheduled date, status (draft/approved/scheduled), and notes. Nothing fancy, just a place to put everything so it doesn't live in my brain.

9am: Starting with LinkedIn

I pasted the full blog post text into Reslice and selected LinkedIn as the first platform. The prompt settings I use for this client: professional but conversational tone, medium length (around 150-200 words), no hashtag stuffing (maximum 3 relevant tags).

Reslice generated 3 LinkedIn post options from the article. I do this rather than taking the first output, because the second or third option is often better structured. In this case, the first option was good but started with "Have you ever..." which I've seen underperform on LinkedIn compared to opening with a direct statement. The second option opened with a counterintuitive claim from the research section of the post and was much stronger.

I pasted the second option into Notion and made two edits: added a specific data point from the original article (employees with no-meeting mornings reported 23% higher output in the study cited), and tightened the closing line. Took about 6 minutes.

I did this for 8 LinkedIn posts total. Not all from the same article section. I pulled different ideas from different parts of the post. One post focused on the async communication framework. Two posts framed the research findings. One used a specific quote from the article. One was a "common mistake" framing drawn from the mistakes section. And so on.

Total time for LinkedIn: just under an hour. By 9:55am I had 8 LinkedIn drafts in Notion, each reviewed and edited.

10am: X Threads

X is faster per post but the thread structure takes more thinking. I generated thread drafts for 3 threads from the same blog post. Each thread covers a distinct idea from the article: one on the "output not hours" thesis, one on the async communication framework, one on the research behind deep work blocks.

Reslice formats these correctly for X's character limits and breaks them into numbered posts automatically. I still had to do more editing on these than on the LinkedIn posts. X threads need a stronger hook in the first post and tighter transitions between posts. The drafts were about 70% there. I spent 12 minutes per thread on average bringing them to publishable quality.

Three threads done by 10:45am.

10:45am: Coffee Break

I'm not going to pretend I powered through six straight hours. This break was 15 minutes. If you're doing a batching session, build in breaks or the quality of your editing will decline noticeably after about 90 minutes of focused work.

11am: TikTok Scripts

This is where the session got harder.

I generated 4 TikTok script drafts from the article. The goal was scripts in the 30-45 second range (roughly 100-120 words spoken at natural pace) with a strong hook in the first line and a clear close.

The first two drafts were good. The hook on draft one was "Your company is probably tracking the wrong thing about remote work" which is exactly the kind of opening that earns watch time. The script flowed well. I made minor edits to make the language more conversational (the AI output is slightly more formal than natural TikTok speech) and it was ready.

Drafts three and four needed two full revision passes each. The issue wasn't the information, it was the tone. TikTok scripts need to sound like a person talking directly to another person, and these two drafts sounded more like a podcast summary. I rewrote the openings, broke up longer sentences, and added a few places where the delivery could be punchy or slightly informal ("And honestly, that's backwards.").

If I'm being honest: the TikTok scripts took longer than I expected. I budgeted 45 minutes and spent 75. That's worth knowing if you're planning your own batching session. TikTok content requires more human intervention than LinkedIn or X content, in my experience, because the platform's conventions around spoken delivery are harder to capture with an AI first draft.

Four TikTok scripts ready by 12:30pm.

12:30pm: Lunch

Real break. 30 minutes. The afternoon session would cover the two newsletter editions and then scheduling everything.

1pm: Newsletter Editions

This client sends a bi-weekly email newsletter. I use the blog post as source material but write the newsletter with a different framing. The newsletter's voice is more personal than the blog — it's written in first person from the perspective of the company's head of content, not as a generic brand voice.

I used Reslice to generate an email draft from the article, then rewrote the opening and closing entirely. The email format Reslice generates is a reasonable structure but it's too formal for this client's newsletter voice. I kept the middle section (the summary of the key points) and rewrote the intro (which should feel like a personal note) and the outro (which ends with a question to the reader).

Two newsletter editions drafted and in Notion by 2pm. Each took about 25 minutes.

2pm: Scheduling in Buffer

The last hour was scheduling. I had:

• 8 LinkedIn posts
• 3 X threads (9 individual posts)
• 4 TikTok scripts (these go to a separate folder for the client to record; they don't auto-schedule video)
• 2 newsletter drafts

LinkedIn posts were distributed across 6 weeks, roughly one per week, with the two strongest posts scheduled for weeks with lower planned activity elsewhere. X threads were spaced every two weeks. Newsletter drafts were scheduled for the client's newsletter platform with notes on which week each should go out.

Done at 2:58pm.

What Surprised Me

LinkedIn significantly outperformed what I expected based on this client's historical engagement. The post focused on the async communication framework got 1,400 impressions and 67 reactions in its first 48 hours, which is well above their baseline. The topic clearly resonated with their audience (HR professionals at distributed companies) more than some of the other content they'd been posting.

That's actually one of the hidden benefits of batching in volume: when you generate 8 posts from the same article, you're naturally testing different angles of the same topic. You learn quickly which angle your audience responds to. Over time, that shapes your content strategy because you have real data on what your specific audience cares about.

I also didn't expect the total time to be as manageable as it was. Six hours for 6 weeks of content across 4 platforms. That's not nothing, but compare it to the alternative: 15-20 minutes of content scrambling every other day, often resulting in lower-quality content because you're rushing. The math favors batching.

The Results, 6 Weeks Out

Six weeks after this batching session, here's where things stand for this client:

• LinkedIn reach increased 34% compared to the same 6-week period the prior quarter
• X follower count up 8% (modest, but they weren't posting consistently before)
• Newsletter open rate held steady at 31% (industry average for their category is around 22%)
• TikTok: three of the four scripts were recorded and posted; two performed well (12k and 8k views), one underperformed (2k views)

The TikTok underperformer was one of the scripts I said needed two revision passes. In hindsight, I should have scrapped it and written a fresh one instead of forcing it to work. That's the lesson: if a draft doesn't feel right after two passes, it's probably not going to perform. Cut your losses and write something new.

How to Set Up Your Own Batching Day

If you want to try this, here's the minimum setup you need:

1. One solid piece of long-form source content. A blog post, a recorded talk, a long interview, a detailed newsletter. It needs to have enough substance to yield multiple distinct ideas.
2. A tool to generate first drafts. Reslice is what I use for multi-platform generation from a single input. If you prefer, you can use ChatGPT with detailed platform-specific prompts. Either way, you want something to generate the structural first draft quickly so you're editing, not starting from nothing.
3. A simple organization system. Notion, a spreadsheet, even a Google Doc with sections by platform and week. Something that lets you see all your content at once and track what's scheduled.
4. A scheduler. Buffer, Later, Hootsuite, whatever you already use. The batching session is worthless if the content sits in a folder and never goes out.

The first batching session will take longer than subsequent ones because you're learning the workflow. Block 6-8 hours for your first attempt. Once you've done it a few times, you'll get it down to 3-4 hours for a month's worth of content.

If you want to see how quickly Reslice can generate multi-platform drafts from a single article, the free tier is a good place to start. Paste one blog post and see what comes out. The editing time is on you, but the generation step takes about 30 seconds.

For more on building a consistent content schedule after you've batched, the follow-up to this is how to maintain consistent social posting long-term. And if you want to see how the full one-day content workflow looks in practice, this post covers the broader approach.