Scout keeps track of who has served, who needs a rest week, and who is waiting to be asked.

Scout reads who is on rotation, who has served the most weeks without a break, who declared a skill on their own profile, and who said they’re open to serve but hasn’t been asked yet. You decide what to do with it.

Today

The five-person rotation.

Every Sunday is built on the same five reliable volunteers, and they have been serving without a break for months.

Recruitment starts cold. You scroll the directory and text the same handful of people, some of whom said yes once and haven’t answered since.

A member who used to be a nurse would probably love to help with first aid, and nothing in your system has ever asked her.

On Scout

The thirty-person bench.

Members declare what they’d love to help with on their own profile, including skills, openness to new roles, and availability, all in their own words.

When a slot opens, Scout suggests three people who said they’re open to this role and haven’t been asked recently. You invite them in two clicks.

After they serve, Scout asks how it went. When the same people keep answering that it was difficult, you see it while the pattern is still forming.

What Scout knows about your volunteers.

  • The bullpen knows who to ask next

    Recruitment starts from people who said they’re open.

    Members declare on their profile what they’d love to help with and how often. When a slot empties, Scout suggests three names, ranked by capacity match, reliability, and how recently they served. The suggestions come from the whole church, including people you haven’t worked with yet.

    How serving works
  • Post-serve feedback you read

    Feedback takes a volunteer about sixty seconds.

    Scout asks every volunteer how it went after they serve: difficult, fine, good, or great, plus an open line for anything else. Over weeks you can see which Sundays were hard, which roles keep coming back difficult, and which volunteers have been answering that way for a while.

    Read about what Scout notices
  • Capacity members declare for themselves

    About them, in their own words.

    Members fill in their own profile with the skills they have, the roles they’re open to, and when they’re free. When you need someone who can run A/V, Scout already knows who has said they can.

    See member self-service

What Scout says to you.

The serving loop reports back to you: how each serve actually felt, and when a pattern needs a person.

How the intelligence works
Scout noticed

Marked their last Kids Ministry serve “difficult.” Asked again two weeks later, and declined.

The difficult serve and the decline happened weeks apart, on different screens. You hear them as one sentence.

Scout noticed

You followed up with Jess on Jul 19. How did that land?

After you check in with a volunteer, Scout circles back to ask how it went. Once it's handled, it stops coming up on its own.

What Scout doesn’t do for volunteer teams yet.

  • Scout doesn’t auto-rotate teams to prevent burnout yet. It surfaces who’s been on for six weeks; you decide how to rest them.
  • Scout doesn’t handle volunteer swaps between members in-app. They negotiate the swap; you confirm in Scout.
  • Scout doesn’t track volunteer training certifications or background-check expiry. Those onboarding gates still live in your existing process.

Come find the volunteers your church already has.

  • Bullpen suggestions
  • Post-serve feedback
  • Capacity declared
  • 30-day trial