Church HR, Staffing & Child Safety

Volunteer Agreements and Codes of Conduct

Published 2026-08-16 · Church HR, Staffing & Child Safety

Short answer: the code of conduct describes the behavior expected of anyone serving; the volunteer agreement is the short signed document in which a person accepts it. Write the code as observable behaviors rather than values, keep it to two pages, have every volunteer sign it annually, and be careful the agreement doesn't read like an employment contract.

A youth leader has been messaging a fifteen-year-old privately for two months. Nothing in the messages is improper. A parent sees the thread and asks the pastor why an adult is texting her daughter at eleven at night.

The pastor has no rule to point to. The leader hasn't done anything the church ever told him not to do. Now a reasonable conversation becomes an argument about whether anything was actually wrong, and there's no standard either of them can appeal to.

That's what a code of conduct prevents. Not misconduct: no document stops misconduct. It prevents a church having to invent a rule in the middle of a disagreement. A volunteer code of conduct church leaders adopted last year, sitting under the child safety policy, gives everyone something to point at.

The difference between the two documents

They get used interchangeably, and they do different work.

The code of conduct is the standard. It describes how people serving in your church behave: supervision, contact, communication, boundaries, transport, and what to do when something concerns them. It's written once, adopted by the board, reviewed annually, and applies to everyone.

The volunteer agreement is the signature page. It's short, usually one page, and it records that a named person, on a stated date, received the code, read it, and agreed to serve under it. It also sets out the practical terms of the role: what they're being asked to do, that the position is unpaid, that either side can end it at any time, and what happens with expenses.

A code with no signed agreement is a suggestion. An agreement with no code attached is a signature on nothing.

Write behaviors, not values

The most common failure is a code that reads beautifully and directs nobody.

"Volunteers will conduct themselves with integrity and treat all children with respect" is true, and it changes no behavior, and it settles no dispute. Here's the test to apply to every line:

Could a new volunteer follow this on their first Sunday without asking anyone what it means?

Compare:

The right-hand column can be followed, observed, and noticed when it fails. The left cannot.

The sections a code should contain

1. Who it applies to. Everyone with access to minors or vulnerable adults: staff, volunteers, board members in ministry roles, contractors, drivers, short-term helpers.

2. Supervision. Two approved adults present whenever children are in a room. Visibility into every space. Ratios by age group. The rule for restrooms. The rule for the last child at pickup.

3. One-to-one contact. When it's permitted at all, and under what conditions: in sight of others, door open, another adult informed. This is the section that saves the most difficulty later.

4. Communication and digital contact. Specify the platforms. No private one-to-one messages with a minor. Group threads or a parent copied. State the hours. Say what happens to a private message a student sends anyway: the leader copies a second adult in and responds in the open.

5. Physical contact. Concrete, and written as guidance for good people, because that is who is reading it. Most volunteers want to know exactly where the line is so they can stay well inside it.

6. Transport. Never one adult and one minor alone in a vehicle. Parent permission. License and insurance requirements for drivers. What happens on the last drop-off of the evening, which is where this rule usually breaks.

7. Gifts, favoritism and social contact outside church. Including babysitting, social media following, and one-to-one meetings arranged privately with a student.

8. Substances and conduct. No alcohol or impairment while serving with minors. Any additional standards your church holds, stated plainly rather than implied.

9. Reporting. Who receives concerns, by when, on what form, and a second route for concerns about that person. State that a volunteer who's unsure should report anyway, that it isn't their job to decide whether a concern is founded, and that nobody is penalized for a good-faith report.

10. Consequences. What happens if the code isn't followed, and who decides. Keep it short and don't promise a process you won't run.

What the agreement should say, and what it should not

Keep the agreement itself to a page: the role, the ministry area, the start date, the acknowledgements, the signature and the date.

Include, plainly:

• That the position is voluntary and unpaid, and that the volunteer is not an employee.
• That there is no expectation of compensation for the service given.
• That either the volunteer or the church may end the arrangement at any time.
• That any reimbursement is for actual, documented expenses only, under the church's reimbursement policy (IRC §62, accountable plans).
• Consent to the church's screening process and to the retention of those records.

Be careful with that expense line. Paying a volunteer a flat stipend, a gift card, or a round monthly amount that isn't tied to receipts changes the character of the relationship, and it becomes a payroll and tax question rather than a hospitality one (IRS, Independent contractor or employee). Reimbursement that runs on receipts and a written policy sits in different territory (IRS Publication 463). The distinction is worked through in whether a volunteer can be reimbursed without becoming an employee.

Avoid, deliberately:

• Language borrowed from employment contracts. Required hours, disciplinary procedures, notice periods, performance reviews, benefits. A volunteer agreement that reads like a job description with no pay attached invites exactly the wrong question.
• Promises the church won't keep. An assured placement, a specific role for a specific length of time, a formal appeals process nobody will staff.
• Blanket waivers of liability as a substitute for actually managing risk. Whether such a clause does anything at all varies by jurisdiction, and it isn't a reason to skip supervision, screening or insurance. If liability language matters to your situation, that's a question for a licensed attorney, not a template decision.

How churches get this wrong

One signature, once, at the start. Sign it annually. The renewal is the moment people re-read it, which is the moment it does its work.

Two documents that contradict each other. The code says no private messaging; the youth handbook has the leader's mobile number on it. Read them side by side once a year.

A code nobody was trained on. Signing isn't reading and reading isn't training. The annual session is where the hard cases get worked through.

Nine pages. If a volunteer has to read nine pages to find out whether they can drive a teenager home, the code has failed at the only moment it mattered. Two pages, plus role-specific additions for drivers and trip leaders.

No named recipient for concerns. Name a role, not a person, and publish who currently holds it.

Rules that require a judgment call. "Avoid inappropriate contact" leaves every volunteer to define it privately, which is precisely what a code exists to prevent.

Filing the signed pages nowhere in particular. They belong in the volunteer's file with the application and screening record, access-controlled, and on a stated retention schedule.

What to do about it

1. Adopt the code at board level and minute it. This is a governance decision.
2. Cut it to two pages in language a sixteen-year-old helper can follow.
3. Add role-specific pages for drivers and overnight trip leaders rather than lengthening the main document.
4. Collect signed agreements from everyone in scope, including people who have served for years, on one deadline.
5. Train against it using scenarios, not a reading.
6. Set a renewal month and re-sign annually.
7. Review the code after any incident or near miss, and at least once a year.

Common questions

Does a signed code of conduct protect the church?

It isn't a shield, and anyone selling it as one is overselling. What it does is set a clear standard, make training possible, make correction fair, and show that the church defined its expectations before anything went wrong. That's real, and it isn't the same as immunity.

Should minors serving as helpers sign one?

Yes, in an age-appropriate version, with a parent or guardian co-signing. Student leaders need their own boundaries defined, particularly around younger children, and they're often the least trained group in the building.

Can we require a code of conduct that reflects our church's beliefs?

Churches commonly hold conduct standards grounded in their faith commitments, and there are legal doctrines that give religious organizations latitude here (EEOC, Religious discrimination). The scope of that latitude is genuinely fact-specific and varies with the role and the jurisdiction. If your standards go beyond safeguarding into belief or lifestyle expectations, have a licensed attorney look at the wording before you adopt it. This is one of the few places in volunteer management where a template alone isn't enough.

What if someone breaches the code?

Small breaches: correct it in the moment, in private, and note it. Repeated or serious breaches: remove them from the role and record the decision. Anything involving possible harm to a child isn't a code-of-conduct matter at all. Report it to the authorities your law requires and get legal advice immediately, without an internal enquiry first.

How is this different from the child safety policy?

The policy is the church's governing document: scope, screening, supervision, reporting, records. The code is the volunteer-facing extract, the part that tells a person what to do on Sunday. Same standard, different audience.

Two pages, signed every year

That is the whole ask. A code specific enough to follow, an agreement short enough to sign, and a date in the calendar for doing it again.

The church that has those two documents in every volunteer file isn't protected from everything. It's simply a church where nobody has to invent the rule during the argument.

---

Give volunteers something specific to sign. The Volunteer Application & Screening Packet is the application, the screening authorization and the acknowledgement forms in one set: the paperwork side of onboarding, done the same way for everyone. $39, instant download. The safeguarding policy the code extracts from sits with the rest of the HR documents on the Run My Church hub, and the reference-check script covers the calls.

*Faith Docs provides self-help document templates, not legal advice. We are not a law firm. For representation, consult a licensed attorney.*