The Missing Check-In Screen, and What It Could Cost a Church

Churches should verify event-day access before selecting a software plan. Ask which roles can use each feature, what limits apply during a live event, and have someone demonstrate the exact workflow your team will need.

In April 1970, Apollo 13’s lunar module had a carbon-dioxide problem. The crew had spare filters in the command module, but they were square and the lunar module system required round ones. At Mission Control in Houston, engineer Ed Smylie led the effort to build an adapter from materials already on board. The fix had to work with the equipment the astronauts could actually reach, under the conditions they actually faced. NASA’s Apollo 13 Flight Journal documents the mission and the improvised filter solution.

A conference administrator has a smaller version of that problem at 4:17 PM on a Friday. Registration is open. Volunteers are arriving. Then the check-in screen is missing from the account assigned to the welcome desk.

The plan looked suitable in a pricing table. The event-day role did not have the access needed to use it.

The plan name does not prove the workflow

A church can buy a plan that includes event management and still discover too late that check-in access depends on a particular role, a seat limit, a configuration setting, or an admin account that nobody at the venue can use.

That discovery changes the shape of the day. An usher starts searching for a coordinator. A coordinator calls someone with higher access. Members form a queue while people try to find a phone, password, or laptop that works.

For a church preparing a conference, the question is not “Does this plan have check-in?” Ask: “Can the volunteer at the entrance open the check-in screen on event day?”

ChurchFlow’s conference registration and QR check-in tools are built for that moment. Still, a church should test the role setup, device access, event status, and check-in process before volunteers arrive. Software only helps when the people doing the work can use it without escalation.

Run an event-day access check before the invoice

Set up a short rehearsal using the same kinds of people and devices you expect at the event. Give a volunteer-level user a test registration and ask them to complete the check-in without an administrator taking over.

Check the practical details:

• Can the assigned role open the attendee list and QR scanner?
• Can the team use phone lookup if a member’s QR code will not scan?
• Does the event appear as expected when check-in opens?
• Can someone see attendance updates without receiving wider system permissions?
• Is there a backup person who can resolve access problems quickly?

This is also the right time to confirm the plan’s real boundaries. A feature listed in a package can have conditions that matter deeply on a busy event day: user limits, messaging allowances, role permissions, or setup work that must happen before doors open.

A clear answer is more valuable than a reassuring label. For a related pricing review, see The $49 Plan’s Missing Limits, and What They Could Cost a Church.

Test the handoff, not only the product demo

A polished demo usually shows an experienced presenter using a fully prepared account. Your event will involve volunteers, changing shifts, real registrations, and the occasional member whose phone has no battery.

Ask the provider to demonstrate your actual handoff: a conference admin creates the event, a volunteer checks in an attendee, and a coordinator sees the updated count. Then repeat it with the permissions your church plans to assign.

This protects the team from a common assumption: that the person who can create an event is also the person who should run the door. Those are often different jobs. Giving every volunteer full administrative access creates its own risk. Giving them too little access creates the Friday-afternoon scramble.

Churches that coordinate buses should test the same way. A transport coordinator needs to see capacity and send an update when plans change. Members need the correct assignment and boarding information. What Happens When Two Coordinators Promise the Same 12 Bus Seats? shows how quickly unclear ownership can turn into an operational problem.

Make the rehearsal part of event planning

Ed Smylie’s team could not solve Apollo 13’s filter problem with a part that existed somewhere else. They had to work with the equipment available to the crew. Event software deserves the same practical test: can the right person use the right screen, with the right account, at the moment it matters?

Add an access rehearsal to the event checklist. Do it before choosing a plan, again after assigning roles, and once more before a major conference. The best time to discover a missing permission is during a quiet test, not when the first guests are waiting at the entrance.