CHURCH AI POLICY CHECKLIST
Church AI

A starting point for staff and board discussion—not a completed policy or a guarantee that a tool is safe.

[ ] Name a staff owner for AI use and a person who can approve new tools.
[ ] List the tools and accounts your church has approved, with their intended uses.
[ ] List acceptable tasks: drafting announcements, planning outlines, summarizing approved public information.
[ ] Identify information that must not enter an unapproved AI tool: pastoral conversations, prayer requests, children's details, financial records, passwords and other confidential information.
[ ] Review each provider's access, retention, deletion and model-training settings before connecting church accounts.
[ ] Give tools only the account access needed for the agreed task. Do not share staff passwords.
[ ] Require a named staff member to check facts, names, dates, sources, tone and theological statements before using generated content.
[ ] Keep email sending under staff control. AI may prepare a draft; a staff member reviews and sends it.
[ ] Agree when to disclose AI assistance, and use only material the church is authorized to share or adapt.
[ ] Define what staff should do if private data is entered, an output is harmful or a connected tool acts unexpectedly.
[ ] Train staff on the approved workflows and give them a place to ask questions.
[ ] Record the policy approval date, owner and next review date. Recheck permissions when staff or tools change.

DISCUSSION RECORD
Policy owner: ______________________________
Approved tools: ____________________________
Information restrictions: __________________
Reviewer / approver: _______________________
Training date: _____________________________
Next policy review: ________________________

Keep this completed checklist inside your church's approved systems. Do not send confidential notes through the public newsletter form.