Choose a ChurchWork plan by the work your church needs to do now, then leave room for the next stage of growth. Start with your member count, group structure, and event workflow. Move up when conference registration, QR check-in, bus coordination, or urgent member notifications become part of regular church life.
At 6:40 on a Saturday morning in Accra, Lydia stood beside a folding table with two printed passenger lists and a phone full of WhatsApp messages. She was helping coordinate transport for a conference, and a member at the front of the queue had a QR code while the name she gave appeared on neither list. One bus was already close to leaving. If they sent her to the wrong vehicle, she could miss the conference before it began.
Lydia’s committee had been comparing ChurchWork plans the night before. Their question was practical: what would their church actually use, and what would become an unused line on an invoice?
Start with the church you run every week
A smaller church, or a church beginning with a shared member record, usually needs the plan that covers its current membership and gives leaders a clear place to organize people into groups and subgroups.
That work matters long before a major event. A church may need a single-select group structure for birth months, where each member belongs to one month, alongside multi-select groups for departments such as choir, prayer, and ushering. It may need branch-aware member records so a leader can see the people they serve without working from several copies of the same spreadsheet.
Choose the entry plan when your immediate job is building that foundation: a usable member directory, organized groups, and a clearer view of who belongs where. Do not pay for a higher member limit or event operations before your church has a real reason to use them.
Before the committee decides, count active members rather than estimating from Sunday attendance. Include leaders, volunteers, and regular attendees who should receive event information. Then identify the groups that leaders currently maintain by hand. That gives you a real starting point.
Upgrade when events create a second job for volunteers
The next plan should match a church that runs conferences, conventions, retreats, or recurring large gatherings. Here, the pressure is rarely the event announcement itself. It is the work that starts once people respond.
Conference registration gives each attendee a record and a registration code. QR check-in gives the welcome team a faster way to confirm arrival, while phone lookup provides a backup when a code cannot be scanned. Leaders can also see attendance records instead of beginning Monday with messages asking for headcounts.
For a church running occasional smaller events, this may be the point at which a mid-level plan makes sense. The value comes from replacing a stack of informal lists with one shared record of registration and check-in.
Lydia’s team had learned this the hard way. Their event did not need a complicated new process. It needed one place where a registration could be found, checked in, and counted. When the member at the table was located through her registration details, the uncertainty lifted. She joined the right bus. The volunteer with the paper list could focus on the next person in line.
For a closer look at why a shared attendance record changes the Monday-after workload, read Church Conference Attendance Reporting: How One Shared Record Replaces Guesswork.
Choose bus coordination when transport affects attendance
Bus coordination is a different threshold. It becomes worth paying for when transport is part of your event experience and volunteers are manually assigning people, watching capacity, or responding to last-minute changes.
ChurchWork supports bus routes with pickup locations, departure times, capacity, passenger registration, and QR boarding passes. When a bus fills, coordinators can manage available options instead of rebuilding lists in a chat. Registered members can see their route status, and coordinators can send targeted delay or cancellation updates to the people affected.
This is especially useful for churches coordinating conferences across branches or pickup points. A broad announcement can leave members guessing which instruction applies to them. A route-specific update gives the right people the information they need.
Use the plan that includes this workflow when buses are a recurring operational responsibility, not a one-off experiment. The deciding question is simple: if a bus changes tomorrow morning, can your team tell every affected passenger what to do without checking three WhatsApp threads?
Check notification needs before you commit
Notifications should be evaluated by urgency and audience. A general event reminder has different stakes from a delayed bus. ChurchWork’s notification approach is designed around that difference: urgent transport changes can use SMS, push, and WhatsApp, while less urgent updates can use lighter channels.
Confirm which notification features are included in the plan you are considering, then map them to real moments in your calendar. Write down the last three times your church needed to contact members quickly. Were those messages for everyone, a branch, an event registrant, or people assigned to one bus?
That exercise also reveals what needs fixing before any plan change. If event details are getting buried, start by giving them a shared home. What Happens When Event Details Are Buried in Old WhatsApp Messages? explores the cost of relying on chat history as an event system.
Lydia’s committee left the table with a clearer decision rule. They would choose for the members and events they could name today, then review the plan when their next conference required more capacity, transport coordination, or targeted communication. That is a stronger basis for a decision than buying the largest plan in the hope that it will someday become necessary.
Comments
No comments yet.