Gold Circle Award Winner 2026

Athens Church · Golden Circle · Rock Innovation

Helping people find
the right group.

Our Groups Team changed how groups begin. We rebuilt the finding, the signing up, and the communication around the first night — entirely inside Rock.

The Why

The first night should
feel like your group.

The Groups Team commissioned this project around a simple shift: begin with the person, then use Rock to guide them from choosing a group through meeting that group for the first time.

What needed to change

A good idea needed
better support.

One night for everyone

A single Sunday created schedule conflicts and confusion about when a group actually started.

A cumbersome experience

The finder worked, but narrowing a long catalog through the same filter interface felt clunky and required too much work from the person using it.

A back end built for one night

Managing dates, rooms, and reminders had become complicated. The systems needed to support a full week of launches.

What we built

A clearer path from
choosing to showing up.

Five nights, each group’s own

Monday groups launch on Monday. Tuesday groups launch on Tuesday. The first meeting fits the rhythm people chose.

Relevant questions. Useful suggestions.

A branching wizard asks questions that fit the person. Best matches come first, with other suggestions when a preference hasn’t been recorded.

The right message at the right time

Confirmations, reminders, and roster updates follow each group’s own event time, keeping leaders and members connected before they arrive.

Athens Church Groups team gathered for a group photo
“The biggest improvement was shifting the entire experience to be built around the user rather than around the groups we had available. Previously, the experience was essentially, ‘Here are the groups we offer—find one that works for you.’ Now, we start with the person: What kind of group are you looking for? When are you available? What fits your life? Then we help match them with the best options.”
Kathryn FlemingKathryn FlemingNext Steps Director · Athens Church

The How

More than
a finder.

The search is one part of a connected process. Leaders create the groups, people choose where they belong, and Rock keeps the details moving between them.

  1. Create Your Group

    Leader applications move through Connection Requests. Approved leaders create their own group, meeting time, and personal details.

    Learn More
  2. Choose Your Group

    People answer relevant questions, explore the suggestions, and register for their own group. No login is required.

    Learn More
  3. Connect with Your Group

    A nightly digest gives leaders the changes to their roster. Members receive confirmation and details for their first night.

    Learn More
  4. Meet Your Group

    Reminders follow the group’s own night. Roster follow-up and surveys close the loop; the finder follows the season’s schedule.

    Learn More

Self-selection and leader-created groups were already in place. This rebuild improved the experience of choosing and the systems supporting a multi-day launch.

The User Experience

A few answers.
A place to start.

Try the finder with sixty invented groups. Explore the questions, change your preferences, and see how the suggestions respond.

View Demo

This is a demonstration. Nothing registers anyone. The live finder opens around each Group Launch; the next launch is January 2027.

Group Finder / Interactive demo

Finder results showing men’s, married, college women’s, college men’s, women’s, and coed groups beside editable preferences

The Backend Experience

Built entirely
inside Rock.

The finder and launch process use live Rock data, with Lava, schedules, workflows, and communications working together.

Lava Application + HTMX

Seven endpoints update the wizard one step at a time without a full page reload.

Shortcode + Lava

The Group Finder shortcode provides candidate groups. Lava separates known mismatches from missing preferences.

Defined Types + Attributes

Group attributes supply the filter vocabulary. Defined Values provide the opening cards and their destinations.

Schedules + Data Views

Schedules set event times and the registration window. Data Views identify each night’s cohort.

Workflows + Communications

Registration, reminders, roster changes, and surveys stay connected to the group’s own launch.

Connection Requests

Leader applications move through a tracked review process before groups reach the catalog.

A closer look

The pieces behind the experience

Selected excerpts from the project’s captured Rock application. These illustrate the approach; they are not a standalone installation.

The classification pass

Endpoint 28 asks the shortcode for candidate groups with no filter children at all, then classifies each one itself. Two counters decide where a group lands: gfFails means a real mismatch, gfUnknown means we simply have no value recorded. That second counter is what the whole two-tier result rests on.

{[ groupfinder origin:'73198' grouptypeids:'130'
   include:'Group.Schedule,Group.GroupLocations' maxresults:'500' ]}

  {% for result in MatchedGroups %}
    {%- comment -%}
      gfFails   > 0  -> excluded
      gfUnknown > 0  -> "Other Suggestions"
      both zero      -> "Your Best Matches"
    {%- endcomment -%}
    {% assign gfFails = 0 %}
    {% assign gfUnknown = 0 %}

Lava Application endpoint 28 · step-results

A missing preference

Every preference filter follows this shape. A group with no value recorded increments gfUnknown and stays in the running as a suggestion. A group with a value that genuinely doesn't match increments gfFails and drops out. Reads use 'RawValue' to return GUIDs — the default read returns display labels and would never match.

{% if ageRangeGuidsRaw != '' %}
  {% assign v = result.Group | Attribute:'Ages','RawValue' %}
  {% if v == '' or v == null %}
    {% assign gfUnknown = gfUnknown | Plus:1 %}
  {% else %}
    {% assign hit = false %}
    {% for sel in selAges %}
      {% if v contains sel %}{% assign hit = true %}{% endif %}
    {% endfor %}
    {% unless hit %}{% assign gfFails = gfFails | Plus:1 %}{% endunless %}
  {% endif %}
{% endif %}

Lava Application endpoint 28 · the Ages filter

Category and gender stay strict

Group category and gender behave the opposite way on purpose. A missing value excludes, because category is identity rather than preference — someone asking for a Married group must never be offered a College group, not even as a suggestion.

{% if communityTypeSelectionGuid != '' %}
  {% assign v = result.Group | Attribute:'CommunityGroupType','RawValue' %}
  {% if v == '' or v == null %}
    {% assign gfFails = gfFails | Plus:1 %}
  {% elsif v contains communityTypeSelectionGuid %}
  {% else %}
    {% assign gfFails = gfFails | Plus:1 %}
  {% endif %}
{% endif %}

Lava Application endpoint 28 · category filter

The opening cards

The wizard's opening cards aren't in the template. Each one is a Defined Value carrying its own title, colour, icon, description and the endpoint it routes to — so the first screen is data, not code.

{% definedvalue where:'DefinedTypeId == 207' sort:'Order' loadAttributes:'true' %}
  {% for dv in definedvalueItems %}
    {% if dv.CategoryName == 'Group Type Selection' %}
      {% assign isEnabled = dv | Attribute:'Enabled' %}
      {% if isEnabled == 'Yes' %}
        {% assign iconClass = dv | Attribute:'SelectionIconClass' %}
        {% assign color     = dv | Attribute:'SelectionColor' %}
        {% assign endpoint  = dv | Attribute:'SelectionEndpoint' %}
        ...
      {% endif %}
    {% endif %}
  {% endfor %}
{% enddefinedvalue %}

Lava Application endpoint 32 · step-grouptype

The launch window

The schedule defines the registration window: 21 days before the next launch until one hour before it. The template checks that the window has usable dates before deciding whether to show the finder.

{% schedule id:'1092' securityenabled:'false' %}
  {%- for sched in scheduleItems -%}
    {%- assign launchDate = sched.NextStartDateTime | Date:'M/d/yyyy h:mm tt' | Default:'' -%}
  {%- endfor -%}
{% endschedule %}

{% if launchDate != '' %}
  {% assign groupsopen = launchDate | DateAdd:-21,'d' | Date:'M/d/yyyy h:mm tt' | Default:'' %}
  {% assign launchEnd  = launchDate | DateAdd:-1,'h'  | Date:'M/d/yyyy h:mm tt' | Default:'' %}
  {% if groupsopen != '' and launchEnd != '' %}
    {% assign nowStr = 'Now' | Date:'M/d/yyyy h:mm tt' %}
    {% assign between = nowStr | IsDateBetween:groupsopen,launchEnd %}
  {% endif %}
{% endif %}

Content block 5207 · page 1096

Messages timed to each group

One workflow serves all five launch nights. Every delay is computed from that group's own event time, so the roster reminder reaches a leader ninety minutes into their evening — not a fixed hour for everyone.

{% assign eventDT = Workflow | Attribute:'EventDateTime'
                    | AsDateTime | DateAdd:90,'m' %}
{{ eventDT | Date:'yyyy-MM-dd' }}T{{ eventDT | Date:'HH:mm:ss' }}

Leader track:  day-of text -> delay to post-event -> roster reminder
               -> delay to next day -> survey email
Member track:  day-of text -> delay to post-event -> survey

Workflow 555 · Group Launch | Daily Communication

The Results

The relationship starts
before the first night.

The project produced meaningful improvements across the journey. Some appear in measurable shifts in attendance and finder behavior; others are qualitative, reflected in the experience of the people choosing groups and the leaders welcoming them.

Showing up

A larger share of invited people attended.

On matched launch weekdays, show-up rose from 69.0% to 78.5%—an increase of 9.5 percentage points from August 2025 to August 2026.

How we measured attendance

Distinct people who attended divided by people messaged that night. The comparison uses Sunday, Monday, and Wednesday in both years. Tuesday is excluded because a 2026 WiFi outage prevented check-in. Duplicate launch and community-group check-ins count once.

Matched launch weekdays
SeasonMessagedAttendedShow-up
August 202558440369.0%
August 202649839178.5%

This is a year-over-year comparison of the launch experience. It does not isolate the effect of the finder.

Time on the finder

More visits lasted a minute or less.

Among finder-only sessions, the share recorded at 60 seconds or less rose from 53.7% to 88.9%. Visits over five minutes fell from 8.9% to 2.5%.

How we measured visit duration

Rock records a minimum duration of 60 seconds, so no finer timing is claimed. The same floor applies in both years. Only sessions containing finder activity and nothing else are included: 1,768 of 4,175 sessions in August 2025 and 1,965 of 4,111 sessions in August 2026.

Sessions over one hour are excluded from both years: 97 in 2025 and none in 2026. Mean duration was 149.9 seconds in 2025 and 82.4 seconds in 2026. Session duration does not establish that a visitor registered or found a group.

Control stays with the person

People manage their own group changes.

When someone chooses a different group, Rock recognizes that they already belong to one and asks whether they want to keep it or move to the new group. The person stays in control of their own experience, and staff can spend launch night supporting people and the event instead of processing membership changes at a table.

Evidence from the registration workflow

Across the life of the current workflow, 39 people chose “Yes, Change Groups” and 16 chose “No, Keep Me In That Group.” Each of those 55 decisions was resolved by the person in Rock without a staff conversation.

Leaders reach their people first

The first meeting isn’t a blind date.

The nightly roster digest gives leaders what they need to make contact before the first meeting — helping people know who to look for and where to go.

Group Launch participants celebrating with colorful confetti
“This new process allowed our team to move away from simply presenting the groups we had available and toward intentionally guiding people to the right next step. The improved functionality made the process easier for the user while also helping us accomplish our larger goal as a team: connecting more people into meaningful community. Ultimately, it was a win-win—a significantly better experience for the person looking for a group and a more effective tool for our team to help people get connected!”
Kathryn FlemingKathryn FlemingNext Steps Director · Athens Church

Where we’re going next

Put the season
in the team’s hands.

Coming January 2027

Leaders already build their own groups. People already choose their own group. Season configuration still depends on the developer.

A prototyped staff console would let the Groups Team choose available group types and nights, and control their own season through Defined Values. That’s the next step in moving the work closer to the people doing the ministry.

Built in partnership

+

A connected Group Launch experience, from creating a group to showing up for the first meeting.