Instagram

Verified against ChatGPT · 2026-08-10

Map a month of Instagram content to the batch-shoot days you actually have, not an idealized daily grid

Builds a content calendar backwards from the real number of shoot days and available hours a creator has this month, instead of a generic 'post daily' grid that assumes unlimited production time.

ChatGPT (GPT-5.1)5 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are building a one-month Instagram content calendar for a creator, and the starting constraint is production capacity, not posting frequency — the calendar has to be built backwards from the actual shoot days available this month, not forward from an ideal posting cadence that assumes unlimited time to produce content.

SHOOT DAYS AVAILABLE THIS MONTH
4 shoot days this month, each roughly a Saturday.

CONTENT PILLARS
Studio process, finished-product reveals, behind-the-scenes mistakes, customer features.

FORMATS IN ROTATION
Reels, carousels, and single-image posts — no Stories-only content counted here.

RECURRING DATES OR LAUNCHES TO HIT
New glaze color drops on the 18th and must have a reel ready that morning.

HOURS AVAILABLE PER SHOOT DAY
About 3 hours per shoot day, including setup and teardown.

CALCULATE CAPACITY FIRST
Before assigning any post, calculate roughly how many pieces of finished content the stated shoot days and hours per day can realistically produce, given that a single shoot day typically yields multiple pieces (a carousel, a reel, and several photo posts) but not an unlimited number — state this capacity number explicitly and build the calendar to that number, not to a round posting target like 'one per day' that ignores it. If the fixed dates and content pillars together would require more output than the stated capacity supports, say so explicitly and propose what to cut or combine rather than quietly overcommitting the calendar to more posts than the shoot days can produce.

BUILD THE CALENDAR
Assign each planned post to the specific shoot day its raw material would come from, not just to a calendar date — a post scheduled for the 14th but shot on the 3rd should show both dates, so the creator knows when to actually capture it. Rotate through the stated content pillars and format mix so no single pillar or format repeats more than twice in a row. Place fixed dates and launches on their exact required day, then build the rest of the calendar around them, not the other way around.

OUTPUT FORMAT
A table with columns: Post Date | Shoot Day | Content Pillar | Format | Working Title/Hook | Notes. Precede the table with the calculated realistic capacity number and one sentence stating whether the requested output fits inside it. Follow the table with a short list of anything cut or combined to make the plan fit actual capacity.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Forcing an explicit capacity calculation before any post gets assigned addresses the most common failure mode in AI-generated content calendars: asked to 'build a month of content,' GPT-5.1 defaults to a clean, evenly-spaced grid (a post every day, or every other day) because that's the statistically dominant pattern in the content-calendar templates it has seen, regardless of whether the stated production constraints could actually support that cadence — the calendar comes out looking complete and professional while being quietly unbuildable. Requiring the model to state the capacity number out loud and check the requested output against it converts an invisible assumption into a checkable claim, which is what makes the difference between a calendar that looks right and one that a single creator with four Saturdays a month can actually execute. Tying each post to the specific shoot day its raw footage comes from, rather than only to a publish date, closes a second gap: a generic calendar treats 'when to post' and 'when to shoot' as the same question, but for a solo creator they're not, and conflating them produces a plan where the creator discovers on the 13th that the footage for the 14th's post was never captured. The instruction to flag overcommitment and propose cuts, rather than silently fitting everything in by assuming more output per shoot day than was stated, matters because a model asked to satisfy multiple constraints at once (pillars, formats, fixed dates, capacity) will tend to resolve the tension by quietly relaxing whichever constraint was stated least precisely, and capacity is usually the one given as a rough number rather than a hard rule — naming it as the binding constraint stops that silent drift.

What you get back

Realistic capacity: 4 shoot days x ~3 hours ≈ enough raw footage for roughly 10-12 finished posts this month, not the 20 a strict alternate-day cadence would need — this plan fits 11. Post Date: Aug 18 | Shoot Day: Aug 16 | Pillar: Finished-product reveal | Format: Reel | Hook: "The glaze we almost didn't ship" | Notes: must be edited and scheduled by morning of the 18th for the launch.

Verified against

ChatGPT GPT-5.1 · 2026-08-10

Changelog

  • 2026-08-10 Initial publish, verified against ChatGPT GPT-5.1.

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All Instagram prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY