Compare

Five signs your church spreadsheet has quietly stopped working

It never crashes or throws an error. It just gets a little less true every week until nobody trusts the numbers.

7 min read

Ask AI · in the $19/mo plan

Ask your own records a question. Which regulars have quietly stopped coming?” — answered from the records you already keep. It reads your church and no other, and it can't invent a number.

10 questions a month included · no AI add-on to buy

No spreadsheet announces its own failure. There is no error message, no red banner, no moment where it stops opening. It just keeps quietly getting a little less true every week, until one day someone asks a simple question — how many households give regularly, who followed up with the Petersons, why does this total not match the bank deposit — and nobody in the room can answer it with confidence.

The failure is gradual enough that it is easy to miss from the inside. What follows are five symptoms that show up again and again in small churches, roughly in the order they tend to arrive. If you recognize two or three, the sheet is not broken exactly — it has just stopped doing the one job you actually need it to do, which is tell you the truth.

It helps to say plainly why this matters before getting into the list. A spreadsheet is a general-purpose tool being asked to do a specific job it was never designed for: hold a record of people, over years, that multiple volunteers touch without stepping on each other, and that stays correct even when nobody is watching it closely. Word processors are fine at prose and calculators are fine at arithmetic; a shared grid of cells is a reasonable place to start tracking a church of thirty people, and a genuinely poor place to keep the memory of a church of two hundred.

1. The same person shows up as three different rows

Duplicate rows are usually the first crack, and they are almost never intentional. A guest fills out a card on a Sunday, a volunteer adds them to the sheet. Three weeks later they come back, a different volunteer does not recognize the name — maybe it was entered as “Bob” the first time and “Robert” the second — and adds them again. Now there are two rows for one person, with two different phone numbers, two different first-visit dates, and no way to know which one is current without asking Bob directly.

The real cost is not the extra row. It is that every report built on top of that sheet is now counting some people twice and some people zero times, and nobody can say by how much. If you have never sat down and actually deduplicated the list, it is worth reading through our database cleanup checklist once, just to see how many duplicates a real audit turns up. Most churches are surprised by the number.

2. Nobody remembers what the formulas do

Every long-lived church spreadsheet accumulates formulas that made perfect sense to whoever wrote them, on the day they wrote them, and to nobody else since. A giving total that quietly excludes a certain fund. A conditional format that flags “inactive” based on a rule from three volunteers ago. An attendance percentage calculated against a membership count that was never updated after the building addition.

This becomes dangerous the moment the person who wrote the formula leaves — a treasurer moves, a secretary retires — and someone new inherits a sheet full of logic they cannot explain and are afraid to touch. So they work around it instead of fixing it, adding a new column next to the old one rather than risk breaking something they do not understand. Do this for a few years and the sheet becomes an archaeology site: layers of columns, each one a different person's attempt to patch the layer beneath it.

3. Year-end statements take a full weekend

This is usually the sign that finally forces a decision, because it has a deadline attached. Pulling twelve months of giving out of a spreadsheet into per-household statements means reconciling entries against bank deposits, catching the gift that got entered under the wrong name, and formatting a hundred-plus letters by hand — and doing all of it correctly, because a wrong statement is not a formatting error, it is a trust and compliance problem.

If your treasurer disappears for an entire weekend every January to produce these, that is not a sign of diligence. It is a sign the tool is making a routine task heroic. Our guide on year-end giving statements walks through what a clean statement actually requires, and it is a useful gut check for how much of that weekend is truly necessary work versus spreadsheet friction.

4. Follow-up depends on someone remembering a row exists

A guest visits, a volunteer adds a row with a note to call them, and then that row sits in a sheet nobody opens between Sundays. There is no owner column that anyone actually checks, no date that flags it as overdue, no notification that eight days have passed with no follow-up. The system for making sure a guest is not forgotten is, in practice, one person's memory of a spreadsheet tab.

This is the symptom with the highest real cost, because the failure is invisible until the guest simply does not come back a third time and nobody can say why. If your current process for a promising follow-up is “someone will remember,” it is worth comparing it against the bar set in the guest-to-member path, which lays out what a follow-up actually needs to have — an owner and a date, at minimum — to not quietly disappear.

5. Two people have two different “current” copies

This is the sign that the sheet has stopped being a shared record at all. It happens innocently: someone downloads a copy to work on offline, makes real edits, and the master file moves on without them. Weeks later, someone pastes the old copy back in to “update” it, and now the sheet has forgotten three weeks of attendance and gained back two people who left. Nobody did anything wrong. The spreadsheet simply has no concept of a single source of truth, only whichever file happens to be open.

Once this has happened once, trust in the sheet drops fast, and people start keeping their own private notes “just in case,” which only fragments the record further. A regular weekly admin rhythm — one person, one sitting, one file — slows this down considerably, but it does not solve the underlying problem: a shared spreadsheet has no real way to enforce that there is only one copy.

A five-minute test you can run this week

You do not need a full audit to get a rough read on how far along the decay has gone. Open the sheet and try three small things. First, sort by phone number and scan for repeats — a shared number across two rows almost always means a household split into two people, or one person split into two rows. Second, pick any formula cell in the totals and ask, out loud, whether you could explain what it does to a new volunteer in one sentence. If you cannot, neither can whoever inherits it. Third, ask two people who both touch the sheet regularly which file is the current one. If they do not answer instantly and identically, you already have your answer.

None of these three checks takes longer than a few minutes, and none of them requires you to fix anything yet. They are diagnostic, not corrective — the point is just to see, plainly, how many of the five signs above are already present rather than guessing from memory. Most churches who run this test are surprised it is not one problem but two or three, quietly compounding each other.

What to do about it

None of these five signs, on its own, means you need new software. A duplicate list can be cleaned in an evening. A confusing formula can be rebuilt and documented. What they mean together, especially when two or three keep recurring after you fix them, is that the spreadsheet has reached the size and age where a shared file with no owner, no structure, and no memory of its own history is the wrong shape for the job.

A dedicated record keeps the things a spreadsheet cannot: one profile per person instead of one row that can be copied, a follow-up that ages itself instead of waiting to be remembered, a statement that generates instead of gets assembled by hand. SundayBridge is built around that idea — people, giving, follow-up, and serving teams in one place, at $19 a month, with a public demo you can walk through with your own church's numbers in mind before deciding anything.

Before you migrate anything, print or export the current spreadsheet exactly as it stands. It is your record of where you started, and the easiest way to notice what a cleanup actually caught.

Frequently asked questions

Our spreadsheet still technically works. Isn't that good enough?
It depends what you mean by works. If it opens and the formulas still calculate, that is not the same as being trustworthy. A spreadsheet can run perfectly and still be wrong, because nothing in it checks whether a row is a duplicate, a formula was overwritten, or a number was typed into the wrong cell. Working and correct are different claims.
How do we know if we have duplicate people, not just duplicate rows?
Sort by last name and phone number, not by whatever order the sheet is already in, and read through slowly. Duplicates usually come from two different volunteers adding the same guest on two different Sundays, so they will not look identical — a nickname, a maiden name, a slightly different phone digit. You are looking for the same person wearing two names.
What is the actual cost of a spreadsheet that has quietly failed?
Mostly it is trust, spent a little at a time. A statement with the wrong total, a guest who never gets a follow-up because their row got overwritten, a Sunday morning spent explaining why the numbers do not match — none of it is a disaster on its own, but it adds up to people quietly not trusting the record, which means they stop updating it, which makes the problem worse.
Do we need to switch to church software the moment we see one of these signs?
No. One symptom is worth fixing in place — clean the duplicates, rebuild the formula, agree on who owns it. It is when three or four of these show up at once, and keep coming back after you fix them, that the spreadsheet itself has become the problem rather than whatever mistake caused this particular mess.