Changing Your Screen Design Mid-Service Without Breaking the Stream

Most screen-design mistakes are discovered at the worst possible time: eight minutes into the service, with the thing already on camera. The verse font is too small for the back row. The lower third is clipping. The scripture styling you built for the sermon series looks wrong against this week's stage lighting.

Historically the options were bad — live with it for an hour, or edit a live screen and hope. Looks change that, because switching a screen's style is now a two-click operation that doesn't disturb what's on air.

The mechanic that makes this safe

Here's the part worth understanding, because it's what lets you touch a live screen without flinching.

A Look holds styling and placeholder text. The screen's live text — the verse an operator pushed, the lyric line currently up — comes from a different place entirely, and it always wins. When a Look changes, the styling merges in and the live text is preserved.

Practically: if John 3:16 is on screen when you switch Looks, John 3:16 stays on screen. It restyles. It doesn't blank, doesn't flash back to "Your verse here," and doesn't need re-pushing.

The same is true for visibility. A layer that's hidden stays hidden; a layer that's showing keeps showing. You're changing appearance, not state.

Doing it from the dashboard

You don't need to open the full screen editor to change screen design live. The dashboard has a Screen & Look card built for this:

1. Pick the screen you want to change.
2. Choose the layer — Scripture, Lyrics, or Elements.
3. Click a Look from the list.

It applies immediately and confirms with a toast telling you which Look is now live on which screen. Element Looks use checkboxes instead, since several can be active at once, so you're toggling bundles on and off rather than replacing one.

The Scripture and Lyrics pages have the same switcher locked to their own layer, so an operator working scripture can restyle scripture without navigating anywhere or seeing controls they don't need.

Two ways to fix a problem, and when to use each

There's an important distinction once something is wrong mid-service:

Switch to a different Look when a workable alternative already exists. This is the safe move. You're picking a known-good design rather than editing under pressure.

Edit the Look itself when the problem is small, specific, and you know the fix — the reference box needs to come up two percent. Be aware that this changes every screen using that Look, live. That's usually what you want (the clipping is probably happening everywhere), but it's not a local fix, and it isn't the moment to experiment.

If you catch yourself opening a Look editor at 10:47 to try things, switch to a different Look instead and fix the original on Tuesday.

Build the escape hatch before you need it

The switch-don't-edit approach only works if there's something to switch to. That's a Tuesday job, not a Sunday one.

A simple, boring, high-contrast Scripture Look — white text, solid dark background bar, large font, nothing clever — is the most useful Look most churches never build. It's not for normal Sundays. It's for the morning the stage lights change, or the projector's color is off, or the camera is exposing differently than usual, and the pretty design has stopped being readable.

Name it something obvious. "Fallback — High Contrast" is findable under pressure. Tell your operators it exists and that using it is a legitimate call, not an admission of failure.

The habit to build

After any live fix, write down what happened and fix the underlying Look properly during the week. Live switching is a recovery tool, and the measure of a good tech team isn't never needing it — it's how rarely the same problem needs recovering from twice.