Circles Health
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 FreshCircles Health Score
CirclesThe Circles Health Score job computes a composite health rating for each active small group based on attendance, meeting consistency, and group size. The score is used to surface struggling groups on the Circles dashboard and help leaders identify groups that need attention.
Schedule
When: Daily at 4:00 AM, in your church's timezone.
The job recalculates the score for every group in your church in one pass. Taking attendance doesn't recalculate a group's score on its own, so a meeting logged today shows up in the score after the next 4 AM run. A Super Admin can run it sooner with Run Now on Settings → System → Background Jobs (circles-health-score). It sends no email and no notifications.
How It Works
The health score algorithm evaluates three dimensions and produces a weighted composite score from 0 to 100:
Scoring Dimensions
Each part is scored 0 to 100. A meeting still to come never counts as missed.
| Field | Type | Description |
|---|---|---|
| Attendance | 45% weight | The member attendance rate over the group’s last 8 meetings dated today or earlier that had attendance taken: members present out of members marked present, absent or excused. Prospects and visitors are left out. 50 when no meeting has had attendance taken. |
| Consistency | 35% weight | The meeting rate over the group’s last 8 expected meetings on its meeting calendar (see the Circles overview): the share held with attendance taken. Breaks and an excused “Didn’t meet” are not among the 8; a “Didn’t meet” for any other reason and a meeting not recorded count as not held. So a group that simply stops recording scores lower, week by week. A group with no calendar (no schedule that can be worked out and nothing planned) is scored on the share of its last 8 meeting logs that had attendance taken, 0 with none. |
| Size | 20% weight | From the active members (prospects excluded): 6 to 15 members score 100, fewer than 4 score 30, more than the group’s capacity (30 when none is set) score 40, and any other size 70. |
Composite Calculation
Each part's points are rounded: Attendance × 0.45, Consistency × 0.35 and Size × 0.20. The score is exactly the sum of those three points, so the breakdown on the group's page always adds up to the score. Super Admin's “recalculate all” uses the same rule.
What Gets Stored
| Field | Type | Description |
|---|---|---|
| Overall Score | 0-100 | The composite health score, stored in the CircleGroupHealthScore table with dimension = OVERALL. |
| Previous Score | 0-100 | The previous OVERALL score, used to calculate trend direction (improving, declining, stable). |
| Period | Date range | The run’s 90-day look-back (periodStart to periodEnd). One row per run; the latest 20 are kept per group. |
| Factors | JSON | The three parts (attendance, consistency, size), the member count, the meetings with attendance taken, the meetings read, and whether consistency came from the meeting calendar or the meeting logs. The group page prints its breakdown from these. |
| Denormalized Score | Integer | The healthScore field on the CircleGroup record is updated directly for fast querying and dashboard display. |
Included Groups
The job scores all groups that are not in CLOSED, MERGED, or ARCHIVED status. This means active, paused, and forming groups all receive health scores.
Interpreting Scores
- 70-100 (GREEN): Healthy. The group is meeting consistently with good attendance and appropriate size
- 45-69 (AMBER): At risk. Some areas could improve (e.g., inconsistent meetings or declining attendance); consider reaching out to the group leader
- Below 45 (RED): Critical. The group may need leadership support, restructuring, or to be merged with another group
Job Output
Each run reports how many groups received a new health score. If the run fails, the Background Jobs page shows it as Failed with the error.