Plan
Brief
Build a quarterly comms calendar
Give it your known dates and recurring sends; get a week-by-week calendar with collision rules and trade-offs made visible.
The prompt
Build an internal communications calendar for [quarter].
Context: known events and dates: [town halls, enrollment windows, launches, holidays, fiscal deadlines]. Recurring sends: [newsletter cadence, leadership updates]. Priorities leadership has named: [list].
Audience: the comms team and the stakeholders who will request sends against this calendar.
Tone: organized and decisive; make the trade-offs visible.
Must include:
– A week-by-week view with every planned send, its audience, owner, and channel
– The rules you applied to avoid collisions (e.g., no more than [two] all-employee emails in a week; quiet weeks around [dates])
– Which requests you deprioritized or merged, and why
– Placeholder slots held for unplanned news
Constraints: one row per send; flag any week that exceeds [three] all-employee messages.
Output: the calendar as a table, then a short “how to use this calendar” note for stakeholders. Ask me about anything you need before building it.
Works in
Any AI toolHow to use
Set your own collision rules in Constraints — the numbers in brackets are a starting point, not a recommendation.
The prompt
Build an internal communications calendar for [quarter].
Context: known events and dates: [town halls, enrollment windows, launches, holidays, fiscal deadlines]. Recurring sends: [newsletter cadence, leadership updates]. Priorities leadership has named: [list].
Audience: the comms team and the stakeholders who will request sends against this calendar.
Tone: organized and decisive; make the trade-offs visible.
Must include:
– A week-by-week view with every planned send, its audience, owner, and channel
– The rules you applied to avoid collisions (e.g., no more than [two] all-employee emails in a week; quiet weeks around [dates])
– Which requests you deprioritized or merged, and why
– Placeholder slots held for unplanned news
Constraints: one row per send; flag any week that exceeds [three] all-employee messages.
Output: the calendar as a table, then a short “how to use this calendar” note for stakeholders. Ask me about anything you need before building it.
