Serve Stats
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 FreshServe Stats and Burnout Detection
ServeThe Serve module runs several background jobs to keep volunteer statistics current and protect volunteers from burnout. These jobs feed the Serve dashboard, volunteer profiles, and team leader notifications.
Job Schedule
Times are in your church's timezone. The Run Now column is what Settings → System → Background Jobs offers.
| Field | Type | Description |
|---|---|---|
| serve-stats-recalc | Daily at 2:00 AM | Recomputes serve counts, confirmation rates, and estimated hours for every team membership, past members included. Run Now: yes. |
| burnout-scan | Mondays at 1:00 AM | Identifies volunteers serving significantly more than their team average and notifies team leaders. Run Now: asks first, because every team leader is notified again and dismissed burnout alerts are opened again. |
| serve-escalation | Every 6 hours | Finds confirmation requests that have timed out and assigns the slot to the next available volunteer, who is emailed. Run Now: asks first. |
| serve-reconfirmation | Daily at 10:00 AM | Sends "Still coming?" reminder emails to confirmed volunteers whose service is within the next 24-48 hours. Run Now: not offered, because a second run the same day would email volunteers again. |
Serve Stats Recalculation
This nightly job works out the statistics for every team membership in your church, past members included, because their figures are still shown. Served means confirmed at a service that has happened: not cancelled, and started before your church's now. An upcoming confirmed service is never counted as served. The following metrics are calculated:
| Field | Type | Description |
|---|---|---|
| Serve Count (90 days) | Integer | Times served in the last 90 days. |
| Serve Count (YTD) | Integer | Times served since the start of your church's reporting year (its fiscal year), on your church's clock. Each slot counts once. |
| Serve Count (All Time) | Integer | Times served ever. |
| Estimated Hours (90 days) | Decimal | Estimated volunteer hours in the last 90 days (serve count x 2 hours per service). |
| Confirm Rate | Decimal or none | Confirmed out of answered (confirmed + declined, the slot status the pages show) for services from 90 days ago on, upcoming ones included. When nothing has been answered there is no rate, shown as "—", never 0%. |
| Last Served At | Timestamp | The most recent service served at. |
| First Served At | Timestamp | The earliest service served at. |
Burnout Scan
Every Monday at 1 AM (your church's time), the burnout scanner evaluates each active team and compares individual serve counts against the team average:
- For each team, calculate the average 90-day serve count across all members
- Flag any member whose 90-day count exceeds the average by the configured threshold multiplier (default: 2x)
- Create or update a
BurnoutAlertrecord for flagged volunteers - Send an in-app notification to the team leader with the volunteer's name, their serve count, and the team average
Configuration
| Field | Type | Description |
|---|---|---|
| Burnout Threshold Multiplier | Decimal | A volunteer is flagged when their 90-day serve count exceeds (team average x multiplier). Set in Settings → System → Configuration → Serve (1.5, 2.0, 2.5 or 3.0). Default: 2.0. |
Escalation Check
Every 6 hours, the escalation job looks for volunteer confirmation requests that have gone unanswered past the configured timeout (default: 48 hours):
- Find pending slot confirmations where
sentAtis before the cutoff and no response has been recorded - Mark the confirmation as declined with a note “Auto-escalated: no response”
- Set the serve slot back to OPEN status
- Attempt to auto-assign the slot to the next best available candidate (not blacked out, not already assigned, not overloaded)
- If no suitable candidate is found, the slot remains open for manual assignment
Escalation Configuration
| Field | Type | Description |
|---|---|---|
| Escalation Timeout | Hours | How long to wait for a volunteer response before escalating. Configured via Tenant Configuration (serveEscalationTimeoutHours). Default: 48 hours. |
Re-confirmation Emails
Daily at 10 AM (your church's time), the re-confirmation job sends reminder emails to volunteers who have already confirmed but whose service is coming up within the configured window (default: 24-48 hours).
The job respects user notification preferences: if a volunteer has muted SERVE_REMINDER_DUE notifications or disabled email for that type, the reminder is skipped.
Re-confirmation Configuration
| Field | Type | Description |
|---|---|---|
| Hours Before Service | Hours | How far before the service to send re-confirmation. Configured via Tenant Configuration (serveReconfirmHoursBefore). Default: 48 hours. |