From Manuscript to Monitor: Building a Teleprompter Workflow That Doesn't Break on Sunday

Most churches solve their teleprompter problem twice. First they buy the hardware — a monitor, a beam-splitter glass, maybe a PTZ camera with a built-in prompter mode. Then, months later, they solve the real problem, which has nothing to do with hardware: getting a clean, correctly formatted script onto that screen every single week without someone recreating it from scratch at 7am.

If you've ever watched a pastor go quiet mid-sentence because the prompter operator is still hunting for last night's Google Doc, you know which problem actually costs you on Sunday.

If the manuscript itself is what runs late every week, Sermoni is built for that part of the problem.

Start with the script, not the screen

Prompter software has gotten good. The hardware has gotten cheap. Neither of those things fixes a workflow where the sermon manuscript lives in three different formats by the time it reaches the monitor — a voice memo, a Word doc with the pastor's mid-week edits, and whatever got typed into the prompter app at the last minute.

The fix is to standardize where the manuscript comes from before you worry about how it displays. A growing number of pastors are writing and refining their manuscripts inside sermon-prep tools that keep the structure clean — headers, Main Idea, transitions — instead of a wall of unformatted text. Sermoni is one of these: it's built specifically for sermon co-authorship (the pastor writes the actual content; the tool helps with structure, word study, and organizing the manuscript around a clear Main Idea), and it exports a clean, plain-text version of the finished manuscript that's genuinely easy to drop into a prompter app without reformatting line breaks or stripping out comments and highlight colors. If your current process involves exporting from one app, cleaning it up in a second app, and pasting into a third, that's three places for Sunday morning to go wrong. Collapsing that to one export step is the actual win — which tool you use to get there matters less than committing to just one.

Try Sermoni →

Pick a prompter tool that matches your operator situation

Once the script is clean, the app you scroll it on should match who's actually running it.

• PromptSmart uses voice tracking to follow the speaker's pace automatically, which is worth the subscription if your pastor moves around and you don't want a dedicated human on scroll speed every week.
• Teleprompter.com gives you three scroll modes (fixed speed, timed, and voice-driven auto-scroll) plus color-coded stage directions like [pause] that live volunteers can follow without a headset cue.
• ProPresenter is the heavier option, but it's the right call if you're already running ProPresenter for lyrics and lower-thirds — its built-in Stage Display module can pull double duty as your confidence monitor feed, so you're not maintaining a second piece of software.

For a one-person AV booth, PromptSmart or Teleprompter.com is usually enough. For a church already running ProPresenter for the full service, just extend what you have instead of adding a fourth app to train volunteers on.

The Tuesday habit that prevents the Sunday scramble

The churches that never have prompter drama share one habit: the final manuscript gets exported and loaded into the prompter app days before service, not hours. Whatever your source tool, build the export into your sermon-prep rhythm — Tuesday or Wednesday, once the manuscript is basically locked, someone loads it and does a two-minute scroll-through at a normal reading pace. That's the whole fix. It's not a hardware problem, and it's not really a software problem either — it's a "make it someone's job on a specific day" problem.

The gear, briefly

If you're building the physical side from scratch: a 15" or 19" monitor with a beam-splitter hood (Ikan and Prompter People both make budget-friendly units under $400) mounted on your existing camera stand covers most sanctuaries. You don't need a dedicated prompter camera rig unless you're running multi-camera with a hard cut to a tight shot — a stage-monitor style setup (screen at the base of the camera, not through the lens) works fine for the vast majority of church streams and costs a fraction of the price.

The lesson underneath all of it: prompter problems that look like hardware problems are almost always workflow problems wearing a hardware costume. Fix the script pipeline first.

Keep reading from Church Tech Mag

• Worship presentation software in 2026: four tools compared
• 25 things every AV booth should have
• The pastor who built the tool he wished he had