Use case

A church timer for services that end on time

A countdown the preacher can see, a running order for the whole service, and silent cues from the sound desk — in the browser, on screens you already own.

3 min read5 stepschurch timer
TIME REMAINING
03:00

Every church knows the moment: the service is running long, the next thing is waiting, and nobody wants to be the person signaling the preacher from the back row. A church timer solves it structurally — a countdown the person speaking can see, warnings that arrive as colors instead of interruptions, and a service order that keeps every segment honest.

MaestroTimer does this in the browser, on hardware the church already owns. This page walks through the service setup: the pulpit display, the running order, and the sound desk's controls.

01

A countdown the preacher actually sees

The timer's viewer is a clean fullscreen countdown, and it reaches the platform through any screen with a browser: a confidence monitor at the stage edge, a tablet on the pulpit, or a repurposed TV on the back wall.

The setup:

  1. Create a room and add a timer for the sermon — timers carry a name, a speaker, and notes, so "Sermon — Pastor Dave" reads as exactly that on the schedule.
  2. Open the room's viewer link on the platform-facing screen and make it fullscreen. Every view in MaestroTimer is a link, so this is the entire installation.
  3. Set a wrap-up threshold. As time runs low the display changes its appearance — the preacher sees the warning without anyone in the booth doing anything.
02

The whole service as a running order

A service is more than the sermon: pre-service countdown, worship set, announcements, offering, closing. Give each its own timer and the list becomes the service order — named, timed, and visible to the team on the agenda view's own link.

Link the timers and each segment starts the moment the previous one ends. Schedule the first one and the pre-service countdown starts itself at a set time. Services that habitually run long can plan for it honestly: add a short buffer timer between segments — named "Transition" — so the running order absorbs the overrun instead of the closing song.

03

Silent cues from the sound desk

Control lives in the controller view, open on the booth computer or a volunteer's phone. Starting, pausing, and adjusting time happens there, and every screen follows.

When a segment needs more than a color change, send a message: a bold, colored, or flashing note appears on the platform display next to the countdown — "2 minutes to livestream cut", "kids ministry needs you after" — read by exactly the person who needs it, heard by nobody.

Before the service, the live connections view lists every device attached to the room. If the pulpit monitor and the lobby screen are on the list, they are receiving — checked from the booth, not by walking the building.

04

Built for volunteer teams

Church tech teams rotate, so the tool cannot assume training. Here the whole operational surface is links: the viewer for screens, the agenda for the team, the controller for whoever runs the service. A new volunteer opens a URL and is looking at the same thing last week's volunteer saw.

Nothing is installed, nothing is licensed per machine, and the room persists week to week — set up the service order once, adjust the details each Sunday.

05

FAQ

How does the preacher see the timer without the congregation seeing it?

Put the viewer link on a platform-facing screen — a confidence monitor or tablet angled at the pulpit. The congregation-facing screens never show it unless you want them to.

Can we run a pre-service countdown on the lobby or main screen?

Yes. Schedule a timer to start at a set time of day and open the viewer on that screen — the countdown to the service runs on its own.

Does this replace our presentation software?

No. Slides and lyrics stay in your presentation tool on the projection screens; the timer runs its own displays. The two drive different screens, so there is nothing to integrate.

What does the tech team need to install?

Nothing. Every view is a URL that opens in a browser — booth computer, pulpit screen, and a volunteer's phone included.

This Sunday, end on time

MaestroTimer runs in the browser: build the service order, open the viewer on the pulpit screen, and run everything from the sound desk. Wrap-up colors, silent messages, and a live connections view are built in.

Try MaestroTimer
Questions, feature requests, or a bug to report?
Let's get in touch!
© 2026 maestrotimer.com