Church Health
How to measure engagement across giving, serving, and groups in one place
You measure engagement across giving, serving, and groups by putting all three on one person record instead of pulling three separate exports. Read each domain over time for frequency and recency, then read them together. One person, three signals, side by side, tells you who is steady and who is pulling back far better than any single metric.
A few months into pastoring, I had a man in our church I'd have told you was thriving. He gave every month without fail. What I couldn't see from the giving report was that he'd stopped serving in the spring and hadn't been to his group since Easter. His gift was still landing because it was automatic. The story was somewhere else, and I was reading the wrong page.
What metrics actually measure church engagement?
Use frequency and recency in each domain: how often someone gives, serves, and shows up to a group, and how recently they last did each. The shape of those numbers over a few months tells you more than any single total. Engagement is a pattern across time, not a score you check once.
Frequency answers "how connected is this person normally?" Recency answers "is that still true?" A volunteer who served twice a month for a year and hasn't been on a team in six weeks is a different person than the number "24 serves" suggests. The same goes for giving and groups. You're not looking for a high score so much as a change in the line.
Three domains carry most of the weight for a typical church:
- Giving: how regularly someone gives, and whether that rhythm changed. A regular monthly giver who stopped is worth a conversation.
- Serving: how often someone is on a team, and whether they've stepped off. Stepping off a team is one of the earliest signals you'll see.
- Groups: how consistently someone shows up to a small group or class, and the gap since they last did.
None of these is the whole person. Read together, they get close.
Why does measuring giving alone miss the person?
Giving alone misses the person because it lags and because it's one domain pretending to be the whole story. Someone can keep an automatic recurring gift running for months after they've stopped serving and gone quiet in their group. The money keeps arriving while the connection thins out, and the giving report shows you none of that.
This is the trap I fell into with the man I mentioned. Recurring giving is wonderful for a church's stability, but it decouples the gift from the person's week. The gift is a standing instruction to a bank. It tells you what someone set up once, not how they're doing now. If giving is your only lens, the people you'll miss are exactly the ones who set up autopay and then started pulling back everywhere else.
The reverse happens too. A regular weekly servant might give irregularly because of how their finances work, and a giving-only view would mark them as marginal when they're some of the most connected people you have. One domain will mislead you in both directions. What works better is reading giving next to serving and groups on the same screen, where the three lines sit together. If you want to go deeper on the giving side specifically, I wrote a whole piece on spotting the givers who quietly stopped.
How do I combine giving, serving, and group data into one view?
Combine them by anchoring every record to the person rather than the ministry, then bringing each domain's frequency and recency onto that one record. The manual version is a spreadsheet you rebuild from three exports; the sustainable version is software that keeps a single connected record current for you. Here's the manual method, which works and is worth doing at least once.
- List your people as rows. One row per person or household. This is your anchor. Every domain hangs off this list.
- Pull your giving export. From your current system, export giving by person for the last 90 to 180 days. In Planning Center, that's the Actions button, not a gear icon. Add two columns to your sheet: last gift date, and gifts in the window.
- Pull your serving export. Export team assignments and serve dates for the same window. Add columns for last serve date and number of serves.
- Pull your group data. Export group rosters and any participation you track. Add last group date and a rough count.
- Read each row across. Now you can see one person's three domains side by side. Look for the gaps: a recent gift but no serve in two months, a steady group member who stopped giving, anyone whose three "last" dates are all old.
- Sort by the gaps, not the totals. The people worth a call this week are the ones whose pattern changed, not the ones with the highest numbers.
That sheet is useful the day you build it. The hard part is week two, when all three exports are stale and you have to do it again. Most of us build that spreadsheet once, use it for a month, and let it die. That has more to do with the tooling than with anyone's discipline.
What's the difference between a spreadsheet and a connected person record?
A spreadsheet is a snapshot you have to rebuild by hand; a connected person record updates itself as giving, serving, and group activity happen. Both can show you all three domains at once. The difference is whether the view is current when you actually need it, on a Tuesday, between meetings, without you re-exporting three reports first.
| Three exports + spreadsheet | One connected person record | |
|---|---|---|
| Setup | Free, you already have the data | Import once, then it stays current |
| Stays current | Only when you rebuild it | Updates as gifts, serves, check-ins happen |
| Reads across domains | Yes, the day you build it | Yes, every day |
| Effort each week | You re-export and re-merge | None |
| Catches a changed pattern | If you happen to rebuild that week | When it changes |
| Good for | A one-time audit | Ongoing pastoral care |
Planning Center, Breeze (which moved to Tithely Church Management in 2025), and the spreadsheet method all hold the underlying data well. What none of the export-and-merge approaches do is keep the cross-domain picture live without your hands on it every week. If you're weighing systems on this exact capability, my nine-question framework for choosing church software walks through what to ask.
How does Scout measure engagement across all three at once?
This is where I'll name what I built, because cross-domain reading on one record is the specific problem Scout exists to solve. Scout keeps giving, serving, group participation, check-ins, forms, and prayer requests on a single person record, and reads them together automatically. When someone's pattern changes, it shows you the actual evidence.
Instead of a vague risk flag, Scout shows the math: gave every month for two years and the last gift was in March, served twice a month and stepped off the team in April, last group check-in was eight weeks ago. That person gets a "Needs attention" status, and you see why in plain language, so you can decide whether it's a season of travel or someone stepping back. We import your people, your gifts, and your groups for you, including a one-click Planning Center import, so the connected record exists from day one rather than after a month of spreadsheet maintenance.
One honest note on giving, since this pillar is about giving and engagement in one system. Scout takes no cut of donations and makes no money on giving. You still pay the payment processor's standard fees (Stripe is 2.9% + 30 cents on cards, or 2.2% + 30 cents at the nonprofit rate). The point is to get as much of every gift into the church's hands while the giving data lives on the same record as everything else. If you want the fuller cost picture, here's what online giving actually costs. And on the broader concept underneath all of this, participation versus attendance is worth a read.
Frequently asked questions
How do I measure engagement across giving, serving, and groups in one place?
Put all three on a single person record instead of three separate exports. Read each domain over time, then read them together. One person record showing giving, serving, and group participation side by side tells you who is steady and who is pulling back, which three disconnected reports cannot.
What metrics actually measure church engagement?
Use frequency and recency in each domain: how often someone gives, serves, and shows up to a group, and how recently they last did each. The shape over a few months matters more than any single number. A regular giver who stopped serving and went quiet in their group is a clearer signal than any attendance count alone.
Is giving a good measure of engagement on its own?
No. Giving is one domain, and it lags. Someone can keep an automatic recurring gift running long after they have stopped serving and stopped showing up to their group. Reading giving alongside serving and group participation is what tells you whether someone is connected or stepping back.
Can a spreadsheet measure engagement across all three?
It can, but it goes stale fast. Exporting giving, serving, and group data into one spreadsheet works for a snapshot. The problem is keeping it current every week by hand. A spreadsheet is a fine way to start; the question is whether you can sustain it, or whether one connected record does it for you.
What is the difference between participation and attendance?
Attendance is a Sunday headcount. Participation is everything a person actually does: giving, serving, joining a group, filling out a form, sharing a prayer request, checking a child in. Participation is richer because it spans domains and tells you how connected someone is, not just whether they were in the room.
Nic Moore is a pastor and the founder of Scout. He once spent a whole month rebuilding the same three-tab spreadsheet before admitting the tool was the thing that had to change, not his resolve.