The Four-Hour Sermon Week.
You have four hours this week for sermon prep. Not twenty. Not ten. Four. You have a day job, a family, a midweek service, three hospital visits pending, and a board meeting on Thursday.
This appendix is not aspirational. It is the actual workflow.
Here is the whole principle:
Let the Bible speak first. Let AI help second. Let the pastor carry it last.
That is simple enough to remember and strong enough to govern the whole week.
AI is useful when it helps you with work you have already begun. It becomes dangerous when it begins the work for you, frames the sermon for you, or gives you words you cannot carry as your own.
So the workflow is not complicated:
- Read the text before the tool.
- Ask AI for help, not for a sermon.
- Check the sermon before you preach it.
- Preach from conviction, not from a download.
The Ground Rules
Before the schedule, three rules.
1. AI is never the first voice. Scripture, prayer, and your own study come first. If AI frames the sermon before the text has formed you, the tool is leading.
2. AI is never the final voice. Before the sermon reaches your people, you check Scripture, doctrine, and the actual congregation in front of you.
3. AI is never the pastoral voice. It can help with research, structure, and clarity. It cannot carry spiritual responsibility for the flock. That responsibility stays with you.
The Four-Hour Week
1. Read the Text — 45 minutes
Tool: Bible. Notebook. Pen. No AI.
Read the text. Read it again. Read it in a different translation. Read it out loud.
Write three sentences:
- What does this text plainly say?
- What does this text ask of my people?
- Where am I stuck?
That is enough for the first movement. You are not trying to finish the sermon. You are lighting the fire.
The rule is simple: bring something to AI before AI brings something to you.
You have now done the one thing the AI cannot do for you.
2. Ask for Targeted Help — 75 minutes
Tool: AI, directed by your own study.
Now you open the tool. Not before. And when you open it, do not ask for a sermon. Ask for help with the part you named on Monday.
Use this prompt shape:
I am preaching [text] to an Assemblies of God congregation in [place]. I have already studied the passage. Here is what I think it says: [your sentence]. Here is where I am stuck: [your question]. Do not write the sermon. Help me with [background / structure / cross-references / possible objections]. Cite sources where possible. Flag anything that may conflict with a Pentecostal reading.
Then run one source check:
Given this text, does a generic Pentecostal reading differ from your default response? Where?
Write down what it says. That becomes your flag list for review.
The rule is simple: do not ask AI to make the sermon; ask it to help with the sermon you are already forming.
You leave this movement with research, options, and warnings. Not a finished sermon.
3. Build the Sermon — 90 minutes
Tool: Bible, notes, sermon draft. AI closed.
Now you write and finish the sermon. The AI has done its job. It can leave the room.
You have your first reading, the research notes, and the flag list. You are not generating from scratch. You are synthesizing material you have already carried.
Build the sermon around three plain parts:
- What does the text say?
- Why does it matter to our people?
- What faithful response is God asking for?
This keeps the sermon pastoral. It keeps you from turning Sunday into a lecture, a content dump, or an AI-assisted essay.
4. Check and Carry — 30 minutes
Tool: Bible, doctrine, congregation. No AI.
Before you stop, ask three questions:
- Bible: Can I point to the text for every major claim?
- Doctrine: Can an AG credentialed minister sign this without hesitation?
- People: Does this speak to my congregation, or to a generic audience?
If anything fails, fix it before Sunday.
Then, before the service, take fifteen minutes with no screen and no AI. Put the notes down and preach the center of the sermon out loud. Not every word. The center.
If you cannot say the center without the machine, the sermon is not inside you yet.
The rule is simple: verify it, own it, and carry it before you preach it.
The Total Budget
| Step | Time | Tool |
|---|---|---|
| Read the Text | 45 min | Bible, notebook |
| Ask for Targeted Help | 75 min | AI, directed |
| Build the Sermon | 90 min | Bible, notes, draft |
| Check and Carry | 30 min | Bible, doctrine, no AI |
| Total | 4 hours |
When Life Breaks the Schedule
It will. A hospital call Wednesday night. A kid with a fever Saturday afternoon. A funeral Thursday that was not on the calendar Monday.
The rule is not "keep the schedule." The rule is keep the order.
If you have three hours, shorten the text.
If you have two hours, preach a simpler sermon.
If you have one hour, preach one faithful point from a passage you actually studied.
Do not use the emergency as an excuse to let AI go first or last. A shorter sermon that went through the rhythm is better than a polished sermon that bypassed your pastoral labor.
A bivo pastor's week is already a broken schedule. The schedule helps. The order matters.
The One Sentence
If you forget everything else, remember this:
Study before AI. Ask for help, not replacement. Check before preaching.
Six months from now, ask one test question:
Can I still preach without AI?
If yes, the tool helped, but the craft stayed alive.
If no, close the tool for a month. Preach four sermons fully without it. The skill comes back. It always does. But only if you make it come back.
AI should make the week lighter. It should not make the pastor smaller.
