Ask ten church leaders what "operations" means and you'll get ten flavors of the same answer: everything that has to work so ministry can happen. True — and useless, because you can't fix "everything."

After nearly twenty years running operations at a multisite church — finance and admin, communications, events, technology, five campuses — I've landed on a simpler way to think about it. Every operational problem I've ever been handed sorts into one of six domains. Name the domain, and the fix usually names itself.

I call it the Church Operations System. Here's the whole thing.

The six domains

1. People. Roles, job descriptions, volunteer pipelines, and the honest question of who actually owns what. Most "systems problems" I'm asked to diagnose turn out to be one faithful person quietly doing three jobs — and the system is what breaks when they finally take a vacation. If a responsibility doesn't have exactly one owner, it has zero.

2. Process. How things get done: event requests, purchasing, new-staff onboarding, the communications calendar. The test is brutally simple — if the answer to "how do we do this?" is a person, you have a dependency, not a process. Write it down. A one-page checklist beats an oral tradition every time.

3. Finance. Approval rules, monthly budget-vs-actual, nonprofit pricing on every tool, reserves that earn something. Finance is where operational drift becomes measurable, which is also what makes it the best place to start: the money you stop leaking funds every other improvement. When I audited my own church's books line by line, the findings weren't exotic — they were unwatched.

4. Data. The handful of numbers leadership sees weekly — attendance split by ministry, giving households (not just dollars), group participation, volunteer health, second-visit rate. I've written about exactly which numbers and why, but the principle matters more than the list: a number seen weekly gets a response; a number seen yearly gets an autopsy.

5. Technology. Fewer tools, better connected. The pattern I find everywhere: a tool per ministry, adopted one emergency at a time, none of them talking to each other, several doing the same job. Modern church technology isn't about buying more — it's consolidation, sync instead of re-keying, a website machines can actually read, and AI pointed at busywork, never at pastoral care.

6. Governance. Board-ready reporting, policies people actually follow, guardrails written before the incident. This domain feels optional until the week it isn't. Trust is an operational asset; governance is the maintenance schedule for it. (Exhibit A: an AI policy written now, calmly, beats one written the week after a volunteer pastes prayer requests into a chatbot.)

The part nobody tells you: the domains leak into each other

Weakness in one domain always surfaces as symptoms in another, which is why churches so often treat the wrong thing.

  • A data gap (nobody sees giving-household trends) becomes a finance crisis (a budget built on a soft assumption) becomes a governance problem (a board blindsided in November).
  • A people gap (no owner for subscriptions) becomes a finance leak (zombie tools billing for years).
  • A process gap (event requests by hallway conversation) becomes a people problem (your best coordinator burns out absorbing the chaos).

So when something hurts, ask: which domain does the root cause live in? It's frequently not the one where the pain shows up.

How to use the framework

Diagnose before you change anything. Score yourself honestly, domain by domain, weakest first. If you want outside eyes, that's precisely what my free 15-minute checkup is for — and the free tools each probe one domain: the savings report and budget stress test for finance, the health check for data, the visibility scorecard and AI readiness assessment for technology, the policy generator for governance.

Fix one bottleneck at a time. The failure mode isn't lack of ambition — it's five simultaneous half-finished improvements. Pick the weakest domain, fix the single most painful thing in it completely, and only then move. Momentum compounds; scattered effort doesn't.

Build the weekly rhythm. The framework's maintenance mode is boring on purpose: a handful of numbers in front of leadership weekly, budget-vs-actual monthly, renewals on a calendar with owners. Rhythm is what keeps a fixed system fixed.

What this is not

This framework won't grow your church, write your sermons, or set your vision — and any operations consultant who implies otherwise is selling something. Operations exist so that the people called to ministry can spend their hours on ministry. That's the entire point. Every hour of re-keying eliminated and every dollar that stops leaking goes back to the reason the church exists.

If you want the interactive version of this framework — each domain with its tools and next steps — it lives at the church operations guide. And if you'd rather just talk through where your church feels stuck, the checkup below is free, fifteen minutes, and comes with no pitch.