The two-person counting rule is easy to agree to in a meeting and hard to keep on a Sunday when one of the two people you always use is out of town. Most churches do not break the rule on purpose. They break it because the schedule lived in someone’s head, that someone forgot to mention a conflict, and by 11:40 a.m. the only fix left is asking whoever is standing nearby to help count the offering — which defeats the point of having a rule at all.
A counting team schedule template fixes this before it becomes a Sunday-morning problem. It is not complicated: a rotation of names, a fixed pairing for each week, and a short backup list that gets used the moment someone does not show. The template below is built for a team of five or six volunteers covering a once-a-week count, and it assumes the people involved are busy and will occasionally forget — because they will.
Why the two-person rule keeps breaking
The rule itself is simple: no one person handles the offering alone, from the moment it leaves the plate to the moment it is recorded. It protects the money and it protects the volunteer, since an accusation is much easier to make against one person than two. Almost every church with any giving volume already knows this and already says they follow it.
What breaks it is not disagreement. It is absence with no plan. A counter has a sick kid, or a work trip, or simply forgets it was their week, and there is no second name written down anywhere that someone can call. The rule was never wrong — the schedule supporting it just did not account for the ordinary fact that people miss Sundays.
Build the roster before you build the calendar
Start with people, not dates. Write down everyone who is trained, trusted, and willing to count — not just the two or three names that come to mind first. For most churches this is five to six people. Fewer than that and a single bad month can leave you without a valid pair; more than that and people forget they are even on the team.
- List names, then pairings. Do not assign “Tom and Linda” as a permanent unit. List six names and let the rotation combine them differently each month.
- Note real constraints once. If someone travels every third weekend for work, write it beside their name so the rotation skips those dates automatically instead of you re-discovering it every quarter.
- Confirm training, not just willingness. A counter needs to know the process — how the count gets recorded, who has the second key, what happens with checks versus cash — before they are on the schedule alone with a partner who assumes they know it too.
The rotation: four weeks, six names, two per week
With six names on the roster and two counting each Sunday, a simple round-robin covers a month with three names left over each week — which is exactly your backup pool. The trick is rotating who pairs with whom, not just whose turn it is.
- Week 1: Names 1 and 2 count. Names 3, 4, 5, 6 are backup, in that order.
- Week 2: Names 3 and 4 count. Names 5, 6, 1, 2 are backup, in that order.
- Week 3: Names 5 and 6 count. Names 1, 2, 3, 4 are backup, in that order.
- Week 4: Names 2 and 5 count — a cross-pairing, not a repeat. Names 1, 3, 4, 6 are backup.
By week five you are back to a version of week one, but you have already broken the habit of the same two people always sitting at the table together. Print four weeks at a time and hand every person on the team the same sheet, so nobody is guessing whether they are up this Sunday or the next.
The backup list is the part people skip
Most counting schedules stop at “who counts this week.” That is only half a schedule. The other half is a short, ordered list of who gets called the moment one of the two scheduled counters is not there — and a plain answer to who is responsible for making that call.
Put the backup order directly on the same sheet as the week’s assignment, not in a separate document nobody opens on a Sunday. Assign the call itself to a specific role — often the usher captain or whoever locks the offering in the safe — so it is not a diffuse responsibility that everyone assumes someone else will handle.
A worked example: a church of 140
Take a congregation of 140 with an offering taken most Sundays. The counting team has six volunteers: two who serve on the finance committee and are always available, and four others who rotate around family and work schedules. Two vacations overlap in July, and one volunteer takes a new job with occasional Saturday shifts that bleed into Sunday mornings.
With the four-week rotation above, no single absence removes both scheduled counters for a given week, because the pairings change and the backup list has four other names on it. The one risk left is two absences landing on the same Sunday — which is exactly why six names, not four, is the minimum worth building around for a team this size.
Keep the schedule where the count actually happens
A schedule that lives in a spreadsheet nobody opens on Sunday morning is not much better than no schedule. Post it somewhere the team sees it without hunting: a shared note, a printed sheet in the counting room, a text thread the week before. The format matters less than whether the two people scheduled this week actually know it before they arrive.
Once the count is done, what happens to the numbers is a separate step worth planning just as carefully — who enters the total, against which households, and how soon. If your church tracks that part loosely, it is worth reading how to track giving in a way that respects the giver alongside this schedule, since the two habits reinforce each other.
Where the counting team fits into the rest of serving
A counting rotation is one small piece of a much bigger scheduling problem most churches carry across every volunteer team — greeters, nursery, ushers, and counters all fighting for the same finite pool of willing people. The same backup-list logic applies everywhere, and it is worth building the habit once rather than reinventing it team by team. SundayBridge keeps a serving schedule with roles and assignments in one place, so a missing counter shows up the same way a missing nursery volunteer would — as a gap someone can see and fill, not a surprise discovered at 11:40 on Sunday.
If counting is the only rotation you have ever formalized, it is worth looking at scheduling volunteers in a small church next, and at keeping a serving team from burning out once the schedule itself is solid, since a well-built rotation is also the simplest way to keep any one person from being asked too often.
What to do this week
Write down six names, not four. Build a four-week rotation that mixes pairings instead of repeating the same two people. Put an ordered backup list on the same page as the schedule, and assign one person the job of calling down that list the moment a counter is missing. None of this takes more than an hour to set up, and it is the difference between the two-person rule being a policy you wrote once and a habit that holds on the Sundays when someone does not show.