How to Prepare a Sermon: A Step-by-Step Guide for Pastors (2026)

If you want to know how to prepare a sermon that is faithful to the text, clear to the room and finished before Saturday night, you need a process — not more effort. Most pastors were taught homiletics. Very few were handed a repeatable weekly workflow, so preparation expands to fill whatever time is left after everything else, and “everything else” in ministry is endless.

The numbers bear this out. In Lifeway Research’s survey of more than a thousand pastors, nearly seven in ten reported spending eight or more hours a week preparing sermons, and more than one in five spent fifteen hours or more. That is before hospital visits, counseling, meetings and the second job many bivocational pastors hold.

This guide lays out the whole process in five stages, with a realistic time budget for each, a worked example from Philippians 2, and a checklist at the end. It is written for a pastor preparing one main sermon a week; if you preach twice, the stages are the same and the budget roughly doubles.

Before you start: the one decision that saves hours

Decide the passage before the week begins. It sounds obvious, but Lifeway found that 22% of pastors choose their text the week before they preach it, and in churches under 100 people the figure rises to 28%. A pastor who knows in August what they are preaching on the third Sunday of October reads the passage early, notices illustrations in ordinary life, asks the worship leader for a fitting song, and never opens Monday with a blank page.

You do not need a twelve-month plan to get this benefit. A one-month horizon changes the week. A full-year preaching calendar changes the year. Either way, the first step in preparing this week’s sermon was taken weeks ago.

Stage 1 — Study the passage (about 3 hours)

The goal of the study stage is to understand what the text meant to its first readers before deciding what it means for yours. Skipping this is how sermons become opinions with a verse attached.

Read it more times than feels necessary

Read the passage aloud in your main translation, then in one or two others. Read the whole chapter, then the paragraph before and after. Note where the unit of thought begins and ends; chapter and verse divisions are medieval additions and are often wrong about that. Write down every question the text raises, every repeated word, every command, every contrast, every “therefore.” This raw observation is where the sermon actually comes from.

Settle the context

Answer four questions in writing, even briefly: Who wrote this and to whom? What was happening to them? Where does this passage sit in the argument of the book? What kind of literature is it (letter, narrative, poetry, prophecy, apocalyptic)? Genre changes everything: a psalm is not preached like a Pauline argument, and an Old Testament narrative is not a list of morals with names attached. Our guide on how to study a Bible passage for preaching walks through this inductive method in more depth.

Do the word work — carefully

Identify the two or three words the passage turns on and look them up in the original language. You do not need seminary Greek to do this responsibly; you need a good lexicon and the discipline to ask how the word is used in this book by this author, not what its root “really means.” (The root fallacy — “dynamis means dynamite” — has embarrassed a great many pulpits.)

Only now open the commentaries

Read two or three commentaries of different kinds — one technical, one pastoral — and note where they confirm your reading, where they correct it, and where they disagree with each other. Log what you take from them. A commentary should sharpen a sermon you already have, not supply one you do not.

Output of Stage 1: a page of observations, a paragraph of context, a short list of key words with your findings, and a first draft of the passage’s main point in your own words.

Stage 2 — Find the big idea and build the structure (about 2 hours)

Haddon Robinson’s rule still holds: a sermon should be a bullet, not buckshot. Before you outline anything, write one sentence that answers two questions — What is this passage talking about? (the subject) and What is it saying about that? (the complement).

Weak: “Philippians 2 is about humility.” Better: “Because Christ emptied himself for us, the church is called to count others more significant than itself.”

The second sentence can be preached. The first can only be discussed. If you cannot write the sentence, go back to Stage 1; the sermon is not ready to be built.

Choose a structure that fits the text

There is no single correct sermon shape, but there are five reliable ones:

Structure	Best for	Shape
Textual / expository	Epistles, wisdom literature	Points follow the passage’s own divisions
Three-point deductive	Doctrinal passages, topical sermons	State the big idea early; each point supports it
Inductive	Skeptical or mixed audiences	Raise the question; walk toward the big idea; land it near the end
Problem – solution	Applied and pastoral sermons	Name the human problem, show the text’s answer, apply
Narrative	Gospels, Old Testament stories	Scene, tension, turn, resolution — the big idea emerges from the story

Our sermon outline template article gives fill-in-the-blank versions of all five with worked examples. Whichever you pick, every main point should be a full sentence, not a label, and each should be traceable to the text.

Output of Stage 2: the big idea, the structure with two to four main points as sentences, and the verses that support each point.

Stage 3 — Illustrate each point (about 1 hour)

An illustration exists to make a truth visible, not to entertain. The test for any illustration is simple: does the listener understand the point better after it than before? If the story is memorable but the point is not, cut it.

Good illustrations come from six places, in roughly this order of usefulness:

1. The Bible itself — a parallel story or a type that the passage echoes.
2. Your congregation’s shared life — the town, the season, last month’s funeral (with permission and discretion).
3. History and biography — specific, sourced, and short.
4. Analogy — “faith is like…” explanations that make an abstract point concrete.
5. Your own experience — used sparingly; the sermon is not about you.
6. Culture — films, news, sports; useful, but they age fast and divide rooms.

Aim for one illustration per main point, and never three in a row. The full list of sources, with a test for weak illustrations, is in how to find sermon illustrations that actually land.

Output of Stage 3: one illustration per point, each written out in two or three sentences so you know it works.

Stage 4 — Write the application (about 1 hour)

Application is where most sermons go vague. “Let’s all be more humble this week” is not application; it is a restatement of the point with a time limit attached. Specific application answers the question a listener is silently asking: What would this look like on Tuesday?

A simple grid helps. For each main point, ask what it asks of the listener’s:

• Head — what must they believe or stop believing?
• Heart — what should they feel, grieve, hope for, or repent of?
• Hands — what could they do this week, concretely?
• Habits — what pattern would change over a year if they took this seriously?

Then write applications for two or three different people in your room: the new believer, the exhausted parent, the retiree who has heard this passage sixty times. If an application would sound the same in any church in the country, it is probably too generic for yours. We work through examples from three passages in our article on sermon application.

Output of Stage 4: two or three concrete applications per point, at least one of which names a specific situation.

Stage 5 — Write the manuscript and rehearse (about 3 hours)

Now, and only now, write the sermon from beginning to end. Writing a full manuscript — even if you will preach from an outline — forces you to find the transitions, discover that point two is really two points, and hear where the introduction drags.

The introduction

You have about ninety seconds before people decide whether to listen. The introduction should do three things: surface a real need or question, show that this passage speaks to it, and tell the room where you are going. It should not summarize the whole sermon and it should not apologize for the passage being hard.

The body

Write the sermon the way you talk, in short sentences. Read every paragraph aloud as you finish it. Mark the transitions between points explicitly — “That is the first thing this passage says. The second is harder.” — because listeners cannot see your headings.

The conclusion

Land the plane once. A good conclusion restates the big idea in fresh words, makes the primary application unmistakable and stops. The most common preaching mistake is three conclusions in a row; the second most common is introducing new material in the last two minutes.

Rehearse out loud

Preach it once, alone, standing up, timed. Cut what runs long. Note where you stumbled — that is usually where the thinking is unclear, not the wording. If you preach from notes, distill the manuscript to one page now; if you preach without notes, this is where you memorize the structure rather than the sentences.

Output of Stage 5: a finished manuscript or one-page outline, timed, and a small stack of things you cut and can use another week.

A worked example: Philippians 2:1–11 in five stages

Study. The passage sits inside Paul’s appeal for unity in a church he loves (1:27–2:18). The “therefore” of 2:1 ties it to the call to stand firm together in 1:27. The controlling verb is “count” (hēgeomai, 2:3, 2:6): the Philippians are to count others more significant, because Christ did not count equality with God something to be grasped. The hymn of verses 6–11 is not there to teach Christology for its own sake; it is the example that makes the command in verse 3 possible.

Big idea. Because Christ counted our good above his rights, we can count each other above ourselves.

Structure (textual, three moves). (1) The call: unity built on humility (vv. 1–4). (2) The pattern: Christ’s descent (vv. 5–8). (3) The promise: God’s vindication of the humble (vv. 9–11).

Illustrations. For (1), the church that split over the color of the carpet — a real pattern with the names removed. For (2), the analogy of a surgeon who leaves the operating theater to sit on the floor with a frightened child: not less a surgeon, but choosing the lower place. For (3), the historical example of a leader whose reputation was restored only after death.

Application. Head: humility is not thinking less of yourself; it is counting others more significant. Heart: where do I feel my rights most keenly in this church? Hands: one conversation this week in which I let the other person be right. Habits: a year of asking “what does this person need?” before “what am I owed?”

Manuscript. An introduction that starts with the carpet story, not the Greek; three moves of roughly equal length; a conclusion that returns to “count” one last time and stops.

Total time on that sermon, following the budget above: about ten hours across four days.

A weekly schedule that protects your weekend

The single most effective change most pastors can make is moving preparation earlier in the week and splitting it into separate sittings. A workable pattern for one sermon a week:

Day	Stage	Time
Monday (or your first study day)	Stage 1 — read, observe, context	2 h
Tuesday	Stage 1 finish (words, commentaries) + Stage 2	3 h
Wednesday	Stages 3 and 4	2 h
Thursday	Stage 5 — manuscript	2–3 h
Friday	Rehearse, trim, prepare slides/notes	1 h
Saturday	Rest. Read the manuscript once in the evening.	—

If Saturday is currently your main writing day, this schedule will feel impossible for about three weeks and then feel obvious. We look at why sermon prep bleeds into the weekend and how to stop it in The Saturday Night Problem.

How Pastor Rhema fits

The five stages above are exactly how Pastor Rhema is built. Its guided workflow moves through Study & Context, Sermon Structure, Illustrations, Applications and Final Sermon in that order, with the research — context, original-language notes, cross-references — gathered for you at the first step and the draft exported to Word, PDF or slides at the last. The decisions in the middle remain yours, which is the point: it shortens the mechanical parts of the process so the pastoral parts get your best hours.

Common mistakes and how to avoid them

Opening the commentary first. You will preach the commentator’s sermon and wonder why it does not sound like you. Read the text first.

Outlining before you have the big idea. Points without a governing sentence produce three short sermons instead of one.

Too many illustrations. One strong illustration per point. If you have a great story that does not fit this week, keep it; it will fit another.

Generic application. If it could be said about any passage, it is not application of this one.

Writing on Saturday. Fatigue makes for long, unclear sermons and short, tense Saturdays. Move the writing to Thursday.

Never rehearsing. The first time you say the sermon aloud should not be in front of the church.

Conclusion: a process you can repeat

Learning how to prepare a sermon is not a matter of finding the perfect method but of having a method you follow every week, in the same order, in separate sittings, early enough that Saturday is free. Study before structure; structure before illustration; illustration before application; application before manuscript. Write the big idea in one sentence. Rehearse aloud. Then preach it as your own — because, after all that work, it is.

Print the checklist below, tape it inside your study Bible, and see whether your Saturday nights change.