Sermon prep deserves better than a Google Doc
The most important hour a pastor spends on Sunday
starts on Tuesday morning, in a document.
Most pastors write sermons in a word processor. That works — until the slide team asks for the final scripture references on Friday, the communications director needs a sermon title for the bulletin by Wednesday, and three weeks later someone wants the manuscript for the church library and nobody can find it. Sermon prep ends up scattered across documents, drives, and emails. The one thing that took the most time becomes the hardest to retrieve.
Sermon Planning is a workspace built for the actual work of preparing a sermon. It treats the manuscript as a first-class object — versioned, linked to a service plan, organized into series, and tied to scripture references that load the passage inline. When the sermon is done, it's already in the right place. When it's archived, it's already searchable. When the slide team needs the final references, they're reading the same record the pastor is writing in.
Pastors don't adapt to the tool. The tool adapts to how pastors actually study, write, refine, and deliver.
Two modes for the same sermon. Switch when the writing demands.
Some pastors think in outlines — three points, a conclusion, the moves between them. Others write full manuscripts, every word committed to paper before they preach. Most do both at different stages: outline first, manuscript second, then a final pass to mark the moments where they'll come back to the outline live.
Sermon Planning supports both, in the same document. Toggle to outline mode and see the structure. Toggle to manuscript and see the prose. Edits in one mode show up in the other. The bullet you moved in outline mode lifts the matching paragraph in the manuscript with it.
- Manuscript and outline are two views of one sermon
- Drag a point in outline mode, the prose moves with it
- Per-section word count + estimated speaking time
- Distraction-free writing mode for the first draft
Type the reference. The passage appears.
When a pastor writes “Romans 8:28” in the manuscript, the passage loads next to the cursor — full text, in whichever translation the church has chosen as the default. No more leaving the document to look up a verse. No more pasting in text that drifts from the actual translation.
Switch translations and the inline text re-renders. The slide team picks up the same references from the same record, so what's on screen Sunday matches what the pastor wrote Tuesday.
- Inline scripture passages — type the reference, read the verse
- Default translation per church; per-sermon override available
- Reference list auto-generated for the slide team and the bulletin
- Cross-reference suggestions surfaced from passages in the same week
A sermon is a piece of an arc. The workspace knows.
Sermons rarely stand alone. They're part of a series — a six-week arc through Ephesians, a four-week Christmas series, a topical year-long walk through the parables. Sermon Planning groups every sermon under a Series record, so you can see the arc, jump between weeks, and catch the week-three sermon that accidentally covers the same passage as week one.
When a series ends, it's already a body of work — every sermon in the arc, published to the library together, with the series narrative intact. Visitors browsing your sermon archive find a series the way they'd find an album, not a pile of standalone files.
- Series grouping with arc-level metadata (title, hero image, summary)
- Cross-sermon scripture conflict detection within a series
- Series-level publishing to the public sermon library
- Reusable series templates for recurring annual rhythms
The rest of the workspace
What else lives in a sermon record.
Manuscript and outline are the heart. These are the parts that surround them.
Status pipeline
Draft → ready → delivered → archived. The executive admin can see at a glance whether next Sunday's sermon is ready or still in draft. The slide team knows when references are final. Nobody asks “is the sermon done?” on Friday again.
Prep notes + study trail
A side panel for the commentary excerpts, the cross-references, the illustrations, the pastoral-conversation memories that fed the sermon — separated from the manuscript but tied to it, so the study trail survives.
Tied to the service plan
Every sermon record links to the service plan it's scheduled for. Pull the manuscript open from the service's Sunday tab, or open the service from the sermon. Worship, production, and the bulletin all read the sermon record for context.
Speaking-time estimate
Word count plus a configurable speaking-words-per-minute rate gives a live time estimate. Including buffer for pauses, response moments, and a typical sermon's ad-lib factor.
Version history
Every save creates a version. Roll back to Tuesday's draft if Friday's rewrite went the wrong direction. The Saturday-night edit doesn't overwrite Tuesday's research.
One-tap publish
When the sermon is delivered, one tap moves it from prep to the public sermon library — title, summary, scripture references, audio, video, manuscript (if you want), all packaged for the congregation to revisit.
From Tuesday study to Sunday delivery — one place, the whole way.
Tuesday morning, a pastor opens the sermon for the upcoming Sunday, adds three scripture references they pulled from study time the night before, and roughs out the outline. The status reads “draft.” By Thursday, the manuscript is most of the way through, references are finalized, and the slide team is already building from the reference list. The status flips to “ready.”
Saturday night, the pastor revises one paragraph and tightens the conclusion. The version history keeps both. Sunday morning, the manuscript is on a tablet at the pulpit, the slides are on the screens, and the references are in the bulletin. After the service, one tap publishes the sermon to the library. By Monday, it's searchable, listenable, and part of the series record.
No documents were emailed. Nothing was copied between tools. The sermon archive built itself.