Workflows are flexible — anything that has a few steps and needs follow-through can become one. Here are the most common pipelines churches build.
Volunteer Application
Someone fills out the "I want to serve" form on your website. Their card lands in the first column of the Volunteer Application workflow. A leader reviews it, conducts a quick interview, and (if a background check is required for that ministry) the next stage automatically kicks off the check. When the check clears, the card advances to onboarding, then to the team they'll be serving on.
Get Baptized
A guest signs up to be baptized. Their card moves through pastor follow-up → baptism class → scheduling → baptism day → follow-up touch. Every step is visible to the pastoral team, and nothing gets lost between Sunday services.
Pastoral Care / Prayer Requests
A request comes in through the website or in person. The card lands in the on-call pastor's queue. They contact the family, log notes, and either close the card or escalate to ongoing care.
Leadership Development
A multi-month track for raising up future leaders. Cards move through Prospect → Assessment → Coaching → Growth Track → Hiring Process → Hired (or Removed). Unlike a public form, leadership pipelines usually start with a leader manually adding the person to the first column.
New Believer Follow-Up
Someone made a decision at a service. A card is created and moves through pastor call → next-steps class → a mentor pairing → ongoing discipleship.
What every workflow has in common
- An entry point — either a public form or someone manually adding a card.
- A series of stages — each with someone assigned to do the work.
- A finish line — a terminal stage that closes the card out.
- A history — every move, comment, and approval is logged on the card.
You can build as many workflows as you need. Most churches start with one or two and add more as patterns emerge.