AI in service of the mission

Our vision is a movement for all people to discover and deepen a relationship with Jesus Christ. That work happens through people, as God leads. AI can take some of the busywork around ministry so more of your week goes to those people. Our four core values say how we use it.

Our Code of Conduct says more. AI and our Code of Conduct walks through all ten attributes with AI in the room.

The four moves

What is in the kit

Your first 30 days

1. Week 1

   Get set up

   Log in to the church's approved AI account. Keep it open all day. Try two jobs: explain something, and improve an email.

2. Week 2

   Make one skill

   Pick a task you repeat. Do it with Claude, then say: "Build a skill from the work we just did."

3. Week 3

   Teach one person

   Sit with a teammate, laptops open, for 15 minutes. Show them one thing that works.

4. Week 4

   Count it and spend it

   Log the time you saved. Write down where it went. A conversation with a serve staff member counts.

Five habits that change the answers

Which model to use

This guide changes as models change. The current version is on the Choose your tool page.

Three rules that do not bend

Church policy comes first. If anything here differs from church policy or from what your leader has told you, follow that and tell your leader so the kit can be fixed.

Who to ask

The ten attributes, with AI in the room

Five questions before you hit send

Run these when a use of AI feels new or uncertain.

1. Would I be comfortable if the person this is about read my prompt? If not, take their details out. (We Glorify God by Honoring Others)
2. Is my name going on this? Then read every word and make it yours. (We Live Authenticity)
3. Did I check the Scripture, the names and the facts? Open the Bible. Open the calendar. (Biblical Integrity, We Choose to Trust)
4. Is this a decision? Pray first. AI can lay out options. People decide. (We Pray 1st and Decide 2nd)
5. Where will the time go? Name the person or the rest it frees you for. (We Are Family, Sacrificial Love)

Work that stays with people

Some work is ours to do. AI helps only around the edges of it, if at all.

Carry it, live it, teach repeatedly, expect it

Every staff member carries culture. The same four steps apply to how we use AI.

When it goes well, remember a line we say often: "We know this is God because we're not that good."

For everyone

Explain [topic or term] to me in plain language, as if I am smart but new to it.
Give me the three points that matter most and one example.
Then tell me what I should double check with a trusted source.

I need to understand [question]. Research it and give me:
1. A short answer
2. The details that matter
3. What is still uncertain or depends on the campus or the situation
4. Where I should verify it
Ask me any questions you need before you start.

Here is a draft email. Make it clearer, warmer and shorter. Keep my meaning.
Do not add promises, dates, times or details I did not give you.
Reader: [who is reading]. What I want them to do: [action].

[paste draft with names removed]

I want to [goal]. Ask me questions, one at a time, until we have a good plan.
Then write the plan as a short list of steps.

Summarize the document below in five bullets. Then list every date, time, deadline and dollar amount you found, exactly as written. Flag anything that looks unclear.

[paste text with names and personal details removed]

List every fact, number, date, name and Scripture reference in your last answer that I should verify against a source before I use it. Mark the ones you are least sure of.

You explained how to do this. How much of that can you do for me right now?
Do that part, and tell me exactly what is left for me to do.

Based on all the work we did in this chat, build a skill so I never have to type this prompt again. Include the steps, the questions to ask me first, the rules to follow and a short checklist to run before I use the result.

Campus teams

Write a follow-up email to someone who came to [campus] for the first time this weekend.
Write it as a template, with [Name] where the person's name goes.
The reader may be new to church. Use warm, plain words and no insider church terms.
Thank them for coming. Give them one next step: [next step, with date, time and place].
Tell them they can reply to me with any question.
Under 110 words. Do not add dates, times or details I did not give you.

Here are my rough notes from this weekend at [campus]. Sort them into:
1. Wins worth celebrating with the team
2. Fixes, each with what happened and one suggested next step
3. Questions nobody has answered yet
Under every fix, add a blank line that says "Who's owning that?"
Do not invent owners, numbers or details that are not in my notes.

[paste notes with names removed]

Write a short message asking serve staff on the [team] team at [campus] to serve on [date] at [time].
Say what the need is and where and when to be there.
Say how to reply yes: [how to reply] by [date].
Tone: direct, grateful and specific. No guilt and no pressure. Under 90 words.
Use [Name] where a name goes. Do not add details I did not give you.

Build a run-of-show for [event] at [campus] on [date], from [start time] to [end time].
Give me a table with these columns: time, what happens, where, who is owning it and what they need. Leave the owner column blank for me to fill in.
Then list what could go wrong and what I should confirm with facilities, production and the communication team.
Ask me any questions you need before you start.

Ministry teams

Nothing about a specific child or student goes into a prompt. Write the draft with event details only and add names yourself before you send.

Write an email to parents about [event] for [Eleven22 Kids or Eleven22 Students] at [campus].
Details: [date, time, place, cost, what to bring, drop-off and pick-up, sign-up deadline].
Put the date, time and place near the top. Say what parents need to do and by when.
Plain and warm, under 150 words. Do not add details I did not give you.
Do not include or ask for information about any child or student.

Below is the outline of this weekend's message. Write eight discussion questions a disciple group leader can use.
Start with two easy questions that get people talking. Then move from the text to real life. End with one question about a next step this week.
Use only the Scripture references in my outline. Give references only. Do not quote verse text from memory, because a person will check every reference in the ESV.
Do not add points the outline does not make.

[paste outline with names and personal stories removed]

I have an idea for [event] for [ministry] at [campus], around [date], for about
[number] people. The goal is [what we hope happens for the people who come].
Ask me questions, one at a time, until the plan is clear. Then give me:
1. A timeline that works back from the date
2. The serve staff roles we need
3. A supply list and a simple budget outline
4. What facilities and the communication team need from me, and by when

Turn my notes from [lesson or event] into a recap for my leader and my team:
two sentences on what happened, the wins, what we would change next time and the follow-ups that still need an owner.
Do not invent numbers, names or stories. If my notes leave something out, list it as a question.

[paste notes with names removed and nothing about a specific child or student]

Communication and creative

External communication goes to the communication team for review before it is published. All video goes through the film team.

Rewrite this in the Eleven22 voice: real, warm, direct and clear.
Write so a neighbor who has never been to church would understand every word.
Point to Jesus more than to the program. Say "serve staff" and "campus."
Keep every fact, date and time as I wrote it.
If the draft includes Scripture, keep the reference and do not quote verse text from memory, because a person will check every reference in the ESV.

[paste draft with names removed]

Give me 10 subject lines for this email. Five should be plain and specific.
Five should be warm. None should use all caps, exclamation points or pressure.
Each one should tell the reader what the email is about.

[paste email with names removed]

Here are the details for [event or news]: [what it is, who it is for, date, time, campus or campuses, cost, how to sign up, deadline].
Draft an announcement set for the communication team to review:
1. A stage announcement that takes about 30 seconds to read out loud
2. An email paragraph
3. A social caption
4. A one-line version for a slide
Use the same facts in all four. Do not add details I did not give you.
List anything that is missing.

Check the draft below against these Eleven22 style rules. List every miss with a suggested fix.
- No oxford comma
- Numbers under 10 are written out
- Times look like 5-9pm and 10am. Dates look like October 12, with no "th"
- "email" and "log in to"
- Lowercase: gospel, biblical, godly, campus, pastor without a name, disciple group, serve staff, worship center
- Capitalize: Scripture, Bible, the Word and pronouns for God
- "Jesus's" takes an apostrophe s
- #onemore is lowercase
Then list every Scripture reference, name, date and time so I can check each one.
Do not quote verse text from memory. A person will check every reference in the ESV.
Do not rewrite the draft. Only list the fixes.

[paste draft with names removed]

Worship and production

Here is the run-of-show for [service] at [campus], with names removed. Check it for:
- Timing that does not add up to a total of [minutes] minutes
- Transitions with no owner or no cue
- Moments where worship, production and the host each need to know something and the plan does not say it
List your questions for me. Do not change the order of the service.

[paste run-of-show]

Build a training outline for new serve staff on the [team] team, such as
[cameras, audio, lyrics or stage]. I have [number] minutes.
Include why this role matters to the person sitting in the room, the five things someone must know on day one, a hands-on practice step, common mistakes and who to ask for help.
Write it so someone with no production background can follow it.
Ask me any questions you need before you start.

Here are my notes from [service or event]. Turn them into a debrief:
1. Wins
2. What went wrong, in the order it happened, with the cause if my notes give one
3. Fixes, each with a blank for the owner and the date
4. What to test before next weekend
Write about the gear and the process, and leave people's names out.
Do not guess at causes my notes do not support.

[paste notes with names removed]

Care and pastoral

Every prompt in this section uses no personal details at all. Notes to people who are hurting are written by a person, and prayer requests and care notes never go into AI.

I have a hard conversation coming up about [general topic, such as grief, conflict or a big decision]. I will not share any details about the person.
Help me prepare myself. Give me eight open questions I could ask, things to avoid saying and ways to listen well.
Keep it general. Do not ask me for the person's name or story.

Build a checklist for a church staff member making a [hospital or funeral] visit.
Cover what to confirm before I go, what to bring, how long to stay, what to do when I arrive and what to follow up on afterward.
Keep it short and practical.
If you suggest Scripture to read, give references only. Do not quote verse text from memory, because a person will check every reference in the ESV.
Do not ask me about the person or the family.

Explain [topic, such as how grief often shows up in the first year] in plain language so I can learn it.
Give me the main ideas, what people often get wrong and the kinds of trusted sources where I can read more.
Tell me where a trained counselor or a doctor should be the one to speak.
Do not give advice for a specific person.

Operations

Here are my rough notes on how we do [process]. Turn them into a step-by-step SOP with who does each step, what they need and how they know it is done.
Use roles, with no names. List the questions you would need answered to make it complete.

[paste notes with names removed]

I am comparing [number] options for [need, such as a vendor, a piece of equipment or a repair]. Here is what I know about each one: [paste quotes and notes with people's names removed].
Build a comparison table with cost, what is included, timeline, risks and open questions.
Then tell me what to ask each one before we decide.
Do not pick one. I will take this to my leader.
Do not invent prices or terms that are not in my notes.

Turn these meeting notes into:
1. A two-sentence summary
2. Decisions made
3. Action items, each with an owner and a due date
4. Open questions
Do not invent owners or dates. If an action item has no owner, list it under "Who's owning that?"

[paste notes]

Leaders

Staff HR matters never go into AI. The coaching prompt below is for everyday feedback, described in general terms.

Here is my M.A.P.S. draft for [ministry or campus] for next year. Act as a wise, skeptical advisor who wants this plan to work.
Tell me the three weakest assumptions, the limiting factor most likely to stall it, what could go wrong in the first 90 days and what evidence would change my mind.
Ask me questions before you answer.

[paste plan with names removed]

I need to give feedback to a team member about [situation in general terms]. I will not share the person's name or anything that identifies them.
Help me plan a conversation that is direct and kind: an opening, two specific things to say, questions to ask and what a good outcome looks like.
Remind me to have it in private and to go directly to the person.

Our team saves about [hours] hours a month using AI. We want to use the time we save on people.
List realistic ways to spend it on people and ministry: time with serve staff, follow-up with guests, developing leaders, care, prayer and rest.
For each one, say what we would do differently next month and what we would watch to know it made a difference.
Do not suggest cutting roles or budget.

Make your own

The best prompts start as a real task. Do the task once with Claude, and when the result is right, ask it to build a skill from the work you did. After that the skill does the setup for you. Never type the same prompt twice.

What goes in the shared project

Rule for everything you load: no information about real people. That means no names, no contact details, no prayer requests, no care notes, no giving records and nothing about a child or student. Load how Eleven22 works. Leave every person's story out.

How to set it up

1. In the church's approved AI account, create a new Project named "Eleven22 Shared Context."
2. Paste the project instructions below into the instructions field.
3. Upload the documents from the table above.
4. Test it. Ask: "Write a short email inviting a first-time guest to come back next weekend." Read the result. Does it sound like us? If it does not, add an example and try again.
5. Share the project with the staff. Ask people to start their email and message drafts inside it.
6. Review it every month. Remove anything out of date.

Starter project instructions

Copy this into the project instructions. Edit it with the communication team. These are starter rules, and church policy comes first.

You are a writing and planning assistant for paid staff at The Church of Eleven22, a multi-campus church based in Jacksonville, Florida. The short name is Eleven22.

Who we are:
- Vision: A movement for all people to discover and deepen a relationship with Jesus Christ.
- Mission: We glorify God by surrendering to Jesus, making disciple-making disciples and transforming communities.
- Core values:
  - Biblical Integrity: knowing right and wrong according to God's Word.
  - Spirit-led Courage: the willingness and ability to do what's right.
  - Christ-like Character: a lifetime of integrity and courage.
  - Sacrificial Love: love God and love people.

How we sound:
- Real, warm and direct. Authentic over polished. Clear over clever.
- Short sentences and plain words. If a neighbor who has never been to church would not understand a phrase, rewrite it.
- A family tone that is generous and full of hope.
- Point to Jesus more than to programs.
- To guests and people new to church: warm and plain, with no insider words.
  You can belong here before you believe.
- To serve staff and staff teammates: direct, grateful and specific about what, when and where.

Words:
- Say "serve staff," "campus" and "campuses," "disciple group," "wins" and "#onemore"
  (the person you are praying for).
- Do not use: "volunteers," "locations," "committee." Never suggest forming a committee.
- With guests, do not use church words they would have to look up.

Style rules:
- No oxford comma.
- Write out numbers under 10, unless it is a range, a time or a hyphenated term like "15-minute."
- Times: 5-9pm, 10am. Dates: October 12, never October 12th.
- "email" and "log in to."
- Lowercase: gospel, biblical, godly, campus, pastor (unless with a name), disciple group, serve staff, worship center.
- Capitalize: Scripture, Bible, the Word and pronouns for God (He, Him, His).
- Ministry descriptors are lowercase: "Eleven22 student ministry."
- "Jesus's" takes an apostrophe s.
- #onemore is lowercase.
- Do not use em dashes.

Rules that never bend:
- Everything you write is a draft. A person checks it and sends it.
- Scripture: give the reference only. Do not quote verse text from memory. A person will check every reference in the English Standard Version (ESV) and add the words.
- Never invent a name, date, time, place, number, quote or testimony. If you do not have it, say so and ask.
- External communication goes to the communication team for review before it is published. That includes announcements, posts and any email to a large list.
  Remind me when a draft needs that review. All video goes through the film team.
- A note to someone who is grieving, in crisis, confessing or asking for prayer is written by a person. Do not draft it. You may help me think about what to say, with no names and no details.
- Never ask for, or repeat back, prayer requests, care or counseling notes, giving records, medical details or anything about a child or student. If I paste something like that, tell me to stop and remove it.

Before you write, ask me any questions you need: who is reading, which ministry or campus, what the situation is, what we want them to do next and by when.

After you write, list every Scripture reference, name, date, time and fact in the draft that a person must check.

Our values, in your writing

Every draft should pass the same four tests.

Words we use, words we do not

Most of the right-hand column is church jargon. If an unchurched neighbor would not understand a phrase, pick the plain one.

Two voices to keep straight

To guests and people new to church: warm and plain, with no insider words. The reader may never have been to church and may not know what a disciple group is. Tell them what to expect, where to go and who will meet them. "You can belong here before you believe."

To serve staff and staff teammates: direct, grateful and specific about what, when and where. They give their time, so put the ask in the first two sentences. Thank them for something specific and name the win when there is one.

Sample rewrites

Keep the sources honest

The voice above comes from the Eleven22 Culture Guide and the brand and style guide. The communication team owns it. If a rule changes, change it in the project first, then tell the staff.

The routine: Draft, Check, Send

1. Draft (two minutes)

Work inside the "Eleven22 Shared Context" project (file 02) or with the Staff Email Writer skill (folder eleven22-staff-email-writer). Give Claude five things:

1. Who is reading: a first-time guest, a serve staff member, a parent or a member.
2. Which ministry or campus.
3. The situation in your own words, with names removed.
4. What you want them to do next, and by when.
5. The tone if it is unusual: extra warm, extra direct, first contact or hard news.

Say: "Ask me any questions you need before you write."

If the message is about a child or student, give Claude the event details only. Nothing about the child goes in.

2. Check (1 to 2 minutes)

Before it goes anywhere, run this list.

• Names and details are right, and nobody else's details slipped in.
• Every date, time, campus and room is correct.
• Every Scripture reference was checked in the ESV.
• Nothing promises what we cannot deliver.
• It says what happens next.
• It sounds like us when you read it out loud.
• No insider church words for someone new.
• It would honor the person reading it.
• It has the communication team's review if it needs one. Anything sent to a large list does.

3. Send (30 seconds)

Put your name on it. Send it from your own account. Add the names and details Claude never saw.

When not to use AI

A note to someone who is grieving, in crisis, confessing or asking for prayer is written by you. We Live Authenticity, and a person who is hurting should get your own words. Prayer requests and care notes never go into AI.

AI can help you think about what to say before you write, as long as you give it no names and no details. The care and pastoral prompts in file 01 show how.

Ten chatbot phrases to delete

If you see these, rewrite the sentence.

• "I hope this email finds you well"
• "I am thrilled to share"
• "I wanted to take a moment to reach out"
• "Please do not hesitate to reach out"
• "Rest assured"
• "We are working tirelessly"
• "Exciting things are happening"
• "We are blessed to announce"
• "Join us for a time of fellowship"
• Any sentence that sounds like a press release

Example replies

These show the shape and the voice. Fill in the [brackets] with the real details. Check each one before you send.

First-time guest follow-up

Serve staff schedule ask

Event change for parents

Hard news: an event is canceled

Missing form for camp

Track it

To see the change, record two numbers for two weeks before you start and two weeks after:

• Time to first draft: minutes from sitting down to write to a draft ready to check.
• Time to reply: hours from the person's message to your reply.

Use the Time-saved tracker in time-saved-tracker.xlsx.

Where this goes next

When a kind of message keeps coming back, turn it into a skill so you never type the same prompt twice. The five starter skills cover the common ones: Staff Email Writer, Serve Staff Message, Meeting Recap, Announcement Drafter and Style and Scripture Check.

The routine stays the same whatever does the drafting: draft, check and send. Then use the time you save on people.

The traffic light

A simple habit: swap names for labels

Before you paste anything, replace real details with labels.

Claude can do nearly everything with labels. You add the real details back when you send.

If you made a mistake

• Tell your leader and the IT team right away.
• Say what you pasted and where.
• Nobody gets in trouble for reporting quickly. The problem gets bigger when it stays quiet.

We Are Family and We Choose to Trust both mean you can say it out loud and expect help.

Accuracy: trust, then check

AI is right often and wrong sometimes, and it sounds the same both times. What you get out depends on what you put in. Here is how to turn checking into a habit.

Four checks before anything leaves

1. Check the Scripture. Open the ESV and read the verse. AI misquotes verses and invents references with confidence. Never paste AI's wording of a verse as a quotation. Copy the words from the ESV yourself.
2. Check the facts. Names, dates, times, campuses, rooms and costs. Match each one to Rock, Planning Center or the event plan.
3. Check the promises. Nothing commits a pastor, a team or the church to something nobody agreed to. Trustworthy people do what they say and do not over-promise.
4. Read it out loud. Does it sound like us? Would you say it to this person face to face?

Anything going outside the church still goes to the communication team for review before it is published.

Convincing is not the same as correct

AI writes confident, polished text even when it is wrong. A draft can look finished and still carry the wrong service time or a verse that does not say what the draft claims. So:

• Ask Claude to check itself: "List every Scripture reference, name, date, time and fact in your answer that I should verify."
• Test with something you already know. Give it notes from a meeting you attended and see whether the recap matches what happened.
• Test the edges. Ask about something that is missing from what you gave it and see if it says so.
• Keep a person in the loop before anything reaches a guest, a parent, a serve staff member or a member, and before anything changes a record.

Red flags in AI output

• A verse reference you did not give it
• A quote from a pastor or an author
• A statistic with no source
• A story or testimony that "sounds right"
• A date or service time you did not give it

When you see one, ask Claude: "Where did that come from? Show me the source or say you are not sure."

AI must never invent a testimony, a quote or a story. Biblical Integrity and We Live Authenticity both apply here. What we say about God's Word and about people's lives has to be true. If a draft needs a story, use a real one and ask the person first.

For tools that touch people's information

If you are building or asking for a tool that will hold people's information, it needs more than a good prompt.

• A named owner. "Who's owning that?" needs a real answer.
• A label for the information it touches
• Access limited to the people who need it
• Approval from the IT team
• Testing before anyone depends on it, including the odd cases

Fast experiments with nothing about a real person can move quickly. Anything that touches people's information goes through the front door in file 05.

Quick questions

Can I use ChatGPT, Grok or Copilot? For work with nothing about a real person, follow church policy on approved tools. For anything about real people, use only the church's approved account. Ask your leader if you are not sure which tools are approved.

Can I dictate with a voice tool? The same rules apply to what you say. Ask the IT team before you install a dictation tool.

Can I upload a list from Rock or Planning Center? Only what the task needs, and only in the approved account. A short list, such as the names and roles on one serve team, is fine. Never upload full profiles, contact details, bulk lists or any list of children, students or giving. If you are unsure, ask your leader first.

Can AI write my teaching or devotional? Teaching comes out of prayer, study and the Holy Spirit's leading. This kit is for the work around ministry: the emails, recaps, schedules and plans. Talk with your leader about your own preparation.

What if someone asks whether we use AI? Tell the truth. Staff use AI to help with drafts and planning, and a person reads and sends everything.

The four forms

Rule of thumb: if you are the only one using it, a session or a skill is enough.

Five questions

1. Do I do this more than once a month? If no, use a session.
2. Do I do it the same way each time? If yes, make a skill.
3. Does it need to read from or write to Rock, Planning Center or Basecamp? If yes, look at a plugin or a connection.
4. Will many people use it, or does it hold people's information? If yes, it may need to be an app, and it goes through the front door.
5. Can I run it by hand first? If yes, do that first. See "Skinny first."

How to make a skill (no coding)

Take a weekend debrief as the example. You write one after every weekend, in the same shape each time.

1. Do the task with Claude until the result is what you would send. For the debrief, that means wins first, then what to fix, then who is owning each fix.
2. Say: "Based on all the work we just did, build a skill so we never have to do this again."
3. Read what it wrote. Fix anything that is off.
4. Save it to your account. In the church's approved account, share it with your team.
5. Use it for a week and improve it each time it misses.

The five starter skills in this kit are ready to upload: Staff Email Writer, Serve Staff Message, Meeting Recap, Announcement Drafter and Style and Scripture Check. In Claude, look for Settings and then the Skills area. Menu names change, so ask Claude to walk you through it if you cannot find it. Each skill is a folder with one SKILL.md file.

Skinny first

For anything bigger than a skill, build the skinny version first. Automations often fail because they were built before anyone learned the process by hand.

• Run it by hand until it works and you understand each step.
• Use a spreadsheet, a shared folder or a simple checklist before you ask for a system.
• Add the connection or automation after the manual version proves the idea.

A camp forms tracker is a good example. Run it in a spreadsheet for one camp season. You will learn which forms come in late, who follows up and what parents ask. Then you will know what a tool would need to do. The spreadsheet stays in the church's own systems, and nothing about a child goes into AI.

An event plan works the same way. Plan one event with Claude in a single session. If the second and third events follow the same steps, you have a skill.

The front door

1. Step 1

   Ask

   Bring the idea to your leader. Say the problem, who it helps and what information it touches.

2. Step 2

   Own it

   Who's owning that? Every tool gets a named owner and a label for the information it touches.

3. Step 3

   Build

   The IT team says yes before anything connects to Rock, Planning Center or Basecamp.

Any tool that touches people's information or connects to Rock, Planning Center or Basecamp needs a named owner and a yes from the IT team before anyone builds. A quick experiment with nothing about a real person can move fast.

Not sure whether to ask? If the tool would touch people's information, or if more than one person will use it, ask.

Which model to use

This guide changes as models change.

Pick one default and stop thinking about it. If you are unsure, use Sonnet.

Talk instead of typing

Most people speak faster than they type. A dictation tool types what you say into any window. Ask the IT team before you install one. The information rules in file 04 apply to what you say as much as to what you type.

Sort your week before you speed it up

Before you automate a task, sort it. This is called DADS. Start with Delete, because many tasks people try to automate did not need to exist.

Where the time goes

Time saved is for people. Spend it there before it fills up with more tasks.

We Are Family says rhythms rule: work hard, play hard, rest well. An hour back can serve any of those. We say, "Ministry is not something you do to people, it's something you do with people." AI can take some of the work that keeps you at a desk, so you can be with people more.

Write down what you would do with an hour back. Some ideas:

• A conversation with a serve staff member
• A guest follow-up you keep putting off
• Prayer, including for your #onemore
• Going home on time

Tell your leader what you wrote. It helps them see where the time is going.

The 15-minute sit-down

Before you start

• Ask the person: "What is one task you did this week that felt slow or repetitive?"
• Pick a task with nothing about a real person in it. Good picks are a huddle agenda, a serve staff training outline, an event checklist or a first draft of a sign-up page.
• Both of you log in to the church's approved AI account.

Minutes 0 to 3: Frame it

Say: "We are going to try one thing on a real task. If it does not help, we stop."

Minutes 3 to 8: Do the task with Claude

• Have the person describe the task in their own words. Speak it if that is easier.
• Have them give Claude the goal along with the task.
• Add: "Ask me questions until we have a good plan."
• Let Claude ask. Let the person answer.

Minutes 8 to 12: Improve it

• Ask the person what is off. Say "push back on it" and let them ask for a second version.
• Ask: "How much of that can you do for me?" and watch what happens.
• If a name, date or Scripture reference shows up, check it together before you move on.

Minutes 12 to 15: Save it

• Ask Claude: "Based on all the work we just did, build a skill so we never have to do this again."
• Read the skill together. Fix one thing.
• Have the person say what they will use it for next week.

After the sit-down

• Ask them to teach one other person in the next two weeks.
• Ask them to log the minutes saved in the Time-saved tracker.
• Share the win at your next huddle.

Coaching moves that work

The 60-minute laptops-open session

Do this with a team of up to 12. It could run in place of a team huddle. Everyone has a laptop and the church's approved AI account. This is a working session, so people spend most of the hour on their own screens.

Room tips

• Keep the group to 12 or fewer for each person leading.
• Have one champion for every four people.
• Do not demo for more than five minutes at a time.
• Tell the room to use tasks with nothing about a real person in them.
• Screenshots and short guides beat long documents. If you make a guide, make it one page of screenshots.

Follow-up that makes it stick

• Week 1: Ask each person how they used Claude. Give each person two minutes.
• Week 2: Ask each person to show one skill or prompt they use.
• Week 4: Ask each person how many minutes they saved. Use the Time-saved tracker.
• Every month: Ask the team what to add to the Eleven22 Shared Context project (file 02).

When to say "let's get help"

Help yourself before you get help, but do not spin your wheels for too long. If you and the person are stuck, ask a champion (file 07). Use the front door (file 05) if the idea needs people's information or involves more than a few people. Use it too if the idea connects to Rock, Planning Center or Basecamp.

What to watch for

• Overconfidence. Someone trusts the output without checking. Walk them through the checks in file 04. Start with Scripture, names and dates.
• Underuse. Someone tried it once and stopped. Pick a task they dread and start there.
• Data slips. Someone pasted a person's information in the wrong place. Coach, do not scold. Correct privately. Church policy comes first, so tell the IT team what happened and follow their lead.
• Quiet fear. Someone worries AI replaces them. Say plainly that AI does the middle work and that relationships, discernment, prayer and care stay with people.
• Overwork. Someone uses saved time to take on more and more. Rhythms rule: work hard, play hard, rest well. Ask how they are doing, and help them spend that time on people and on rest.

Your job

• Show teammates one thing at a time.
• Turn your own repeat work into skills and share them.
• Spot ideas that should go through the front door (file 05).
• Keep the Eleven22 Shared Context project (file 02) useful.

Your role is to show what works and then let people run with it. You do not have to fix every AI problem on the team.

Run a 10-minute demo

1. 1 min

   The pain

   "This task used to take me..."

2. 5 min

   The live run

   Do it on screen with no real person's details.

3. 2 min

   The result

   Show the output and what you fixed.

4. 2 min

   The skill

   Save it and hand it to the team.

Pick one workflow from your own week. Keep it small. Follow this shape.

1. The pain (one minute). "This task used to take me [time]."
2. The live run (five minutes). Do it on the screen with a real task that has no personal information in it. Say out loud what you tell Claude and why.
3. The result (two minutes). Show the output. Show what you had to fix.
4. The skill (two minutes). Show how you saved it. Give the team the skill.

Rules:

• Use a real task from your job. People remember real work.
• Show the mistakes. People trust a demo that shows the fix.
• Never show real people's information on screen. Use labels or a made-up example.
• If the output includes Scripture, open the ESV and check it in front of the room.

Demo ideas by team

Peer coaching in 15 minutes

Use the sit-down script in file 06. Your job is to ask questions.

• "What are you trying to end up with?"
• "What did you tell Claude?"
• "What is off about that?"
• "What would you say to a new teammate to help them do this?"

Answer your own questions last.

Building skills the team will use

A good shared skill:

• Solves one job.
• Asks for the missing information before it starts.
• Names the rules to follow (the Eleven22 voice, the style rules, no invented facts, Scripture as references only).
• Ends with a short checklist for the person to run.
• Was tested on three real tasks.

Give each skill a clear name and a one-line description. Then ask "Who's owning that?" and write the name down. Post the skill where the team can find it. The five starter skills in this kit are good models to copy.

What to log

Each month, record:

• Minutes saved on your top three tasks (the Time-saved tracker).
• Skills you built or improved.
• Ideas you sent to the front door.
• Questions people keep asking. Those belong in the Eleven22 Shared Context project.

When to send someone elsewhere

Help yourself first, then ask

You will get asked things you do not know. That is fine. Try it yourself first. Ask Claude. If you are still stuck after a short time, ask another champion or bring it to the group. Do not spin your wheels.

Keep the bar honest

We Choose to Trust asks each of us to be trustworthy: do what you say, do not over-promise and tell the truth. That applies to how you talk about AI. Do not oversell it. If a skill saves 10 minutes, say 10 minutes. If a demo failed, say why. If Claude got a verse or a date wrong, show the room how you caught it.

Words you will hear

FAQ

Two lines to remember

Never type the same prompt twice.

Use the time you save on people.