The Policy Won't Save You

You have a communications intake system. You built the forms, set the lead times, wrote the guidelines, got them approved, sent them to every ministry leader, and walked through them at the all-staff meeting. For about six weeks, things ran more smoothly than before. Requests came in with enough time to actually do the work well. Then the children's director needed something on a one-day turnaround. Then the senior pastor had an idea on Friday night for a graphic he wanted Sunday morning. Then the women's team forgot to submit their slide content until the day before.

The policy didn't fail because people are difficult or malicious. It failed because a document was never going to change a culture on its own.

What does a church communications policy actually do?

A request intake process is useful. Lead times matter. Having a shared understanding of how communications work gets submitted, reviewed, and executed is legitimate and worth building. None of that is inherently wrong.

But a policy is a description of how things should work. It has no authority of its own. It can't enforce itself. It doesn't follow up when someone bypasses it. It doesn't sit in the room when a pastor decides his Friday night idea is urgent enough to warrant a Sunday morning exception. A policy is only as strong as the culture that has agreed to it. And in most churches, that culture doesn't exist yet when the policy gets written and rolled out.

This is why the intake form becomes a source of resentment instead of relief. You built something that was supposed to create order, and now you're the person who keeps pointing to it while everyone else finds reasons their situation is different. That's not a policy problem. That's a culture problem wearing a policy's clothes.

What actually changes behavior on a church staff?

Culture in a staff environment changes through relationships and repeated experience, not documents. The ministry leader who blows past your deadline does it because, in his experience, you've always found a way to make it work anyway. The senior pastor bypasses the process because nobody has ever shown him what the process actually produces when it's respected. The student pastor submits on Tuesday for a Thursday need because she genuinely doesn't understand what good lead time makes possible.

These aren't malicious people. They're busy people operating on assumptions your policy hasn't displaced, because a policy can't displace an assumption. Only experience and collaboration can do that.

So let them experience it. When a request comes in too late to do well, produce what the time allows and be honest about it. Not as punishment. As information. "Here's what we were able to do with two days. Here's what we could have done with ten." That conversation, repeated over time with grace and without resentment, does more than any intake form ever will. It makes the value of the process visible in a way a document never can.

When I worked in corporate, the creative team faced many unsustainable requests. I would always nod and take notes, then ask my favorite seven-word phrase: "Who do I send the invoice to?" Once leaders understood there was a cost associated with rushing through something, they were able to process the tradeoff themselves. The collaboration usually landed at something reasonable based on their own prioritization. Suddenly, the AC/DC song for the CEO walkup didn't seem so important when they understood the cost of licensing a streamed event. People just need to understand the limitations associated with doing good work the right way.

Why does trust matter more than your intake process?

The ministry leaders who respect your process consistently are almost always the ones who trust you. They've seen what you do with good information and adequate time. They know that submitting early isn't bureaucratic compliance — it's how they get better work for their ministry. That trust gets built one project at a time, through showing up ready when they give you what you need, and through being honest, not punitive, when they don't.

The communications director's job isn't just execution. It's education. And the most effective education happens through celebrating results, not defining more rules.

What is a communications policy actually good for?

When a genuinely unreasonable request lands, a documented process gives you something to point to that isn't just your personal opinion. "Our standard lead time for a project this size is ten days" is easier to hold than "I don't think that's enough time." The policy doesn't solve the problem, but it depersonalizes the boundary, and that matters in a staff culture where everything can quickly become relational. Your written rules of engagement get to be the bad guy in the conversation.

Use it for that. Don't use it as a substitute for the harder, slower work of building a staff culture that actually understands why the process exists. The policy is scaffolding. The culture is the building.