PTCC Tech
Using AI at Preston Trail,What’s Fine, What to Ask, and What to Never Do
How we use AI here, where your church data belongs, and how to keep people’s trust while you do it.
Your Data
Use our systems — don’t make your own copy.
Knowing real things about real people is good ministry, and we want you to have it. The line isn’t how detailed the insight is — it’s that the data stays on our systems.
Ask Preston Trail
Our staff assistant, connected to church data the right way.
Use itPlanning Center
The primary home for people and giving data.
Primary systemSpreadsheets & Files
Fine for people data — as long as they stay inside Microsoft 365.
Keep it in M365Public AI Tools
Never paste congregant info into free ChatGPT, personal Gemini, and the like.
NeverYour Own Databases
No personal apps or websites that store congregant data.
NeverConnections
Claude and Microsoft links are set up and locked down by Tech — like cybersecurity.
Tech-governedClaude Enterprise is our primary and approved AI tool — not our primary tool overall. For people and giving data, that’s Planning Center.
Everyday Use
Most of what you’ll do needs no permission.
Go right ahead — just review what it gives you before it goes out.
Emails & Announcements
Draft them and clean them up.
Go aheadMeeting Notes
Summarize and turn into action items.
Go aheadFirst Drafts
Budgets, project plans, documents.
Go aheadSermon Prep
Brainstorm illustrations, outlines, research starts. Check Preaching & Teaching before you deliver it.
Go aheadProofreading
Polish anything you’ve written.
Go aheadTranslation
Turn documents and messages into other languages.
Go aheadStudy & Research
Commentaries, cross-references, historical context.
Go aheadDesign Concepts
Graphic design ideas and slide deck layouts.
Go aheadTranscription
Sermons, meetings, and interviews — as long as everyone has agreed to be recorded.
With consentBible Translations
Compare translations side by side.
Go aheadRule of thumb: you review it, you edit it, you own it.
Check With Us
A few things just need a quick conversation.
Most of these get a yes. We just need to know so it’s set up safely.
Automated AI Communication
AI that messages or replies to congregants on its own — chatbots, auto-replies, automated follow-up. A person needs to stay in the loop.
Ask firstNew AI Subscriptions
Buying or subscribing to a new AI tool for the church.
Ask firstAI Images & Video
Allowed with heavy review — and be careful depicting Scripture or biblical figures in a comedic or satirical way.
Review neededPilots & Experiments
Anything new that isn’t already under Go Ahead.
Ask firstOff Limits
These are never okay.
No exceptions — these protect people, trust, and the church.
AI Pastoral Care
No “ask our AI pastor” for counseling or care.
NeverAI-Written Prayers
Don’t have AI write a personal prayer for someone. When you pray for a specific person, those words come from you.
NeverPrivate Info in Public Tools
Never put people’s personal details — names, contact info, giving, notes about them — into public or personal AI.
NeverAI as Your Testimony
Don’t present AI writing as your own lived experience.
Never“Prophetic Words”
No AI-generated revelation or claims of divine insight.
NeverDeepfakes & Voice Clones
Cloning your own voice or likeness is fine. Doing it of anyone else — leader or member — is never okay.
Never of othersFinal Decisions
AI doesn’t make the call on money, hiring, or membership.
NeverStanding Up Your Own Tools
Don’t build or host an AI tool on your own. Anything the church runs on lives on Preston Trail infrastructure — bring it to Tech and we’ll set it up with you.
Never on your ownPreaching & Teaching
Let AI help you prepare — never preach for you.
Researching background, brainstorming structure, or proofreading a manuscript you wrote is all fine. Handing a passage to AI and preaching the result is not. Before you deliver anything AI helped with, you should be able to honestly say:
- ✓I’ve studied the text and can defend my interpretation on my own.
- ✓The convictions in this message are mine, not just what a model produced.
- ✓I’ve personally checked every quote, citation, and reference — I asked the AI to show me exactly where each one comes from, and I verified it myself.
- ✓Every story I present as personal actually happened to me, or is clearly attributed.
- ✓AI sped up my prep — it didn’t replace it.
When AI gives you a fact, quote, or verse, ask it: “Show me exactly where this comes from.” Then check it. AI can get things wrong — and can say them just as confidently when it does.
Your Part
What we need from you.
Tech sets up the tools and guards the data. Keeping people’s trust is a two-way street — here’s your side of it.
People’s Trust
Be honest when AI helped.
If something would be assumed to be personal, say it was AI-assisted.
Don’t pass AI off as your story.
Never present AI writing as your own testimony or lived experience.
Data
Keep church data in our systems.
Planning Center, SharePoint, and Microsoft 365 are where it belongs.
Don’t carry it out.
No personal spreadsheets, drives, or tools that live outside M365.
If Something Goes Wrong
Tell Tech right away.
If sensitive info went into the wrong tool, submit a ticket through the PT Support app in Teams. Grab one of us directly if it’s urgent.
Don’t hide it.
The longer it sits, the harder it is to fix. Early is always easier.