Why we built offline QR check-in (and why it matters for your church event)
Three weeks after Gathrd launched, a church leader emailed me. They'd booked 200 people for a prayer conference in rural Wales. One problem: the venue had no reliable internet. They asked if our QR check-in would work without it. At that moment, I realised we'd designed for cities, not the church as it actually exists.
The gap between how we assumed churches work and how they really do
I spent the first month after launch reading every email and message from organisers. Most were straightforward: "How do I set up Gift Aid?" or "Can I list my retreat?" But there was a pattern I couldn't ignore. Rural churches. Conference venues in the Cotswolds with patchy mobile signal. A cathedral with stone walls that block WiFi. Monasteries. Village halls. Caravan parks where events happen.
What struck me wasn't the problems themselves. It was how apologetic people felt asking about them. "I know this is probably a silly question," one organiser wrote, "but do you need internet for check-in?" They'd already chosen Gathrd over Eventbrite because of Gift Aid and the lower fees. But they were genuinely unsure if we'd actually work in their real world.
That email landed on a Wednesday. By Friday, offline QR check-in was on our roadmap.
You can't ask people to depend on something that might disappear
Building offline support isn't complicated. But it's one of those features that only feels necessary once you've shipped. Before that, it's easy to assume your users have decent connectivity. Most app makers work in cities. Most cities have signal.
But churches aren't geographic abstractions. They're in market towns. They're in valleys. They're in 200-year-old buildings where WiFi doesn't reach the entrance hall. And once you've promised someone they can use your platform to manage their event, you can't then say, "Oh, but only if the internet cooperates."
That's the opposite of what we built Gathrd to be. We wanted to remove friction from running faith events, not add it. So we made offline QR check-in work even when the mobile signal doesn't. Organisers scan tickets at the door with no internet connection. The app stores the check-ins locally and syncs them once you're online again. No lost data. No manual workarounds.
Then we added NFC because some venues are even older
After offline QR went live, we got another request. A cathedral had a 12th-century stone entrance. The lighting was dim. Volunteers were scanning QR codes and struggling to read them off people's phones. They asked if we could support NFC cards instead, so attendees could just tap their way in.
We partnered with TapTrust, an NFC provider, and now Gathrd organisers can offer both. Some events use QR. Some use tap cards. Some use both. The point is the same: your check-in should work the way your event actually needs it to, not the other way around.
It's a small feature. But it's the kind of small feature that makes the difference between "this app is designed for our church" and "we'll probably use something else." We chose to build it because we weren't interested in building for a hypothetical version of the church. We were interested in building for this one.
Offline support is a philosophy, not just a technical choice
A few months in, I noticed something. Most of the people using offline check-in weren't in villages. They were in London, Manchester, Birmingham. Good signal everywhere. But they used offline check-in anyway, because they liked knowing it was there. It removed a worry they didn't even realise they had.
That changed how I thought about the feature. Offline support isn't really about rural churches, though it helps them. It's about trust. It's about knowing that if the one day your event happens and three things go wrong, your check-in system won't be one of them. Your internet connection might flake out. Your phone might die. But Gathrd will still work.
That's the kind of reliability you'd expect from a platform built for churches, not borrowed from a generic events company. Churches are relying on you to handle something real: the people who show up, the money they give, the experience they have. You can't treat that casually.
The things we didn't build matter as much as what we did
I mention offline check-in because it's a good example of something we've tried to do consistently at Gathrd: listen to what church organisers actually say they need, not what we think they should need.
We kept the 3% platform fee instead of copying Eventbrite's 6.95% plus per-ticket charge because church budgets are already stretched. We automated Gift Aid splits at checkout because treasurers asked for it. We made the directory faith-only because churches told us they didn't want their worship night listed next to nightclubs. We added denomination filtering because a Baptist organiser said it would help their community find the right events faster.
None of these are flashy. Most people won't know they exist until they need them. But each one came from a real conversation with someone trying to run a real event, not from a product roadmap handed down by a marketing team.
If you're running a church event, the question probably isn't whether Gathrd has offline check-in. It's whether the platform you're using was built by people who actually understand what you need. Have you ever chosen a tool because it solved a problem you didn't know you had until you tried it?