10 DAYS AGOΒ β€’Β 8 MIN READΒ β€’Β STAFF & TEAMS

πŸ“ How to Write a Job Description Your Staff Will Actually Use

profile

STREAMLINE YOUR MINISTRY

Helping maximize your time, resources, teams, and budget so you can reach furtherβ€”faster. Less guesswork. More ministry.

🩺 Take the Church Health Audit

Take a few minutes to find out how healthy and aligned your ministry really is. The free Church Health Audit gives you an honest snapshot and clear next steps to get your team in sync.

Go find one of your staff members' job descriptions right now. I'll wait.

If you're like most churches, one of three things just happened. You couldn't find it (or likely never had one to begin with). You found it, and it's three years out of date. Or you found it, read it, and realized it describes a job that only faintly resembles what that person actually does all week.

Here's the uncomfortable truth behind all three: for most churches, the job description is a document you write once, to make a hire, and then never look at again. It gets filed in a folder nobody opens. And the moment that happens, it stops being a leadership tool and becomes paperwork.

That's a waste. Not because job descriptions are sacred, but because a good one is one of the most powerful clarity-creating tools you have. When a staff member knows exactly what their job is, what a win looks like, and how their role connects to where the church is going, everything gets easier β€” evaluations, coaching, delegation, even the hard conversations. When they don't, you spend your leadership energy managing confusion instead of leading people.

So let's fix it. Here's how to write a job description your staff will actually use β€” one that lives on their desk, not in a drawer.


Why Most Church Job Descriptions Die on the Shelf

Before the how, it's worth naming the why. Most church job descriptions fail for the same handful of reasons, and every one of them is fixable.

They're a list of tasks with no purpose. A bulleted dump of duties tells someone what to do but never tells them why it matters or what they're actually responsible for producing. People don't get up early for a task list.

They have no definition of success. If there's no measurable win anywhere in the document, then "doing a good job" is just a matter of opinion β€” usually yours, and usually communicated only when something goes wrong.

They ignore the church's mission entirely. The description could belong to any church, anywhere. Nothing in it connects the role to the specific thing God has called your church to do.

And they never get updated. The role evolves, the church grows, the person's responsibilities shift β€” but the document stays frozen at the moment of hire. Within a year it's fiction.

A job description your staff will actually use solves all four. It's built around purpose, it names success in numbers, it's anchored in your mission, and it's designed to be revisited. Here's how to build one.


Start With Mission, Not Tasks

The biggest mistake I see is job descriptions that open with a task list. Open with identity instead.

Before a staff member reads a single responsibility, they should see the church's mission, vision, strategy, and values right there at the top of their own job description. Why? Because it reframes everything that follows. Their ten responsibilities aren't ten random chores β€” they're ten specific ways this person advances the mission of the church. That framing is the difference between an employee who's checking boxes and a team member who understands they're building something.

This section does something else, too. It quietly reveals whether you have clarity. If you sit down to write "our mission, vision, and values" at the top of a job description and you find yourself hedging, guessing, or writing something generic β€” that's not a job description problem. That's a leadership-alignment problem, and it's worth stopping to solve. (More on that at the end.)

Put the mission first. Every role should be a spoke pointing back to the same hub.


Write a "Heart of the Role" Before You Write Duties

After the mission, before the task list, write two or three paragraphs describing what this role actually exists to do. Not what the person does β€” what the role is for.

I call this the heart of the role. Picture what would be lost if this position disappeared tomorrow. What would go undone? What would the church feel the absence of? That's what you're trying to capture. A Worship Pastor doesn't exist to "plan Sunday setlists." They exist to lead the church into the presence of God through worship, week after week, and to build a team that can do it with excellence and humility. The setlist is a task. The presence of God is the point.

Then boil it down to a single sentence β€” one your staff member could say from memory if you stopped them in the hallway. "My job is to ______." If they can't finish that sentence clearly, the description hasn't done its job yet. If they can, you've given them something a task list never could: a reason.


Give Every Role a Number

Here's the line I come back to over and over with church leaders: a KPI without a number isn't a KPI. It's a wish.

Ministry people flinch at metrics. I understand why β€” we're shepherding souls, not manufacturing widgets, and not everything that matters can be counted. All true. But here's what's also true: every role has real, measurable expectations, whether you've named them or not. When you refuse to name them, you don't remove the expectations. You just leave your staff to guess at them β€” and then evaluate them against a standard you never shared.

So give every role three key performance indicators. Three measurable outcomes that define success. For a Connections Pastor, that might be the percentage of first-time guests who return within 30 days, the number of people who move from attender to member each quarter, and the number of active volunteers on the assimilation team. Real numbers, tracked over time.

You set the targets based on your church's specific goals β€” I can't set them for you, and neither can a template. But name the metric, attach a number, and put it in writing. The moment you do, you've handed your staff member the exact measuring stick they'll use to evaluate their own success. Most people desperately want to know if they're winning. This is how you tell them.


Name the Things That Apply to Everyone

There's a category of expectation that isn't about the specific job at all β€” it's about being part of your staff. Character. Spiritual health. Culture. How you treat teammates. Whether you protect the unity of the team. Whether you actually attend and give to the church you work for.

Put these in every job description, and keep them consistent across the whole team. These aren't job requirements in the technical sense β€” they're the non-negotiables of being part of a church staff family. Naming them plainly does two things. It sets a shared standard so no one wonders whether it applies to them, and it makes the eventual hard conversation possible. You can't hold someone accountable to an expectation you never wrote down.

While you're at it, be honest about the schedule. What does "full-time ministry" actually mean at your church? Which nights? How many Sundays? What's the on-call reality? People deserve to know what they're signing up for before day one, not to discover it in month three and feel like they were misled.


Make It a Living Document (This Is the Whole Point)

Everything above matters. But this is the step that separates a job description your staff uses from one they file away and forget β€” so don't skip it.

A job description is not a hiring artifact. It's a leadership instrument you pick up all year long. Here's what that looks like in practice.

Use it in one-on-ones. When you meet with a staff member, the job description is your agenda. How are the KPIs trending? Where are they thriving in their primary responsibilities? Where do they need help? The document keeps the conversation on what matters instead of drifting to whatever's most urgent that week.

Use it in reviews. A quarterly or annual review should never surprise anyone. If you're both looking at the same document all year β€” same responsibilities, same metrics, same expectations β€” the review becomes a conversation about a shared reality, not a verdict delivered from on high.

Use it when the role changes. When you add a responsibility or shift a priority, update the description that day. A five-minute edit keeps it true. Skip it a few times and you're right back to fiction.

Review it on a rhythm. Once a year, sit down together and ask: Is this still accurate? Has the role grown? Have the numbers changed? Then revise it together. When your staff member helps shape their own description, they own it β€” and people use what they own.

That's the difference. A document you write at someone gets ignored. A document you build with someone, revisit regularly, and lead from all year β€” that's a job description your staff will actually use.


The Bigger Picture

Notice something about everything above: writing a great job description is almost impossible if you haven't first answered the bigger questions. What is our mission? Where are we going? What do we value as a team? What does a win look like for the church as a whole?

If those answers are fuzzy, every job description you write will be fuzzy too β€” because you'll have nothing solid to anchor each role to. That's not a paperwork problem. It's an alignment problem, and it's the most common one I see in churches that feel busy but not aligned.

That's the work of the Ministry Sync Framework β€” the 10-part strategic process that gets your entire leadership team in sync around a plan that's clear, biblical, and executable: Purpose, Mission, Vision, Strategy, Values, Kingdom Mindset, Keystone Ministries, Target Audience, Distinctives, and Annual Calendar. Do that work first, and writing job descriptions becomes almost effortless β€” your mission is already written, your values are already defined, your strategy is already documented. You're just pointing each role back to a hub that already exists.

"Whatever you do, do it from the heart, as something done for the Lord and not for people" (Colossians 3:23, CSB).

Your staff want to do their work from the heart. A clear job description β€” one that names the purpose, the win, and the why β€” is one of the most practical gifts you can give them.


You Don't Have to Start From Scratch

Here's the good news: you don't have to build all of this from a blank page.

​The Staff Job Description Kit gives you 20 fully written, ready-to-customize job descriptions for the most common church staff positions β€” from Lead Pastor to Social Media Coordinator. Every one already follows the exact structure in this post: mission and vision up top, a heart-of-the-role summary, ten clear responsibilities, three KPIs with placeholder targets you set, the strengths that define excellence, team structure, the personal commitments that apply to everyone, and honest schedule expectations. It also includes an implementation guide that walks you through customizing each one, setting real numbers, and using these as the living leadership tools they were meant to be.

​Stop managing vague expectations. Start leading with clarity. Get the Staff Job Description Kit at efficient.church.


Get Our New Book! πŸŽ‰

Ready to get your team in sync? Head to Amazon and get the Kindle version of Ministry Sync Handbook: Ten Decisions That Get Your Church Rowing in the Same Direction. If it helps you at all, please leave a review to help other pastors find this resource. 🌟

Have questions? Hit reply to this email and we'll help out!

600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246
​Unsubscribe Β· Preferences​

STREAMLINE YOUR MINISTRY

Helping maximize your time, resources, teams, and budget so you can reach furtherβ€”faster. Less guesswork. More ministry.