How to batch a week of posts in two hours

Two hours is enough to plan a full week of posts — but only if you stop doing all four stages of content creation at once for every single post. Batching works because it groups similar mental work together instead of context-switching between idea generation, writing, and scheduling five separate times.

The four stages, done once each

1. Idea (15 minutes). List 5–7 rough post ideas, one line each. Don't write anything yet — just capture the angle. A notes app or voice memo works fine here.
2. Draft (45 minutes). Write one solid draft per idea, for whichever platform is your primary one. Don't polish — get the core idea and structure down.
3. Adapt (40 minutes). Take each draft and adjust it for your other platforms: trim it for X, restructure it for LinkedIn, add a visual hook note for Instagram.
4. Schedule (20 minutes). Drop everything into your calendar at your chosen times. No writing during this step — just placement.

The moment you catch yourself editing a caption during the "schedule" step, stop — that's next week's batching session leaking into this one, and it's the single biggest reason batching sessions run long.

Why this order matters

Idea generation and polishing use different mental modes, and switching between them mid-task is what makes a "quick batch session" balloon into four hours. Generating seven ideas back to back is fast because you're not also trying to make each one perfect. Drafting seven posts back to back is fast because you're not also trying to think of new ideas mid-draft.

A practical two-hour breakdown

• 0:00–0:15 — Idea list
• 0:15–1:00 — Draft primary-platform posts
• 1:00–1:40 — Adapt for other platforms
• 1:40–2:00 — Schedule everything

Three things that make it actually stick

• Keep a running idea list between sessions. Don't start from zero every week — jot ideas down whenever they occur to you, so your 15-minute idea block starts half-full.
• Write drafts slightly rough on purpose. A too-polished draft resists adaptation; a slightly loose one is easier to reshape for a different platform's voice.
• Protect the two hours like a meeting. Batching only saves time if it replaces five separate 30-minute sessions spread across the week — which is where most of the wasted time (re-loading context every time) actually comes from.