From the pew, a greeter and an usher look like the same volunteer in a different spot. Both are standing near the entrance before service, both are smiling at people they may or may not know, both disappear into the pews once things start. It is an easy thing to lump together when you are scheduling serving teams, and an easy thing to regret the first Sunday a substitute shows up not knowing which job is theirs.
The two roles pull in different directions. A greeter's job is a person: the one walking through the door, hopefully noticed, hopefully welcomed, hopefully remembered next week. An usher's job is a room: seats filling in some order, an offering that gets collected and handled the same way every time, an aisle that is clear when someone needs to move through it. Writing one description that tries to hold both jobs produces a volunteer who is unsure which one they are doing this week, and a visitor who either gets fussed over walking in and then ignored in the seat, or the reverse.
Why one job description for both roles falls apart
Most small churches do not sit down and write role descriptions at all — the job gets passed along by whoever trained the last person, usually in about thirty seconds at the door before the prelude starts. That works fine as long as the same three people keep doing it. It stops working the day one of them is out and somebody's well-meaning teenager or new-to-the-church volunteer gets handed “just stand by the door and help out,” which is not a role description, it is a shrug.
The instinct to write one combined sheet for “greeters and ushers” comes from a real place: in a congregation of eighty or a hundred, the same handful of people often do rotate through both. But the description should still separate the two jobs, even if one person does both most weeks. A description that names one job clearly is something you can also hand to a substitute who is only covering the door, or only covering the aisles, without them having to figure out which half applies to them.
What a greeter role description actually needs to say
A greeter description earns its keep by being specific about timing and about what “welcome” means in practice, not just in spirit. A workable version covers:
- Arrival time. Fifteen or twenty minutes before the service, not “early,” because early means something different to everyone.
- Where to stand. Front door, parking lot, or both, and whether that changes in bad weather.
- What to hand a first-time guest. A bulletin, a connect card, directions to the nursery — whatever your church actually uses, named specifically.
- Who they hand a first-timer off to. A greeter who notices a guest is not the same as a guest who gets followed up on. The description should name who takes it from there, so it does not depend on the greeter remembering to mention it later.
- When their job ends. Usually once service starts, with a note on whether they are expected back at the door for latecomers.
That last point — who a greeter hands a first-time guest to — matters more than it looks. A friendly conversation at the door is worth little if it evaporates the moment the guest sits down. Writing that handoff into the role description is what turns a warm hello into the start of the guest-to-member path instead of a nice moment nobody remembers by Tuesday.
What an usher role description actually needs to say
An usher description is less about warmth and more about repeatable mechanics — which is exactly why it needs to be written down rather than passed along by memory. It should cover:
- Seating. Whether ushers actively seat people, fill the room front-to-back or however your church prefers, and what to do when a section is full.
- The offering. When it happens in the service, which route ushers take through the room, and what happens to the plates or baskets afterward — who counts it, where it goes, and how it is logged.
- Late arrivals and the aisle. Whether latecomers are seated immediately or held until a natural pause, and how the center aisle stays clear for a baby dedication, a baptism, or communion.
- Building basics. Where the thermostat is, who to find if someone needs a wheelchair-accessible seat, what to do about a crying child or a minor medical issue in the room.
None of this is complicated, which is exactly why it gets skipped: it feels too obvious to write down, until the Sunday a substitute usher does not know whether to seat a family mid-song or hold them at the back, and guesses wrong in front of everyone.
Write for the substitute, not the regular
The test of a role description is not whether your most reliable greeter needs it — she does not, she has done this for six years. The test is whether a substitute who has never done the job can read it once and do it competently. That means naming things the regulars do automatically: which door, what to say, who to flag down if the sound system is not working, what “early” means in minutes.
This is also where SundayBridge earns a small mention: once roles exist with real names attached, a substitute usher for a given Sunday is a visible assignment on the serving team, not a text message you hope reaches the right person. The description itself still has to be written by you — software holds the assignment, not the judgment about what a greeter says at the door.
Keep the two roles separate even when one person fills both
In a congregation of sixty or eighty, it is common for the same three or four people to rotate through greeting and ushering both, sometimes in the same service. Resist the urge to write a single merged description for them. Keep the descriptions separate and let the schedule combine them. That way a person covering only the door on a given week has exactly the document they need, and nothing they do not.
It also makes recruiting easier. “Can you greet for one Sunday next month?” is a small, clear ask that most people can say yes to. “Can you help out at church sometime?” is vague enough to decline without feeling bad about it. Separating the roles is part of what makes them easy to hand to someone new, which matters when you are scheduling volunteers and it is the same ten people every time.
Review the descriptions once a year, not once
A role description written once and never revisited drifts from what the job actually is. The offering procedure changes when you add online giving records, the seating pattern changes when you add a second service, the connect-card question changes when your follow-up process changes. A short annual review — even just reading the description out loud with your current greeters and ushers and asking what is missing — keeps it matching reality instead of the way things worked three pastors ago.
Well-defined roles are also part of a larger pattern worth getting right across every serving team, not just these two: clear, bounded asks are what keep serving from wearing out the same willing few people. A greeter and an usher description are a small, concrete place to start practicing that habit.