Real tools for the people carrying the weight of how the church runs. No email gate, no pitch. Take them, put them to work this Monday, and pass them on.
Before anything gets fixed, get honest about where things stand.
Twenty honest statements across your data, follow-up, staffing, tools, and decisions. Find out where the weight is.
(02 · staff meeting guide · 4 min)Run your own diagnostic in one staff meeting. The uncomfortable answers are the useful ones.
(03 · benchmarks · 3 min)Staffing ratios, volunteer engagement, and payroll benchmarks from national church data, so you can see where you stand.
Fix the design around the tools before adding anything new.
Roughly 8 in 10 first-time guests never come back. A six-week rhythm that changes that, in Planning Center, Rock RMS, Subsplash, whatever your week runs on.
(05 · field guide · 6 min)Five design failures that leak guests in Planning Center, Rock RMS, and every ChMS. The tool is rarely the problem.
Health is a rhythm, not a project.
Five numbers, fifteen minutes, every Monday. The smallest habit that keeps a growing church honest.
(07 · field notes · 6 min)Why the way you led at 200 stops working at 400 and 800, and the three shifts to make before you hit the wall.
Twenty statements. Check the ones that are true of your church today, honestly. Nobody is grading you, and the ones you can't check are simply the map of where the weight is.
There is one place where every person's information lives, and the whole staff knows what it is.
You trust your attendance and giving numbers enough to make decisions with them.
Duplicate and outdated profiles are rare, and someone owns cleaning them up.
When the elders ask how the church is doing, you can answer with numbers you believe.
Every first-time guest hears from a real person within 48 hours.
One specific person owns follow-up, and the process is written down somewhere that isn't their memory.
You know how many guests from last month came back.
If a regular attender quietly stopped coming, someone would notice within a month.
Staff meetings are mostly about people and ministry, not logistics.
Announcements have one owner and one process, and things rarely get missed.
Nobody on staff types the same information into two different places.
Volunteers get scheduled without a group-text scramble.
You can say what each tool you pay for is for, in one sentence.
No two tools are doing the same job.
If the one person who understands your systems left, Sunday would still work.
Logins and access are documented, and more than one person can get in everywhere.
Routine operational decisions move without waiting on the senior pastor.
How things get done is written down, not carried in one or two heads.
Your leaders see a simple picture of church health on a regular rhythm.
You have room in your week to think about what's next, not just what's now.
16 to 20 checked: the systems are serving the ministry. Steward them and keep going.
9 to 15: cracks are forming, and your staff is quietly absorbing the cost. Pick your weakest area above and fix that one first.
8 or fewer: your church has outgrown the way it's being run. That's not failure, it's growth. But it won't fix itself, and you shouldn't carry it alone.
Write the answers down where everyone can see them. No fixing anything yet; the goal is one shared, honest picture of how the church actually runs. The uncomfortable answers are the useful ones.
Where does a first-time guest's name go after Sunday, and who sees it next?
What did our staff actually spend last week on? Would they say it matched their calling?
Which tool would break Sunday if it went down, and how many people understand it?
What's the last thing that slipped through the cracks? What made that possible?
If the senior pastor stepped away for a month, what would stop working?
Which of our numbers do we trust? Which do we quietly not?
How many spreadsheets are quietly running our ministries right now?
Where do decisions wait, and how long is the line?
What are we paying for that nobody uses?
If the operational noise disappeared tomorrow, what would we do with the time?
Counting isn't corporate. A shepherd counts the flock; that's how he knows when one is missing. Benchmarks aren't commandments, but they tell you when something is off. These come from national studies of hundreds of churches. Pull your own numbers and set them side by side; the gaps will tell you what to work on.
One honest caution: numbers describe health, they don't create it. A church can hit every benchmark and still be running on duct tape. Use these to find the conversation, not to end it.
A rhythm that works in any tool you already have. The system matters more than the software: every step has one owner, and every guest lives in one list.
A real person says thank you. A text or a short call from someone on the team, not a bulk email. The only goal is warmth. This one step is the highest-leverage thing on this page.
Something in their hands. A handwritten note or a small gift in the mail. Almost nobody does this anymore, which is exactly why it lands.
One clear next step. Not five ministries and a brochure. One invitation: a lunch, a newcomers' table, a tour. One yes is the win, because second-timers return at double the rate.
A personal connection. Introduce them to a group, a serving team, or a family in their season of life. People stay where they know someone.
Check the signal. Did they come back? Did they take the step? If no, one more personal reach-out. If yes, hand them to the ministry they landed in, on purpose, with a name attached.
Once a week, someone opens the list and asks one question: who is slipping? Those fifteen minutes are the whole ballgame, and they are the first thing that dies when nobody owns the system.
Most churches that leak guests already run Planning Center or Rock RMS. The leak is almost never a missing feature. It's one of five design failures around the tool, and every one of them is visible if you know where to look.
The double front door. A guest's info can enter in two places, the Planning Center connect card and the check-in kiosk, and the two half-profiles never meet. The question to ask: where can a person's information enter our systems, and do those places merge? Healthy is one list, however many doors.
Automation without an owner. The workflow fires, the steps sit assigned to nobody or to someone who left, and cards quietly age in a queue. The question: open the queue right now. How old is the oldest untouched card? Healthy is every step carrying a name, and the queue reviewed weekly.
Stages that mirror hope, not reality. The pipeline says visit, connect, join, serve. The people pile up in stage two, because the stages describe the journey you wish for, not the steps your team actually takes. The question: which stage has the pile-up, and is it a stage or a graveyard?
Configured at 200, running at 600. The Rock instance or PCO setup was configured years and hundreds of people ago, and nobody has re-designed it since. Teams blame the software; the configuration is guilty. The question: when did someone last rethink this setup, rather than just use it?
No loop-closer. The reports exist. Nobody opens them on a rhythm and asks who is slipping. Without that fifteen-minute habit, every automation upstream is watering a garden nobody visits.
Fix the design around the tool before you shop for a new one. Churches switch software to escape these five problems and meet them again on the other side.
Health isn't measured at the annual meeting. It's measured in a fifteen-minute Monday habit. One person pulls these five numbers and shares them with the team, every week, no exceptions.
Attendance against the 13-week rolling average. The trend is the truth; any single Sunday is weather.
First-time guests this week, and how many from four weeks ago have come back. That second number is your front door's honest grade.
The follow-up queue: guests and care needs that have sat untouched for more than seven days. Healthy is zero. Anything else has a name attached, and that name gets a call this week.
Volunteer fill rate for next Sunday. Holes should be visible on Monday, not discovered on Saturday night.
Giving households against last quarter. Count households engaged, not just dollars; dollars can hide a quiet back door.
One test worth taking: if pulling these five numbers takes more than fifteen minutes, the dashboard isn't the problem. The systems underneath it are.
Growth barriers aren't spiritual failures. They're structural. Every church that grows passes through the same walls, and what breaks at each one is predictable. Tim Keller's work on size dynamics maps it better than anyone.
Everyone-knows-everyone dies. The pastor can no longer personally carry the care of the whole church, and the first members who loved the small feel begin to grieve it. Care has to move from the pastor's memory to an actual structure, or people start slipping unseen.
Complexity explodes. A church of 400 needs four to five times more programs than a church of 200, and the informal habits that ran the church break down. Decisions bottleneck at the senior pastor, staff become overloaded generalists, and this is usually where the spreadsheets take over.
Generalists break. Past this line, staff must specialize, the pastoral span of care shrinks again, and the majority of the congregation has to be carried by well-run small groups doing real care, not just Bible study. If the systems can't see who belongs where, this wall wins.
1. Move care off the senior pastor early. Build the group and leader structure before you need it. Healthy is one volunteer leader for every five attendees; the average church runs one to seventeen, and it shows.
2. Give operations one owner before it feels justified. Churches almost always hire for ops a size too late, after the senior pastor has quietly been the ops director for two years.
3. Write it down. Every barrier is really the same barrier: the church runs on what's in a few people's heads. Documented systems are what let the next size of church exist at all.
These tools are yours either way. But if the honest look showed you a wall, that's the exact moment we serve you.