Plan a sustainable month of channel-specific content from goals, evidence, capacity, and dates
9 min setupTested with:ChatGPTReviewed: 2026-08-28
1
Add your context
Your text stays in this browser. AILesson Prompts does not send it to a model or server.
2
Your prompt
Unfilled fields remain visible as placeholders, so you can still copy and edit the prompt
Create a realistic one-month content calendar from the supplied strategy and capacity.
Month, timezone, audience, goal, content role, funnel stage, and metrics:
[strategy]
Approved themes, facts, research, events, assets, claims, and exclusions:
[materials]
Channels, frequency, capacity, owners, lead times, approvals, holidays, and reuse limits:
[capacity]
Calculate available production units before scheduling. Build a coherent monthly narrative with a deliberate mix of education, proof, objection handling, participation, and conversion only where supported. For each dated item specify channel, audience need, content objective, topic and angle, source evidence, format, hook, key points, CTA, owner, draft date, review date, publish date and timezone, reuse relationship, status, and metric. Respect channel differences; do not paste identical copy across channels. Do not invent events, facts, testimonials, trends, links, or owners. Mark asset gaps and approval dependencies. Avoid filling every capacity slot; include buffer and a replacement rule. Audit thematic balance, audience coverage, claim evidence, workload by owner, date conflicts, repetitive angles, and connection to the stated goal.
Private by defaultPrompt assembly happens locally in your browser. Avoid placing confidential information into any AI service unless your organization allows it.
From input to outcome
A worked example
See how concrete context turns this recipe into a usable result
Actual input
Goals and audience
September 2026, Asia/Shanghai. Audience: operations managers at 20-100 person companies evaluating process tools. Goal: generate 40 qualified guide downloads; content should build problem awareness and evaluation confidence. Primary metric: qualified downloads; diagnostics: saves, click-through, and completion.
Evidence and assets
Approved assets: workflow audit guide, anonymized survey of 48 managers showing handoff visibility as top issue, product fact sheet, one approved case study reporting a 22% reduction in overdue handoffs over 8 weeks at Company K. Webinar Sep 23 confirmed. No broad industry benchmark or unapproved quotes.
Channels and capacity
LinkedIn twice weekly, newsletter weekly, one webinar. One writer can create 3 units/week; designer 2 visuals/week. Legal needs 3 business days for numerical claims. Writer is unavailable Sep 14-16. Owners are Content Lead, Designer, Legal; webinar presenter not assigned. Leave 20% buffer.
Example output
Capacity: nominally 12 writing units across four weeks; retain about 2-3 as buffer, so schedule 9 primary units plus the webinar. The requested 8 LinkedIn posts and 4 newsletters exceed that unless some are adaptations. Use four source packages, each producing one newsletter plus one channel-specific LinkedIn adaptation; add one webinar post.
Sep 3 LinkedIn — Problem awareness: “Where does a handoff disappear?” Carousel based on the 48-person survey, with sample and scope visible. CTA: run one audit question. Draft Aug 28; legal review only if numerical wording is used; owner Content Lead; metric saves.
Sep 5 newsletter — Audit guide introduction. Explain three observable handoff signals from the approved guide; CTA download. Draft Sep 1, review Sep 3, publish 10:00; metric qualified downloads.
Sep 10 LinkedIn — Evaluation: distinguish visibility from more status meetings, grounded in the guide and fact sheet. CTA guide download; metric click-through.
Sep 12 newsletter — Case-study walkthrough using the qualified 22% over eight weeks at Company K. Draft Sep 7, legal by Sep 9, publish 10:00. State that one case does not predict every result.
Sep 17 LinkedIn — Case-study visual adapted for scanning, not copied from the newsletter. Draft before Sep 14; legal dependency remains. CTA: review the method; metric completion.
Sep 19 newsletter — Webinar preview: three questions operations managers can bring. Presenter remains an asset blocker; do not name one. CTA register.
Sep 21 LinkedIn — Webinar reminder using agenda facts only. Sep 23 webinar — live evaluation session; owner missing and must be assigned by Sep 9. Sep 26 newsletter — post-webinar guide path, contingent on approved recording or notes. Sep 29 LinkedIn — month-end self-audit checklist and guide CTA.
Buffer: Sep 8 and Sep 24 remain unscheduled production capacity. If a numerical item misses legal review, replace it with the non-numerical guide checklist rather than publishing the claim. Workload audit: writer blackout is protected; numerical items have three business days; no unsupported benchmark or quote is used. Confirm the definition and tracking source for “qualified download” before launch.
Why this works
1
Capacity-first scheduling prevents an attractive calendar from hiding impossible production work.
2
Source and metric fields make every item traceable to evidence and purpose.
Check the result
Do drafting, approval, and publication dates fit actual capacity and lead time?
Does every claim point to an approved source and every item to a useful metric?
Are channel adaptations distinct, with buffer for disruption?
ChatGPT