---
name: plain-english-staff-handbook
description: Drafts a tailored, two-page Plain-English Staff AI Handbook for a specific church, nonprofit, or company, including approved tools, three safe role-based examples, three unmistakable red lines, and internal AI Champions contacts. Use to replace staff fear and guesswork with clear, practical confidence.
license: CC-BY-4.0
metadata:
  author: Paul Yerrick (paulyerrick.com / COKI Studio)
  version: "1.0"
  category: governance-and-training
  source: https://www.paulyerrick.com/ai/
---

# The Plain-English Staff Handbook Builder

Create a **two-page beginner AI handbook** tailored specifically to your organization's real staff roles so non-technical teammates stop feeling intimidated or quietly guessing what is allowed.

## When to Use This Skill

- Right after your leadership team, elders, or board adopts a one-page AI governance policy.
- When onboarding new staff or launching an internal AI Champions group.
- Whenever staff are either avoiding AI out of anxiety or using unapproved consumer tools on personal phones.

## When Not to Use This Skill (Red Lines)

- Do not treat this handbook as legal counsel. Have leadership, HR, or legal review data and privacy language before distributing organization-wide.
- Never publish a handbook that skips privacy rules, human ownership, or clear escalation paths for care/crisis situations.
- Do not include real personal phone numbers or private logins in an unapproved AI tool; use placeholders like `[IT Helpdesk Link]` or `[Champion Name]` and fill them in locally if needed.

## Inputs Needed

If the user has not already supplied these details, ask these **6 brief questions** in one message before drafting:

1. **Organization name and type:** (e.g., multi-site church, mid-sized SaaS company, nonprofit)
2. **Approved 1 to 2 AI tools:** (e.g., Claude Team, ChatGPT Enterprise, Google Gemini Workspace) and how staff request access
3. **Top 3 staff departments to tailor examples for:** (e.g., Ministry/Pastoral, Creative/Comms, Operations/Admin)
4. **Your 3 to 5 AI Champions (names or roles):** Who staff can walk up to with a quick question
5. **Your Governance Group or Pause Button owner:** Who approves new tools or pauses workflows
6. **Any specific organizational values or red lines** you want highlighted verbatim

## Step-by-Step Instructions

1. **Keep it strictly to two printable pages** (roughly 650 to 850 words). Nobody reads a 40-page technical manual.
2. **Start with reassurance, not rules.** Open with a short leadership posture statement naming what AI is for (subtracting administrative friction) and what AI will **never** replace (human presence, pastoral care, relationships, leadership discernment, and creative ownership).
3. **Include the four non-negotiable guardrails** in plain English:
   - Always disclose
   - Route care and crisis to real humans
   - Protect private data
   - Honor the Governance Group's pause button
4. **Write three concrete, safe everyday examples** pulled directly from the user's actual departments so a non-technical teammate immediately sees how it helps on a normal Tuesday.
5. **Write three unmistakable red lines** (what never goes into AI and what AI never does).
6. **Include a clean Green / Yellow / Red quick-reference box** and a **"Who to Ask" directory** naming the organization's AI Champions.

## Output Format

Use this exact markdown structure:

```markdown
# [Organization Name] Staff AI Handbook
**Version:** 1.0 | **Last Reviewed:** [Month Year] | **Policy Owner:** [Governance Group]

## Why We Use AI (And What It Will Never Replace)
[2 to 3 clear sentences framing AI as subtractive help for administrative friction, explicitly naming what remains 100% human.]

## Our Approved Tools
- **Approved Workspace(s):** [Tool 1, Tool 2] (team/enterprise privacy enabled, model training turned off)
- **How to get a seat:** [Exact step or contact]
- **Rule of thumb:** Never use personal or free consumer AI accounts for organizational work.

## Four Non-Negotiable Guardrails
1. **Always disclose:** Never let AI pose as a human staff member, pastor, or leader.
2. **Route care and crisis to real humans:** Prayer requests, counseling, grief, safeguarding, or personal crisis always go immediately to a human.
3. **Protect private data:** Never paste confidential pastoral, HR, donor, payroll, legal, or minors' data into unapproved tools. Strip identifying names whenever summarizing notes.
4. **Human ownership and the pause button:** Every published piece has a human name on it. Our Governance Group has full authority to pause any workflow that drifts from our values.

## Three Safe Ways to Use AI This Week
1. **[Department 1 example]:** [Concrete 2-sentence everyday example]
2. **[Department 2 example]:** [Concrete 2-sentence everyday example]
3. **[Department 3 example]:** [Concrete 2-sentence everyday example]

## Three Unmistakable Red Lines (Never Do This)
1. **Never** paste private personal, pastoral, donor, HR, or minors' records into unapproved or free AI tools.
2. **Never** outsource personal relational care, apologies, counseling, or spiritual authority to a machine.
3. **Never** publish AI-generated facts, quotes, or Scripture references without verifying them yourself.

## Quick Traffic Light
- **Green (Go):** Internal meeting summaries (names stripped), first-pass checklists, editing for clarity, brainstorming discussion questions inside approved tools.
- **Yellow (Ask First):** New AI subscriptions, public-facing website tools, connecting AI to ChMS/CRM/email, public AI imagery or video.
- **Red (Off-Limits):** Private data leaks, simulated human care, unverified public claims.

## Need Help? Ask an AI Champion
You do not have to figure this out alone. Walk up to or message one of our internal AI Champions:
- **[Department 1]:** [Name / Role]
- **[Department 2]:** [Name / Role]
- **[Department 3]:** [Name / Role]
- **Governance / New Tool Requests:** [Contact or Governance Group]
```

## Voice and Style Rules

- Write at a clear, warm, non-technical reading level. Zero tech buzzwords (no "LLM orchestration," "token windows," or "agentic pipelines").
- Lower the temperature: cautious staff should feel protected, and curious staff should feel clearly guided.
- Never use em-dashes or emojis.

## Quick-Start Example

**Example Input:**
> We are Grace Valley Church (45 staff). Approved tool: Claude Team (request a seat from Ops). Top 3 departments: Kids/Students Ministry, Creative/Comms, and Facilities/Ops. AI Champions: Jenna (Kids), Marcus (Comms), Dave (Ops). Governance Group: Executive Pastor, Lead Pastor, Comms Director, IT Director.

**Expected Behavior:**
Generate a complete, ready-to-print two-page handbook customized for Grace Valley Church with concrete examples for Kids/Students, Creative/Comms, and Facilities/Ops, zero jargon, and all four guardrails intact.
