Most church admin job descriptions are written once, by committee, and then never read again. They list duties nobody asked for — “manages communications strategy,” “oversees database integrity” — and skip the plain thing the role is actually for: making sure the guest from three weeks ago got a call, the giving got recorded, and the volunteer schedule went out before Thursday.
A job description built from aspiration attracts the wrong person or scares off the right one. A job description built from your actual Monday, Tuesday, and pre-Sunday tasks does something more useful: it tells a volunteer or part-time hire exactly what they are agreeing to, and it tells you, in writing, what is not covered.
Start from the week you already have, not the one you wish for
Before writing anything, spend fifteen minutes with whoever has been doing this work — even informally — and write down what they actually did last week. Not what the bylaws say the role should do. What happened. Most churches find the honest list is shorter and more specific than the aspirational one:
- Entered three first-time guests and assigned each one a follow-up owner.
- Recorded Sunday’s giving and flagged one envelope with no name on it.
- Updated two households whose address changed.
- Reminded a volunteer who was scheduled but had not confirmed.
- Printed the class roster for Sunday school.
That list, not a generic template pulled from another church’s website, is your first draft. If you want a structure for what that week should look like before you write it down, a weekly rhythm that keeps your records current lays out a version of it in about thirty minutes a week.
Separate what the role owns from what it merely touches
A common failure in these descriptions is conflating “does this” with “is responsible for this ever happening again.” An admin who enters giving is not the same as an admin who is accountable for the treasurer’s year-end statements going out correctly. Both matter, but only one belongs on a part-time volunteer’s plate unless you say so explicitly.
Write two columns if it helps: does and owns. A volunteer might do data entry for giving every week but not own the year-end statement process, which might sit with the treasurer instead. Naming this distinction in the description prevents the quiet resentment that builds when someone discovers, in December, that a task they never agreed to has become theirs by default.
The people and follow-up section
This is usually the heart of the role. Write it as tasks, not adjectives:
- Enter new people and update household information as it changes — address, phone, family members.
- Turn each first-time guest into a follow-up step with a named owner and a date, and check weekly for steps nobody has picked up.
- Keep group and serving-team rosters current as people join, leave, or change roles.
If your congregation has more than a handful of guests some Sundays, the follow-up piece alone can eat an hour a week. Be specific about how many guests you expect and how long the admin has to log them — a description that says “follows up with guests” with no timeframe invites the exact drift this role exists to prevent. For a fuller picture of what a guest’s path should look like once it is written down, see guest to member: the path worth writing down.
The giving section, written narrowly
Recording giving is clerical, sensitive, and easy to write badly. Keep this section narrow and explicit about what it does not include:
- Record each week’s contributions against the correct person or household.
- Flag anything unclear — an unlabeled envelope, a name that does not match a record — for the treasurer to resolve.
- Does not decide how funds are spent, and does not have access beyond what the treasurer approves.
That last line matters more than it looks. Giving data is the most sensitive information a small church holds, and a written boundary protects both the admin and the giver. It also heads off the assumption that whoever enters the numbers should also be the one answering questions about them.
The serving and scheduling section
If the role touches volunteer scheduling at all, say exactly how much. “Manages the serving schedule” could mean building it from scratch every week or simply keeping a roster current after someone else builds it. Pick one and write it down. If background checks are part of your process, name who watches for expirations and who acts on them — those two things do not have to be the same person, but the description should say so either way. For a longer look at building a schedule that does not burn out the person running it, see scheduling volunteers without burning out the scheduler.
What to leave off the list on purpose
A short, honest description also states what the role is not. This protects the person in it from scope creep and protects the church from assuming coverage that does not exist. Consider naming explicitly that the role does not:
- Send email or text messages on the church’s behalf — if you use a separate tool for that, name it and its owner separately.
- Take or process payments; giving is recorded, not collected, by this role.
- Decide who can see what data. If everyone with access can see everything, say so, so no one assumes otherwise.
These are not weaknesses to hide. They are boundaries that keep the job description honest, and an honest description is easier to fill and easier to hand off later, because the next person can read it and know exactly where their responsibility starts and ends.
A short template you can copy
Here is a skeleton built from the sections above. Fill in your own numbers — average weekly guests, congregation size, hours available — rather than leaving it generic.
- Title: Church administrator (volunteer or part-time, X hours/week)
- People: enter new households, update changed information, keep group rosters current
- Follow-up: assign an owner and date to every first-time guest within 48 hours, review the board weekly for anything unaddressed
- Giving: record each week’s contributions, flag anything unclear to the treasurer, no access to fund decisions
- Serving: keep the team roster current; [building the schedule / only maintaining it — pick one]
- Not included: sending communications, processing payments, deciding data access
- Reports to: [name], reviewed [monthly/quarterly]
Whatever tool holds the records — a spreadsheet, a shared folder, or software built for the job, like SundayBridge — the description should describe the work first. If you later decide the tool is the bottleneck rather than the role, that is a separate conversation, and how to choose church management software is a reasonable place to have it.
Revisit it after the first real month
No description survives its first month unchanged, and that is fine. The point of writing it down was never to be complete on day one — it was to give the person doing the work a place to point when something falls outside it, and to give you a record of what changed and why. Set a date, thirty days out, to sit down again with whoever holds the role and adjust the list to match what actually happened. A job description that gets revised once is doing its job. One that never changes was probably never read.