Every regular attender eventually misses a Sunday. Most of the time it is nothing — a work trip, a sick kid, a wedding out of town. The trouble is that the absence which means nothing looks, from the back of the room, exactly like the absence that means someone is quietly leaving. The only way to tell them apart is to notice, and the only way to notice reliably is to have a short, repeatable sequence you run every time, instead of relying on someone happening to remember a face.
What follows is that sequence: five steps from “this crossed into worth noticing” to “someone has actually made contact,” written for the volunteer or part-time staffer who is the one who has to run it on a Tuesday morning with everything else on their plate.
Step one: decide what “a gap” means for this person
Resist the urge to set one absence threshold for the whole church. A gap is relative to the individual, not a fixed number of Sundays. The member who has not missed a service in two years and then misses three in a row has crossed a real threshold. The member who comes every other week, most weeks, has not — that is just their rhythm. Reading attendance the right way means comparing a person to their own history, and that comparison is only possible if the history is actually recorded somewhere you can look back through, rather than living in one usher's memory.
A practical rule of thumb: ask whether this absence, on its own, would make you say “huh, that’s odd” if you noticed it in passing. If the honest answer is yes, it has crossed from normal into worth noticing, and it is time to move to step two.
Step two: confirm it is not already explained
Before anyone reaches out, check the easy things first. Did the person tell a leader they were traveling. Are they in a group or serving on a team that might already have context — a small group leader who knows they are dealing with a new baby, or a serving-team lead who granted them a planned week off. A five-minute check against what is already known saves an awkward “we noticed you were gone” call to someone who was simply at a family reunion, and it is the difference between a gap checklist that builds trust and one that makes people feel watched.
Step three: turn the gap into a named next step
A gap that lives only as a feeling — “I think we haven’t seen the Andersons in a while” — rarely turns into an actual call. The moment it is worth noticing, write it down as a next step with one owner and one date, the same discipline used for a first-time guest on the guest-to-member path. An unassigned concern ages into nothing; a concern with a name and a date attached either gets done or visibly does not, and either outcome is more useful than silence.
Pick the owner deliberately. The person best placed to reach out is rarely whoever happens to be reading the attendance chart — it is usually someone who already has a relationship: a small group leader, a deacon assigned to that section of the directory, a friend who sits near them. The next step should name that person specifically, not “someone from care team.”
Step four: make contact, and make it easy to make
The contact itself can be small. A text asking how someone is doing. A call that starts with “we missed you” rather than “where were you.” A conversation after the service the next time they do show up. The goal of this step is not to solve anything — it is simply to close the loop between noticing an absence and a human being aware of it, which is the entire point of running a checklist instead of hoping someone remembers.
SundayBridge holds this part cleanly: the follow-up board carries an owner and a date on every open item, and it visibly ages what nobody has picked up yet, so a gap that got assigned three weeks ago and never touched is easy to spot rather than easy to forget. It will not make the call for you. It just makes sure the call does not quietly disappear.
Step five: record what you learned, briefly
After contact, write down what actually happened — even one line. Back from vacation. Struggling with a new work schedule. Asked to be left alone for a while. That note becomes part of the person's engagement timeline, so the next gap, months from now, is read in light of this one instead of starting from zero. If what surfaces is more sensitive than a scheduling conflict — a health crisis, a family situation, a quiet crisis of faith — that belongs in a private pastoral record kept separately from the open follow-up list, not in a note anyone assigned to the board can read.
Building the checklist into a weekly habit
None of this works as a one-time project. It has to sit inside a weekly admin rhythm — the same ten minutes each Monday or Tuesday where someone looks at who was and was not there, decides which absences have crossed into worth noticing, and assigns the ones that need a human touch. Skip a week and the gaps do not go away; they just pile up unnoticed until the list of people who quietly stopped coming is long enough to be discouraging.
The checklist is short on purpose: notice, confirm, assign, contact, record. Five steps, repeated weekly, run by one person with fifteen minutes and a list they trust. It will not catch every person who is drifting, and it is not meant to replace a pastor's judgment about who needs a visit versus a text. What it does is make sure the ordinary absence — the one that might be nothing, or might be the first sign of something — does not slip past everyone simply because nobody was looking that week.