Church HR, Staffing & Child Safety

Job Descriptions for Church Roles: Why They Matter

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

Short answer: a church job description isn't an administrative nicety. It's the primary written record of what a person actually does, and that record is what worker classification, ministerial status, accommodation obligations and every difficult termination conversation get decided against. Write it around duties actually performed rather than titles, keep it current, and have the employee sign it.

Nobody writes a job description because it's urgent. They write one when a role is being filled, and then it sits in a folder while the job changes around it.

The problem shows up years later, always at the worst moment. An employee is being let go and there's no written standard to point to. A worker classification is questioned and there's no description of the actual duties. A role's status is challenged and the only evidence of what the person did is what everyone remembers. It's the same document doing all that work, which is why it belongs early in the hiring sequence rather than after the fact.

The description is the contemporaneous record. It's worth twenty minutes a year.

Duties decide things, not titles

This is the sentence to take away, because it recurs in every area below.

Churches assign titles generously and precisely. "Pastor of Worship", "Director of Family Life", "Executive Minister of Operations". The titles mean whatever your church decided they mean.

The legal and tax questions that attach to a role are decided almost entirely by what the person actually does. A title with no matching duties isn't evidence of anything, and a title that overstates a role can actively create difficulty. So can one that understates it.

The job description, kept current and signed, is where the duties get written down while nobody is in dispute about them.

Where the description does real work

1. Employee or independent contractor

Whether a worker is an employee or a contractor turns on the substance of the relationship: behavioral control, financial control, and the nature of the relationship as a whole (IRS, Independent contractor or employee). A detailed job description setting hours, supervision, methods and expectations is strong evidence of an employment relationship.

That cuts both ways, and churches should notice it. Writing a full job description for someone you're treating as a contractor, complete with a schedule and a reporting line, is producing evidence against your own classification. If a worship leader has a job description, a supervisor and set hours, calling them a contractor is a decision that won't survive contact with scrutiny.

2. Exempt or non-exempt

Whether an employee must be paid overtime turns on the duties actually performed, together with how they're paid. Not on the job title, and not on whether the church calls them salaried.

An administrator titled "Office Director" who spends the week on reception, filing and data entry is very likely non-exempt whatever the title says. A job description listing real duties is how a church works this out honestly. One listing aspirational duties is how a church gets it wrong sincerely.

This is genuinely technical and the tests are fact-specific. Use the description to establish the facts, then have someone qualified apply the test.

3. Ministerial status

Some employment claims are treated differently when the employee's role is ministerial, on the basis that a religious organization must be free to choose who carries out its religious functions.

Whether a particular role qualifies has been assessed by looking at what the person actually does, meaning whether they teach the faith, lead worship, provide spiritual formation, or convey the church's message. The label attached to them matters less. Ordination and title count for something, but they aren't the whole analysis, and the boundaries of a religious organization's latitude are narrower than most boards assume (EEOC, Religious discrimination).

The practical consequence for a church is straightforward: if a role genuinely carries religious duties, write them down. A youth director whose job description reads "coordinate events, manage calendar, order supplies" has no written record of teaching, discipleship or spiritual leadership, even if that's most of what the job is.

Don't overstate it either. Adding religious duties to an administrative role that doesn't perform them isn't a strategy; it's a document that will be compared to reality.

4. Minister for tax purposes

Separately from the employment question, whether someone is treated as a minister for federal tax purposes affects payroll treatment and eligibility for a housing allowance (IRS, Ministers' Compensation & Housing Allowance). That determination looks at function: the duties performed, together with ordination, licensing or commissioning and the role the person holds in the congregation.

Again, the job description is the evidence of function. And a reminder that belongs in every sentence on this subject: a housing allowance only covers compensation earned after the church designates it, in advance, by board action. It's never retroactive. The description supports the *who*; the board's advance designation handles the *when*.

5. Accommodation and essential functions

When an employee requests an accommodation, the analysis starts with the essential functions of the job. A description that separates essential duties from marginal ones gives both sides something concrete to work with.

Without it, everything is essential or nothing is, and the church is arguing from memory.

6. Performance management and termination

The most common use, and the one churches feel most.

You can't fairly hold someone to a standard that was never written down. A description with clear responsibilities and a stated reporting line lets a supervisor address a problem early, in writing, against something specific.

By the time a termination is being considered, the file either shows a standard and a pattern or it shows nothing. And once a dispute is genuinely live, whether that's a threatened claim, a lawyer's letter, or an allegation of discrimination or retaliation, stop working from templates and get a licensed attorney involved. Terminating a church employee is one of the few areas where the cost of advice is obviously smaller than the cost of getting it wrong.

7. Insurance and governance

Employment practices coverage, D&O, and any denominational or insurer requirements frequently assume documented roles and reporting lines. And a board that has approved the staffing structure in writing is doing its governance job rather than ratifying whatever emerged.

What a church job description should contain

Ten elements. Two pages at most.

1. Job title, and the ministry or department.
2. Reports to: a role, not a person's name.
3. Status: full or part time, exempt or non-exempt, employee or contractor. State it explicitly; an unstated classification is a decision nobody made.
4. Purpose: two or three sentences on why the role exists.
5. Essential duties, in order of time spent. Use verbs. If the role carries religious functions such as teaching, leading worship, pastoral care, discipleship or representing the church spiritually, write those first and write them plainly.
6. Marginal duties, separately labeled.
7. Qualifications: education, experience, credentials, licenses, ordination or commissioning where genuinely required.
8. Faith and conduct expectations, where your church holds them. Be specific about what is required and why it relates to the role.
9. Working conditions: hours, evenings and weekends, travel, physical requirements, and any screening requirement for roles with access to minors.
10. Signature and date, from both the employee and the supervisor, with a line saying the description will be reviewed annually and may be updated.

That last line does more work than people expect. It sets the expectation that the document is live.

How churches get this wrong

No description at all for long-serving staff. The people who've been there longest usually have the least documentation, and they're the hardest to manage without it.

Copying a corporate template. A generic administrator description misses everything distinctive about a church role, most importantly the religious functions.

Leaving religious duties out. The single most consequential omission in church job descriptions. A role that teaches the faith should say so.

Adding religious duties that aren't performed. Equally damaging, and easier to disprove.

"Other duties as assigned" doing all the work. A useful catch-all at the end of a real list. Not a substitute for one.

Titles that outrun the job. Generous titles are cheap to give and expensive to explain later, particularly around classification.

Never updating it. Roles drift. A description five years out of date is evidence of what the job used to be, which may be worse than no evidence at all.

Writing it after the hire. It belongs at the start, because it's what the posting, the interview and the offer letter are all built from.

No signature. An unsigned description is a draft, and it's the first thing anyone will point out.

A worked example

A church employs a part-time "Youth Director" at 20 hours a week, paid a flat salary, with no written description.

What she actually does in a normal week: teaches Wednesday youth group and prepares the teaching, leads a Sunday small group, meets students and parents for pastoral conversations, plans and leads the summer trip, orders supplies, manages the ministry calendar, and posts to the ministry's social accounts.

Three problems in one role, all invisible until they aren't.

Classification. Flat salary plus 20 hours plus an administrative core raises a genuine question about whether she's exempt. Duties answer that question, and there's no record of them.

Ministerial status. Roughly two thirds of the week is teaching, discipleship and pastoral care. None of it is written anywhere. If the role's status ever matters, the church is relying on recollection.

Managing the job. Nobody has agreed what the priorities are, so the calendar and the social accounts expand to fill the week and the teaching preparation gets squeezed. Nobody can address that fairly, because no standard exists.

The fix is one page, written this month, listing the teaching and pastoral duties first and the administration second, with hours attached, signed by both sides, and reviewed each year at the same time as the compensation decision.

Nothing else about the job changes. Everything about the church's position does.

What to do about it

1. List every paid role, including part-time and seasonal.
2. Write or refresh a description for each, starting with the roles that carry religious duties and the roles you are least sure how to classify.
3. Build it from the actual week, not from what the job was supposed to be. Ask the person to log a fortnight if you're unsure.
4. State the classification explicitly and get advice on any you aren't confident about.
5. Have both parties sign and date it.
6. Review annually, alongside the compensation and budget cycle, and update after any real change in duties.
7. Get the board to approve the staffing structure, and minute it.

Common questions

Do we need job descriptions for volunteers?

A short role description is useful, and it should look different from an employee's. Keep required hours, performance standards and disciplinary language out of it. A volunteer document that reads like an employment contract with no pay attached invites the wrong question. The conduct side belongs in the volunteer agreement and code of conduct instead.

Does a job description make someone an employee?

No, but it's evidence. A detailed description with schedules, supervision and methods points strongly toward employment. If you've written one for a worker you treat as a contractor, look again at the classification rather than at the document. Where a case is genuinely unclear, the IRS will make the determination on request (IRS, About Form SS-8).

Should the pastor have one?

Yes, and it's the one most often missing. It changes the relationship with the board from impressions to expectations, and it makes reviews and compensation decisions possible. Writing a pastor job description covers what makes that one different.

Can we include faith and lifestyle expectations?

Churches commonly do, and there's real latitude for religious organizations here. Its scope is fact-specific, though, and it depends heavily on the role. State the expectation clearly and connect it to the duties. If your standards go beyond doctrine into conduct or lifestyle, have a licensed attorney review the wording before you adopt it.

How often should we update them?

Annually as a fixed item, and immediately after any real change in duties, reporting line or classification. Ten minutes a role, once a year.

What if an employee disagrees with the description?

That's the document working. Talk it through, and if their account of the week differs from yours, one of you is wrong about what the job is. Better to discover that now than during a termination.

Write down what people actually do

That's the whole discipline. Not aspiration, not titles, not the version that sounds best in a newsletter. The real week, on two pages, signed and dated.

Every hard employment question a church faces starts with the same request: show me what this person did. A church that can answer that in writing is in a completely different position from one that can't.

---

Start from descriptions written for ministry roles. The Church Job-Description Library is a set of ready-to-edit descriptions for real church roles, pastoral through worship, operations and admin, plus the blank template to build the ones you don't find. $69, instant download. The rest of the HR and hiring set is on the Run My Church hub.

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