The administrative task list nobody assigned to anybody
Every church over 200 has a list of tasks that got assigned to nobody: renewing the software subscription, updating the staff directory, following up with the guest from three weeks ago. They land on the pastor by default, not by design.
Every church over 200 has a list of tasks that got assigned to nobody: renewing the software subscription, updating the staff directory, following up with the guest from three weeks ago. They land on the pastor by default, not by design.
This is one post in the pastor's capacity problem, and it exists because a conversation like this one keeps happening: a board member asks, offhand, who renews the church management software subscription, and the pastor realizes it has just been him, by accident, for four years. Nobody decided that. It just never landed anywhere else.
What administrative tasks actually fall through the cracks at a growing church?
The pattern below repeats at church after church over 200 attendance. The task is real, somebody assumes it is covered, and somebody else quietly ends up covering it.
| Task | Who assumes it's covered | Who actually does it |
|---|---|---|
| Software subscription renewals | The office, or "IT" | The pastor, when the card declines |
| Staff directory updates | HR, if the church has one | Whoever notices the extension is wrong |
| Guest follow-up past the first week | The follow-up team | Nobody, past week one |
| Vendor contract renewals | The office manager | The pastor, on the renewal notice's ninth day sitting in his inbox |
| Distribution list maintenance | "Whoever set it up" | Nobody, until an email bounces |
| Filing recurring compliance reports | The board treasurer | The pastor, closer to the deadline than anyone would like |
A practical inventory built from common church operations patterns, not a cited survey. Your church's version is the one worth building.
Why does the senior pastor end up doing them?
Each task on that list shares two traits. It is too small on its own to justify a hire, and it is too frequent to treat as a one-time project. A church will not hire someone whose entire job is renewing three software contracts a year. But those three renewals still have to happen three times a year, forever, and somebody has to be the one who notices the reminder email.
That somebody defaults to whoever is paying the closest attention to the whole operation, which is usually the pastor. Not because the org chart says so. Because nobody else is positioned to notice a gap that has no name attached to it anywhere.
How do you find the full list at your own church?
The audit is simple, and it takes exactly one week to run. Track everything that crosses your desk that has no name attached to it in any job description on your staff. Not the sermon. Not the funeral. The other things: the email you forwarded because you did not know whose job it was, the renewal you approved because the notice landed in your inbox, the schedule gap you filled because nobody else saw it open up.
At the end of the week, sort the list by how much judgment each item actually required. Most of it will not require pastoral judgment at all. It will require competence and follow-through, which is a different qualification entirely.
The list is not a complaint
Naming this list is not the same as saying the tasks do not matter. Every item on it is real work that keeps the church running. The problem is not that the work exists. It is that nobody drew a box around it on an org chart, so it landed on the one person who cannot say no to anything.
Who should actually own this list?
Most of it requires competence and trust, not pastoral authority or theological training, which is exactly what makes it delegable. Software renewals do not need a seminary degree. Neither does a directory update or a guest follow-up call. What they need is a named owner and a recurring reminder, which is precisely the structure that never got built the first time around, because the tasks arrived one at a time instead of as a list.
Our companion post on the weekly church office checklist covers the recurring side of this in more detail, week by week rather than task by task. And the reason this list keeps landing on the pastor in the first place, rather than a genuine faith question about who should be trusted with it, is worth reading straight through in the theology and practice of delegation in ministry.
CoLabor Staffing places full-time Christian co-laborers with churches and Christian-owned businesses. A generalist can own this exact list, the renewals, the directory, the follow-up past week one, so it stops defaulting to whoever notices first.
The question
What did you personally do last week that somebody else could have done? Run the one-week audit above before you answer. See what did you personally do last week for the fuller version of the exercise.
Common questions
What administrative tasks fall through the cracks at a church?
Software renewals, directory updates, guest follow-up past the first week, and vendor contract renewals are the most common. See the table above.
Why does the pastor end up doing tasks nobody assigned to him?
Because they are too small individually to justify a hire and too frequent to ignore, they default to whoever notices first.
How do I find the unassigned tasks at my own church?
Track everything that crosses your desk for one week with no name attached to it in any job description, then sort by how much judgment it actually requires.