One Visual Identity Across Every Campus Screen With Shared Looks

Design drift in a multi-site church is never a decision anybody makes. It's an accumulation. The north campus adjusts a font size because their projector is dimmer. Someone at the downtown campus rebuilds a lower third from memory after a screen gets deleted. Six months later three campuses are running three different versions of what was supposed to be one brand, and nobody can point at when it happened.

The structural cause is copies. If each campus's screen holds its own independent design, drift isn't a risk — it's the default outcome of normal maintenance.

Referencing instead of copying

Shared Looks remove the copies. A Look is a single saved style, and screens point at it rather than containing it. Your north campus overlay, downtown overlay, lobby displays, and stage monitors can all reference the same Scripture Look.

That flips the maintenance math. Under the copy model, one brand update meant finding and editing every screen — and being wrong about how many there were. Under the reference model, you edit the Look once and every screen using it changes, including screens at campuses you weren't thinking about.

Consistent church branding across campuses stops depending on everyone remembering to make the same change, which is the only version of consistency that survives volunteer turnover.

What still varies, and should

Shared style doesn't mean identical screens, and that distinction is what makes this workable rather than restrictive. Screen-level settings stay local:

• Background — a lobby display wants a background image; a livestream overlay must stay transparent.
• Which Element Looks are active — a campus with a different service rhythm runs a different countdown.
• Triggers and persistence — how layers interact, and what happens when an operator's connection drops.

So a campus can absolutely have a different pre-service countdown while running byte-identical scripture typography. Style is shared; local configuration isn't.

Handling the legitimate exception

Some campus differences are real. A room with a smaller screen at the back genuinely may need a larger minimum font. The instinct is to edit the shared Look "just slightly for us" — which is exactly how drift starts, since that edit lands on every campus.

Make the exception explicit instead: create a second Look, name it for the reason it exists, and apply it only where it's needed. "Scripture — Large Room" is an intentional variant that anyone can understand. An undocumented tweak to the shared Look is a mystery that someone will eventually un-fix.

The test for whether a variant is legitimate: can you state the physical or operational reason in one sentence? "The back row is 90 feet away" qualifies. "I liked it better" doesn't.

Practical governance

A few habits keep this from unravelling as your team grows:

• Limit who edits. Creating and editing Looks is restricted to team owners and admins. Keep it that way. Operators can view Looks without being able to change what every campus sees.
• Name for purpose, not appearance. "Guest Speaker Lower Third" survives a volunteer handover; "LT v3 final" doesn't.
• Audit occasionally. Once a quarter, open the Looks list and ask which ones are still earning their place. A variant built for a series that ended in March is clutter now.
• Delete deliberately. Deleting a Look is blocked while screens still use it — you'll be told to reassign them first. That's a guardrail, not an obstacle; it's telling you that something out there depends on this.

The measure that matters

The goal isn't that your campuses look similar when someone compares them side by side. It's that a person who attends the downtown campus in the morning and the north campus in the evening never has a reason to notice they're different systems.

That kind of consistency isn't a design achievement. It's a structural one — and it holds up precisely because nobody has to maintain it by hand.