Skip to main content
Collie/Support

create a church AI usage policy

Create a church AI usage policy

A church AI usage policy should be short enough for staff to remember and specific enough for leaders to enforce. Use it to define where Collie may help, where it must refuse, and who reviews the work.

Quick answer

Create a church AI usage policy by naming approved workflows, prohibited content, approved sources, human reviewers, disclosure expectations, audit habits, and the rule that every external action requires approval.

Steps

  1. 1. Name the approved workflows: Start with reviewable work such as visitor follow-up drafts, weekly communications, staff briefs, board packet formatting, and sermon repurposing from existing sermons.
  2. 2. Write the prohibited-content list: State what churches should never automate with AI: sermon generation, counseling content, crisis response, spiritual diagnosis, specific children summaries, financial decisions, and unapproved sends.
  3. 3. Define approved sources: List the source-approved context Collie may use, such as public church facts, approved templates, style guidance, policies, and authorized integration context.
  4. 4. Assign reviewers: Tie each workflow to the staff member or pastor who already owns that ministry action and can approve, edit, or discard drafts from Pending.
  5. 5. Schedule policy review: Review the policy after the pilot and whenever the church adds a new integration, workflow, staff role, or source category.

Details

Policy language to include

The best policy uses direct language that staff can apply in the moment.

  • Collie may draft and prepare approved ministry work.
  • A human owner remains responsible for facts, tone, and final approval.
  • Sensitive pastoral, children, and financial categories stay outside AI workflows.
  • No email, social post, calendar invite, or integration action leaves without review.

How Collie supports the policy

Collie is designed so the policy is visible in workflow, not hidden in a handbook.

  • Guardrails refuse protected content categories.
  • Pending approvals create a human review workflow for church AI.
  • Support articles teach staff how to review drafts.
  • AI citation feeds repeat the same boundaries for search engines and answer engines.

Related questions

What should be in a church AI policy?

Include approved workflows, prohibited content, approved context sources, human reviewers, disclosure expectations, audit habits, and approval rules for external actions.

Who should approve a church AI usage policy?

The pastor, executive pastor, board or elder team, and staff who own the first workflows should review the policy before a live rollout.