Exegesis vs Eisegesis: Three Red Flags You'll See in Your Own Sermon Notes

Exegesis vs Eisegesis: Three Red Flags You'll See in Your Own Sermon Notes

By Saturday at 10 p.m., the question isn't exegesis vs eisegesis as a seminary definition. The question is whether the point you built three illustrations around is actually in the text, or whether you carried it in with you when you opened to the passage on Monday.

Here's the working version that matters when you're staring at a sermon manuscript: exegesis is the meaning you can defend from the words on the page. Eisegesis is the meaning that was already in your head before you read the chapter. Both feel the same while you write. They sound very different from the pew six weeks later, when a congregant quotes your sermon back to you as if it were Scripture.

This piece gives you three red flags that show up in your own study notes when eisegesis is creeping in, and the specific tools on Selah that catch each one. A congregation memorizes the sermon, not the footnotes. If the reading is off, it gets repeated for years.

Key takeawaysBefore you write a single application bullet, paste the full pericope plus the chapter before and after it at the top of your sermon doc. If you can't defend your point from those verses, cut the point.Run every sermon's key verb or noun through a Strong's interlinear check. If the English word you're preaching on covers three different Greek or Hebrew words across the passage, your sermon needs to address which one is actually there.Read a pre-1900 commentator on your passage before reading any contemporary source. If Matthew Henry didn't see what you're seeing, ask why your reading needed the last 50 years of culture to become obvious.Write down the one sentence a congregant will quote back to you in six weeks. If that sentence isn't a direct paraphrase of a clause in the text, rewrite it until it is.

On this pageRed flag #1: your application showed up before your outline didRed flag #2: your big word means something different in Hebrew or GreekRed flag #3: the character or place in your illustration isn't doing what you said they didA 20-minute self-audit before the sermon leaves your deskWhen the text won't say what you wanted it to say

Red flag #1: your application showed up before your outline did

The tell is simple. You wrote the closing illustration, or the three application bullets, before you finished reading the passage in its full context. The sermon's shape now decides what the verse is allowed to say.

What this looks like in your notes

Open your Monday document. If the bottom of the page has "So what does this mean for us?" filled in before the top of the page has the pericope copied out with the surrounding chapter, you have already started backwards. The same thing happens when the sermon title was assigned in October for a January series, and now the January passage has to deliver on a title written by a different version of you.

How to test it against the text

Read the full pericope plus the chapter before and the chapter after in the Selah reader before any application line gets written. Then pull Matthew Henry on the chapter as a sanity check, not as a sermon source. If a careful 17th-century reader landed nowhere near your application, the burden of proof is on you, not on him.

Action: delete every application line written before the exegetical work. Rewrite them from the passage. If a line survives the rewrite untouched, fine. Most won't.

Red flag #2: your big word means something different in Hebrew or Greek

The tell here is that your main point hangs on an English word, used the way modern English uses it. Hope. Fear. Know. Love. Flesh. Peace. Each of these carries freight in the original that the English flattens.

The English-shaped sermon point

Take "the peace of God, which passeth all understanding" in Philippians 4:7. Modern English peace is a felt calm, the absence of anxiety. Eirene in Paul's vocabulary carries the weight of Hebrew shalom: covenant wholeness, right relation, the state of things being as God intends. A sermon built on "feel calm" is preaching a narrower thing than Paul wrote. Not wrong exactly. Smaller.

Checking the word against Strong's

In Selah, open the Strong's interlinear reader, click the word, read the concordance entry, then jump to two or three other verses where the same Strong's number appears. If your sermon definition still fits in all of them, good. If it only fits in your verse, you've narrowed the word to make it preach.

The word study fallacy. A lexicon gives you the range of a word's possible meanings across the canon. It does not give you permission to import every meaning into one verse. Sarx doesn't mean "flesh, body, sinful nature, kinship, and human weakness" all at once in Romans 7. Context picks one. The reverse error is to ignore context entirely and let the dictionary preach the sermon for you.

Action: before you preach a word, list every other verse in Scripture that uses the same Strong's number. Ask whether your definition still works there. If not, narrow your claim.

Red flag #3: the character or place in your illustration isn't doing what you said they did

You can describe what a biblical figure "was thinking" or "had been through," but you can't cite the verse it comes from. That's the tell. The detail came from another sermon, a film, or a children's Bible, and it has been sitting in your memory long enough to feel canonical.

When the backstory is borrowed from a sermon you heard

Common culprits: David's exact age at Goliath, what Bathsheba knew and when she knew it, why Jonah ran, what the innkeeper said in Bethlehem, the geography of the road in the Good Samaritan. Most of these come from other preachers, not from the text. Repeated often enough, they become "what the Bible says."

Verifying with character and place profiles

Selah's 272+ character profiles give you every verse a figure appears in, plus family tree and life timeline. Pull those before you describe motive. The 111+ place profiles include coordinates and modern names. Jerusalem to Jericho is roughly 18 miles and drops about 3,400 feet in elevation. That detail preaches. The invented one embarrasses you six months later when a retired geologist in row four mentions it after the service.

Action: for every named person and place in your sermon, paste the verse list into your notes. If a claim about them isn't backed by a verse, cut it or label it as tradition out loud from the pulpit.

A 20-minute self-audit before the sermon leaves your desk

Run this Saturday night. It takes under half an hour if your notes are already in front of you, and it catches most of what would have made you wince Monday morning.

Run the passage, the words, the names

1. Read the passage cold in one translation, then a second translation, and write the main point in one sentence with no commentary open. Compare to the main point in your manuscript. If they're not close, something drifted between Monday and Saturday.
2. Run Strong's on the two or three load-bearing words in your sermon point. Confirm your definition holds in at least two other verses that use the same number.
3. Pull cross-references via Treasury of Scripture Knowledge for the verse your point depends on. If TSK's linked passages pull your reading in a different direction, you have eisegesis to fix, not a footnote to add.
4. Check every character and place claim against the Selah profiles. Verse list or cut it.
5. Read Matthew Henry on the chapter last, after your own work. Use it to test your reading, not to source it.

Then run the cross-references

Step 3 is the one most preachers skip and the one that catches the most. A point that's true in your verse but contradicted by three cross-referenced verses isn't a sermon point. It's a hunch wearing a sermon's clothes.

Action: save the audit as a recurring checklist in whatever app holds your sermon files. Don't try to remember it. Saturday-night you is not the version of you to trust with that.

When the text won't say what you wanted it to say

Sometimes the audit kills the point you were excited about on Tuesday. That isn't a system failure. That is the system working. The same tools that protect your congregation from a bad reading just protected them this week.

Two honest options. Preach the text you actually have, even if it lands smaller than you hoped. Or pick a different text that genuinely teaches what you wanted to say, and preach that next week. The middle path is the one to refuse: keeping the original point and softening it with "the principle here is" language. That's eisegesis with a disclaimer attached.

Congregations trained on exegetical preaching learn to read their own Bibles the same way. That is the deeper win, and it compounds.— The long game

Keep a running file of sermon points you cut during the audit. One line each: the verse, the point you almost made, and why it didn't survive. Review it every six months. Your defaults will surface. The assumptions you keep importing into Scripture have a pattern, and once you can name the pattern, you stop importing it. That's the work behind every sermon worth preaching twice.

Frequently asked questions

How is hermeneutics different from exegesis and eisegesis?

Hermeneutics is the set of rules you use; exegesis and eisegesis are the outcomes. Hermeneutics asks how a covenant text from the 8th century BC should speak to a 21st-century church. Exegesis is what happens when you apply those rules honestly. Eisegesis is what happens when you skip them and import meaning anyway.

Is allegorical or typological reading the same as eisegesis?

No, but it can collapse into eisegesis quickly. Typology reads later Scripture as the interpretive authority on earlier patterns (Hebrews doing this with the tabernacle, for example). It becomes eisegesis when the type isn't actually claimed by another biblical author and you're the one assigning it based on a sermon hook.

Can a sermon be exegetically correct and still pastorally wrong?

Yes, and this is the harder failure to catch. You can preach the accurate meaning of a rebuke text to a congregation that needed comfort, or a comfort text to people who needed to be confronted. Exegesis tells you what the passage says. Pastoral judgment tells you which true thing your specific room needs to hear this week.

How much original-language work is realistic for a bivocational pastor each week?

Twenty focused minutes on two or three key words is enough if you use a Strong's interlinear rather than trying to parse from scratch. Pick the verbs the sermon hinges on and the nouns repeated more than twice in the passage. The Selah interlinear reader handles the lookup so the twenty minutes goes to thinking, not flipping pages.

Are study Bible notes exegesis or someone else's interpretation?

They're interpretation, usually well-defended, but still interpretation filtered by the editor's tradition. Treat them as a second opinion, not the text. The test is whether the note quotes the verse it's commenting on or quietly substitutes a paraphrase that already assumes the conclusion.

How do you pronounce exegesis and eisegesis?

Exegesis is ex-uh-JEE-sis. Eisegesis is eye-suh-JEE-sis. The prefixes carry the whole argument: ex means out of (drawing meaning out of the text), eis means into (reading meaning into it).

Pressure-test this week's sermon textPull up your passage in the Selah reader with Strong's interlinear, Matthew Henry's commentary, and the cross-references from Treasury of Scripture Knowledge side by side. It's free, no account required, and it's the fastest way to catch a reading you imported before Sunday morning catches it for you.Open the Selah reader →