Prompts • Skills • Connectors • Agents • Ministry workflows • Tools
AI Playbook for Churches
A practical guide for pastors, church staff, and ministry leaders using AI to serve people better, starting with prompts, then skills, connected systems, and recurring work, while keeping pastoral care, teaching, and judgment with people.
Start With Your Role
Choose the role closest to your week. Start with one useful prompt, make it repeatable, then add the information it needs.
- Start with: sermon study notes or a sermon-to-small-group guide
- Save as a skill: your study method, tradition, trusted sources, and voice rules
- Connect: sermon archive, series plan, Planning Center Services
- First agent: sermon study packet assistant (research only, never writes the sermon)
- Measure: prep hours spent on research vs. prayer, writing, and people
- Start with: staff meeting agenda or budget-vs-actual summary
- Save as a skill: reporting format, fund rules, approval limits, and board style
- Connect: accounting exports, calendar, shared drive, Planning Center
- First agent: giving & budget pulse or events & facilities coordinator
- Measure: time to prepare board packets, calendar conflicts caught
- Start with: weekly announcement email or sermon social captions
- Save as a skill: voice guide, channel rules, priority order for requests
- Connect: church calendar, Canva, sermon transcripts
- First agent: weekly communications planner
- Measure: hours per week on comms, open rates, request turnaround
- Start with: first-time guest follow-up or a care-team visit schedule
- Save as a skill: next-steps pathway, follow-up timing, privacy rules
- Connect: Planning Center People and Workflows (read-only), care calendar
- First agent: first-time guest follow-up coordinator
- Measure: guests contacted within 48 hours, second-visit rate
- Start with: service run sheet or team rehearsal plan
- Save as a skill: service template, transitions, CCLI reporting, cue format
- Connect: Planning Center Services, song library, team schedules
- First agent: weekly service run sheet builder
- Measure: plans finalized by Thursday, last-minute changes
- Start with: volunteer recruiting post or a parent communication
- Save as a skill: child safety policy, ratios, lesson format, parent tone
- Connect: Check-Ins and Services schedules (read-only, no child names in prompts)
- First agent: volunteer schedule gap monitor or kids ministry readiness check
- Measure: unfilled serving slots, volunteer retention, ratio compliance
100 AI Prompts for Church Teams
Ready-to-use prompts for sermon prep, services, care, groups, communications, generosity, administration, volunteers, leadership, and responsible AI use. Copy one, add your church's context, and review the result.
Prompts that make AI a study partner for the preacher: background, structure, illustrations to verify, and follow-through content. The sermon itself stays yours.
Separates study from writing, so AI accelerates research without taking over the message. The interpretive-questions section surfaces debates you need to address.
Risks: AI may misstate original-language meanings or attribute views to the wrong scholars. Control: Verify word studies in Logos, Accordance, or a lexicon, and check interpretations against your trusted commentaries.
Gives the preacher options to react to instead of a finished product. Keeping the big idea fixed prevents AI from shifting the message.
Risks: AI structures can drift from the text toward generic self-help. Control: Check each movement against the passage before choosing.
Personal-story prompts help pastors use their own experiences, which connect best. Explicitly bans the fabricated anecdotes AI is known for.
Risks: AI frequently invents quotes and stories attributed to famous people. Control: Never use a historical illustration or quote until you find the original source.
Forces specificity across the congregation instead of one-size-fits-all application. Including skeptics and sufferers keeps the sermon pastoral.
Risks: Applications may overreach what the text says. Control: Ask of each one, 'Does the passage actually teach this?'
Puts calendar realities next to the content plan so collisions show up months early. Aligning groups and kids multiplies the series' impact.
Risks: AI may divide a book at awkward points. Control: Teaching team confirms passage breaks after reading the whole book together.
Treats AI as an editor of your work, not an author. Quoting the original line keeps you in control of every change.
Risks: Edits can flatten your natural voice. Control: Accept only changes you'd actually say.
Background details make texts come alive. Asking for misconceptions and debates protects against repeating popular myths from the pulpit.
Risks: Popular-level 'background facts' are often wrong, and AI repeats them. Control: Verify in a scholarly Bible dictionary or background commentary.
Anticipates hurt and objections before Sunday. Naming the church's position keeps AI from importing a different theology.
Risks: AI may present contested positions as settled or soften clear teaching. Control: Discuss with an elder or fellow pastor before preaching.
Gives a teacher a full scaffold in minutes. Asking for named sources lets you check that recommended books are real.
Risks: AI sometimes invents book titles or misattributes authors. Control: Confirm every recommended resource exists and fits your theology.
Aligns kids with the adult service so families can talk about the same idea at lunch.
Risks: Object lessons can oversimplify or distort theology. Control: Kids pastor reviews before Sunday.
Gives preachers regular, specific feedback that is hard to get from busy congregations. Quoting the transcript keeps feedback concrete.
Risks: AI cannot hear tone, sense the room, or judge spiritual fruit. Control: Pair with feedback from a trusted elder or preaching cohort.
Helps volunteers read Scripture with confidence. Avoids reproducing copyrighted translation text.
Risks: Pronunciations of biblical names vary by tradition. Control: Worship leader confirms the preferred pronunciations.
12 Claude-Ready Church Skills
Downloadable Claude Skill packages, not just longer prompts. Each includes a SKILL.md your team can tailor with your tradition, policies, and voice. A copy-and-paste version works in ChatGPT and other AI tools.
Connect Your Work
AI can only help with the information it can see. Start with one system, see what it can do, then add more when you are ready.
Easy start
Start with a limited, low-risk connection your team can test quickly.
- Access: Planning Center's MCP connection lets AI read (view) data in the products you choose: People, Services, Giving, Groups, Calendar, Check-Ins, Registrations, and Publishing
- Useful for: questions about service plans, schedules, groups, and events without copying data by hand
- Setup & limit: read-only; org admins control who can connect and are notified when someone connects; it is an evolving Planning Center Labs experiment. Turn off model training in your AI account settings and start with Services and Calendar before People or Giving
- Access: Gmail, Drive, and Calendar connections in Claude and ChatGPT
- Useful for: finding policies and past documents, drafting from your templates, calendar conflict checks
- Setup & limit: start with a shared ministry folder and calendar, not every staff inbox
- Access: Outlook, SharePoint, OneDrive, and Teams connections, or Microsoft Copilot inside your tenant
- Useful for: staff meeting notes, policy search, and document drafts
- Setup & limit: your Microsoft 365 admin controls access; start with one SharePoint site
- Access: Canva's connection for AI assistants to create and find designs
- Useful for: sermon series graphics, event slides, and social posts from your brand kit
- Setup & limit: review every design for rights, accuracy, and minors' consent before publishing
Needs an administrator
These can be useful, but someone needs to set access and permissions first.
- Access: official Slack and Notion connections for Claude and ChatGPT
- Useful for: staff updates, project notes, and the church's internal knowledge base
- Setup & limit: keep care and personnel channels out of scope; admins choose which spaces are visible
- Access: availability differs by AI product, QuickBooks plan, and country
- Useful for: reports and plain-language questions about the books
- Setup & limit: keep payments, payroll, and accounting changes with an authorized person; use read-only reports where possible
- Access: Pushpay offers AI features inside its own product (some in beta); no official direct Claude or ChatGPT connection is confirmed here
- Useful for: using Pushpay's built-in AI for giving and people insights; exported reports for anything else
- Setup & limit: ask your Pushpay representative about API access before building anything custom
- Access: Subsplash has a developer API and its own Trends AI dashboards; no official direct Claude or ChatGPT connection is confirmed here
- Useful for: giving and engagement trends inside Subsplash; exported reports for AI drafting
- Setup & limit: API work is an integration project that needs an owner and access rules
Integration project
Plan the use case, source data, permissions, and owner before connecting.
- Access: open-source church management with a REST API that a developer could expose through a custom MCP server
- Useful for: one narrow, view-only task (e.g., volunteer schedule gaps) with a named owner
- Setup & limit: this is an integration project; document fields, permissions, and logging first
- Access: no official AI connection is confirmed here; data can be exported
- Useful for: exported reports (attendance, events, aggregate giving) a person checks before use
- Setup & limit: remove personal details you don't need before uploading any export
- Access: transcripts and files from YouTube, Resi, BoxCast, or your podcast host, saved to a shared folder
- Useful for: sermon recaps, group guides, captions, and clips
- Setup & limit: use the final approved transcript; an automated folder is simpler than a live connection
Good to know
Useful limits and honest gaps to keep in mind before you connect anything.
- Access: CCLI SongSelect and most modern Bible translations are licensed content, not AI connections
- Useful for: referencing songs by title and CCLI number, and verses by reference
- Setup & limit: don't ask AI to reproduce lyrics or long translation passages; use your licensed sources and each translation's quotation guidelines
Tools
Choose the AI assistant and church software that fit your team. The goal is to make your existing systems easier to use, not replace everything at once.
AI Assistants & Writing
8Church Management (ChMS)
8Giving & Generosity
7Worship, Media & Sermons
8Bible Study & Sermon Research
6Communications & Design
8Volunteers, Check-In & Next Gen
6Finance & Accounting
6Operations & Productivity
612 AI Agents for Churches
An agent is an assistant for one recurring job. It gathers the right information, follows your process, and prepares the work for someone to review and decide.
A good first agent handles one task your team already does, reads only what it needs, never messages people on its own, and hands its work to a named person.
# Weekly Service Run Sheet Builder ## Job to be done Have a complete draft run sheet ready before the weekly production meeting. ## When it runs Every Tuesday morning, and when a service plan changes after Wednesday. ## Approved context Planning Center Services plans (read-only), service template, team schedules, sermon title and Scripture references. ## Operating loop Read the service plan; build a timed run sheet; check for missing items (keys, readings, slides, team gaps); flag overtime; draft team briefing notes. ## What it delivers A draft run sheet, missing-items list, and team briefing ready for the worship leader. ## Human owner Worship leader approves the service order and resolves gaps. ## What it must never do Never edit the service plan, change songs, message volunteers, or write out song lyrics. ## How to measure it Plans finalized by Thursday, last-minute Sunday changes, hours saved per week. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Sermon Study Packet Assistant ## Job to be done Give the preaching pastor a research head start on upcoming passages. ## When it runs Two weeks before each sermon date in the series plan. ## Approved context Series plan, approved commentaries and resources, church statement of faith, pastor's prior notes on the book. ## Operating loop Read the passage assignment; gather background, cross-references, and interpretive questions from approved sources; prepare outline options; mark claims to verify. ## What it delivers A study packet with cited sources, debated questions, and outline options, delivered to the pastor's folder. ## Human owner Preaching pastor studies, prays, writes, and preaches. ## What it must never do Never write a sermon manuscript, publish anything, or present debated interpretations as settled. ## How to measure it Pastor research hours, packet usefulness rating, verification corrections needed. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Sermon Content Multiplier ## Job to be done Turn each Sunday sermon into a week of discipleship content. ## When it runs When the final sermon transcript is added to the archive folder. ## Approved context Final transcript, series plan, voice guide, channel calendar. ## Operating loop Extract the big idea and key lines; draft recap email, group guide, devotionals, and social captions; mark quoted lines for pastor approval. ## What it delivers A content set by channel with a pastor-approval list. ## Human owner Communications lead schedules; pastor approves quotes. ## What it must never do Never publish, add teaching that wasn't preached, or alter quotes. ## How to measure it Content ready by Monday noon, group guide usage, engagement on recap content. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# First-Time Guest Follow-Up Coordinator ## Job to be done Make sure every first-time guest hears from a real person within 48 hours. ## When it runs When a new connection card or guest form is submitted. ## Approved context Connection card fields approved for use, Planning Center People and Workflows (read-only), next-steps pathway, team roster. ## Operating loop Read new submissions; match each guest to a next step and team member; draft a personal welcome note; set follow-up reminders; flag guests past 48 hours. ## What it delivers A daily follow-up worklist with owners and draft messages. ## Human owner Connections pastor or assigned volunteer personalizes and sends every message. ## What it must never do Never send a message, add people to lists, or contact children. ## How to measure it Percent contacted within 48 hours, second-visit rate, next-step conversions. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Pastoral Care Request Router ## Job to be done Get every care request to the right person quickly, with urgent needs going straight to a pastor. ## When it runs When a new prayer or care request is submitted through the approved form. ## Approved context Care request form fields the requester approved, care team roster and on-call schedule, care categories. ## Operating loop Categorize the request; check for urgent or crisis indicators; route to the on-call pastor or care team lead; create a follow-up reminder; never summarize crisis content beyond flagging it. ## What it delivers A routed request with category, urgency, assigned person, and follow-up date. ## Human owner Care pastor or on-call pastor responds personally. ## What it must never do Never reply to the requester, offer counsel, share requests beyond approved circles, or delay an urgent flag. ## How to measure it Time from request to human contact, urgent requests reached same day, missed follow-ups. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Member Check-In Watch ## Job to be done Help shepherds notice people who may need a caring check-in. ## When it runs Monthly, after attendance and serving records are updated. ## Approved context Attendance, group, and serving participation patterns (read-only), shepherd or group leader assignments. ## Operating loop Identify people whose participation dropped noticeably; group by assigned shepherd; suggest a simple check-in; exclude anyone already in active care. ## What it delivers A short, private check-in list for each shepherd or group leader. ## Human owner Pastor or shepherd decides whether and how to reach out. ## What it must never do Never label anyone's spiritual condition, contact people, or share the list beyond assigned shepherds. ## How to measure it Check-ins completed, people reconnected to groups or serving, shepherd feedback. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Volunteer Schedule Gap Monitor ## Job to be done Catch unfilled serving slots and over-scheduled volunteers before Sunday. ## When it runs Every Monday and when a scheduled volunteer declines. ## Approved context Planning Center Services schedules (read-only), team rosters, serving frequency, screening status (yes/no). ## Operating loop Find unfilled or declined positions; flag people serving too often or with expired screening; suggest who to ask; draft a personal ask for the leader. ## What it delivers A gap report by team with suggested asks. ## Human owner Team leader makes every ask and schedule change. ## What it must never do Never schedule or message volunteers, or place anyone without current screening in a kids or student role. ## How to measure it Unfilled slots by Thursday, over-scheduled volunteers, volunteer retention. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Kids Ministry Readiness Check ## Job to be done Confirm every kids room is staffed safely before the weekend. ## When it runs Thursday before each weekend and before special events. ## Approved context Room plan, expected attendance by room, volunteer schedule, screening and training status (yes/no), ratio policy. ## Operating loop Compare scheduled volunteers to ratio rules and two-adult requirements; check screening and training status; list gaps by room; suggest fixes. ## What it delivers A readiness report by room: ready, at risk, or not ready. ## Human owner Kids pastor and safety lead decide room staffing and openings. ## What it must never do Never use children's names or details, contact families, or mark a room ready that fails policy. ## How to measure it Rooms meeting ratio, screening gaps caught before weekend, last-minute room closures. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Weekly Communications Planner ## Job to be done Turn a pile of announcement requests into one clear weekly plan. ## When it runs Every Wednesday at the request deadline. ## Approved context Announcement requests, church calendar, priority rules, voice guide, channel plan. ## Operating loop Collect requests; rank by priority rules; draft channel versions; check facts against the calendar; list items held for next week. ## What it delivers A weekly comms plan with drafts and a fact-check list. ## Human owner Communications lead approves and publishes. ## What it must never do Never send, post, or promise placement to a ministry. ## How to measure it Hours on weekly comms, fact corrections needed, open rates. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Giving & Budget Pulse ## Job to be done Give leadership a plain-language view of giving and spending each month. ## When it runs Monthly after the books are closed, and when a fund drops below a set threshold. ## Approved context Aggregate giving reports, budget vs. actual, designated fund balances, prior-year figures. ## Operating loop Compare to budget and last year; flag variances and low funds; list possible reasons to verify; prepare questions. ## What it delivers A one-page finance pulse with charts-ready numbers and owner questions. ## Human owner Executive pastor and treasurer verify and decide. ## What it must never do Never view or report individual donors, move money, or change budgets. ## How to measure it Report prep time, surprises caught early, leadership questions answered. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Contribution Statement Prep ## Job to be done Get accurate giving statements and acknowledgments ready for review on time. ## When it runs Quarterly and at year-end statement time; when a single gift of $250 or more needs acknowledgment. ## Approved context Giving system exports (finance staff access only), acknowledgment templates, approved tax language, noncash gift records. ## Operating loop Check statements for missing addresses, unmatched gifts, and required language; flag noncash gifts needing descriptions; draft acknowledgment letters. ## What it delivers A statement readiness report and acknowledgment drafts for finance staff. ## Human owner Finance staff verifies and sends statements. ## What it must never do Never send statements, assign values to noncash gifts, or share donor data outside finance. ## How to measure it Statements on time, correction requests, acknowledgment turnaround. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
# Events & Facilities Coordinator ## Job to be done Catch calendar conflicts and setup needs before an event is approved. ## When it runs When a new room or event request is submitted. ## Approved context Church calendar, room list and capacities, facility use policy, setup templates. ## Operating loop Check conflicts with rooms, times, key people, and teams; list setup, tech, security, and insurance needs; draft a confirmation or alternative for the coordinator. ## What it delivers A request review with conflicts, needs, and a draft reply. ## Human owner Facilities coordinator approves bookings and replies. ## What it must never do Never book rooms, approve requests, or commit staff or volunteers. ## How to measure it Double-bookings, setup misses, request turnaround time. ## Operating rules 1. Use only approved sources and follow the linked church skill. 2. Cite source records and separate facts from assumptions. 3. Route missing information, safety concerns, and pastoral matters to the human owner. 4. Keep a record of trigger, inputs, output, reviewer, decision, and override. 5. Stop and ask for human review when policy, theology, evidence, or approval authority is unclear. 6. Never handle counseling details, minors' information, or named giving data beyond what the owner approved.
AI for Worship & Teaching
Use AI as a research and production assistant for services and sermons. The preacher owns the message; the worship leader owns the service.
- Prompts: sermon study notes, service run sheet, sermon-to-small-group guide
- Skills: sermon research & study notes; worship service planning; sermon repurposing
- Connect: Planning Center Services, sermon transcript archive, series calendar
- Agent: weekly service run sheet builder or sermon content multiplier, drafts only, never publishes
- What AI does: Gathers background, cross-references, historical context, and outline options for a passage
- Best use: Study partner for the pastor's own preparation, from sources you trust
- Human role: The pastor prays, interprets, writes, and preaches. AI does not write the sermon.
- What AI does: Builds a draft order of service, transitions, and cue sheet from your template
- Saves: 1-2 hours a week of copying between planning tools and documents
- Control: Worship leader approves flow, song choices, and Scripture readings
- What AI does: Turns the delivered sermon transcript into a recap, devotionals, group questions, and social captions
- Rule: Uses only what was actually preached; adds no new teaching
- Result: One message becomes a week of discipleship content
- What AI does: Maps sermon series across the church year, holidays, and church calendar
- Helps: See gaps, collisions with events, and theme repetition 6-12 months out
- Control: Teaching team decides books, themes, and preachers
- What AI does: Generates captions and transcripts; drafts translations of announcements and outlines
- Helps: Hearing-impaired and multilingual members follow along
- Control: A fluent member checks every translation before use
- What AI does: Drafts rehearsal plans, tech checklists, and volunteer briefings
- Helps: Volunteers arrive knowing their role and cues
- Note: Never ask AI to reproduce copyrighted song lyrics; pull them from your licensed source
Worship & Teaching Implementation Checklist
WorkflowBefore You Start
- Agree as a teaching team on how AI may and may not be used in sermon prep
- List your trusted commentaries, translations, and confessional standards
- Create a standard service template (order, timings, cue format)
- Confirm your CCLI licenses (copy, streaming) and where lyrics come from
- Pick one pilot: run sheet, transcript recap, or group guide
After You Start
- Verify every Scripture reference, quote, and historical claim AI provides
- Track hours saved per week on service prep
- Check repurposed content for accuracy against the actual sermon
- Ask volunteers if run sheets and briefings are clearer
- Review the teaching-team AI agreement every six months
- Do NOT: Preach AI-written sermons as your own. Use AI for research and organization; the message comes from the pastor's study and prayer.
- Do NOT: Trust AI quotes, statistics, or illustrations without checking the original source. AI invents quotes and stories that sound real.
- Do NOT: Accept AI theology uncritically. Check interpretations against Scripture, your tradition, and trusted scholarship.
- Do NOT: Ask AI to reproduce copyrighted song lyrics or long passages of copyrighted Bible translations. Use your licensed sources (e.g., CCLI SongSelect) and each translation's quotation guidelines.
- Do NOT: Publish repurposed sermon content without the pastor's review.
- Do: Be honest. If your church has a disclosure practice for AI-assisted content, follow it.
AI for Pastoral Care & Discipleship
AI can organize the logistics of care and discipleship. It must never become the care. Confidentiality and people come first.
- Prompts: guest follow-up plan, care-team visit schedule, small group leader guide
- Skills: pastoral care follow-up; guest & assimilation follow-up; groups & discipleship pathway
- Connect: Planning Center People, Workflows, and Groups (read-only), care calendar
- Agent: first-time guest follow-up coordinator or care request router, organizes and routes, never responds
- What AI does: Turns connection cards into a follow-up worklist and draft welcome notes
- Helps: Every guest hears from a real person within 48 hours
- Control: A staff member or volunteer personalizes and sends every message
- What AI does: Builds meal trains, hospital visit rotations, and follow-up reminders
- Uses: Initials or IDs, not names and diagnoses
- Control: Care pastor assigns and approves all care contacts
- What AI does: Sorts requests by type and urgency for the prayer team
- Rule: Shares only what the requester approved for sharing
- Escalation: Any sign of crisis or danger goes to a pastor immediately, not to a queue
- What AI does: Drafts next-step pathways, membership class outlines, and reading plans
- Helps: Make the path from guest to member to leader visible
- Control: Pastors set the theology and expectations of each step
- What AI does: Writes discussion guides, icebreakers, and leader tips from sermon content
- Helps: New leaders feel equipped without hours of prep
- Control: Groups pastor reviews curriculum before release
- What AI does: Builds a calendar of follow-up touchpoints after a loss, birth, or move
- Helps: People are remembered at 1 month, 6 months, and the first anniversary
- Control: Every touchpoint is a real person's call, card, or visit
Pastoral Care Implementation Checklist
ControlsBefore You Start
- Write down what care information may never go into an AI tool
- Use business or enterprise AI accounts with model training turned off
- Define how care requests are de-identified (initials, ID numbers)
- Document crisis protocol: who is called, how fast, and referral resources (e.g., 988 in the US)
- Confirm mandated-reporting obligations for staff and volunteers in your state
After You Start
- Spot-check AI worklists for any identifying details that slipped in
- Measure guest follow-up speed and second-visit rate
- Confirm every urgent request reached a person the same day
- Ask care-team members whether the tools help or get in the way
- Review care data access quarterly; remove anyone who no longer needs it
- Do NOT: Counsel, comfort, or respond to anyone in crisis. AI is never the first or only responder. A pastor or trained person responds directly.
- Do NOT: Paste counseling notes, confessions, diagnoses, addiction, abuse, or family conflict details into AI tools.
- Do NOT: Use AI to decide who 'needs' care or to judge anyone's spiritual condition. Patterns are prompts for a human conversation, nothing more.
- Do NOT: Send automated messages that pretend to be from a pastor.
- Do NOT: Share prayer requests beyond the circle the person approved.
- Do: Refer to licensed professionals when needs exceed pastoral care, and follow all mandated-reporting laws.
AI for Communications & Outreach
AI turns one set of church information into clear messages for every channel. Your communications lead keeps the voice and the priorities.
- Prompts: weekly announcement email, social media calendar, event promotion plan
- Skills: church communications & announcements; sermon repurposing
- Connect: church calendar, Canva, Google Drive or SharePoint, sermon transcripts
- Agent: weekly communications planner, drafts and prioritizes, never posts
- What AI does: Drafts the email, bulletin, slides, and stage announcement from one list
- Saves: 2-4 hours a week for small comms teams
- Control: Comms lead sets priorities and approves before sending
- What AI does: Writes captions, plans a calendar, and suggests clips from the sermon
- Helps: Stay consistent without posting for posting's sake
- Control: Photos of children only with parent consent; no names of minors
- What AI does: Builds a promotion timeline and drafts every touchpoint for an event
- Helps: Easter, VBS, and fall launch don't sneak up on you
- Control: Ministry leader confirms dates, costs, and details
- What AI does: Rewrites 'I'm New' pages, ministry pages, and FAQs in plain language
- Helps: Guests understand what to expect before they visit
- Control: Check every service time, address, and contact
- What AI does: Drafts partner letters, local press releases, and outreach event plans
- Helps: Clear, warm communication with neighbors and partners
- Control: Outreach leader owns relationships and commitments
- What AI does: Helps structure a first draft after leaders decide what to say
- Rule: Leaders, and often legal counsel, decide the message; AI only helps with clarity
- Control: Never send a sensitive statement without senior leadership approval
Communications Implementation Checklist
WorkflowBefore You Start
- Write a one-page voice and style guide AI can follow
- List your channels and what each is for (email, app, social, stage)
- Set a priority order for announcement requests
- Collect photo and video consent forms; flag no-photo families
- Baseline: hours per week on comms, email open rate
After You Start
- Fact-check dates, times, locations, and costs in every draft
- Track hours saved and request turnaround time
- Watch engagement: are fewer, clearer messages working better?
- Review AI-generated images for rights and appropriateness
- Refresh the voice guide when drafts start sounding generic
- Political activity: Churches are 501(c)(3) organizations. Follow current IRS guidance and your legal counsel on candidate and campaign communications; don't let AI draft anything that could be read as campaign activity without review.
- Minors: No names, faces, or identifying details of children without documented parent consent.
- Accuracy: AI confidently invents dates and details. Check every fact against the calendar.
- Voice: Edit drafts so they sound like your church, not like a generic marketing email.
- Images: Don't generate images of real people or copyrighted characters, logos, or artwork.
- Approval: Nothing goes public without the comms lead, and sensitive items need senior leadership.
AI for Generosity & Stewardship
Use AI to communicate gratitude and impact clearly and to prepare giving records accurately. Keep individual giving data private and pastoral.
- Prompts: giving report narrative, contribution acknowledgment letter, stewardship campaign plan
- Skills: generosity & giving communications; church finance & budget review
- Connect: Planning Center Giving or your giving platform (aggregate reports), accounting exports
- Agent: giving & budget pulse or contribution statement prep, prepares for review, never contacts donors
- What AI does: Turns aggregate giving data into a clear summary for leadership
- Shows: Trends vs. budget and last year, recurring vs. one-time, by fund
- Control: Uses totals, not individual names or amounts
- What AI does: Drafts thank-you letters and checks statements for required language
- Helps: Accurate, on-time acknowledgments for gifts of $250 or more
- Control: Finance staff verifies every amount and sends
- What AI does: Plans a series, drafts messages, testimonies outline, and FAQs
- Helps: Teaching generosity as discipleship, not fundraising
- Control: Pastors shape the message and the ask
- What AI does: Shows what giving accomplished: missions, benevolence, ministry
- Helps: Givers see the fruit of their generosity
- Control: Protect the dignity and privacy of people who received help
- What AI does: Drafts case statements, timelines, and pledge materials
- Helps: Clear communication on a big, multi-year effort
- Control: Board and campaign team approve every number and promise
- What AI does: Tracks designated gifts against their purpose and flags low or idle funds
- Helps: Honor donor intent and keep funds moving to ministry
- Control: Treasurer and leadership decide any use or re-designation
Generosity Implementation Checklist
ControlsBefore You Start
- Decide who may see individual giving data (usually very few people)
- Use aggregate exports for AI; never paste donor names with amounts into public tools
- Confirm acknowledgment language with your accountant or tax advisor
- Write down your church's theology and tone for talking about money
- Baseline: statement prep time, acknowledgment turnaround
After You Start
- Tie every AI-drafted number back to the giving system
- Track statement errors and corrections each year
- Check campaign messages for pressure, guilt, or overpromising
- Review who has access to giving data every quarter
- Ask a few givers whether communications feel grateful, not transactional
- Privacy: Individual giving is confidential. Limit access to designated finance staff and the pastors your policy names.
- No targeting by amount without a policy: Don't let AI segment or score people by giving size unless leadership has approved a pastoral, written approach.
- Acknowledgments: For U.S. churches, written acknowledgment is required for single gifts of $250 or more; it should state whether goods or services were provided (or that only intangible religious benefits were provided). Confirm details with your tax advisor.
- Noncash gifts: AI should never value donated property, stock, or vehicles. Describe the item; the donor is responsible for the value.
- Restricted funds: Honor designations. Re-designation is a leadership decision, often requiring donor contact.
- Tone: Generosity is discipleship. Avoid manipulative urgency in any AI-drafted appeal.
AI for Church Administration & Finance
AI prepares reports, policies, and schedules so leaders can decide. Financial approvals, tax treatment, and personnel decisions stay with people.
- Prompts: budget vs. actual summary, staff meeting agenda, policy first draft
- Skills: church finance & budget review; church policy & governance documents
- Connect: accounting exports, shared drive, calendar, board minutes folder
- Agent: events & facilities coordinator or giving & budget pulse, flags and drafts only
- What AI does: Summarizes monthly financials for staff, board, and congregation
- Helps: Non-finance leaders understand what changed and why
- Control: Treasurer verifies every number and explanation
- What AI does: Assembles agendas, summaries, and draft minutes
- Helps: Meetings start prepared and end with clear action items
- Control: Board clerk or secretary approves minutes before filing
- What AI does: Drafts first versions of policies (facility use, social media, AI use)
- Helps: Get from blank page to a reviewable draft quickly
- Control: Leadership, denomination, and legal counsel review before adoption
- What AI does: Checks room requests against the calendar and setup needs
- Helps: Fewer double-bookings and forgotten setups
- Control: Facilities coordinator approves every booking
- What AI does: Drafts job descriptions, onboarding plans, and review templates
- Helps: Small staffs get consistent HR basics
- Control: Personnel decisions and pay stay with leadership; consult counsel for employment questions
- What AI does: Summarizes vendor spend, contract renewals, and insurance dates
- Helps: Find savings and avoid auto-renewal surprises
- Control: Finance committee approves changes
Admin & Finance Control Checklist
ControlsBefore You Start
- Use exports or reports, not live write access to accounting systems
- Document approval limits and who signs checks (two-person rule)
- List your funds and designations so AI keeps them separate
- Note ministerial tax items (e.g., housing allowance) as human-only decisions
- Baseline: hours to prepare monthly reports and board packets
After You Start
- Reconcile every AI summary back to the general ledger
- Have a second person review financial narratives before distribution
- Keep AI-drafted policies marked DRAFT until formally adopted
- Track time saved on reporting and packet prep
- Review AI tool access and data retention settings annually
- Do NOT: Approve payments, move money, or change accounting records.
- Do NOT: Decide clergy tax matters such as housing allowance designation or minister tax status. These need board action and qualified tax advice.
- Do NOT: Make hiring, firing, discipline, or pay decisions.
- Do NOT: Adopt AI-drafted bylaws or policies without leadership, denominational, and legal review where required.
- Do NOT: Paste payroll, Social Security numbers, or bank details into AI tools.
- Do: Keep segregation of duties: the person counting and depositing offerings is not the person reconciling them.
AI for Volunteers & Next Gen Ministries
AI helps you recruit, schedule, equip, and thank volunteers, and prepare kids and student ministry. Child safety rules come first, every time.
- Prompts: volunteer recruiting post, serving schedule review, parent communication
- Skills: volunteer scheduling & team health; kids & student ministry safety & communication
- Connect: Planning Center Services and Check-Ins (read-only, no child names in prompts)
- Agent: volunteer schedule gap monitor or kids ministry readiness check, flags gaps, never contacts families
- What AI does: Writes role descriptions and invitations that explain impact and commitment
- Helps: Clear, specific asks get more yeses than general appeals
- Control: Ministry leader confirms requirements, including screening
- What AI does: Finds unfilled slots and people serving too often
- Helps: Spread the load before faithful volunteers burn out
- Control: Leaders make the ask personally
- What AI does: Builds role guides, checklists, and quick-reference cards
- Helps: New volunteers know exactly what to do on day one
- Control: Safety and policy content comes from your official policies
- What AI does: Adapts curriculum for ages, abilities, small rooms, or time limits
- Helps: Include kids with different needs and learning styles
- Control: Kids or student pastor approves content and theology
- What AI does: Drafts weekly parent emails, event details, and take-home guides
- Helps: Parents know what kids learned and how to continue at home
- Control: Incident or behavior communication is always human-written
- What AI does: Builds packing lists, schedules, permission forms, and safety plans
- Helps: Camps, retreats, and VBS run smoothly
- Control: Safety lead approves ratios, transport, and medical plans
Volunteers & Next Gen Safety Checklist
ControlsBefore You Start
- Re-read your child safety policy; AI work must follow it exactly
- Never put minors' names, photos, medical, or custody details into AI tools
- Track screening as yes/no status only (background check current, training current)
- Confirm room ratios and two-adult rules your church requires
- Baseline: unfilled slots per month, volunteer retention
After You Start
- Review every parent-facing message before sending
- Check AI schedules against screening status before publishing
- Measure unfilled slots and over-scheduled volunteers monthly
- Thank volunteers personally; AI can remind you, not replace you
- Audit any AI-generated lesson content for age-appropriateness
- Screening: AI scheduling never replaces background checks, references, or abuse-prevention training.
- Data: No children's names, photos, allergies, custody notes, or behavior notes in AI tools. Use room or group labels.
- Incidents: Any injury, allegation, or safety concern goes immediately to the designated leader, and to authorities as required by law. AI does not draft incident decisions.
- Communication: Adults do not use AI tools to message minors privately; follow your church's communication policy for students.
- Content: Review all AI-generated lessons, games, and images for age-appropriateness.
- Ratios: AI may flag ratio gaps; leaders decide whether a room opens.
Set Up & Get Running
If you already use prompts, here is how to turn one into a repeatable skill and then a useful first agent. Start with a task that already works.
From prompt to first agent
- Choose a task you do every week
- Use a real example, not a hypothetical
- Good first choices: announcement email, service run sheet, or guest follow-up
- Write down what to give the AI, what you want back, and who checks it
- Try it on three real weeks
- Improve it when results are unclear
- Start with files your reviewer already trusts
- Connect one source at a time, read-only
- Keep care, minors, and giving data out until rules are set
- Start with a prep or monitoring task, never one that messages people
- Set when it runs; a person checks every output
- Track time saved and what reviewers change
It's useful, low-risk, and easy to check. It reads the service plan, builds a draft run sheet, and flags missing items before the production meeting. It doesn't change plans, message volunteers, or write out song lyrics.
Copy these builders
Use the first after a prompt works. Use the second only after the skill has been tested on real work.
Days 1-30: Foundation
- Name an AI champion (staff member with interest and good judgment)
- Write a one-page 'never put into AI' guideline and share it with staff
- Set up business or team AI accounts with training turned off
- Pick 1 pilot workflow (e.g., weekly announcement email or run sheet)
- Record baseline: hours per week on that task
- Train 3-5 staff on 5 starter prompts from this playbook
- Teaching team discusses AI use in sermon prep
Days 31-60: Expand
- Turn the pilot prompt into a saved skill and test it for 3 weeks
- Launch a 2nd workflow (e.g., sermon recap and group guide)
- Connect one read-only source (calendar, Drive, or Planning Center Services)
- Build a shared church prompt library
- Measure hours saved vs. baseline
- Draft the church AI use policy
- Train ministry leaders, not just central staff
Days 61-90: Standardize
- Add a 3rd workflow (e.g., guest follow-up or volunteer gaps)
- Board or elders adopt the AI use policy
- Pilot one review-only agent with a named owner
- Write simple SOPs for each AI-assisted workflow
- Share results with leadership: time saved, what changed, what didn't work
- Tell the congregation how the church uses AI
- Plan the next three workflows
Implementation Success Measures
Measurement30-Day Targets
- Staff know and follow the 'never put into AI' list
- Pilot workflow running weekly with human review
- Baseline hours recorded
- No privacy or accuracy incidents in published content
60-Day Targets
- Pilot task time down noticeably (e.g., 30-50%) vs. baseline
- First saved skill used by more than one person
- One read-only connection working safely
- Draft AI policy reviewed by leadership
90-Day Targets
- 3 workflows running with SOPs and owners
- AI policy adopted
- First agent piloted with reviewer feedback
- Recovered hours redirected to people: visits, guests, leaders
- Leadership decision on the next wave
Week 1: Lead or executive pastor tells staff why: more time for people, not replacing people. Name the champion and share the 'never put into AI' list.
Weeks 2-4: 20-minute check-in at staff meeting. Share one good example and one mistake caught.
Day 30: Pilot review: hours saved, quality, concerns. Decide what to adjust.
Days 31-60: Add the second workflow. Publish the prompt library. Train ministry leaders.
Day 60: Leadership or elder briefing: results, draft policy, questions to discern.
Days 61-90: Policy adoption. First agent pilot. SOPs written.
Day 90: Short note to the congregation on how the church uses AI and what it means for them.
How the Pieces Fit Together
Start with a prompt. Save the ones that work. Add the systems and files they need. Then use an agent for recurring work, with someone checking the result.
- Ask AI to do one clear task
- Use it for a quick draft, outline, or summary
- Check the result before you use it
- Save the instructions for a task your team repeats every week
- Include your church's voice, beliefs, policies, and examples
- Update it when your process or policy changes
- Let AI see the calendar, service plans, and files it needs
- Stop copying and pasting the same information by hand
- Start read-only, with only the sources the task needs
- Run a skill on a schedule or when something happens
- Gather information, prepare the work, and flag issues
- Leave messages to people, decisions, and care with staff
Where AI Can Help Church Teams
Use AI to get routine ministry administration into a clear first draft, so people have more time for people. Keep teaching, care, and spiritual discernment with your leaders.
- Draft service run sheets and transitions
- Write the weekly announcement email and bulletin
- Turn the sermon into group guides and recaps
- Prepare staff meeting agendas and notes
- Organize first-time guest follow-up
- Build care-team visit and meal schedules
- Prepare volunteer recruiting and thank-yous
- Draft parent and member communications
- Summarize budget vs. actual in plain language
- Prepare giving statements and acknowledgments for review
- Draft policies, job descriptions, and board packets
- Catch calendar and facility conflicts early
- Preaching, teaching, and theological conclusions
- Pastoral care, counseling, and crisis response
- Prayer, discernment, and spiritual direction
- Decisions about people, money, discipline, and safety
AI Capabilities Explained
No jargon. What each kind of AI does, and what it looks like in church work.
Large language models like ChatGPT, Claude, and Gemini understand and write text. They can follow instructions, summarize, outline, and draft.
In church: announcement emails, small group questions from a sermon, volunteer job descriptions, policy first drafts.
Condenses long material (transcripts, meeting notes, reports) into the key points.
In church: a 40-minute sermon transcript into a 5-point recap; a 2-hour elder meeting into draft minutes.
Converts spoken audio and video into text, often with timestamps.
In church: sermon transcripts for accessibility, captions on livestreams, clips for social media.
Renders text in another language. Quality varies by language and topic.
In church: first drafts of bulletins or announcements for multilingual congregations, always checked by a fluent member.
Tools like Perplexity and NotebookLM answer questions from the web or from documents you upload, often with citations.
In church: comparing what your trusted commentaries say on a passage; finding the right section of your bylaws.
Finds trends and changes in data such as attendance, serving, or giving.
In church: noticing that a group of regular volunteers has not served in two months, so a leader can check in.
Rules that move work along: when X happens, do Y. AI can add a drafting or sorting step.
In church: a new connection card creates a follow-up task and a draft welcome note for a staff member to send.
Creates or edits graphics from a text description.
In church: sermon series graphics and event slides. Avoid recognizable characters, logos, or artwork you don't have rights to.
Guardrails: Privacy, Integrity & Safety
Simple rules for using AI faithfully in a church. People trust churches with their most personal moments; protect that trust.
- Counseling, confession, or pastoral conversation details
- Children's names, photos, medical, or custody information
- Named individual giving records
- SSNs, bank details, payroll, or personnel files
- AI researches; the pastor preaches
- Verify every quote, story, statistic, and Scripture reference
- Check theology against your tradition and statement of faith
- Agree as a teaching team on what is and isn't OK
- AI never counsels, comforts, or responds to crisis
- Crisis indicators go to a pastor immediately
- Patterns prompt human check-ins, never judgments
- Follow mandated-reporting laws without exception
- AI never replaces background checks or training
- No minors' data in AI tools; use room labels
- Incidents and allegations go to the safety lead at once
- Adults follow your policy for communicating with students
- Use business, team, or enterprise accounts
- Turn off model training on church data
- Connect read-only first; limit who can connect
- Remove access when staff or volunteers leave
- Don't send AI messages that pretend to be personal
- Have a disclosure practice your leaders agree on
- Tell the congregation how you use AI
- Correct mistakes openly
- No AI-reproduced song lyrics; use CCLI or your licensed source
- Follow Bible translation quotation limits
- Don't generate images of real people or copyrighted characters
- Credit sources you use in teaching
- Preaching and theological conclusions
- Pastoral care, prayer, and spiritual direction
- Money movement, tax matters, and approvals
- Hiring, discipline, membership, and safety decisions
Church AI Readiness Checklist
ControlsLeadership & Policy
- A pastor or elder is named as AI sponsor
- Teaching team has agreed on AI use in sermon prep
- AI use policy drafted and adopted by the board or elders
- Approved tools and accounts listed (training turned off)
- Staff and key volunteers trained on the 'never put into AI' list
Practice & Review
- Every public message has a human reviewer
- Care, minors, and giving data rules are enforced in connections
- Crisis and mandated-reporting paths documented and known
- Quarterly review of AI use, mistakes caught, and time saved
- Congregation informed about how the church uses AI
Purpose: Use AI to serve people well and steward staff and volunteer time, while protecting the trust people place in our church.
Guiding principles: People before productivity. Honesty in everything we publish. Confidentiality in care. Safety for children and students. Faithfulness to Scripture and our statement of faith.
Approved tools: [List, e.g., Claude Team or ChatGPT Business with training off; Planning Center MCP read-only; Canva]
Approved uses:
- Drafting announcements, emails, social posts, and event plans
- Sermon research, background study, and organizing notes (not writing sermons for delivery as one's own)
- Turning delivered sermons into recaps and group guides
- Service run sheets, schedules, checklists, and meeting agendas
- Plain-language summaries of aggregate financial reports
- First drafts of policies, job descriptions, and training materials
Never enter into AI tools:
- Counseling, confession, or pastoral conversation details
- Information identifying children or students
- Named individual giving records
- SSNs, bank details, payroll, medical, or personnel information
Human review: A named staff member reviews and owns anything sent, posted, preached, or filed. AI never responds to care requests, crises, or safety concerns.
Disclosure: [Describe your church's practice, e.g., we tell the congregation how we use AI and never present AI-written content as personal correspondence.]
Training & review: Annual training for staff and key volunteers. Quarterly review of AI use by [role]. Policy reviewed each year.
Approval: [Elders / Board / Session], [date]
AI Maturity Model for Churches
See where your church is today. Choose a realistic next step.
Curious + Ad Hoc
- Individuals use free AI tools on their own
- No guidelines on what's OK to paste in
- No shared prompts or review
- Leadership hasn't discussed AI
- Nothing connected
Shared Prompts & Guidelines
- Staff share a prompt library
- Basic 'never put into AI' guideline in place
- Business accounts with training off
- Human review before anything goes out
- Teaching team has talked about sermon prep
Embedded Ministry Workflows
- Saved skills used weekly (services, comms, guests)
- Board- or elder-approved AI policy
- One or two read-only connections
- Ministry leaders trained, not just central staff
- Quarterly review of time saved and incidents
- Congregation informed
Connected & Intentional
- Several review-only agents with named owners
- Clear data rules for care, minors, and giving enforced in connections
- Recovered time measurably redirected to people
- Policies reviewed annually
- Practices shared with partner churches or denomination
Maturity Self-Assessment
AssessmentLeadership
- AI sponsor named
- Teaching-team agreement on sermon prep
- AI policy adopted
- Staff and volunteers trained
Practice
- Shared prompt library
- Saved skills for weekly tasks
- SOPs for AI-assisted workflows
- Read-only connections to approved sources
Protection
- No care, minors, or named giving data in AI
- Human review on all public content
- Crisis and reporting paths documented
- Access removed when people leave
Measurement
- Baseline hours recorded
- Quarterly time-saved review
- Incidents and corrections tracked
- Recovered time redirected to people