The rundown is in Sheets, the timer is on a phone, and nobody agrees what time it is

It is 10:47 on a Sunday morning. The message was supposed to end at 10:45. The worship team is waiting in the wings for a cue that has not come, because the person who gives it is looking at a printed order of service that stopped being true about twenty minutes ago.

In the booth, the sheet is open in Google Sheets on a laptop. The countdown is a stopwatch on a phone, started roughly when the first song began. The speaker on stage has no idea how far over they are, because the only clock they can see tells them the time of day, not how much of their slot is left. Two volunteers are messaging each other about whether to cut the closing song.

Every one of those tools is doing its job correctly. The problem is that there are four of them, and none of them knows about the others.

What the four apps actually cost you

It is worth being specific, because "use one tool instead of four" sounds like tidiness rather than a real problem. It is not tidiness. Here is what breaks.

• Nobody shares a clock. The producer, the person on sound and the speaker each have a different idea of how far behind you are, so every decision is a negotiation instead of a fact.
• The sheet goes stale the instant anything moves. One song added in the green room and every printed copy is wrong for the rest of the morning.
• Overruns do not ripple. Worship runs five minutes long, every time below it is now wrong, and nobody can redo that arithmetic while the show is moving.
• The person on stage is flying blind. They are the one who can actually fix an overrun, and they are the only person with no information.
• Handoffs are brutal. A volunteer who arrives twenty minutes before the service has to reconstruct the whole plan from a piece of paper and a conversation.
• Nothing is recorded. Next week you plan the same service from memory, because there is no record of what actually took how long.

The tools are not the problem. Having four of them, none of which shares a clock, is the problem.

One timeline, and every screen reads from it

That is the whole idea behind PilotCue. There is one run of show, it lives in one place, and everything that needs to know the time reads from it continuously, without anyone updating anything while the show is live.

In practice that means all of the following in one console, rather than five tabs and a phone.

• Your rundown, imported rather than retyped. Paste straight from Excel or Google Sheets, or upload the file. Durations written the way people actually write them, like "15min" or "1hr 20 mins", are understood, and you get an editable preview before anything is created.
• A live clock that does the arithmetic. Start the show and every start time recalculates as reality moves. When an item runs long, everything below it shifts by itself.
• A backstage monitor. Current item, what is next, and time remaining, on a screen anyone can see. No phone stopwatch.
• A speaker screen. The person on stage sees their own countdown, so they can wrap up without being waved at from the wings.
• Messages to the stage. Send "wrap up" or "2 minutes left" straight to the speaker screen instead of trying to catch an eye.
• Share links. Send a read-only view to anyone who needs to follow along, with no account and nothing to install.
• A dry run. Play the whole thing through at speed beforehand and find the segment that does not fit while you can still change it.
• A post-show report. What was planned against what actually happened, so next week starts from evidence instead of memory.

What actually changes on the day

The specific thing that changes is that arguments stop being arguments. When the producer, the backstage monitor and the speaker screen all show the same countdown, "are we behind?" has an answer instead of three opinions. The decision to cut the closing song gets made at 10:30 with information, rather than at 10:47 in a panic.

The second thing is that a rotating volunteer team stops being a liability. Somebody arriving cold can see what is happening now, what is next, and how long is left, without being briefed by whoever ran it last week.

Bring the sheet you already have

You do not need to rebuild anything to try this. Whatever you run from now, a spreadsheet, a document, or a sheet you retype every week, paste it in and it becomes a run sheet. Most of the first hour with a new tool goes on fighting a format, and that is the part worth skipping.

There is a free tier, and there are ready-made templates for a Sunday service, a conference day, a wedding reception and a webinar if you would rather start from one of those than from your own sheet.