← All writing

A One-Page AI Governance Policy for Churches and Faith-Driven Teams

A practical, board-ready AI governance policy framework for churches and leadership teams: four non-negotiable guardrails, clear red lines, and how to govern AI without slowing your staff down.

Most churches and organizations do not have an AI adoption problem. They have an AI silence problem.

Leadership has not named the rules, so two things happen at the same time: half the staff quietly avoids AI out of fear or guilt, and the other half pastes sensitive notes into free consumer chat tools on their personal phones because they are behind on a Tuesday deadline.

Governance is not bureaucracy. Good governance is pastoral care for your staff, your elders, your board, and the people you serve. When the lines are clear in writing, people stop guessing and start working with peace.

As I wrote in Wells, Not Towers, “Digital is a conduit, not a cathedral. AI is a tool, not a tower.” Daniel did not refuse Babylon’s resources. He mastered them while holding a line the empire could not cross. That is the posture of wise AI governance.

Here is the one-page framework I recommend for church leadership teams, nonprofits, and values-driven companies.

The Four Non-Negotiable Guardrails

Before you write a 30-page manual nobody reads, put these four commitments on one page and have your executive team, elders, or board review and adopt them.

1. Always Disclose

Never let AI pose as a human pastor, counselor, or leader. People deserve to know when they are reading, hearing, or interacting with a machine.

  • No synthetic voices, avatars, or chatbots pretending to be a staff member.
  • If a church or organization deploys a website Q&A assistant for service times, events, or basic logistics, label it clearly as an automated tool.
  • Never outsource deeply personal relational notes (apologies, grief responses, personal pastoral check-ins) to a model pretending to be you.

2. Route Care and Crisis to Real Humans

The gospel is incarnational, not informational. Presence cannot be simulated.

  • Any automated tool, form, or workflow that touches prayer requests, spiritual struggle, counseling, safeguarding, or crisis must immediately escalate to a real human being.
  • AI may help organize intake logistics behind the scenes only when private data is properly protected, but it must never act as a counselor or spiritual authority.

3. Protect Private Data

Assume anything pasted into a free consumer AI account with model training enabled is public forever.

  • Never paste pastoral care notes, counseling records, donor/giving details, HR reviews, payroll data, minors’ information, or unpublished legal/financial documents into unapproved or consumer-grade tools.
  • Use paid team or enterprise workspaces with zero-data-retention / training-off settings verified by leadership before staff touch internal documents.
  • Strip names and identifying details whenever summarizing meeting notes or real-world scenarios.

4. Name an Owner and a Pause Button

Technology without an owner drifts toward convenience over conviction.

  • Appoint a small, cross-functional AI Governance Group (3 to 5 people across executive leadership, pastoral/mission voice, creative/comms, and operations/IT, not IT alone).
  • Give that group explicit authority to approve new tools, retire unused ones, and pause any AI workflow that starts eroding culture, trust, or human dignity, even under deadline pressure.

The Green, Yellow, and Red Zone Matrix

Staff do not need abstract philosophy when they are staring at a blank page on Wednesday afternoon. They need a traffic light. Adapt this table for your own one-page staff policy:

Zone Rule Practical Examples
Green (Go) Approved everyday workflows using sanctioned tools; human reviews every output before publishing. Turning meeting transcripts into action items; drafting first-pass event briefs, volunteer checklists, or social hooks; summarizing long internal docs; editing for clarity and grammar; auditing redundant software.
Yellow (Ask First) Requires review by a department lead or the AI Governance Group before launch. Any public-facing tool or website assistant; new AI software subscriptions; connecting AI to church management (ChMS), CRM, or email systems; AI-assisted image/video generation in public campaigns.
Red (Off-Limits) Strictly prohibited across all roles. Pasting confidential pastoral, HR, counseling, donor, or minors’ data into unapproved tools; pretending AI output is personal human care; deploying autonomous chatbots for crisis/counseling; publishing unverified theological, factual, or Scripture claims without human review.

Copy-and-Adapt One-Page Policy Template

You can paste the structure below into a single document, fill in your organization’s name and approved tools, and bring it to your next leadership meeting:

  1. Purpose: Why we use AI: to eliminate administrative friction and give humans more time for people, craft, and mission, never to replace human presence or judgment.
  2. Approved Tools: The exact 1 to 2 sanctioned workspaces our team uses (with training turned off) and who to ask for a seat.
  3. Human Ownership: Every piece of published work has a human name on it. Staff are 100% responsible for accuracy, tone, Scripture/source verification, and integrity of anything they ship.
  4. The Four Guardrails: Always disclose; route care and crisis to humans; protect private data; honor the Governance Group’s pause button.
  5. Green / Yellow / Red Zones: Concrete examples tailored to your actual departments.
  6. Review Cadence: Reviewed quarterly by our Governance Group so the rules stay useful and current.

What Happens Right After You Publish the Policy

Publishing a one-page policy does two surprising things immediately:

First, your cautious staff exhale. They realize leadership is not chasing hype or trying to replace people with machines. Second, your curious staff step into the light. Instead of hiding how they are saving two hours a week, they can share safe, repeatable workflows with the rest of the team.

Governance is the foundation. Once your guardrails are in place, the next move is building practical staff literacy without overwhelming non-technical people. I walk through that next in How to Train a Non-Technical Church Staff on AI and Five Boring AI Workflows That Save Teams Hours.

If you want help drafting a governance policy with your leadership team, elders, or board, you can explore my AI Strategy & Staff Training Workshops or reach out directly.

Quick answers

Common questions

Does a small or mid-sized church really need an AI governance policy?
Yes. Your staff and volunteers are already using AI tools on personal phones and laptops whether you have a policy or not. A simple one-page policy protects your people, prevents accidental leaks of pastoral or donor data, and removes fear so staff know what is encouraged and what is off-limits.
Who should own AI governance inside a church or company?
Do not hand AI governance exclusively to IT or to one enthusiastic early adopter. Appoint a small cross-functional group of 3 to 5 people (typically representing executive leadership, pastoral or mission oversight, communications, and technology/operations) with clear authority to review tools and hit pause when something drifts.
Should a church ever use AI for pastoral care, counseling, or sermon writing?
AI can help with administrative prep, organizing notes, or brainstorming discussion questions, but it should never pose as a human pastor, replace embodied pastoral care, or ghostwrite a leader’s personal voice and convictions. Any interaction involving care, vulnerability, or crisis must always route immediately to a real human.
How often should a leadership team review its AI policy?
Review a one-page AI governance policy quarterly for the first year and twice a year after that. The tools change every few months, so your list of approved tools will evolve, while your core ethical and theological guardrails should stay steady.