Quick answer: Get your AI policy approved in one twenty-minute meeting by leading with boundaries instead of benefits. Open with what AI will never be allowed to do, then the human review requirement, then the hours recovered and what they will fund. Bring a one-page policy, present it jointly with a pastor, and be ready for the five questions elders always ask.
The mistake that stalls approval
Most communications directors walk into this meeting and open with efficiency. "This will save us ten hours a week."
It sounds like a strong opening. It is the weakest one available.
Elders and board members are not primarily responsible for productivity. They are responsible for the church's doctrine, reputation, and stewardship. When the first thing they hear is speed, the question forming in their heads is "at what cost?" — and now you are answering objections for the rest of the meeting.
Flip the order. Lead with the limits.
The twenty-minute agenda
Minutes 1–2: The honest situation
Open with reality, not a proposal.
"Our team already uses AI tools for some communications work. Right now there are no written rules, which means every person is making their own judgment calls. I'd like to fix that."
This reframes the meeting from "should we adopt something new" to "should we govern something already happening." Those are very different conversations, and the second one is much easier to win.
Minutes 3–7: What AI will never do
Read the prohibited list out loud. Do not summarize it.
- No pastoral care, grief, or crisis communication.
- No conflict or church discipline matters.
- No new doctrinal positions — AI reflects what we already teach.
- No political endorsements.
- No member data, prayer requests, or giving records entered into any tool.
- No invented statistics, testimonies, or quotes.
Watch the room relax. Most of the concern in the meeting evaporates in these four minutes, because you have named the exact fears before anyone had to voice them.
Minutes 8–11: Who approves what
Present the review requirement and the approval tiers: routine content approved by the communications lead, ministry content by the ministry leader, anything under a pastor's name or touching doctrine by that pastor.
Add the detail that matters to governance: approvals are recorded. When approvals live on the copy, there is always an answer to "who approved this."
Minutes 12–15: How the boundaries are enforced
This is where you distinguish a policy from a document.
"These boundaries aren't just written down. Our mission, values, statement of faith, tone, and prohibited topics are loaded into the workspace, and every prompt reviews them before producing anything — for everyone, including a brand-new volunteer."
Our AI Policy and Guardrails settings exist precisely for this moment. Boards approve policies confidently when enforcement does not depend on people remembering.
Minutes 16–18: The stewardship case
Now, and only now, talk about time.
Be specific and modest. "Our last three events took about six hours each of writing and rewriting. With this, they take closer to ninety minutes." Then answer the question they are actually asking: what will that time be used for? Follow-up with guests, volunteer development, better planning — name it.
Minutes 19–20: The ask
One sentence: "I'm asking the board to approve this one-page policy, with an annual review each [month]."
The annual review is what makes approval feel safe. It is a decision they can revisit, not a door closing.
The five questions you will be asked
"Will this replace staff?"
No. It removes repetitive production work. It does not know what happened at our church this week or which ministry is struggling. Our team's job shifts toward editing and planning.
"What if something wrong gets published?"
The same thing that happens today — we correct it. The difference is that every piece now has a named approver on record, so we know exactly where the process broke.
"Is member information safe?"
We never enter personal information, prayer requests, counseling notes, or giving records into any AI tool. That is a hard rule in the policy.
"How do we know it matches our doctrine?"
Our statement of faith and positions are loaded into the settings and reviewed at the start of every prompt. On topics where we have not stated a position, it defers to a pastor rather than answering.
"What happens when it makes a mistake?"
A person reads everything before it publishes. The policy makes that non-negotiable, and we audit quarterly to confirm the review step is genuinely happening rather than becoming a formality.
What to bring
- The one-page policy, printed.
- A short list of the last month's communication volume.
- One before-and-after example — a real draft and the published version — to show what review actually catches.
Leave the software demo at home unless someone asks. Showing the tool shifts the conversation from governance to features, and features are not what a board is deciding.
Present it with a pastor
This is the single highest-leverage detail. When the communications lead presents alone, the implicit question is whether a staff member is setting theological boundaries.
When a pastor presents the doctrinal section and the communications lead presents the workflow, that question never comes up. The governance structure is visible in who is standing there.
If they say not yet
Ask which section concerns them, and offer the cautious version: AI drafts internal and logistical content only, with pastoral approval on anything public, for ninety days. Then report back with what actually happened.
Most boards approve the broader policy after seeing one quarter of uneventful use. Real evidence beats a persuasive argument, and a narrow yes now is far better than a wide maybe.
Why the meeting is worth doing well
An approved AI policy does something quiet and valuable: it moves the boundaries from one person's judgment to the church's shared agreement. Your communications lead stops carrying decisions alone. Your volunteers get a clear rule. Your leadership gets a real answer when a member asks how the church decides what it says.
Twenty minutes, one page, and the whole question is settled for a year.
The one-page leave-behind
Whatever you say in the meeting, what survives is the document left on the table. Make it one page with five sections, in this order.
1. What AI will never do at our church. The prohibited list, in full, at the top. Putting it first tells a board everything they need to know about how this was thought through.
2. Who approves what. The three tiers, with roles named. Add one sentence noting that approvals are recorded and attributable.
3. How the boundaries are enforced. Two sentences explaining that the settings are loaded into the workspace and reviewed at the start of every prompt, so enforcement does not depend on anyone remembering.
4. What this changes about our work. One short paragraph with real numbers from your own church, and one sentence naming what the recovered time will be used for.
5. The review date. A specific month, annually.
Resist adding anything else. No screenshots, no vendor comparison, no discussion of features. A board is approving a set of boundaries, and every extra page makes the boundaries harder to find.
One more thing worth doing: send the page two days before the meeting rather than handing it out at the table. Board members who have had time to read carefully ask better questions, and better questions produce a stronger policy. It also means the twenty minutes you have are spent on decisions instead of reading.
Churches that get this right walk out with an approved policy and a leadership team that feels informed rather than sold to. That is worth more than a fast yes.
Try for free — put your approved policy to work in every draft.