Building a Sunday Run Sheet That Actually Gets Followed

Somebody's always asking "wait, when do we start the slides?" two minutes before the service starts, and somebody's always answering it from memory because it's not written down anywhere real. A run sheet is supposed to fix that. Most of them don't, because most of them get written once, printed once, and then ignored by week three.

Why most run sheets get ignored

A run sheet fails for one of two reasons: it's too vague to actually use, or nobody owns keeping it updated. "Start slides when ready" isn't an instruction, it's a shrug. And if the sheet from three months ago still says the old countdown video, your volunteer's either guessing or asking someone, and you're back where you started. A run sheet that doesn't get maintained is worse than no run sheet, because it looks official and isn't.

What actually belongs on it

• Real times, not vague ones. "8:45 mic check" beats "check mics before service." Specific enough that two different volunteers would do the same thing at the same moment.
• Who's doing it. Not just "someone checks the stream," but the actual role or name. Vague ownership means nobody owns it.
• The exact cue, not just the task. "Start countdown video at 8:55" instead of "get things going." Your volunteer shouldn't have to interpret anything under pressure.
• A backup contact. One name and one number for "something's broken and I don't know what to do." Every team needs this line even if it's rarely used.
• What happens after. Shutdown steps, what gets unplugged, what gets logged. The run sheet doesn't end when the service does.

Keep it where people will actually see it

A run sheet buried in a shared drive folder from two reorganizations ago doesn't count as documentation. Print it, tape it to the booth, or pin it somewhere your team already looks, like the group chat you actually use. If checking it takes more effort than asking someone who remembers, people will just ask someone who remembers, and you're back to tribal knowledge living in one person's head. That's usually the same person who ends up carrying the whole team, which is exactly how burnout happens in the first place.

Update it after every service that goes sideways

The best run sheets aren't written once, they're patched. Something goes wrong Sunday, you write down what actually happened and what should happen next time, right then, while it's fresh. Six months of that and you've got a document that actually reflects reality instead of what someone assumed back in January.

Grab the Sunday Checklist if you want a version of this already built out for you, from night-before prep through post-service wrap-up, so you're not starting from a blank page.