64% of church leaders say policy matters. 5% have one.

A 2024 Lifeway Research survey of church leaders found that 64 percent of them believe their church needs a policy or guidelines for using new ministry tools. Five percent have one.

That gap is worth dwelling on. It is not a gap between those who care and those who do not. It is a gap between those who know they need something and those who have found the time and resources to build it.

Why the gap exists

Governance frameworks for new tools are not something most churches have had reason to build before. The traditional decision about technology in the church was about procurement: should we buy this software or that one. Those decisions did not require policies because the software did not generate content in the pastor’s name.

New tools that answer questions from the congregation, generate curriculum from sermons, or produce content for ministry use are different in kind. They require thinking through questions that most church leadership teams have not encountered before: What sources can this tool draw on? Who approves what it produces before it reaches people? What happens when it is wrong? Who is accountable?

These are governance questions, not technology questions. Most churches have not built the muscle to answer them quickly.

The accountability question

One question that surfaces consistently in conversations with church leaders is who is accountable when a tool produces a wrong answer.

This question has a clear answer in traditional ministry: the pastor is accountable for what is taught in his church. When a tool produces content in the church’s name, that accountability does not disappear. It gets distributed in ways that can become unclear very fast.

A tool that produces answers to congregational questions without an approval workflow removes the accountable person from the loop at the exact moment accountability matters most. The answer goes out. The congregant acts on it. If it was wrong, there is no trail from the answer back to a decision a human made.

What governance actually requires

The church leaders who have thought most carefully about this tend to converge on similar requirements.

The first is sourcing. Anything the tool says has to be traceable back to what the church has actually taught. Not a general corpus, not a paraphrase of broadly orthodox theology, but the specific teaching of this pastor in this church.

The second is approval. Every piece of content that reaches the congregation should pass through a human reviewer before it does. Not as a formality, but as a real editorial step.

The third is an audit trail. The church should be able to see every answer that was given, who approved it, and what source it was drawn from. This is not about surveillance; it is about being able to identify and correct errors.

The policy most churches need

Most churches do not need a twenty-page governance document. They need a few clear commitments: we only draw on our own teaching, we approve everything before it goes out, we keep a record of what we said and what we approved.

The tool that earns trust from pastors who have thought this through is the one where those commitments are built into the product, not the one that promises a flexible configuration panel that the church can set up later.

The 64 percent who know they need a policy and the 5 percent who have one both need the same thing. A framework that is simple enough to adopt and specific enough to be meaningful. The best place for it to live is inside the product itself.

---

Berean Library ships with governance built in. Staff review, then leadership sign-off, then publication. An append-only audit trail. Sourcing limited to your own sermons. This is not a configuration option. It is the product.