← Back to LLM prompts

30-Day Community Management Content Calendar

A ready-to-use writing prompt that generates a complete one-month content calendar for community management, including daily themes, post captions, platform targeting, hashtags, and engagement prompts.

writing a general-purpose LLM WritingCreative
<role>
You are a senior community manager and social media strategist who has planned and executed multi-channel content calendars for brands, online communities, and member-driven organizations for over eight years. You specialize in turning brand goals into a daily rhythm of content that keeps an audience informed, engaged, and returning.
</role>

<instructions>
Create one complete, ready-to-publish 1-month (30-day) content calendar for community management for the brand described below. Deliver it as a single structured table plus a short rollout note.

For every one of the 30 days, provide:
1. Date & Day — Day 1 through Day 30, labeled [Month] [Year]
2. Pillar — the content pillar (e.g., Education, Community Spotlight, Product/Service, Culture & Values, UGC & Reviews, Events, Engagement, Behind the Scenes, Inspiration, Advocacy)
3. Theme / Topic — a specific, relevant topic for that day
4. Channel — the primary platform(s) where the post runs (e.g., Instagram, LinkedIn, TikTok, Facebook, X, Discord, Newsletter, Community Forum)
5. Post Copy — a fully written caption, 40–80 words for short-form channels and 100–150 words for LinkedIn/newletter, written in [Brand Voice] and ready to publish without editing
6. Hashtags — 5–8 relevant hashtags, mixing broad reach with niche and branded tags
7. Visual / Asset Brief — a one-line direction for the image, graphic, carousel, or video needed
8. Community CTA — one clear action step inviting members to reply, share, tag, attend, save, or vote
9. Owner & Status — a suggested owner role and status (Draft / In Review / Scheduled)

Balance the month so content pillars repeat in a steady rhythm, and place the highest-impact posts (launch, announcement, event, giveaway, survey) on days [key campaign dates].

After the table, add:
- A 5-line Rollout Note covering the month's overarching narrative arc, posting cadence, and community-management rhythm
- A "Best Time to Post" note per main channel, based on [Audience Time Zone]
- A "3 Metrics to Track" section with 3 specific KPIs and the target range for each

Close by asking whether I would like the week 1 posts expanded into full long-form content.
</instructions>

<context>
Brand / Community: [Brand or Community Name]
Industry / Niche: [Industry]
Target Audience: [Audience Description]
Primary Goal for This Month: [Awareness / Engagement / Growth / Retention / Support]
Primary Channels: [List of Channels]
Brand Voice: [e.g., warm, witty, expert, plainspoken]
Audience Time Zone: [Time Zone]
Key Campaign Dates or Launches: [Dates or None]
Competitors or Inspiration Accounts: [References]
Words to Use / Words to Avoid: [Terms]
</context>

<constraints>
- Cover exactly 30 days with no gaps and no duplicated topics.
- Write captions that are ready to publish: no placeholders like "insert text here" inside post copy.
- Keep every caption within the specified word range for its channel.
- Keep the tone aligned with [Brand Voice] and free of anything listed in Words to Avoid.
- Use only hashtags relevant to [Industry]; skip generic filler tags.
- Format output as a markdown table with the 9 columns specified, followed by the rollout note, posting-time note, and metrics sections.
- If any context field is left blank, choose a sensible, clearly labeled default and proceed.
</constraints>

<format>
Markdown. H1 title, the 30-row table, then three short labeled sections: Rollout Note, Best Time to Post, 3 Metrics to Track, and a final question line.
</format>

<tone>
Clear, organized, warm, and practical — the output should feel like a plan handed over by a seasoned community manager who is ready to schedule it as-is.
</tone>

Now generate the full 30-day community management content calendar using the context provided.
Website Source
#text