What's the Mission?

Rock's Check-In system is extremely flexible, and this extraordinarily helpful!  It means that you can quickly respond to any ministry needs when they become clear.  But if you're not careful, this flexibility can make it difficult to keep everything straight, especially as size and complexity change.

• "Why is this kiosk not working?"
• "Did someone remember to change all of that back after Wednesday?"
• "Wait... How am I supposed to set up this iPad?"

When managing Rock for our teams, it's important that we make sure that these questions are the last things on their mind on a weekend while they connect with attenders. Tools like Rock should burden pastors with extra work and worries.  Rock should solve those worries.

To make Rock Check-In excellent on a weekend (and to avoid creating a ton of upkeep and technical debt that slows down future changes) we had to build a sustainable way to implement Check-In without needing to train all ministry teams to be Rock Check-In experts.

What's at Stake?

We currently manage about 450 physical Check-In devices.  We have 7 different "Kiosk personas" per campus (used on about 10 devices), 45 campuses, and different campuses have Kiosks serve different roles between Weekend Services and Wednesday.

Since we launched Rock Check-In back in 2019, we have no recurring Kiosk issues & no recurring Kiosk complaints in the thousands of services held across all of our locations since launch.

What's the Cost?

• We don't have to maintain any custom plugin
• We don't have to maintain custom check-in clients
• We don't have to maintain a fleet of shortened urls

This whole solution is built & managed using core tools (Lava and Attributes).  And you can probably have a testable version of this ready at your Church if you have an afternoon set aside to dig into this article.  (It took us a couple of days from idea to testable when we first built it)

Check-In at Life.Church