How to plan a Sunday
service running order.

Start with the shape of the gathering

List the moments your church needs: welcome, worship, Scripture, message, prayer and announcements. Choose a service start and finish time, then give each part a realistic duration. Leave room for transitions rather than using every minute on paper.

Agree the plan with the people responsible for each part. A useful running order names an owner, not just an activity.

A one-hour running order example

This is an example to adapt with your church team, not a fixed format for worship. A transition is included in each activity's time allowance.

Write the cues Tech can act on

Replace vague instructions such as 'play video later' with the file name, the moment it is needed, whether it has audio and who gives the cue. Confirm Bible references and translations before the service.

Share the agenda, preparation notes and files with the same service. If something changes, put the update in that service's conversation so the operator can find it.

Check the plan before people arrive

1. Confirm the running order and the person leading each part.
2. Check the lyrics, Bible passages and announcements.
3. Import and review slides, images and video. Check audio separately.
4. Test the audience display and microphones, then agree the cues with Tech.
5. Make sure saved services and needed local media are available on the presentation computer.

Keep one current plan during the service. Afterward, note any useful changes for next time and keep the completed plan with that gathering.

Keep planning and member notes separate

The team's running order may include private preparation. Write a separate member-facing summary and review it before publishing. Include the highlights, verses and next steps your church wants people to revisit.