Church Attendance Tracking System | Self Check-In, Absence, Trends and Care
Church Attendance Tracking System: Counting People So You Can Care for Them
Church attendance tracking system is a phrase that makes some pastors uneasy, because counting sounds like something a business does and a church is not a business.
The unease is worth taking seriously and then setting aside, because the alternative to counting is not humility — it is not knowing.
A church that does not track attendance does not know that the Mwangi family has not been seen for six weeks, that the youth service has lost a third of its numbers since January, that the second service is now fuller than the first, that the midweek fellowship in the eastern estates has quietly stopped meeting, or that the four hundred people the pastor believes attend on a Sunday are actually two hundred and eighty.
Each of those is something a shepherd would want to know, and none of them is visible from the pulpit. Attendance tracking is how a church of any size sees its own people — who came, who has stopped coming, where the congregation is growing and where it is thinning — so that someone can respond.
The risk is that the same data becomes a tool for pressure or comparison, which is why how it is used matters as much as whether it is collected. This guide covers both: what to count and why, aggregate versus per-person, the methods from usher headcounts to QR self check-in, children’s check-in and safeguarding, first-time visitors, multiple services and midweek, meetings and conferences, accuracy, absence detection and the pastoral response, trends and seasonality, capacity, multi-branch, keeping attendance and giving apart in public, privacy and dignity, and introducing it to a congregation.
The value of a church attendance tracking system is that the church sees the person who stopped coming, and a church attendance tracking system that flags a member absent three weeks running is what turns a number into a phone call — which is why a church attendance tracking system is pastoral care infrastructure rather than a statistic.
Table of Contents
- Why Count
- The Kenyan Church Context
- What Counting Is For and What It Is Not
- Aggregate Versus Per-Person
- Headcount Methods
- Usher Counts
- Self Check-In by QR Code
- Self Check-In by Phone
- Leader-Marked Attendance
- Children’s Check-In and Check-Out
- First-Time Visitors at Check-In
- Multiple Services on a Sunday
- Midweek Services and Fellowships
- Meetings and Departments
- Conferences and Events
- Online Attendance
- Accuracy and Double Counting
- Absence Detection
- Responding to Absence With Care
- Trends Over Time
- Seasonality
- Capacity and Venue Planning
- Keeping Attendance and Giving Apart
- Multi-Branch Attendance
- Attendance as Pastoral Information
- What Leadership Does With It
- Volunteer Load Against Attendance
- Attendance in Annual Reports
- Reporting
- Privacy and Dignity
- Data Protection
- Introducing It to the Congregation
- Common Mistakes
- Systems and Costs
- Frequently Asked Questions
Why Count {#why-count}
The reasons are pastoral first and administrative second.
To notice who has stopped coming.
To know whether the church is growing or shrinking and where.
To plan services, seating, parking and children’s rooms for the people who actually come.
To see which ministries are reaching people and which are not.
To resource fellowships and departments proportionately.
To report honestly to leadership and the membership.
To know the real number rather than the remembered one.
Every one of these serves people, since a church attendance tracking system that shows a fellowship has halved lets someone ask why, and a church attendance tracking system that shows the children’s room is over its safe number on the second service lets someone act before the problem.
The Kenyan Church Context {#kenyan-context}
Local conditions shape what tracking involves.
Congregations are frequently large and multi-service, which makes counting hard and estimates unreliable.
Attendance fluctuates with school terms, the rains, harvest, funerals and travel upcountry.
Fellowships and cell groups meet in homes across estates, out of leadership’s sight.
Ushers count by impression and figures are rounded generously.
Members move between churches and between branches.
Phones are universal and QR codes are familiar from payment, which makes self check-in practical.
Children’s ministries are large and check-in is frequently informal, which the safeguarding point addresses.
Pastors know families by name in smaller churches and cannot in larger ones.
Absence is noticed late or not at all.
Multi-branch churches want to compare sites.
Each shapes what a church attendance tracking system must do, and a church attendance tracking system designed for a small single-service congregation with a printed register will not serve a three-service church with fellowships across the city.
What Counting Is For and What It Is Not {#for-and-not}
The purpose should be stated before the counting starts, because the data will be used according to whatever purpose is understood.
For: noticing absence, planning, resourcing, honest reporting, and seeing the congregation as it is.
Not for: ranking members, pressuring attendance, publicising who comes and who does not, comparing families, or tying spiritual standing to a number.
Not for linking attendance to giving in any public way, which its own section addresses.
Not for surveillance, since a member who feels watched will feel it as control rather than care.
State it, since a church attendance tracking system introduced as “so we can notice when someone is missing and reach out” is received differently from one introduced as “so we know who is committed”, and a church attendance tracking system whose purpose was never stated will be assumed to be the second.
The purpose determines who sees the data, which the privacy section addresses.
Aggregate Versus Per-Person {#aggregate-per-person}
Two kinds of attendance data exist and they serve different ends.
Aggregate: how many were present at a service, a fellowship, an event.
Per-person: which individuals were present.
Aggregate serves planning, trends and reporting.
Per-person serves pastoral care and absence detection.
Aggregate is easy and low-sensitivity; per-person is more work and more sensitive.
Most churches should collect aggregate for every gathering and per-person where it serves care — main services, fellowships, children’s ministry and departments.
Per-person without a care purpose is surveillance, and a church attendance tracking system that collects per-person data because it can, without anyone using it to reach out, has taken on sensitivity for no benefit, while a church attendance tracking system that uses per-person data to notice and visit has earned it.
Decide per gathering which is needed.
Headcount Methods {#headcount}
Aggregate counts have several methods and each has an accuracy.
Usher counts at a set moment during the service.
Seat counts by section.
Door counts on entry.
Counting from a photograph of the congregation, which is surprisingly accurate.
Self check-in totals where the congregation checks in.
A combination, with one method as the standard and another as a check.
Consistency matters more than the method, since a church attendance tracking system that counts the same way at the same moment every week produces comparable figures, and a church attendance tracking system where the method changes with the usher produces trends that are noise.
Record the method with the count so the figure is interpretable later.
Usher Counts {#usher-counts}
Ushers are the traditional counters and the method can be made reliable.
A set moment, typically during a sermon when movement is least.
Sections assigned to specific ushers.
Counted, not estimated.
Children’s rooms and overflow counted separately.
Recorded immediately on a phone or a form.
Submitted to the system the same day.
Training, since an usher who understands why the count matters counts carefully.
Rounding is the enemy, since a church attendance tracking system fed with counts rounded to the nearest fifty cannot show a decline of thirty, and a church attendance tracking system fed with actual counts by section can.
Cross-check occasionally with a photograph count.
Self Check-In by QR Code {#qr-checkin}
A QR code the member scans on arrival is the most practical per-person method for larger churches.
A code displayed at the entrance, on the screen and in the bulletin.
The member scans it, identifies themselves once, and is checked in.
Subsequent weeks are a scan and a tap.
Household check-in so one adult can check in the family.
Multiple codes for multiple services or entrances.
It scales, since a church attendance tracking system with QR check-in records a thousand people without an usher writing a single name, and a church attendance tracking system that links the scan to the member record has per-person attendance with no data entry.
Not everyone will scan, which is why aggregate counts continue alongside, and the accuracy section addresses the gap.
Familiarity with QR from payment makes adoption faster here than it would be elsewhere.
Self Check-In by Phone {#phone-checkin}
For members without smartphones or who prefer it, phone-number check-in serves the same purpose.
A short code or number to message on arrival.
Or a phone number entered at a check-in desk.
The number matched to the member record.
Household check-in by the same route.
Older members and those with basic phones served.
Both routes feed the same record, since a church attendance tracking system that accepts a scan or a message treats them identically, and a church attendance tracking system that offered only QR would miss the members least likely to use it, who are frequently the ones absence detection matters most for.
Keep the message route simple, since a member asked to type a long code will not.
Leader-Marked Attendance {#leader-marked}
Fellowships, cells and departments are best recorded by their leaders.
The leader opens the group’s list and marks who was present.
From a phone, at or after the meeting.
Visitors added.
Notes where relevant.
Submitted to the central record.
It is the only practical method for home groups, and a church attendance tracking system that gives every fellowship leader their own list to mark keeps attendance for gatherings leadership never sees, while a church attendance tracking system that depends on paper registers collected monthly gets half of them.
Leaders who understand that marking attendance is how the church notices absent members do it, and the small groups article’s points about leader support apply.
Children’s Check-In and Check-Out {#childrens-checkin}
Children’s ministry is where attendance tracking and safeguarding meet.
Each child checked in by a parent or guardian.
A matching tag or code issued so the same adult collects.
Check-out recorded against the check-in.
Allergies and medical notes held for the session.
Headcount per room against the safe ratio.
Volunteer-to-child ratio visible.
No child released to an adult without the matching identifier.
This is not administration, since a church attendance tracking system that issues a tag at check-in and requires it at check-out is preventing a child leaving with the wrong adult, and a church attendance tracking system that shows the room at forty children with two volunteers is showing a ratio that must be fixed before the session continues.
Confirm the church’s safeguarding policy and qualified advice govern the process, and the volunteer article’s screening requirements apply to everyone in the room.
First-Time Visitors at Check-In {#first-timers}
Check-in is where a visitor first appears in the record.
A visitor scanning the code is asked for a name and a number, briefly.
Flagged as a first-timer.
Passed to the visitor follow-up process.
Not treated as a member until they are.
Welcomed without being processed, since a visitor asked for six fields at the door has been given a form rather than a greeting.
The visitor management feature is where they go next, and a church attendance tracking system that creates the visitor record from the first check-in means nobody re-enters them, while a church attendance tracking system that ignores visitors at check-in loses the people the church most wants to keep.
Keep the visitor’s first interaction light and let the follow-up carry the rest.
Multiple Services on a Sunday {#multiple-services}
Churches running several services need each counted separately and the day summed.
Attendance per service.
Members attending more than one service counted once for the day.
Service-level trends, since the first and second services move differently.
Total unique attendance for the day.
Check-in codes per service so scans land correctly.
Ushers assigned per service.
The per-service view is where shifts show, since a church attendance tracking system that shows the second service growing while the first shrinks tells leadership something about the congregation’s changing pattern, and a church attendance tracking system that reports only the Sunday total conceals it.
Avoid double counting across services, which the accuracy section addresses.
Midweek Services and Fellowships {#midweek}
Midweek gatherings are where engagement shows and where tracking is weakest.
Midweek services counted like Sunday.
Fellowships marked by leaders.
Cell groups likewise.
Prayer meetings and bible studies.
Attendance at these relative to Sunday shows depth of engagement.
A member on Sunday only and a member at fellowship too are different pastoral pictures.
Track them, since a church attendance tracking system that shows a member’s fellowship attendance dropping before their Sunday attendance drops has seen the early signal, and a church attendance tracking system that tracks only Sunday sees it late.
Fellowships that stop reporting are fellowships that may have stopped meeting, which the department article addresses.
Meetings and Departments {#meetings}
Departmental and committee meetings have attendance that matters for governance.
Who attended, for quorum.
Apologies.
Attendance over time per member, for engagement.
Recorded with the minutes, as the department article describes.
The same member record, so a person’s departmental attendance appears beside their service attendance.
Linked to leadership eligibility where the church’s rules require attendance.
The department article covers meeting discipline, and a church attendance tracking system that records meeting attendance against the member gives a full picture of participation, while a church attendance tracking system that keeps meetings separate cannot show that a department leader has not attended their own meetings in three months.
Conferences and Events {#conferences}
Larger gatherings need registration, check-in and counting at scale.
Registration in advance where possible.
Check-in on arrival by QR or list.
Sessions counted separately for multi-session events.
Visitors and members distinguished.
Capacity monitored live.
Post-event attendance report.
The events feature holds the event, and a church attendance tracking system that checks conference delegates in by the same QR method used on Sunday needs no separate process, while a church attendance tracking system that shows which sessions drew attendance tells the organisers what to repeat.
The events article covers the logistics.
Online Attendance {#online}
Streamed services have an audience that should be counted on its own terms.
Concurrent viewers as a measure of live attendance.
Total views over the following days.
Members who identify themselves online where the platform allows.
Not added to in-person attendance as if equivalent, since a view is not a presence.
Reported separately and alongside.
Trend over time, since a growing online audience with a shrinking in-person one is a pattern worth understanding.
Keep the categories distinct, since a church attendance tracking system that reports four hundred in person and two hundred online has described two audiences honestly, and a church attendance tracking system that reports six hundred has described neither.
The streaming article covers the technical side.
Accuracy and Double Counting {#accuracy}
Attendance figures are only useful if they are approximately true.
Double counting across services, where a member attends twice.
Double counting between usher count and self check-in where both are summed.
Under-counting where members do not check in.
Over-counting where children are counted in both the main count and the children’s room.
Household check-in recording people who did not come.
One method as the standard for the aggregate, with self check-in as the per-person layer, not both added.
Periodic validation, since a church attendance tracking system whose usher count and check-in count are compared monthly shows how much of the congregation is checking in, and a church attendance tracking system that never compares them does not know whether per-person data covers half the church or nine tenths.
Accept that per-person coverage is partial and design absence detection accordingly.
Absence Detection {#absence}
Absence detection is the pastoral capability the whole system exists for.
A member who attended regularly and has missed a defined number of consecutive weeks.
Flagged automatically.
Routed to the right person: a fellowship leader, a pastor, a care team.
With context: how long they attended, which services, which fellowship.
Threshold appropriate to the church and the member’s pattern, since a member who came weekly missing three weeks differs from one who came monthly.
Not triggered for members who are known to be away.
Resolved when contact is made and recorded.
It is the number becoming a name, since a church attendance tracking system that flags the Mwangi family after three absent Sundays gives someone the prompt to call, and a church attendance tracking system without it leaves absence to be noticed by whoever happens to notice, which in a large church is nobody.
Coverage matters, since a member who never checked in cannot be flagged, which is one argument for encouraging check-in.
Responding to Absence With Care {#responding}
How the church responds to a flag determines whether tracking is care or pressure.
A call or a visit from someone who knows them.
Asking how they are, not where they were.
Listening for the reason: illness, bereavement, travel, difficulty, disaffection, or simply life.
Offering help where help is needed.
Not reprimanding.
Not implying their absence was noticed as a failing.
Recording the outcome so the flag is closed and the context is known.
Respecting a member who is stepping back, since a person who has chosen to leave should be released with grace rather than pursued.
The response is the whole point, since a church attendance tracking system that produces a caring call has done its job, and a church attendance tracking system that produces a message saying “we noticed you have not been in church” has done harm the counting was not meant to cause.
Train the people who make the calls, since the tone is everything.
Trends Over Time {#trends}
Aggregate attendance over months and years shows the church’s direction.
Weekly attendance plotted over a year.
Year-on-year comparison for the same week.
Per-service and per-fellowship trends.
Growth, plateau or decline, seen rather than felt.
Inflection points linked to events, changes or seasons.
The trend is what leadership cannot see from the pulpit, since a church attendance tracking system that shows a slow decline over eighteen months has surfaced something a pastor who sees a full church every week would not perceive, and a church attendance tracking system that shows growth concentrated in one service or one fellowship shows where to invest.
Look at it monthly at leadership level.
Seasonality {#seasonality}
Attendance moves with the calendar and trends should be read against it.
School terms and holidays.
The rains.
Harvest and planting in rural and peri-urban congregations.
Christmas, Easter and other high days.
Travel upcountry at holidays.
Funerals and community events.
Exam periods for youth.
Compare like with like, since a church attendance tracking system that compares August to August rather than August to May avoids mistaking a school holiday for a decline, and a church attendance tracking system that shows the seasonal pattern lets leadership plan for the lean months rather than being surprised by them.
Record local seasonal factors so future years can be read.
Capacity and Venue Planning {#capacity}
Attendance data is what venue decisions should rest on.
Seats available against attendance per service.
Overflow frequency.
Children’s rooms against child attendance and ratios.
Parking against vehicles.
Whether to add a service, move to a larger venue or plant.
Timing of services against when people actually come.
Decisions on evidence, since a church attendance tracking system that shows the second service at capacity forty Sundays a year has made the case for a third service, and a church attendance tracking system that shows the building at sixty percent has made the case against a building project.
The building project article insists on this evidence before commitment.
Keeping Attendance and Giving Apart {#attendance-giving}
The two records exist in the same system and their public separation matters.
Giving records identify who gave what, as the tithe and offering article describes.
Attendance records identify who came.
Combining them per person produces a view of each member’s “commitment” that no one should be looking at.
Aggregate correlation — attendance up, giving up — is legitimate leadership information.
Per-person correlation is not, since a church attendance tracking system used to see that a member who stopped coming also stopped giving has turned two pastoral facts into a judgement, and a church attendance tracking system whose access controls keep giving and attendance in separate role views has prevented it.
Never mention giving in an absence follow-up.
Never rank members by either.
Multi-Branch Attendance {#multi-branch}
Churches with several sites need attendance per branch and across the whole.
Per-branch counts by service.
Members assigned to a home branch.
Members attending a different branch recorded there and counted once.
Consolidated attendance for the church.
Comparison between branches, read with care since branches differ in size, age and area.
Branch trends, since one growing and one shrinking is information.
Fellowship attendance per branch.
The branch management article covers the structure, and a church attendance tracking system that shows church-wide leadership every branch’s attendance in one view lets them see which is thriving and which needs attention, while a church attendance tracking system maintained separately per branch cannot show the whole.
Attendance as Pastoral Information {#pastoral}
The per-person record, used rightly, is a shepherd’s tool.
A member’s attendance pattern over time.
Changes in it.
Which gatherings they attend and which they have stopped.
Whether they are connected to a fellowship.
Context for a pastoral conversation.
Held by pastors and care leaders, not broadcast.
Used to notice and to ask, never to confront.
The record is the church’s memory of a person’s presence, since a church attendance tracking system that shows a pastor a member has moved from weekly to monthly over six months has shown a story worth hearing, and a church attendance tracking system accessed only by those with a pastoral reason keeps that story where it belongs.
What Leadership Does With It {#leadership}
Data unused is data collected for nothing, and leadership should have a routine.
Weekly: the count, first-timers, absence flags routed.
Monthly: trends by service and fellowship, flags resolved, children’s ratios.
Quarterly: seasonal comparison, branch comparison, capacity review.
Annually: the year’s pattern, growth, and the report to the membership.
Decisions recorded: services added, fellowships supported, venues changed.
A routine is what makes tracking useful, since a church attendance tracking system reviewed monthly by leadership produces decisions, and a church attendance tracking system whose reports nobody opens produces numbers.
The pastor view exists for this review.
Volunteer Load Against Attendance {#volunteer-load}
Attendance and volunteer capacity should move together and frequently do not.
Attendance rising while volunteer numbers are flat means each volunteer serves more people.
Children’s attendance against children’s workers is the sharpest case.
Ushers against congregation size.
Fellowship leaders against fellowship attendance.
The ratio is a workload indicator, since a church attendance tracking system read beside the volunteer register shows that the children’s ministry has doubled while its team has not, and a church attendance tracking system that surfaces that ratio has given leadership a recruitment target.
The volunteer article covers load and burnout, and this is one of its inputs.
Attendance in Annual Reports {#annual-reports}
The annual meeting hears attendance and the figures should be real.
Average weekly attendance for the year.
Comparison with the previous year.
Per-service and per-branch.
Fellowship and midweek.
Children’s and youth.
Visitors and how many stayed.
Seasonal pattern.
Honest, since an annual report that inflates attendance misleads the members who fund the church, and a church attendance tracking system that produces the year’s figures from weekly counts gives the report a basis, while a church attendance tracking system absent leaves the report to the pastor’s impression.
The report generation article covers the document.
Reporting {#reporting}
A focused set serves leadership without drowning them.
Weekly attendance by service, branch and total.
First-timers this week.
Absence flags open and resolved.
Trend for the past twelve months.
Same week last year.
Fellowship attendance by group.
Children’s attendance and ratios.
Check-in coverage as a proportion of the headcount.
Online alongside, separately.
Absence flags and check-in coverage are the operational measures, since a church attendance tracking system reporting fifteen flags open and check-in covering seventy percent of the congregation tells leadership what the pastoral queue is and how much of the church the per-person layer sees, and the twelve-month trend is the strategic one that a church attendance tracking system should put at the top of every monthly report.
Privacy and Dignity {#privacy}
Attendance records are about people and their handling should reflect that.
Individual attendance never published, announced or displayed.
No lists of absentees circulated to the congregation.
No public recognition of “most faithful attenders”, which shames everyone else.
Absence handled privately by the person who calls.
Members able to know what is recorded about them.
Reasons for absence recorded with restraint, since “bereavement” is enough and the details are not the church’s to hold.
Children’s records held with particular care.
A church that would not read out who gave what should not read out who came, and a church attendance tracking system whose data stays with the people who use it for care keeps the dignity of every member, while a church attendance tracking system whose figures reach the building group has turned care into exposure.
Data Protection {#data-protection}
Attendance is personal data and the Data Protection Act applies.
Who was where and when, over time, is a detailed picture of a person’s life.
Children’s check-in records are children’s data.
Medical notes at children’s check-in are health data with heightened obligations.
Absence notes may contain sensitive circumstances.
Access limited by role: pastors and care leaders for per-person, leadership for aggregate, fellowship leaders for their own group.
Retention defined, since attendance from five years ago serves no pastoral purpose.
Members informed that attendance is recorded and why.
Confirm obligations with qualified advice, and a church attendance tracking system should be configured to whatever position that establishes, since a church attendance tracking system holding years of per-person attendance for hundreds of households with broad access has created an exposure the church did not need.
Introducing It to the Congregation {#introducing}
How tracking is introduced determines whether members check in or resent it.
Explain the purpose: noticing when someone is missing, planning for the people who come, and caring better.
Say what is not done with it: no rankings, no publication, no linking to giving.
Show how easy check-in is.
Make it optional at first and encourage rather than require.
Leaders check in visibly.
Thank people for checking in.
Address concerns directly.
Members who understand it is for their care check in, and a church attendance tracking system introduced from the front by a pastor who says “this is so that if you go quiet, someone will call you” is welcomed, while a church attendance tracking system that appeared as a QR code with no explanation is treated as surveillance.
Common Mistakes {#mistakes}
The errors recur and each is avoidable.
Collecting per-person data with no one assigned to act on flags.
Adding usher counts and check-ins together.
Counting children twice.
Rounding usher counts.
Treating online views as presence.
Comparing May to August.
Publishing individual attendance.
Following up absence with a reprimand.
Linking attendance to giving in a conversation.
Introducing check-in without explaining why.
Ignoring fellowships because they are hard to count.
Never reviewing the data at leadership level.
Each is prevented by purpose and routine, and a church attendance tracking system used for care and reviewed monthly avoids most of them, while a church attendance tracking system adopted as a feature without a purpose falls into several.
Systems and Costs {#systems}
Attendance capability is part of church administration software and the check-in and absence features are what to assess.
Aggregate counts per gathering with method recorded.
QR and phone self check-in linked to the member record.
Household check-in.
Children’s check-in and check-out with matching identifiers and ratios.
Leader-marked lists for fellowships and departments.
First-timer capture feeding visitor follow-up.
Multi-service and multi-branch handling with unique daily counts.
Absence detection with configurable thresholds and routing.
Trend and seasonal reporting.
Role-based access separating per-person from aggregate and from giving.
Pricing commonly from around KES 3,000 monthly for a small church to more for larger or multi-site churches.
Implementation should begin with consistent aggregate counts from the first Sunday, since a church attendance tracking system needs a baseline before trends mean anything.
Then children’s check-in, since that is the safeguarding priority.
Then QR and phone self check-in introduced with explanation.
Then absence detection with a named person per flag.
Weigh it against the family nobody called, since a church attendance tracking system that produces one caring call a week to someone who had gone quiet has done what the church exists to do.
Frequently Asked Questions {#faqs}
Isn’t counting attendance a bit corporate for a church?
The alternative to counting is not humility, it is not knowing — not knowing that a family has been absent six weeks, that a fellowship has stopped meeting, or that the real Sunday number is far below the remembered one. Counting is how a church of any size sees its own people so someone can respond. What matters is the purpose it is used for.
What is the difference between counting heads and tracking people?
Aggregate counts serve planning, trends and honest reporting and carry little sensitivity. Per-person records serve pastoral care and absence detection and carry more. Collect aggregate for every gathering; collect per-person where someone will actually use it to reach out. Per-person data nobody acts on is surveillance without benefit.
How does self check-in work?
A QR code at the entrance and on the screen; the member scans, identifies themselves once, and thereafter it is a scan and a tap, with household check-in so one adult covers the family. Members without smartphones send a short message or give a number at a desk. Both routes feed the same record with no data entry, and QR familiarity from payment makes adoption fast here.
Why does children’s check-in matter so much?
Because it is safeguarding. A tag issued at check-in and required at check-out prevents a child leaving with the wrong adult, and a live room count against the volunteer ratio shows when a room is unsafe before the session continues. Confirm the process against the church’s safeguarding policy and qualified advice.
What should we do when someone is flagged absent?
Have someone who knows them call or visit and ask how they are — not where they were. Listen for the reason, offer help, record the outcome, and never reprimand or imply the absence was noticed as a failing. If a member has chosen to step back, release them with grace. The response is the whole point; a message saying “we noticed you haven’t been in church” does harm the counting was not meant to cause.
Can we see attendance and giving together?
Aggregate correlation — attendance up, giving up — is legitimate leadership information. Per-person correlation is not; seeing that a member who stopped coming also stopped giving turns two pastoral facts into a judgement. Keep the two in separate role views, never mention giving in an absence follow-up, and never rank members by either.
Our attendance drops every August. Are we declining?
Compare August to last August, not to May. School holidays, the rains, harvest, upcountry travel and exam periods all move attendance, and a trend read without the seasonal pattern mistakes a holiday for a decline. Record local seasonal factors so future years can be read properly.
How do we introduce it without people feeling watched?
From the front, by a pastor, with the purpose stated: “so that if you go quiet, someone will call you.” Say what is not done — no rankings, no publication, no linking to giving. Make check-in easy and initially optional, have leaders check in visibly, and thank people. A church attendance tracking system explained that way is welcomed; a QR code that appeared without explanation is treated as surveillance.
