I.M.P.A.C.T. Church Empowerment Program

A partnership with Pastor Lee Jenkins, the Stewardship Coach, and Allan Bell - CPA, CMA, MBA, Nsites founder and creator

M5 Magnification · Lesson 3 of 4

Lesson 3 — Worship Flow and Ministry Coordination

Review the service as one coordinated experience.

Not started

Nine M curriculum version 1.0 · Nine M methodology, content, exercises and deliverables by Pastor Lee Jenkins.

Where this lesson sits

Curriculum version 1.0 · Pastor Lee Review

Module purpose: Improve the complete shared worship and Sunday experience — from the parking lot to the pew — so that it is hospitable, excellent, accessible, spiritually focused, and consistent.

Official outcome: Sunday Experience Improvement Plan

This lesson produces: Service Timeline Review

Anything you type is kept in this browser session only. This prototype does not save to a server.

Learn

Participant study reading — approximately 75 minutes of learning and shared work.

Learning objective: Review the service as one coordinated experience.

Recommended participants: Pastor, worship pastor, service producer or platform coordinator, ministry leads whose segments appear in the service

Estimated teaching time: 75 minutes

Success indicators

  • • A complete service timeline exists naming every segment and its planned duration
  • • Unclear transitions between segments are specifically identified
  • • Avoidable delays are named with their likely cause
  • • Every segment of the service has a named owner responsible for its timing and handoff

Materials and evidence you will use

  • • Recent orders of service
  • • Guest Journey Map and Hospitality Standards from Lessons 1 and 2
  • • All service segments reviewed with planned and actual duration
  • • Every ownership gap identified has a proposed owner

What you should be able to produce

  • • A complete service timeline exists naming every segment and its planned duration
  • • Unclear transitions between segments are specifically identified
  • • Avoidable delays are named with their likely cause
  • • Every segment of the service has a named owner responsible for its timing and handoff

Foundational ministry principle

1 Corinthians 14:40

40 Let all things be done decently and in order.

King James Version (KJV) · Public domain

This passage's instruction that everything be done decently and in order offers a direct scriptural frame for reviewing the coordination of the worship service.

Draft language for review: if orderliness in worship reflects reverence rather than mere efficiency, then reviewing transitions and delays becomes a way of honoring the service, not simply managing a schedule.

Understand the concept

Your work in this lesson focuses on this outcome: Review the service as one coordinated experience.

Smooth worship flow is not the product of talent alone; it is the product of clear ownership and honest attention to the transitions between segments.

Why it matters for your church

A service that feels disjointed to a guest is often the sum of many small, unowned transitions rather than one large problem.

Reviewing the timeline honestly can reveal that certain delays are structural and predictable, not incidental.

Naming a clear owner for every segment reduces the burden on any single person, usually the pastor, to notice and fix timing problems in the moment.

Examine the evidence

Use Recent orders of service, and Guest Journey Map and Hospitality Standards from Lessons 1 and 2 to compare your church's present practice with its stated intentions. Look for documented patterns, missing information, and differences between what people assume and what the evidence supports.

Your completed work should be supported by All service segments reviewed with planned and actual duration, and Every ownership gap identified has a proposed owner. Record uncertainty honestly so your team knows what still needs to be verified.

Prepare for the shared exercise

Build a complete timeline of the worship service naming unclear transitions, avoidable delays, participation barriers, and ownership gaps. The Service Timeline Review Session produces the Service Timeline Review, which contributes to the module's principal deliverable.

Before working with your team, consider this reflection: Recall the last Sunday you attended. Which transition did you barely notice because you already knew what to expect, that a guest might have found confusing?

Key terms

Service timeline
A segment-by-segment record of the service's planned and actual timing, with an owner named for each segment.
Transition
The moment one segment of the service ends and another begins.
Ownership gap
A segment of the service where no one is clearly responsible for its timing and handoff to the next segment.

What this means for a church

  • • A service that feels disjointed to a guest is often the sum of many small, unowned transitions rather than one large problem.
  • • Reviewing the timeline honestly can reveal that certain delays are structural and predictable, not incidental.
  • • Naming a clear owner for every segment reduces the burden on any single person, usually the pastor, to notice and fix timing problems in the moment.

Common failure patterns

  • • Reviewing only the parts of the service that already have vocal complaints, while ignoring quietly recurring delays.
  • • Assuming smooth transitions require more rehearsal rather than clearer ownership and cues.
  • • Treating this review as a one-time fix rather than something worth repeating as the team and service evolve.

Ministry case

The Three Minutes Nobody Owned

At a fictional congregation, leadership noticed that the transition from the offering to the sermon consistently took an extra three minutes every week, though no single person felt responsible for it. The worship team assumed the pastor would signal when ready, and the pastor assumed the platform team would cue the transition once equipment was reset.

During a service timeline review, this gap became obvious once someone finally timed it across three consecutive Sundays. The fix was simple: the platform coordinator was given clear ownership of that transition, with a specific cue to signal the pastor.

Within a month, the transition dropped from three minutes to under thirty seconds, and several volunteers commented that the whole service felt calmer, even though nothing about the sermon or worship set had changed. This case shows how naming ownership, not adding more effort, often solves coordination problems.

Lesson takeaway

Smooth worship flow is not the product of talent alone; it is the product of clear ownership and honest attention to the transitions between segments.

Discuss

Guided discussion for the leadership table.

With the categories of delay, barrier, and ownership gap fresh in mind, move the group into the exercise by assigning each ministry lead present to walk through the segments closest to their own area first.

  1. Which transition in our service currently feels the least clear to a first-time guest?
  2. Where have we assumed someone else owns the timing of a segment?
  3. Which delay in our service is structural and predictable rather than occasional?
  4. What would change if every segment had one clearly named owner?

Practice

Applied exercise — produces the Service Timeline Review.

Service Timeline Review Session

Build a complete timeline of the worship service naming unclear transitions, avoidable delays, participation barriers, and ownership gaps.

Estimated time: 35 minutes

Participants: Full lesson group, organized by service segment

Artifact produced: Service Timeline Review

Required inputs

  • • Recent orders of service
  • • Observed start and end times from the last two to three Sundays

Instructions

  1. List every segment of the service in order with its planned duration.
  2. Record the actual observed duration for each segment based on recent Sundays.
  3. Identify whether the transition into that segment is clear or unclear, and why.
  4. Note any avoidable delay associated with that segment and its likely cause.
  5. Note any participation barrier a guest might experience during that segment.
  6. Name the current owner responsible for that segment's timing and handoff.
  7. Flag any segment with no clear owner and propose who should take ownership.
Complete it online

Service Timeline Review

  • Sundays observed: ______________________
  • Reviewed by: ______________________
SegmentPlanned/actual durationTransition clarityDelay or barrier notedOwner
     
     
     
     
     
     
     
     
     

Worked example

A fully completed sample using a fictional church. This is illustrative teaching material, not any church's actual data.

Northgate Community Church (illustrative example — not actual church data)

This worked sample continues the fictional Northgate Community Church example, showing how a Service Timeline Review surfaced coordination issues across a typical Sunday.

SegmentPlanned/actual durationTransition clarityDelay or barrier notedOwner
Pre-service welcomePlanned 3 min / actual 3 minClearNone notedPlatform coordinator
Worship setPlanned 20 min / actual 24 minClear into segment, unclear exit cueSet runs long with no signal to wrap upWorship pastor
AnnouncementsPlanned 5 min / actual 8 minUnclear; no consistent handoff from worshipPresenter waits for stage to be readyUnassigned
OfferingPlanned 4 min / actual 4 minClearNone notedUshers lead
Offering to sermon transitionPlanned 1 min / actual 3 minUnclear; no cue between teamsEquipment reset causes delayUnassigned
SermonPlanned 30 min / actual 32 minClearNone notedPastor
Response timePlanned 5 min / actual 5 minUnclear for guests; no explanation givenFirst-time guests unsure what response meansPastor
Closing and dismissalPlanned 2 min / actual 2 minClearNone notedPlatform coordinator
Children's ministry pickupPlanned 5 min / actual 9 minUnclear; check-out process is slowSingle check-out station creates a lineChildren's ministry lead

How this leadership team reasoned

  • • Leadership found that most delays clustered around transitions between teams rather than within any single segment, confirming that ownership, not talent, was the core issue.
  • • They noted that the response time barrier for guests echoed a friction point already identified in the Guest Journey Map, showing how the lessons build on each other.
  • • The children's ministry pickup delay was flagged as a priority since it directly affects whether parents feel comfortable staying through the full service.

Decisions recorded

  • • Assign the platform coordinator ownership of the worship-to-announcements and offering-to-sermon transitions, with a specific visual cue for each.
  • • Add one sentence of guidance for guests during the response time script.
  • • Open a second children's ministry check-out station to reduce pickup delay.

Completed artifact extract — Service Timeline Review

Service Timeline Review: Northgate Community Church. Nine segments reviewed across recent Sundays; two transitions currently unassigned; two segments running consistently over planned duration; children's ministry pickup identified as a priority delay to resolve within two weeks.

Illustrative exercise score: 18 of 20. The timeline is complete and specific, drawing directly on observed durations across multiple Sundays, with clear ownership proposed for every previously unassigned transition.

Score

Transparent 20-point exercise rubric: four criteria rated 0 to 5 with observable anchors.

Criterion0 — not evident3 — acceptable5 — exemplarySample
Completeness (0–5)Only a few segments of the service are reviewed.Most segments are reviewed but one or two, such as children's ministry pickup, are omitted.Every segment of the service from welcome to dismissal and pickup is reviewed.5
Use of evidence (0–5)Durations and issues are estimated with no reference to actual recent Sundays.Some durations are based on observation, others are estimated.Every duration is based on actual observation across multiple recent Sundays.5
Alignment to the module purpose (0–5)The review does not connect to hospitality, accessibility, or the guest experience.The review addresses timing but does not connect findings to the guest experience.The review explicitly connects timing and transition issues to guest experience and earlier findings.4
Actionability and ownership (0–5)No segment has a proposed owner or next step.Some segments have proposed owners, others remain unassigned.Every previously unassigned segment now has a proposed owner and next step.4
Worked sample total18 / 20
  • Completeness: All nine segments of the service were reviewed with duration and ownership noted.
  • Use of evidence: Planned and actual durations were recorded from observed Sundays for every segment.
  • Alignment to the module purpose: The response-time barrier was explicitly connected to the Guest Journey Map, though not every segment was tied back this directly.
  • Actionability and ownership: Both previously unassigned transitions were given clear proposed owners and next steps.

Lesson-exercise scores (20 points each) demonstrate learning and artifact quality. They do not automatically overwrite the official Nine M module assessment, which remains a separate 100-point rating of five module dimensions.

Submit evidence

What must be submitted for this lesson to count as complete.

Submit

  • • Completed Service Timeline Review worksheet

Attach this evidence

  • All service segments reviewed with planned and actual duration
  • Every ownership gap identified has a proposed owner

File upload is not implemented in this prototype. Ticking a box records that the church can produce the document; it does not store a file.

Contribute to official outcome

How this lesson builds the Sunday Experience Improvement Plan.

Artifact produced: Service Timeline Review

This review becomes the worship-flow and coordination section of the Sunday Experience Improvement Plan, giving the service a documented, owned structure.

Open the module deliverable assembly

Participant reflection and notes

Recall the last Sunday you attended. Which transition did you barely notice because you already knew what to expect, that a guest might have found confusing?