Choose a church platform after you have watched the real member and admin flows from setup to event day. ChurchWork currently shows self-serve organization setup, member groups, event registration, QR check-in, and bus coordination in one walkthrough, while its pricing needs a careful feature-by-feature review.
In April 1970, Apollo 13 was headed toward the Moon when an oxygen tank exploded. Jim Lovell, Jack Swigert, and Fred Haise had to use the Lunar Module as a lifeboat, yet its carbon-dioxide filters were built for fewer people. At Mission Control in Houston, engineers had to work out how to connect square command-module cartridges to round Lunar Module openings using only materials known to be on board.
The crew’s return depended on understanding how the separate parts worked together. Lovell and Jeffrey Kluger document the effort in Lost Moon. That is the useful standard for evaluating church software: do not judge a platform from a feature list alone. Watch the connected journey and check where each capability stops.
Start with the setup your church will actually complete
The walkthrough begins with self-serve organization setup. A church can create its organization and begin configuring its account without waiting for a custom implementation process.
That matters when an administrator is comparing platforms between meetings, often with limited technical support. The first question is practical: can your team get from signup to a useful member experience without a long handoff or a specialist in the room?
As you watch, look for the steps your own team would need to repeat. Consider who will create events, assign permissions, manage branches, and support members who need help. A polished welcome screen tells you little. The important test is whether the path remains clear once real people, real events, and last-minute changes enter the picture.
See how groups and events connect to member action
ChurchWork includes group and subgroup management. Churches can organize members into groups, including single-select structures such as birth-month groups and multi-select structures such as departments or volunteer teams. Members can see their assigned groups through their profiles.
The event flow then moves from conference details and registration to a QR code. Administrators can create events, publish information, manage registrations, and use QR scanning or phone lookup for check-in. Location-based check-in can also validate that a member is near the venue when that setting is enabled.
Watch this portion as if you are a member named Akosua. Can she find the event, register, retrieve her code, and arrive knowing what to do next? Then watch it as the administrator. Can Elder Grace see attendance without building a second spreadsheet?
ChurchWork has handled approximately 8,752 registrations for IMPACT 2025. That is meaningful operational evidence, but it should lead to better questions rather than end the evaluation. Ask to see the exact workflow your church will use, including registration limits, check-in fallback, attendee records, and the person responsible for resolving exceptions at the door.
For a broader way to evaluate those priorities, read why generic feature checklists can miss the congregation’s real needs.
Put bus coordination through an event-day test
Bus coordination is where ChurchWork becomes especially concrete. Coordinators can create routes with pickup points, departure times, capacities, driver details, and status updates. Members can register for a route, receive a QR boarding pass, and view current route information. When a bus fills, the system can assign later registrations to another available bus at the same pickup location, with coordinator override available.
A video walkthrough can show the happy path quickly. Ask to see the harder moment: a full bus, a delayed departure, a cancellation, or a member whose QR code will not scan. Those moments determine whether a church reduces confusion or merely moves it into a new screen.
ChurchWork’s notification work is still in progress. The intended routing includes SMS, push, WhatsApp, and email based on urgency, but do not assume every channel is active for your account until it is demonstrated and confirmed. The same discipline applies to any platform promising messaging at scale.
Apollo 13 did not succeed because each piece of equipment looked impressive by itself. The solution worked because the crew and Mission Control understood the interfaces between the pieces. Your church platform deserves that same connected review: member groups should support communication, events should lead to check-in, and transport information should reach the people travelling.
Read the current plans without filling in gaps
ChurchWork has Free, Standard at $49, and Premium at $99 plan tiers, with member-count and feature limits. Standard and Premium are positioned around additional capabilities such as volunteers and custom branding.
Two current caveats belong in every buying conversation. “AI Analytics” appears as a Premium pricing claim but is not a usable product feature today. Online Giving is modeled in the product, but its card payment flow is currently a mock payment method and cannot process real donations. Treat both as items to confirm before purchase, rather than benefits already available to your members.
Bring a short checklist to the walkthrough: your expected member count, one upcoming event, one group structure, one transport scenario, and the features your church must use in the first month. Ask the presenter to show each one live. That gives your team evidence it can use in the budget meeting, instead of relying on assumptions about what a plan label means.
Comments
No comments yet.