The volunteer counting Sunday’s giving almost never asks how accurate the total is. She asks whether she is slow. Forty minutes in, three checks still unmatched to a name, an envelope with no amount written on it — the question in her head is not “is this right” but “why is this taking so long again.”
It is worth answering plainly, because a treasurer who thinks she is bad at this job will eventually quit it. She is not bad at it. Entering a week of giving has a real, predictable range of time it takes, and most of what makes one week slower than another has nothing to do with her.
The honest range
For a church of sixty to a hundred people, a clean week of giving — thirty or so gifts, mostly regular givers, checks with legible names — takes about fifteen to twenty-five minutes to count, match, and enter. For a church of two hundred fifty, with a hundred or more gifts and a wider mix of cash, checks, and a couple of unfamiliar names, forty-five minutes is a normal week, not a bad one. Those are the two ends of a range that almost every small church falls somewhere inside.
What that range does not include is the occasional outlier week: a building-fund push with sixty extra envelopes, or the week after Christmas when everyone who missed December catches up at once. A double-length week a few times a year is not a sign the system is broken. It is a sign more people gave.
What actually slows a batch down
If you compare a fifteen-minute week to a forty-five-minute week of similar size, the time almost never comes from typing numbers into fields. It comes from a short list of exceptions:
- A check with no name in the household’s usual handwriting — is this the grandmother who visits twice a year, or a new giver entirely?
- Cash in an envelope with the amount unwritten, which means counting it twice before you can trust the figure.
- A new giver who is not yet in the directory, which means a quick decision about whether to create the profile now or set the gift aside and come back to it.
- A joint gift from a household where the giving history is split — recorded under one spouse’s name in some years and the other’s in others.
A batch with none of these moves fast. A batch with four or five of them, even if the total dollar amount is small, will eat most of an hour. Counting the exceptions in a given week, rather than judging yourself against the total number of gifts, is the more accurate way to explain why some Sundays feel harder than others.
Weekly beats monthly, even though monthly feels efficient
It is tempting to let giving pile up and do it in one longer session — surely one sitting of two hours beats four separate half-hours. In practice it is close to the opposite. A month-old check does not carry the memory that a same-week check does. You no longer remember that the illegible signature belongs to the Petersons, because three other Sundays have happened since. What would have been a five-second recognition becomes a five-minute lookup, multiplied across every ambiguous gift in the batch.
Entering giving close to the Sunday it happened is the version of this job that stays fast. It is also the version that catches a data-entry mistake — a transposed amount, a gift attached to the wrong person — while the giver or the count team can still confirm it from memory, rather than months later when a year-end statement looks wrong and nobody can say why.
What slows you down that has nothing to do with counting money
Some of the real time in a giving session is spent not on arithmetic but on deciding where a person belongs. Is this gift from the household or from one member of it. Is this the same giver who moved last year and now lives at a different address. A directory that already reflects households the way your church actually gives, not just how it is structured on paper removes an entire category of hesitation from a giving session, because the record you need already exists instead of needing to be reasoned out on the spot.
The same is true of a directory that has been kept current rather than allowed to drift. A stale record of who moved, married, or stopped attending turns every ambiguous name into a small research project. A church that has done the work described in cleaning up a church database finds that giving entry gets faster for a reason that has nothing to do with the giving screen itself.
What a slow week is telling you, and what it is not
A forty-five-minute week is not a verdict on the volunteer doing it, and it is usually not a verdict on the church either. It is most often just what a hundred gifts with a handful of exceptions costs in time, no matter who is entering them or what they are using to do it. The number to watch is not this week’s minutes; it is whether the same categories of exception keep repeating month after month, which is a signal the directory or the process needs attention, not that the person doing the counting does.
SundayBridge records, edits, and deletes contributions against the same household and person records used everywhere else in the system, so a gift does not need its own separate lookup once the person is already in the directory — but it will not shorten a week with genuinely ambiguous cash and unfamiliar names, because that part of the job is a human judgment, not a data-entry one.
Church size is a rough guide, not a rule
It is natural to assume that a bigger church means a longer giving session, and on average that is true, but size alone does not decide it. A church of two hundred with a stable, long-tenured congregation and mostly electronic-adjacent habits — the same fifty households giving the same way most weeks — can move through its batch faster than a church of eighty that is growing quickly and adding several new givers a month. Growth is a good problem, but it is still a problem for the clock: every new giver is a new profile to create or confirm, and that lookup is exactly the kind of exception that adds minutes.
The more reliable predictor than raw attendance is turnover in the giver list itself. A congregation where the same people give the same way, week after week, is a fast batch no matter how large it is. A congregation in flux — new families, a recent building campaign that brought in one-time givers, a season of visitors who dropped something in the plate without introducing themselves — is a slower one, and it will stay slower until those names either become regulars in the directory or stop appearing.
A rough budget to set expectations, not a stopwatch
If a volunteer wants a number to hold onto so a slow week does not feel like failure, this is a fair one: budget about one minute per gift for a routine week, and expect a handful of the gifts each week to take three or four minutes apiece because they are not routine. A church with forty gifts in an ordinary week can expect something like twenty-five to thirty-five minutes. That budget will be wrong some weeks, in both directions, and that is fine. It is a planning number, not a performance target, and no one should be measured against it. If a session runs long two or three times in a row, it is worth a quick look at why before assuming the volunteer has simply gotten slower — the far more common explanation is a run of new givers, an unusual gift, or a batch that arrived out of its normal rhythm.
Read against the calendar it actually keeps
Giving totals move with the season — slower in summer, heavier in December — and the time it takes to enter a week tends to move the same way, since a bigger week has more gifts and more exceptions in it. If a treasurer expects every week to take the same twenty minutes and December takes forty, it can feel like something went wrong. Nothing did. It is worth reading the workload the same patient way you would read the totals themselves, a habit covered in reading giving trends without over-reacting.