How To Plan Your Fall Preaching Calendar With Claude AI In 1 Hour
AI for Church Leaders | Fall Preaching Calendar
Hey there!
Your next service is September 13. Your last one before the year closes is Christmas Eve. Between those 2 dates sit 15 Sundays and one Christmas Eve service, which is 16 services to plan while the fall calendar is already running.
Set aside one hour this week and you can finish the planning in a single sitting.
Sermon planning stalls on fixed dates. Guest speakers, baptism Sunday, the missions weekend, a denominational emphasis, Advent beginning November 29. Ideas are easy to generate. Fitting them around commitments you already made is the slow part, and that is the part Claude handles well.
3 steps, 20 minutes each. Every prompt below follows the same 5-part shape, so you can reuse the pattern on anything else you plan: ROLE, INPUTS, TASK, CONSTRAINTS, OUTPUT.
Before you start, 5 minutes.
Gather these before you open Claude. Hunting for them mid-session is what stretches a 60-minute block into most of a day.
- Your service dates from September 13 through Christmas Eve, including midweek and additional Christmas services.
- Guest speakers and the exact dates each one holds.
- Committed services: baptism, child dedication, missions weekend, a testimony service, anything already promised to a ministry leader.
- Denominational or lectionary requirements, if you follow them.
- Last year's fall series titles and primary texts, so Claude can avoid repeating you.
- Two sentences describing your congregation as it is right now, including the shape of attendance across the fall.
Then create a Project in Claude and put those files inside it. A Project holds one shared context across all 3 steps. Without it, step 2 forgets what step 1 established and you spend your hour re-explaining your church.
Step 1. Load the constraints. 20 minutes.
Ideas come second. First Claude needs an accurate picture of what is already spoken for.
Paste this:
ROLE
You are helping me build a preaching calendar for a local church. You are not writing sermons and you are not interpreting Scripture for me.INPUTS
Service dates: [paste every date from September 13 through Christmas Eve]
Guest speakers: [name, and the exact date each one holds]
Committed services: [baptism Sunday, missions weekend, child dedication, and any date already promised]
Denominational or lectionary requirements: [paste, or write "none"]
Last year's fall series: [titles and primary texts]TASK
Build one table covering every service I listed.CONSTRAINTS
Use only the dates in my input. Do not add services I did not list. If any date I gave you is not the day of the week I claimed, flag it and stop. Treat November 29 as the first Sunday of Advent. Do not propose any series or topic yet.OUTPUT
A table with these columns: date, day of week, service type, status (open or committed), what is committed, notes. Below the table, list every place where my input was incomplete, contradictory, or ambiguous, and ask me about those before we go further.
A correct result has the same number of rows as the dates you supplied, every committed date marked, and a short list of questions underneath. That question list is the valuable part. It usually surfaces a Sunday you forgot you gave away.
Two failure modes show up here. The first is invented dates, where Claude adds a service you never mentioned. Reply with: "Rebuild the table using only the dates in my input. Name any date you added, then remove it."
The second is a dropped commitment, where a guest speaker weekend loses its marking. Reply with: "List every committed date from my original input and confirm each one appears in the table with its commitment intact."
Fix both before you move on. Everything after this inherits the table.
Step 2. Get 3 competing arcs. 20 minutes.
Ask for 3 arcs so you can see what each choice costs you. A single proposal tends to become the decision by default.
Paste this:
ROLE
You are proposing preaching arcs across the calendar table we just built. You are still not writing sermons.INPUTS
Use the service table above.
Our congregation: [2 sentences, honest, including attendance shape across the fall]
By Christmas Eve I want people to be able to: [name 3 concrete outcomes]
Texts or topics I have ruled out: [paste, or write "none"]
Preparation reality: [the hours per week you actually have]TASK
Propose 3 different preaching arcs covering all 16 services.CONSTRAINTS
Every arc must cover every open date on the table. Leave committed dates as they are and show how each arc absorbs them. No arc may assume I preach every single week. Do not reuse a primary text across 2 arcs unless you explain the reason. Advent begins November 29 in every arc.OUTPUT
For each arc: a name and the through line in one sentence, a dated list of all 16 services with primary text and working title, how the arc handles each guest speaker and committed date, and one paragraph on why a first-time guest arriving December 20 would come back in January. Then a comparison table scoring the 3 arcs on preparation load, teaching team fit, and December accessibility.
Now choose, and choose on criteria rather than on whichever one you read first. 4 questions settle it.
Does the arc reach Advent honestly? The through line should arrive at Christmas because of where it started, without a hard turn in late November.
Does it survive a guest speaker? A visiting preacher should be able to take their assigned week without breaking the sequence.
Can a December visitor enter cold? Your highest-attendance services are also your highest proportion of first-time guests.
Can your team resource it? The worship, kids, and communications load has to be something your actual volunteers can carry for 4 months.
If 2 arcs tie, ask Claude to merge them: "Combine arc 1 and arc 3 into a single arc that keeps the through line from arc 1 and the December accessibility of arc 3. Show me the dated list."
Are you in our peer community of over 8,300 pastors and church leaders discussing AI? Join us: www.facebook.com/groups/aiforchurchleaders
Step 3. Turn the winner into 16 briefs your team can work from.
A chosen arc is still just a list of texts and dates. Nobody on your staff can act on it yet, and neither can you on the morning you sit down to write.
What you need now is a brief for every one of the 16 services:
6 labeled lines each, under 150 words, built so the answers you need on a study morning are already sitting on the page.
β TEXT, so you are not re-deciding a passage you already settled.
β ONE IDEA, written as a single sentence you could say out loud from the platform.
β QUESTION IT ANSWERS, which is the question a person in the room is actually carrying that morning.
β OPENING IMAGE, a concrete scene rather than an abstraction.
β WORSHIP TEAM NEEDS, which is what your worship leader needs to prepare and the tone to prepare it in.
β CLOSING ASK, the specific next step you are inviting people into.
16 of those, produced in one pass, is what turns an arc into something your worship leader and your communications person can start building against this week.
The rest of this issue is that step, and it goes further than the prompt.
Here are the 3 prompts written out to copy/paste, plus what to type when Claude starts writing sermon content you did not ask for:
Then the 2 extraction prompts that split the 16 briefs into a worship packet and a communications packet, so you can send both the same day instead of retyping them.
Then the handoff prompt for guest speaker weekends, which turns their assigned date into a note that tells them the arc, the text, and what the service before and after theirs is doing.
Then the 15-minute recurring check that keeps all 16 briefs accurate when a guest speaker cancels or a date moves, along with the exact sentence to paste when it does.
And the review pass to run before any of it reaches your team.
