The night the WiFi failed, and why offline QR check-in became non-negotiable

Why this story matters more than you'd think

That church leader didn't panic. They didn't have to hand-count attendance on a clipboard. They didn't lose a single registration. When the WiFi came back online, every check-in synced automatically.

It sounds like a small thing. Until you've stood in a church lobby with three hundred people queuing to get in, and your registration software has just gone dark because the internet hiccupped.

We built offline QR check-in into Gathrd because we'd heard this story too many times. Church WiFi networks are often stretched. Community halls have spotty coverage. And when you're running an event with real people turning up in real time, there's no margin for technical failures. The door check-in has to work, full stop.

What offline support actually solves

Let's be concrete about what happens. When you check someone in at the door using a QR code in Gathrd, the system works whether your internet is live or not. Each ticket scanned gets logged locally on the device. The moment your connection returns, everything syncs back to your event dashboard. No duplicate entries. No lost data.

This matters for a few specific reasons. First: reliability during the actual event. You're already managing music, seating, announcements. The last thing you need is to troubleshoot software. Second: most churches and community organisers aren't IT teams. They need things that just work. Third: if you're running a ticketed event, you need an accurate count of who paid and who showed up. That accuracy can't depend on a broadband connection being perfect when you need it.

We've also integrated NFC via TapTrust for churches that want tap-to-check-in alongside QR codes. Same offline principle. Different input method. Some organisers prefer it because it's faster at high-volume doors.

The difference between faith events and other platforms

Eventbrite and similar platforms are built for concerts, festivals, and ticketed experiences where the organiser often has dedicated technical support on site. A church running a Saturday prayer gathering? Usually one or two volunteers managing the door. They need something solid and simple, not a platform that requires a strong internet connection to function.

That's also why we price differently. Churches pay 3% on paid tickets. No hidden per-ticket fees. Eventbrite charges 6.95% plus £0.59 per ticket, which adds up quickly when you're running events on a volunteer budget. For a 200-person event at £10 per head, that's the difference between keeping £1,000 and keeping £870.

But the offline check-in is the feature that gets mentioned in our feedback most often, especially from larger church networks and conference organisers. It's not flashy. It doesn't photograph well in marketing materials. But when your event is happening, and your tech is reliable, people notice. They remember it for next time.

How it actually works in a real event

Walk through a practical scenario. You're running a retreat for sixty people. You've sold twenty discounted tickets online, forty are on the door. Your venue is a country retreat centre with patchy mobile signal. You open Gathrd on a tablet at the entrance, pull up your event dashboard, and enable check-in mode. The tablet downloads a local copy of all attendees and ticket data. From that point on, it doesn't matter if there's no signal.

People arrive. Volunteers scan their QR codes with a handheld device or phone running Gathrd. Each scan registers locally. Your door counter goes up. Halfway through the event, someone orders two last-minute tickets on the app. They arrive. You scan them in. All of this happens offline. Later, when you drive home and hit better signal, everything syncs. Your ticketing dashboard updates. Your financial records align. Your attendee list is complete.

Gift Aid claims work the same way for UK churches. You can log which attendees are Gift Aid eligible during check-in, and it's all reconciled when the data syncs. We've had several medium-sized churches tell us they've saved hours on post-event admin because the data was already clean and linked.

What we learned building this

The honest version: we didn't start with offline check-in as a feature. We added it because organisers kept telling us they needed it. Early users were trying to run events in village halls, community centres, and church buildings where internet wasn't guaranteed. Some were in rural areas. Some were in urban venues with networks so locked down that guest WiFi barely functioned.

We could have said, 'Just get better internet.' That's what some platforms essentially do. But we chose to solve the problem instead. That's become part of how we think about Gathrd. We're building for the real world that churches and community event organisers actually live in. Not the ideal world with perfect connectivity and professional AV teams.

The same thinking applies to pricing. Why does Eventbrite charge a per-ticket fee? Because they can. Because most events platforms are built to extract value at scale. We charge a simple platform fee and nothing else because churches are running on margins, and every pound matters.

The ripple effect of reliability

Here's what's interesting. When an organiser knows their check-in system won't fail, they run events differently. They're more confident about scaling up. They try new event formats. They worry less about technical headaches and more about the actual experience. One church leader told us they'd moved an entire conference online and then in-person hybrid because they knew Gathrd would handle both ticketing and door check-in reliably.

That's not a small thing. Event reliability shapes what event organisers attempt. It shapes their confidence. It shapes the experiences they're able to create for their communities.