Around 300 in weekly attendance, a church often has 60 to 120 active volunteers, three to five services a month, and a coordinator who is either part-time staff or a very dedicated volunteer. That context changes which features actually matter — and which ones are just noise.
Scheduling complexity a spreadsheet can't hold
At this size, you have enough roles that a shared Google Sheet becomes a liability. You need slot-level scheduling — nursery team A, parking crew 2, greeter station west — not just a list of names on a tab. The practical approach to building that kind of schedule is in church volunteer scheduling: a practical guide.
You also need the schedule to reach volunteers automatically, not just sit in a file the coordinator emails out every Thursday and hopes everyone reads.
Reminders that don't require coordinator effort
A team of 80 or more generates real no-show risk if the coordinator is managing reminders manually. Automated reminders — especially SMS — close the gap between 'yeah I'm coming' and actually showing up.
At this size, a multi-touch reminder cadence is not a nice-to-have. It is what separates a coordinator who loses Sunday mornings to fire drills from one who doesn't. What that cadence looks like, and how to write reminders that actually get responses, is in church volunteer communication best practices.
A coordinator dashboard that works on a phone
On Sunday morning, the coordinator is not sitting at a laptop. They're walking the lobby, responding to a sub request, and checking whether the children's ministry check-in is running. The tool needs to work on a phone, in real time, without a page refresh.
A responsive web app and a mobile-first design are not the same thing. Ask to see the coordinator view on a phone during any demo.
Pricing that grows with you, not ahead of you
Many tools designed for larger churches price per volunteer or per feature module. At 80 volunteers that's manageable. At 150 — when your church is growing and you're excited about it — you don't want to hit a pricing cliff that makes the software feel like a penalty for success.
Ask what the price looks like at your current size and at twice your current size. The answer tells you whether the tool was designed with churches like yours in mind. 1212's pricing is designed to grow without a cliff — see how it scales.
What you probably don't need yet
Multi-campus management, giving integration, and a full-featured church CRM are not the core problem at 300 people. Adding them before you've solved scheduling and retention usually means paying for features that create more complexity than they solve.
Buy for the problem you have today. You'll know when the next problem becomes real.
How to run a meaningful evaluation
Ask to import your existing volunteer list, build one real Sunday schedule, and send a real reminder. If that takes more than an afternoon to set up, the tool was probably designed for a team much larger than yours.
Give two other people access and ask them to onboard themselves. If they need help with the basics, your volunteers will too.