Absence Alerts
Getting Started
IntroductionStart a ChurchInitial SetupChurch ProfileCampusesLogoModulesSystem ConfigurationUsers & Roles
OverviewCreating UsersRole MatrixFlock Leader ScopesCustom FieldsConnect CardFirst-Time VisitorsPrivacy RequestsFinance Settings
OverviewFundsFiscal YearOnline Giving SetupStatement ConfigPayment MethodsBank AccountsSecurity
OverviewActivity Log
Activity LogStart Fresh
Start FreshAbsence Alert Scan
GatherThe Absence Alert Scan is a weekly background job that finds people who have stopped coming to church. It creates alerts that appear on the Gather dashboard and the Alerts page, so pastoral staff can follow up.
Schedule
When: Every Monday at 7am (your church's time). Settings → System → Background Jobs can also run it now.
How It Works
The scan counts weeks, not services of one schedule. A week counts for a person when their campus held a service that week with people checked in by name. Coming to any service that week, at any time and at any campus, means they attended. Someone who moves from the 10 AM to the 1 PM service, or to a Friday night service, is never flagged for the service they left.
- The scan looks at everyone who has ever been checked in by name. Archived and merged people, and people on the Inactive status, are never flagged.
- For each person it finds the last week they came, then counts the weeks since then that their campus held a service with a named check-in. That number is the person's missed count.
- When the missed count reaches the threshold, the person is flagged. When someone with an alert came back, their alert is resolved.
- Each person gets one decision per run: a new alert, an updated alert, a resolved alert, or nothing. A run never resolves someone and flags them again.
Services counted only by headcount, cancelled services and services that are not over yet are not counted. Children are flagged like everyone else.
Configuration
| Field | Type | Description |
|---|---|---|
| Absence alert threshold | 1 to 5 weeks in a row | Settings → System → Configuration → Absence Alerts. How many weeks in a row a person misses church before an alert is created. Default: 2. |
The threshold is the only setting. The scan counts every service with a named check-in and runs on the schedule above.
Alert Lifecycle
| Field | Type | Description |
|---|---|---|
| ACTIVE | Status | Newly created or refreshed alert. The member has missed the threshold number of services. |
| ASSIGNED | Status | A staff member has been assigned to follow up. The scanner will not overwrite this status. |
| SNOOZED | Status | Temporarily hidden. A snoozed alert stays snoozed until its date, even while the person is still missing. The scanner resolves it if the person returns. |
| RESOLVED | Status | The member has returned to a service. Resolved alerts have a 7-day cooldown before the scanner can recreate them. |
| DISMISSED | Status | Manually dismissed by staff. The scanner will not recreate this alert. |
Auto-Resolution
When a person with an active or snoozed alert has come back (their missed count is now below the threshold), the scanner resolves their alert by setting the status to RESOLVED and recording the resolution time.
What Gets Tracked
| Field | Type | Description |
|---|---|---|
| Missed Count | Integer | The number of weeks their campus held a service with a named check-in since the last week they came. |
| Last Attended Instance | Reference | The most recent service the person attended, at any campus. |
| Last Attended At | Timestamp | The start of the last service they came to. It is never inside the missed weeks. |
| Campus | Reference | The person's campus, or else the campus that hosted the last service they came to. |
Job Output
Each run produces a summary logged to the system:
- Scanned: total members evaluated for absence
- Created: new alerts generated
- Updated: existing alerts refreshed with new missed counts
- Resolved: alerts auto-resolved because the member returned