Preston Trail’s guardrails for using AI in ministry — what staff, volunteer leaders, and contractors may use it for, what needs leadership approval, and what is never permitted.
- Version
- 1.1 (July 2026)
- Effective Date
- August 1, 2026
- Adopted by
- Sarah Davidson
- Classification
- Confidential — For Internal Use
Why This Policy Exists
Artificial intelligence is no longer a future concern for the church — it is a present reality shaping how our people pray, study Scripture, and seek spiritual guidance.
According to Barna’s State of the Church 2026 research (in partnership with Gloo), nearly one in three U.S. adults — and about a third of practicing Christians — now say spiritual advice from AI is as trustworthy as advice from a pastor. Among Gen Z and Millennials, that figure rises to two in five. Roughly four in ten practicing Christians report that AI has already helped them with prayer, Bible study, or spiritual growth. And yet, in Barna and Pushpay’s State of Church Tech 2026 report, only 5% of churches have an established AI policy, and just 12% of pastors say they feel comfortable teaching their congregations about AI.
This policy exists to close that gap for Preston Trail Community Church. It is not primarily a technology document — it is a discipleship document. It provides clear guardrails for how our staff, volunteer leaders, and contractors use AI in ministry while also equipping us to shepherd our congregation through a moment of significant cultural and spiritual change.
Our guiding conviction: AI is a tool, not a teacher. It can assist human effort, but it cannot replace the Holy Spirit’s work through embodied, relational, covenantal community.
Scope
This policy applies to:
- All paid staff (full-time and part-time)
- Volunteer leaders (ministry leads, small group leaders, worship team, tech team, kids/youth workers)
- Elders, deacons, and board members when acting in an official capacity
- Any contractor or vendor producing content or handling data on behalf of the church
It covers all AI tools used for church-related work, including large language models (Claude, ChatGPT, Grok, Gemini, Copilot, etc.), image and video generators, transcription services, data analysis tools, and any emerging AI technologies. Preston Trail’s primary approved AI platform is Claude Enterprise.
Section 1: Theological Foundations
Before addressing practical guidelines, we establish several convictions that undergird this policy.
1.1 The Sufficiency of Scripture
The Bible is God’s authoritative Word and the final standard for faith and practice (2 Timothy 3:16–17). AI-generated theological content must always be evaluated against Scripture, not treated as a parallel source of spiritual authority.
1.2 The Irreplaceability of Human Shepherding
God designed the church to be led by Spirit-filled, called, and accountable human leaders (Ephesians 4:11–13; 1 Peter 5:1–4). No AI tool can fulfill the pastoral functions of presence, prayer, confession-hearing, sacrament administration, or covenantal accountability.
1.3 The Value of Authenticity
Our congregation trusts that what is spoken from the pulpit, written in a pastoral letter, or shared in a counseling session comes from a real person who has wrestled with God’s Word and applied it through lived experience. This trust is sacred and must be protected.
1.4 Wisdom and Discernment
Technology is not morally neutral in its effects. We are called to “test everything; hold fast what is good” (1 Thessalonians 5:21) and to exercise collective discernment about how new tools shape our formation as followers of Jesus.
Section 2: Approved and Prohibited Uses
2.1 Approved Uses (With Human Review Required)
AI tools may be used to assist with the following tasks, provided the responsible person reviews, edits, verifies, and takes full ownership of all output:
Administrative & Operational
- Drafting internal emails, meeting agendas, and scheduling communications
- Summarizing meeting notes or generating action items
- Creating first drafts of budgets, project plans, or operational documents
- Translating documents and messages into other languages
- Data organization and reporting — including individual-level insight — through approved, governed church systems
Content & Communication
- Brainstorming sermon illustrations, outlines, or research starting points (see Section 3 for sermon-specific rules)
- Drafting social media captions, newsletter copy, or website content
- Generating graphic design concepts or slide deck layouts
- Proofreading, grammar-checking, and editing written materials
- Transcribing sermons, meetings, or interviews (with appropriate consent)
Learning & Research
- Exploring commentaries, cross-references, or historical context during personal study
- Summarizing long-form articles or books for staff development
- Comparing Bible translations side by side
2.2 Prohibited Uses
The following uses of AI are not permitted under any circumstances:
Spiritual Care & Counseling
- Using AI to generate pastoral counseling responses (in-person, phone, email, or text)
- Deploying AI chatbots as substitutes for human pastoral interaction (e.g., “Ask our AI pastor”)
- Using AI to write personalized prayers for specific congregants
Congregant Data
Individual-level insight about a congregant — attendance, engagement, follow-up, family participation — is appropriate and encouraged when it is produced through an approved Preston Trail integration that keeps the underlying data on church-controlled infrastructure. The governing distinction is not aggregate versus individual, but governed versus ungoverned. The following are prohibited:
- Entering personal information about congregants (names, prayer requests, giving records, counseling notes, attendance data, contact information) into public or consumer AI tools
- Removing congregant data from governed systems — exporting or copying it into personal spreadsheets, local files, personal drives, or standalone apps or websites, or building any parallel store of congregant information outside church control. (Working with congregant data in spreadsheets and files is acceptable when they remain within the church’s Microsoft 365 environment.)
- Connecting congregant data to any platform that is not an approved Preston Trail integration
Representation & Authority
- Presenting AI-generated content as though it were a personal testimony, lived experience, or firsthand account
- Using AI to generate “prophetic words,” tongues interpretations, or claims of divine revelation
- Creating deepfakes, AI-generated voice clones, or synthetic media of any other person — whether a church leader, staff member, or congregant. An individual may create a synthetic voice or likeness of themselves; producing one of anyone else is prohibited.
Financial, Legal & Decision-Making
- Using AI to make final financial decisions, approve expenditures, or generate legal documents without qualified human review
- Allowing AI tools to access church banking, payroll, or financial systems without approved enterprise controls
- Using AI for hiring, disciplinary, membership, or spiritual guidance decisions
Deployment & Hosting
- Publishing or hosting any AI tool, application, or website that is reachable beyond an individual’s own device, without Tech partnership (see Section 2.4)
2.3 Gray Areas — Requires Leadership Approval
The following require advance conversation with your direct supervisor or the designated AI policy point person before proceeding:
- Deploying automated AI communication to congregants — chatbots, auto-replies, or automated follow-up sequences — where a person does not remain in the loop
- Purchasing or subscribing to new AI tools on behalf of the church
- Using AI-generated images or video in worship services or public communications. These require heavy human review before use; take particular care before depicting Scripture, biblical figures, or biblical messages in a comedic or satirical way.
- Any experimental or pilot use not explicitly covered above
2.4 Deployment, Publishing & Third-Party Access
Any website, application, integration, prototype, or platform — publicly or privately hosted, AI-built or hand-built — that is created for Preston Trail, branded as Preston Trail, or connected to Preston Trail data or systems must be reviewed and provisioned by Tech before it is deployed or shared. A tool that runs only on an individual’s own computer is acceptable; the moment it is reachable from anywhere beyond that device, it requires Tech partnership.
- Church tools must run on Preston Trail-governed infrastructure, not personal hosting accounts (personal Cloudflare, Vercel, Netlify, or similar)
- Internal tools, dashboards, and AI-generated artifacts must not be publicly shared, published, or distributed without Tech review
- Any third-party application or service requesting OAuth or API access to church systems (Microsoft 365, Planning Center, giving, Rock RMS) requires Tech approval before authorization
- AI-generated prototypes remain internal until reviewed. A working prototype is not an approved deployment.
Section 3: Sermon & Teaching Preparation
Because preaching and teaching carry unique spiritual weight and congregational trust, they receive specific treatment here.
3.1 What Is Permitted
- Using AI as a research assistant: generating background on biblical languages, historical context, cross-references, or theological positions you then verify independently
- Using AI to brainstorm sermon structures, illustration angles, or application points — treating output the same way you would treat a conversation with a colleague
- Using AI to edit or proofread a manuscript you have already written
- Using AI to transcribe your spoken draft into written form
3.2 What Is Not Permitted
- Submitting a passage or topic to AI and delivering the resulting output as your sermon without substantial personal study, rewriting, and spiritual preparation
- Using AI to generate the core theological argument or application of a message without doing your own exegetical work first
- Copy-pasting AI-generated illustrations or stories and presenting them as personal experiences
3.3 The Integrity Test
Before delivering any message where AI played a role in preparation, the preacher or teacher should be able to honestly affirm:
- I have personally studied the biblical text and can defend my interpretation apart from what AI suggested.
- The theological convictions expressed are mine, not simply what a model generated.
- I have personally verified every quote, citation, statistic, and Scripture reference — including asking the AI to show me exactly where each one comes from — because AI can produce confident but false information.
- Every illustration or story presented as personal experience actually happened to me or is clearly attributed.
- I could have written this message without AI — the tool accelerated my process, but it did not replace it.
Section 4: Data Privacy & Security
4.1 General Principles
- Church data belongs to the church and, by extension, to the people who entrusted it to us. It must be handled with the same care as a confidential pastoral conversation.
- No congregant data should ever be entered into a public or consumer AI tool (e.g., free ChatGPT, Claude.ai free tier, Gemini, Copilot personal) unless the church has a signed data processing agreement and the tool is accessed through an approved enterprise or organizational account with appropriate privacy protections.
- Staff and volunteers must assume that anything typed into a public AI tool may be used to train future models and could theoretically surface in another user’s session.
- Prefer Claude Enterprise (Preston Trail’s primary approved AI tool) for any work involving church data or internal knowledge.
4.2 Approved Tools & Accounts
The church will maintain a list of approved AI tools and accounts. This list will be reviewed quarterly by the AI Working Group / designated team. Only approved tools may be used for church-related work involving sensitive information.
| Tool | Approved Use | Account Type | Data Restrictions |
|---|---|---|---|
| Claude Enterprise | Primary approved AI tool for staff work | Enterprise (SCIM) | Enterprise privacy protections; follow org instructions |
| Planning Center | System of record for people and giving data | Church-governed | Primary system for congregant data; accessed through approved integrations |
| Other tools (ChatGPT, Gemini, etc.) | Public research, brainstorming only | Personal / free tier discouraged | No congregant or sensitive data |
| Image / video generators | Graphics, slides (with disclosure) | As approved | No faces of real people without consent |
Personal AI accounts must not be used for any work involving church data, internal documents, or congregant information. Claude Enterprise is the preferred and primary AI tool for staff. It is not the church’s primary system overall — Planning Center remains the system of record for people and giving data.
4.3 Incident Response
If a staff member or volunteer believes they have inadvertently entered sensitive congregant data into an AI tool:
- Immediately notify Tech — submit a ticket through the PT Support app in Microsoft Teams, or reach out directly if it is urgent.
- Document what data was entered, into which tool, and when.
- Tech will assess the risk, notify affected individuals if warranted, and determine whether the incident requires disclosure under applicable privacy laws.
4.4 Connections & Integrations (Tech Governance)
Connections between AI tools (such as Claude and Microsoft 365) and church systems (such as Planning Center, Perfect Wiki, and Rock RMS) are established, governed, and restricted exclusively by Tech, using the same controls and diligence applied to cybersecurity. Staff and volunteers do not create, modify, or individually request these integrations; they use the connected tools Tech provides. Tech maintains the registry of approved integrations.
Section 5: Disclosure & Transparency
5.1 When Disclosure Is Required
- Sermons and Teaching: If AI played a significant role in generating content (beyond grammar-checking or transcription), the teacher should disclose this to the team. Public disclosure to the congregation is encouraged but left to pastoral discretion.
- Congregant-Facing Communications: Any AI-generated content sent to the congregation (newsletters, emails, social posts) should be reviewed and approved by a human.
- Counseling & Pastoral Care: If a staff member uses AI to research a counseling topic, that is acceptable. If AI generates language that is used in a pastoral care context, that must be disclosed to the recipient.
- AI-generated images or video used publicly should be labeled when photorealistic or when authenticity could reasonably be questioned.
5.2 When Disclosure Is Not Required
- Using AI for internal administrative tasks (scheduling, note summaries, draft agendas)
- Grammar and spell-checking
- Personal study and research that informs but does not directly produce congregant-facing content
Section 6: Spiritual Formation & Congregational Discipleship
This section addresses the broader concern that AI is increasingly shaping the spiritual lives of the people in our pews — often without pastoral input.
6.1 The Discipleship Opportunity
Barna’s research reveals that one-third of practicing Christians want guidance from their pastor on how to navigate AI, yet few pastors feel equipped to provide it. This policy commits Preston Trail to actively discipling our congregation on faithful AI use, not merely regulating staff behavior.
6.2 What We Will Teach
Our church commits to regularly addressing the following themes with our congregation through sermons, classes, small groups, or other appropriate channels:
- AI is not a shepherd. It cannot know you, love you, pray for you, weep with you, or hold you accountable. It generates plausible text — it does not possess wisdom, discernment, or the Holy Spirit.
- AI reflects its training data, not God’s heart. AI models are trained on the internet’s content, which includes heresy, distortion, and error alongside truth. Every AI-generated theological claim must be tested against Scripture and the wisdom of the historic church.
- Convenience is not the same as formation. Spiritual growth often requires the slow, inefficient, relational work of community — not optimized answers delivered in seconds. Choosing the harder path of in-person conversation, communal worship, and accountable relationships is a form of faithfulness.
- Your data is sacred. We encourage congregants to be cautious about sharing personal prayer requests, struggles, or spiritual questions with AI tools that store and process that data.
- AI can be a useful servant. When kept in its proper place, AI can help with Bible reading plans, language study, scheduling devotional time, and exploring questions. The key is that it serves your spiritual life — it does not direct it.
6.3 Practical Congregational Guidance
We recommend sharing the following principles with congregants:
- Never let AI be your only voice. If you ask AI a spiritual question, bring the answer to a pastor, mentor, or small group for evaluation.
- Protect your inner life. Be cautious about sharing deeply personal spiritual struggles with AI tools. Confession and vulnerability belong in trusted human relationships.
- Watch for the substitution effect. If you notice you’re turning to AI instead of opening your Bible, praying, or calling a friend — that’s a warning sign worth paying attention to.
- Stay in community. The antidote to AI-mediated spirituality is embodied community. Prioritize being physically present with other believers.
Section 7: Training, Oversight & Enterprise Standards
Aligned with the AI Working Group’s phased approach (Governance → Staff Enablement → Integration → Long-term Platform):
- All staff will receive practical training focused on Claude Enterprise, effective prompting, limitations (hallucinations, context windows), and real workflow examples rather than abstract concepts.
- A prompt library, beginner guide, FAQ, and common workflows will be developed and maintained.
- New tools or major integrations (Planning Center, Perfect Wiki, future Rock RMS) require review and approval by Tech and the AI Working Group / designated governance leads.
- Organization-wide instructions for Claude Enterprise will be maintained to reinforce this policy and church values.
- The AI Working Group (or designated oversight person/team) will review usage, tools, and this policy.
Section 8: Accountability & Enforcement
- Staff remain fully responsible for all AI-assisted work. AI does not reduce personal or professional accountability.
- Violations of this policy may result in corrective action, up to and including termination of employment or volunteer role, depending on severity and intent.
- Staff and volunteers must promptly report concerns about AI misuse or data incidents.
- Questions about this policy or specific use cases should be directed to the designated AI policy point person or the AI Working Group.
Section 9: Review & Revision
This policy will be reviewed by the AI Working Group / designated team and updated as needed. AI technology is evolving rapidly, and this policy must evolve with it. Significant revisions require approval from the appropriate governing body.
Acknowledgment
By continuing in your role at Preston Trail Community Church, you agree to abide by this policy. Staff may be asked to sign an acknowledgment form.
Confidential — For Internal Use
This policy was developed with reference to Barna Group’s State of the Church 2026 research (in partnership with Gloo), Technology for Missional Impact: State of Church Tech 2026 (in partnership with Pushpay), and the priorities established by Preston Trail’s AI Working Group (July 2026).
Version 1.1 (July 2026): revised to align staff-facing guidance with the Staff AI Guide — data handling, tool designation, connections governance, deployment, and sermon-preparation integrity.