Good Friday and Easter Weekend: A Tech Team Planning Guide

Easter weekend is the one stretch of the church calendar where your tech team runs two or three distinct productions in under 72 hours, each with a different tone, different attendance, and often different volunteers. Good Friday is somber and stripped down. Easter Sunday is your highest-attendance service of the year, sometimes running multiple back-to-back services. Treating the weekend as one continuous push instead of three separate events is where most teams get into trouble.

Treat Good Friday and Easter Sunday as different productions

It's tempting to build one screen package and reuse it across the weekend, but the two services usually call for opposite visual choices. Good Friday tends to be quieter: dark backgrounds, minimal lower-third graphics, longer scripture readings held on screen without rushing. Easter Sunday is the opposite: bright, high-energy, often with guest-heavy attendance who need more on-screen guidance (where to find kids' check-in, what song is playing, who's speaking).

Build the two screen sets separately rather than trying to make one theme flex both ways. It's less design work in the long run than trying to reskin a triumphant Easter template into something somber for Friday night.

Start the plan at least three weeks out

Easter weekend tech planning falls apart most often because it starts too late — usually when someone realizes on Palm Sunday that nothing is scheduled. Work backward from Easter Sunday:

1. Three weeks out: confirm service times for the whole weekend, including any additional Easter services being added to handle higher attendance, and get scripture references and setlists from whoever is planning each service.
2. Two weeks out: build screen designs for Good Friday and Easter Sunday separately, and confirm who's operating each service — these are often not the same people since some volunteers only serve one or the other.
3. One week out: run a full tech rehearsal for Easter Sunday specifically, since it's the service most likely to have new elements (baptisms, extra songs, guest speakers, additional cameras for overflow rooms).
4. The Wednesday before: confirm every operator for both services knows their call time, and that anyone new to Easter-specific setups (extra services, overflow rooms, guest check-in slides) has walked through it once.

Plan for volunteers who only show up on Easter

Easter Sunday reliably pulls in occasional attendees who also happen to be trained tech volunteers you haven't seen since Christmas. That's a resource, not a liability, if you plan for it. Keep a short list of people who've run screens or camera before but aren't on your regular rotation, and reach out to them specifically for Easter weekend coverage rather than hoping your usual four people can cover three services solo.

For anyone stepping in who hasn't operated recently, a five-minute refresher beats assuming they remember the workflow. If your screen system changed since Christmas, that's exactly the kind of thing to walk through before they're live.

Build screens that don't need last-minute editing

Because Easter services tend to have more moving pieces than a normal Sunday — baptism testimonies, guest speakers, additional worship songs, overflow room instructions — it helps to have your lower-thirds and scripture screens built as reusable templates rather than one-off slides. If your platform lets you duplicate a screen design and swap the text without rebuilding the layout, that's exactly what a baptism testimony lower-third or a guest speaker intro should be: build it once, reuse it across every name that Sunday.

This is where AllStreamHub's screen designer and templates earn their keep during Easter weekend specifically — a lower-third built for one baptism candidate can be duplicated and relabeled for the next five without touching fonts, colors, or animation settings, which matters when you might be running eight or nine baptism intros back to back.

After the weekend, capture what you'd change

The best time to write down what went wrong on Easter is the Monday after, not next February when you're planning again. A short debrief with your operators — what felt rushed, which screen didn't match the moment, where the extra service caught someone off guard — turns into next year's planning document instead of an anxious guess. Easter weekend rewards teams that treat it as a repeatable, improvable production, not a once-a-year fire drill.