Order of Service Template: A Starting Point for Your Sunday

An order of service template is a written run sheet listing every segment of a Sunday gathering — pre-service countdown, worship set, notices, offering, sermon, response, and dismissal — with rough timings, so whoever is planning doesn't start from a blank page. Below is one illustrative structure; most churches adapt it heavily.

A sample order of service, segment by segment

There's no single "correct" order of service — a Baptist church, a Pentecostal fellowship, and a Vineyard-style gathering will each shape their Sunday differently, and even within one church the shape shifts from season to season. What follows is a common starting structure for a typical one-hour-to-ninety-minute evangelical Sunday gathering. Treat it as scaffolding to edit, not a script to follow exactly.

Add it up and a fairly standard Sunday runs somewhere between 60 and 95 minutes depending on sermon length and how much room you leave around worship and response. None of these timings are fixed — a church that leans heavily charismatic might give worship and response 30+ minutes and trim the sermon; a teaching-focused church might do the reverse. The point of writing it down isn't to enforce a formula, it's so that everyone running the service is working from the same expectations for how the morning will flow.

How to adapt the template for a normal Sunday

Most weeks, adapting this template is just filling in the specifics: which songs, who's preaching, what the notices are, who's on the rota for welcome and tech. The shape stays roughly the same, and a lot of churches simply duplicate last week's document and edit it rather than starting fresh — which is exactly why having one shared, living version matters more than having a perfect one.

Special services need extra segments, not a different document

Some Sundays don't fit the standard shape, and the template needs genuine additions rather than just re-timing the same blocks:

• Baptisms — usually inserted after the opening worship set or just before the sermon, with extra time for testimonies, a change of clothes, and often a dedicated song. Budget an extra 15-25 minutes and make sure the tech booth knows in advance if there's a baptism tank or pool involved, since it usually needs its own camera angle or mic.
• Communion — typically slotted in during or right after the response section, needing extra prep time before the service (elements set out, servers briefed) and a few extra minutes in the run sheet itself, plus a note on whether it's served at seats or people come forward.
• Guest speakers — usually need a longer welcome/introduction segment, a briefing on your church's usual sermon length and any equipment they're bringing (their own slides, a translator, notes format), and often a slightly different response section if they're used to ending a different way than your regular preaching team.
• Communion + baptism + guest speaker on the same Sunday — happens more than planners expect around Easter, anniversaries, or missions Sundays. When it does, the run sheet usually needs building fresh rather than bolted together from three separate templates, with real timings tested against how long the service will actually run.

In every case, the fix isn't a separate system for "special" services — it's the same order of service document with extra rows added, so the tech booth and welcome team are reading the same additions everyone else is.

Share the finished order with the whole team — not five different versions

The most common failure point isn't a badly planned order of service — it's a well-planned one that never reaches everyone who needs it in the same form. A worship leader builds a set list in one app, notices get typed into an email, the tech booth is handed a printed sheet from last week with pen amendments, and the welcome team never sees a document at all, just a verbal "usual stuff, plus we've got visitors today." By Sunday morning, four people are each working from a slightly different picture of how the service will run.

A shared order of service — one document that the worship leader, tech booth, and welcome team can all see, at the same time, in its current state — removes that gap. Everyone is looking at the same segment list, the same rough timings, and the same last-minute notes, rather than five people's individual interpretations of a conversation from last Tuesday.

Why a living, shared plan beats a printed sheet

A printed order of service is accurate the moment it's printed and steadily less accurate after that. The guest speaker confirms a different arrival time on Thursday, a song gets swapped on Friday because the worship leader wants something that fits the sermon topic better, and the printed sheet in the tech booth's folder still says the old plan — because updating a paper copy means reprinting it and physically replacing it in everyone's hands, which almost never happens for a mid-week change.

A shared, living plan solves this by having exactly one version that everyone reads from directly, rather than one master copy and several stale duplicates. When the worship leader edits the set list on Friday, the tech booth's copy is the same edit — not a separate document that needs updating too. That's the practical reason a shared plan tends to hold up better under real Sunday-morning conditions than the most carefully formatted printed sheet: it's current by definition, because there's only one of it.

Frequently asked questions

Is there one correct order of service for an evangelical church?

No. The structure above is a common starting shape, but churches vary it a great deal — some spend far longer in worship, some lead with notices, some place the offering at the very end. Use a template as a starting point, then shape it to how your church actually runs.

How long should the opening worship set be?

Most small-to-mid churches run 15-20 minutes across 2-3 songs, though this varies with tradition — more charismatic or Pentecostal-leaning churches often extend it, while teaching-focused churches may trim it to make more room for the sermon.

How far in advance should the order of service be finalised?

Aiming for midweek (Wednesday or Thursday) gives the worship leader, tech booth, and welcome team time to prepare, while still leaving room for late changes — a guest speaker's arrival time, a swapped song — to be updated in the shared document rather than causing confusion on Sunday.

How do I add a baptism or communion without throwing off the whole timing?

Treat it as an added segment with its own realistic time estimate (typically 15-25 minutes for a baptism, a shorter addition for communion) rather than assuming it will "fit" inside an existing slot — then adjust the surrounding segments so the whole service still lands at a reasonable total length.

What's the difference between an order of service and a run sheet?

In practice, evangelical and free churches use the two terms interchangeably — both describe the timed list of segments for a Sunday gathering. "Run sheet" is more common language among tech volunteers; "order of service" is more common from the platform or among pastoral staff.

Does Ekkli include a way to share the order of service with my team?

Ekkli's free trial includes presentation/worship display, a subdomain website, member database, rota and scheduling, push notifications, and a sermon-audio player with a rolling two-hour storage window — free for up to 50 people, no card required. Paid plans add a custom domain, email campaigns, podcast RSS with long-term storage, and higher people caps.