The Church Communications Job Description That Actually Fits

Why undefined scope is the real problem

Most church communicators didn't get a job description. They inherited a newsletter, then the slides, then the website, then "can you make this look better?", and the role grew organically until it had no edges. When people ask what you do, you fumble, because the true answer is a moving target.

Here's the counterintuitive part: the danger isn't that your scope is large. It's that it's undefined. An undefined role can't be prioritized, can't be staffed, can't be handed off, and can't be defended when everything arrives at once and marked urgent. Clarity is the first act of leadership in this role, and it starts with a framework, not a longer task list.

The Own / Influence / Support framework

Instead of listing tasks, sort every area of communication into one of three levels of responsibility. This is the operational foundation for everything else: it tells you (and everyone around you) how you relate to a given piece of work.

The Five Domains of church communications

Own / Influence / Support tells you how you relate to work. The Five Domains tell you what the work actually is: a map of everything church communications touches, so the unsummarizable job finally becomes visible.

• Messaging: language, storytelling, tone, and calls to action. This is the voice of the church.
• Digital Channels: website, email, social media, and event registration systems, the primary ways people find and connect with information.
• Visual Identity: logos, templates, signage, photography style, and brand consistency, how the church looks and feels.
• Sunday Experience: announcements, videos, and screens during gathered worship, communications at its most visible and high-stakes.
• Print and Physical: bulletins, banners, signage, and physical collateral. Often overlooked. Often underestimated.

Run each domain through Own / Influence / Support and you've produced something most churches have never had: an honest, one-page picture of the role. It's the foundation for how announcements get written, and for using AI to build systems around the parts you own.

Communicating scope without starting a turf war

The fear is real: define your lane and you'll sound territorial, like you're guarding your kingdom instead of serving the church. The fix is to frame scope as service, not control. You're not announcing what you refuse to do; you're clarifying how you can help best, so nothing important falls through the cracks.

Try language like: "I want to make sure this gets the attention it deserves. For this one, I'd be supporting your team rather than running it, so here's what I can take, and here's what would stay with you." Said that way, clarity reads as partnership. The director who has one honest conversation like this often changes the whole culture around communications, from bottleneck to trusted guide.