Quick answer: Volunteers need four rules, not a policy document: draft inside the church workspace, never publish directly, never enter anyone's personal information, and ask a staff member before writing anything sensitive. Put those four sentences in your volunteer handbook, cover them in fifteen minutes at onboarding, and give access inside a workspace that already enforces your church's voice and guardrails.
Volunteers are not staff, and the policy should not pretend otherwise
Your staff can hold nuance. They sit in meetings, they know the pastor's preferences, they have context about which families are going through something.
A volunteer who helps two hours a month has none of that, and expecting them to apply a nine-section AI policy correctly is not realistic or fair. Handing them the staff document usually produces one of two outcomes: they ignore it, or they get nervous and stop helping.
What they need is short, memorable, and hard to misread.
The four-sentence volunteer rule
1. Draft in the church workspace, not in a personal AI account.
2. Never publish anything yourself — a staff member approves everything.
3. Never type anyone's personal information, prayer request, or private situation into any AI tool.
4. If a topic feels sensitive, ask a staff member before you write anything.
That is the whole policy. Print it, put it in the handbook, and say it out loud at onboarding.
Why rule one does the heaviest lifting
"Draft in the church workspace" sounds like a preference. It is actually the rule that makes the other three easier to follow.
When a volunteer works inside a workspace that already carries your mission, values, statement of faith, tone, and AI policy, the output starts inside your boundaries automatically. They do not have to remember your voice — the settings apply it. They do not have to know which topics are off limits — the assistant declines and routes them to a pastor.
A personal chatbot account has none of that. Same person, same good intentions, completely different risk.
What to cover at onboarding
Fifteen minutes, once, when a volunteer joins the comms team.
- The four rules. Read them aloud. Ask if anything is unclear.
- One real example. Walk through drafting a social post for an actual upcoming event.
- Where approval happens. Show them the status changing and who sees it.
- The three things to always check. Dates, names, Scripture references.
- Who to ask. Give them one name and one way to reach that person.
That last item matters more than it looks. Most volunteer mistakes happen because nobody knew who to ask at 8pm on a Saturday.
What volunteers should be allowed to do
Be generous here. Restrictive access wastes willing help.
- Draft social posts, event blurbs, and text reminders.
- Edit and shorten existing approved copy.
- Brainstorm ideas for series names, captions, and recruitment angles.
- Assemble content for their own ministry's events.
- View the calendar and dashboard so they know what is already planned.
That last one is free in ChurchCopy — viewers are unlimited and cost nothing, so every ministry leader and volunteer can see the plan and copy finished content without a seat. Paid seats are for the people who create, comment, and approve.
What volunteers should never do
- Publish or schedule anything without staff approval.
- Write about a death, illness, crisis, or conflict.
- Answer doctrinal questions on the church's behalf.
- Enter member data, prayer requests, or giving information into any tool.
- Use a personal AI account for church work.
The approval habit is the whole system
Everything above depends on one thing actually happening: a staff member reads it before it goes out.
That step fails when it lives in text messages. The volunteer sends a screenshot, the staff member replies "looks good" three hours later, and nobody is sure which version was approved.
Keeping comments and approvals on the copy itself fixes it structurally. The volunteer marks it ready, the staff member sees it in their pending list, the feedback lands on the exact sentence, and there is a record of who approved what. No chasing, no ambiguity.
Handling the volunteer who already uses AI
Some volunteers arrive already fluent, having used AI at work for two years. Do not treat that as a problem to manage.
Tell them plainly: "We love that you know these tools. Here is the one thing that is different at church — everything runs through our workspace so your drafts start with our voice and our boundaries, and a staff member approves before publishing."
Competent volunteers respond well to being trusted with a reason. They respond badly to being handed a restriction with no explanation.
What to do when someone gets it wrong
Someone will. Usually it is small — a post published without approval, or a date that was never checked.
Treat the first instance as a training gap, not a character problem. Ask which of the four rules was unclear. Most of the time the honest answer is that nobody ever told them, or the approval step was too slow to be practical.
Fix the cause. If approvals take two days, volunteers will route around them, and no amount of reminding will change that.
Review it once a year
Ask three questions at your annual review: are the four rules still right, did anything publish without approval, and is the approval step fast enough that people actually use it?
Churches that check those three keep volunteer help productive and safe. Churches that write the rules once and never revisit them usually discover the gap the hard way.
The point of all of it
Volunteers are not a risk to be contained. They are people giving your church their Saturday morning, and they deserve clarity about what is expected so they can help confidently.
Four sentences, fifteen minutes of onboarding, and a workspace that carries your boundaries for them. That is enough to let willing people help without anyone losing sleep.
A onboarding handout you can copy
Print this on one side of a page and give it to every volunteer who touches communications. It takes two minutes to read and covers the situations that actually come up.
Welcome to the comms team. We use AI tools to help draft routine communication. Here is how we use them well.
Always work in the church workspace. It already knows our mission, our values, our tone, and what we do and do not talk about. A personal AI account does not, which is why drafts made elsewhere usually do not sound like us.
Never publish or schedule anything yourself. Mark it ready and a staff member will review it. This protects you as much as it protects the church.
Never type anyone's private information into any tool. No prayer requests, no health situations, no family details, no giving information. Not even to ask for help wording something kindly.
If it feels sensitive, ask first. Anything involving death, illness, crisis, conflict, or a specific person's hard season goes to a staff member before it goes anywhere else.
Always check three things before marking something ready: the date and day of week, every name and title, and every Scripture reference.
Edit rather than regenerate. If a draft is eighty percent right, fix the twenty percent. Starting over usually produces a different eighty percent.
When in doubt, ask [name] at [contact]. There is no wrong question, and asking is always faster than fixing.
That is the entire volunteer training program. Everything else they will learn by doing, which is how volunteers learn best anyway.
Try for free — unlimited free viewers for your whole volunteer team.