Policy outline
Allowed use = draft, organize, summarize factual operational context, and prepare reviewable work.
Refused use = sermon generation, counseling content, specific children summaries, writable finance actions, and autonomous external sends.
Approval rule = every email, calendar invite, social post, and integration action waits for a person.
Accountability rule = pastors and authorized staff remain responsible for ministry decisions.
Inputs to collect
- Allowed AI workflows
- Refused pastoral categories
- Required approval owners
- Data retention expectations
- Escalation path for sensitive disclosures
Outputs
- Staff AI use policy outline
- Human approval checklist
- Protected category list
- Implementation questions for leadership
How to use this tool
Step 1
Name allowed work plainly
Use specific workflows such as drafts, summaries, board prep, visitor follow-up, and source lookup.
Step 2
Name hard refusals
List sermon generation, counseling content processing, children summaries, and financial action boundaries directly.
Step 3
Assign approval owners
Decide who can approve drafts, external messages, integration actions, and policy exceptions.
Review checklist
- Does the policy define human approval?
- Does it protect counseling and confessional content?
- Does it say AI will not generate sermons?
- Does it explain how staff report sensitive disclosures?
Related questions
What should a church AI policy include?
A church AI policy should include allowed uses, refused uses, human approval rules, data boundaries, escalation paths, and accountability owners.
Is this church AI policy builder legal advice?
No. It is operational guidance for staff discussion. Churches should review policies with appropriate legal and denominational advisors.