Content Batching: Write a Week of Captions in 90 Minutes

Daily posting dies when every caption starts from zero. Batching is how part-time creators stay consistent without sounding robotic.

The 90-minute batch (timer on)

Minutes 0–15: Theme map

Pick one weekly promise (e.g. “hooks that stop scrolls”) and 5–7 post angles:

• Myth
• Mistake
• Template
• Story
• Checklist
• Hot take
• Soft CTA / offer

Minutes 15–35: Hook bank

Write 14 hooks (2 per angle). Don’t edit. Quantity first. Use styles: question, bold claim, stat, “stop doing X”, story open.

Minutes 35–70: Caption drafts

For each of 7 posts:

1. Hook
2. 3–5 value lines
3. One CTA
4. Optional hashtag set (reuse 2 sets max)

Minutes 70–90: QA + schedule

• Remove filler words
• Match CTA to goal (comment vs save vs click)
• Drop into scheduler / Notion calendar

Caption batching templates

Teach Hook → 3 steps → example → CTA

Story Moment → lesson → what I’d do differently → CTA

List Promise → 5 bullets → which to try first → CTA

Opinion Claim → why → who it’s for / not for → invite debate

Rules that keep quality high

1. One idea per post
2. Rotate CTAs (don’t “link in bio” every day)
3. Reuse winning hooks with new examples
4. Leave 1 slot open for timely posts

Weekly calendar example

Related guides

• 30-day AI content engine
• CTA formulas
• Blog content ideas that rank

Frequently asked questions

Should I batch Reels scripts too?

Yes — batch hooks and spoken CTAs in the same session. Film later in one block.

What if I run out of ideas mid-week?

Keep a “swipe file” of customer questions. One question = one post.

Batching works when similar decisions are grouped, not when one caption is copied seven times. Separate idea selection, drafting, editing, and scheduling so context switching falls while each post keeps a distinct purpose.

Use the 90-minute agenda

• 0–15 minutes: select one weekly theme and five audience questions from comments, search, sales, or support. Assign a purpose to each post.

• 15–30 minutes: attach one example, proof point, story, or demonstration to each idea. Drop any topic that has no useful substance.

• 30–60 minutes: draft openings and bodies without polishing. Rotate formats: lesson, story, teardown, checklist, and opinion with evidence.

• 60–75 minutes: write one fitting CTA, adapt length and packaging to each platform, and add only relevant tags or links.

• 75–90 minutes: fact-check, read aloud, preview line breaks, schedule, and record what metric will indicate success.

Build a reusable input board

Keep columns for audience question, content pillar, evidence, format, status, destination, and result. The board should reduce memory work, not become another publishing bureaucracy. Capture ideas throughout the week and enter batching time with a shortlist.

Protect variation

Change the angle and evidence, not just the hook. If a long guide produces several posts, assign each a different reader problem. Space similar formats apart, and avoid making every caption end with the same question. Consistency should come from judgment and voice, not identical structure.

A practical review checklist

• Each caption has one audience problem.
• Every claim has an example or source.
• Formats vary across the week.
• Line breaks are previewed on the target platform.
• Scheduling leaves room for timely responses.

Frequently asked questions

Should I batch an entire month?

Monthly planning is useful, but draft in weekly blocks so current feedback and events can change the execution.

What if I cannot finish in 90 minutes?

Measure where time goes. Weak inputs usually slow drafting; unclear approvals slow scheduling. Fix the bottleneck instead of rushing the final edit.

Can the same caption go everywhere?

The core idea can travel, but rewrite the opening, length, CTA, and context for how people use each platform.

The related caption tool can provide alternate drafts during the writing block; the input board should still supply the evidence and purpose.