← On the House
Free · No Account · No Sales Call

Your board is going to ask.
Have the answer ready.

Almost every pastor in America is already using AI. Almost no church has written down what is allowed, what needs approval, and what is off limits. Answer a set of plain questions about how your church actually works and walk out with a complete AI Use Policy written for your church, ready to take to your board.

93%
of pastors are using AI in some form
~5%
of churches have a written AI policy
10 min
from first question to finished document
Print or save as PDF Download as an editable Word file One-page staff card included
i What you walk away with

A church AI policy is not a technology document. It is a trust document. It says what your staff and volunteers may do with these tools, what has to be approved first, what never goes near them, and who a person tells when something goes wrong. Every answer you give changes the text you get back.

The policy itself

Front matter, scope, definitions, an approved / approval-first / off-limits table built from your own answers, and the protective language that goes with each one.

A one-page staff card

Green light, yellow light, red light. The thing a volunteer will actually read, printable on its own.

What you tell the congregation

A short, plain paragraph you can read from the platform or drop in a newsletter, plus the anti-impersonation notice every church needs this year.

An adoption page

Signature lines, adoption date, review date, and the questions your board is most likely to argue about, so you walk in ready.

Said plainly

This produces a serious starting template built on published church, nonprofit and denominational guidance. It is not legal advice, and ChurchOps.AI is not your attorney. The document marks the places where the honest answer depends on your state and your bylaws, so your counsel knows exactly where to look.

? Before you start

Does our church actually need an AI policy?

If anyone on your staff or volunteer team uses these tools, you already have an AI policy. It is just unwritten, inconsistent, and different in every person's head. The question is whether it is one you chose. The specific risks that make it worth writing down are pastoral confidences, anything about a child, giving records, and personnel files, because those are the four categories that cannot be un-shared once they leave.

What should a church AI policy include?

At minimum: who it applies to, what counts as AI, a plain list of what is approved, what needs approval first, and what never goes into these tools; a named person accountable for every output; how and when you tell people AI was involved; a path for reporting mistakes that does not punish the reporter; a list of approved tools; and a review date. A church policy also needs positions on sermon preparation, prayer, pastoral communication, and your pastor's voice and likeness, which no generic business template covers.

Is this legal advice?

No. It is a starting template built from published church, nonprofit and denominational guidance, and ChurchOps.AI is not your attorney. The document ships marked as a draft and includes a list of the specific questions that depend on your state and your bylaws, so your counsel can review it quickly rather than starting from a blank page.

What if our church does not use AI yet?

That is the easiest possible moment to write one, and the tool handles it. There is a one-tap option for "nothing yet," and you still get a complete document: the standard set before the first person needs it, rather than after.

Who has to approve it?

Whoever adopts policy at your church: elders, deacons, a council, a board, or the congregation. The document includes a cover memo written to them and motion language you can read as written, because the vote that actually passes is not "should we allow AI" but "should we govern what our staff are already doing."

How long does it take, and what does it cost?

About ten minutes, and nothing. It is free, there is no account, and there is no sales call. You can print it, save it as a PDF, download it as an editable Word file, or have it emailed to you.

1

Your church

This names the document and sets its vocabulary. Nothing here is shared with anyone.

2

A few facts about how you are set up

Each of these switches a whole section of the policy on or off. Answer honestly, not aspirationally.

3

Where AI shows up in your week

Two taps, or none. Leave a row blank if it is not something you do and not something you are weighing. Answer as best you know: nothing in this list is ever attributed to a person in the finished document, it describes the church. If you are unsure what your team is doing, tick what you believe and confirm it with them. The rollout checklist has a step for exactly that.

Most churches find they tick more than they expected.
4

Where your church stands

These are the questions your elders will actually debate. There are no recommended answers here on purpose. Churches land in different places on every one of these and each position gets written up with the same conviction.

5

In your own words

Short answers are fine. These get woven into the document, and anything you describe that our standard language does not cover gets a clause written for it. Plainly: what you write here is sent to us along with your finished policy, the same as the rest of your answers. Write what is useful for the document and leave out anything you would not want a stranger to read.

6

Where should we send it?

The finished policy lands in your inbox so you can forward it to your board without retyping a word.

Straight answer on your data: your answers and the finished policy are emailed to you and a copy reaches Travis at ChurchOps.AI, which is how we can help if you have questions later. Nothing is sold, nothing is shared with anyone else, and you can ask us to delete it at any time by replying to the email. If you would rather we held none of it, print or download the policy instead of emailing it and skip this step.

Assembling your policy
One moment.
Something went sideways

Writing the parts only your church needs

You have a policy. The harder part is the Monday after.

A policy tells your team what not to do. It does not give them back a single hour. If you want the other half, ChurchOps.AI builds the agents and workflows that actually carry the administrative weight in a church: guest follow-up, meeting recaps, volunteer onboarding, event reporting, the work that eats your staff's week.

Get a free plan for your church → See Exec Pastor OS