How to notice who is drifting, without it feeling like surveillance

By Kyle @ Synodo · Updated 2026-10-26

The short answer: Watch what people do with the group, never what they say in it. Record a reason beside each name rather than a score, compare somebody to their own history rather than to the group, and show it only to the people who would already be making the call.

Download the monthly check (print it or paste into a doc)

Is it wrong to keep track of who turns up?

No, and most leaders already do it — in their head, badly. They remember the person who was missing last night and forget the one who stopped coming in March. What makes a record feel wrong is not that it exists, it is what it is for and who can see it. A list that exists so somebody rings Sam is pastoral care. The same list, seen by people with no relationship to Sam, or kept as a record of his reliability, is something else. The question to ask of any such list is: who acts on this, and what do they do?

What is worth noticing, and what is not

The useful signals are the ones that describe somebody’s relationship with the group. The unhelpful ones describe their relationship with your software.

Worth noticing: they have missed the last two or three meetings.
Worth noticing: they have stopped answering things addressed to them — a poll, a sign-up, a question.
Worth noticing: they have not opened the group since it last said anything.
Worth noticing: they were invited weeks ago and never accepted.
Not worth it: how often they open an app. Someone can be deeply committed to a group that meets monthly and open nothing in between.
Not worth it: how much they post. Quiet people are quiet. Introversion is not drift.
Never: what they actually wrote. If you are reading the content of what people say to each other to decide who is struggling, you have built something else.

Why drifting is a change, not a level

This is the part most systems get wrong. Two people have both missed the last three meetings. One has been in and out all year and is exactly as present as he has ever been. The other had not missed once since January. Only the second has drifted, and he is the phone call worth making today — but a list that sorts by "meetings missed" puts them side by side and says the same thing about both. Compare somebody to their own history, not to the group average. It finds the people you actually want to catch, and it quietly ignores the ones who are simply built that way.

How long is too long to be quiet?

It depends entirely on how often the group meets, and this is where good intentions produce nonsense. Three weeks of silence in a group that meets every Tuesday is worth a look. Three weeks of silence in a group that meets monthly is just the gap between meetings. Measure quiet against the rhythm the group actually keeps — roughly two of its own cycles — rather than a fixed number of days for everybody. A monthly group told every month that all its members have gone quiet will stop reading the warnings, including the true ones.

Record a reason, never a score

A number invites comparison; a reason invites a conversation. "Sam: 42%" tells a leader nothing they can act on and quietly ranks people against each other. "Sam — missed the last three meetings, had not missed one before" tells them what to say when they pick up the phone, and it can be argued with: the leader might know Sam has been away with work, and close it there. Scores also outlive their usefulness. A percentage from March follows somebody around; a reason is true this week and gone the next. If you are keeping a history of who has been flagged, you have started a personnel file on your volunteers.

Who should see it?

The smallest group of people who would already be making the call. The group’s own leaders, because they know the person. Whoever oversees groups across the church, because they are the ones who can help a leader who is struggling, or hand a group to somebody else when a leader has quietly stopped. Not the group. Not a noticeboard. Not anybody who would read it as gossip.

The failure nobody measures: flagged, and nothing happened

Most churches that start noticing drift stop there. The list gets longer, everybody can see it, and nobody is quite responsible for acting on it. Within a term it has become wallpaper. Track whether somebody was actually reached, and treat "three people flagged and nobody has been in touch" as a more serious signal than any individual absence — because it usually means the leader is the one who needs help, not the member. A list nobody acts on is worse than no list: it lets everybody feel the problem is handled.

Where the line actually is

Noticing becomes watching at the point where the information stops being something a leader could have seen for themselves. A leader knows who was at their meeting, because they were there. They know who answered the poll, because they posted it. They do not know what two members said to each other, and nothing should tell them. If every signal you keep is something the leader either recorded or could see by looking, you are helping them remember. The moment you add something they could only know because software was watching, you have crossed it.

Doing this in Synodo

Synodo does the remembering and nothing more: the register a leader already takes, the work handed in, and whether somebody has opened the group — never what anyone wrote. Anyone drifting appears with the reason beside their name and whether it is a change for them, timed to how often that group actually meets, and only their own leaders and your church’s admins ever see it.

See how it works