The Executive Pastor's 90-Day Operational Audit

There is a particular kind of quiet that settles over a church staff when something is wrong with the operations but nobody can name it. Reports come in late. Two people think they own the same decision, so neither makes it. A vendor renews and nobody remembers signing the original contract. The giving platform and the accounting system disagree by an amount small enough to ignore and large enough to nag. Nothing is on fire. Everything is just slightly harder than it should be.

I have walked into that quiet more than once. The first ninety days in an operations seat, whether you are a new executive pastor, a newly hired business administrator, or a longtime leader finally given permission to look under the hood, are the rare window where you are expected to ask questions and not yet expected to have all the answers. Spend that window well. What follows is the audit I run, organized into seven areas. For each one I will tell you what to look at, the red flags that should make you slow down, and a diagnostic question or two worth asking out loud in a room.

This is not a substitute for an outside set of eyes, and I will be honest about that at the end. But it is real work you can do yourself, and doing it will make you a sharper steward whether or not you ever bring anyone in.

Start where the trust is most concentrated.

Area 1: Financial Systems and Accounting Structure

Money is where a church's integrity becomes visible. People give sacrificially, often quietly, and they trust that what they gave is handled with the same care they gave it. The accounting structure is the skeleton that holds that trust upright. When it is built well, almost no one notices it. When it is built poorly, everyone eventually does.

Look first at the chart of accounts. Is it designed around how the church actually ministers, or has it grown by accretion, a new line added every time someone needed somewhere to park a transaction? Look at how restricted and designated funds are tracked. Look at the monthly close: how long after month end do leaders actually see numbers they can trust? Look at who can move money and whether the person who approves a payment is ever the same person who enters it.

Red flags worth naming:

• The monthly financials arrive weeks late, or arrive on time but everyone quietly knows they need adjusting before anyone believes them.
• Restricted gifts and designated funds live in someone's head or a side spreadsheet rather than in the accounting system itself.
• One trusted person can initiate, approve, and record a transaction with no second set of eyes. Trust is not a control. The most painful failures I have seen involved people no one would have suspected.

Diagnostic questions: If our most generous family asked tomorrow exactly how their largest designated gift was spent, how quickly and confidently could we answer? And: who, specifically, could move money out of this church without a second person knowing?

The verse is usually preached at individuals. It is just as true of systems. A church that is sloppy with the small reconciliations is training itself to be sloppy with the large ones.

Area 2: HR, Payroll, and Staffing Clarity

Most church operational pain that gets blamed on personalities is actually a design problem. Two good people clash because the org chart never decided who owns the decision they keep colliding over. A staff member underperforms because no one ever told them, clearly, what winning in their role looks like. Before you conclude you have the wrong people, make sure you have a coherent structure for the people you have.

Look at the org chart, and then look at how the place actually runs, because those are rarely the same document. Look at job descriptions and ask when they were last true. Look at how compensation decisions get made and whether there is any defensible logic across roles. Look at the basics of payroll and classification, including the genuinely tricky church-specific questions around ministerial status, housing allowance, and whether anyone treated as a contractor is functionally an employee.

Red flags worth naming:

• You ask three leaders who owns a given outcome and you get three different answers, or worse, three confident answers that all name themselves.
• Job descriptions exist as a hiring formality and have nothing to do with how anyone spends a Tuesday.
• Compensation has been set one conversation at a time over many years, with no framework, so similar roles are paid very differently for reasons no one can now explain.

Diagnostic questions: For our three most important outcomes this year, can I name the single person accountable for each, and would that person agree? And: if a respected staff member asked why they are paid what they are paid, do we have an answer that is true and that we would be comfortable saying out loud?

Area 3: Technology Stack and ChMS Health

I spent the early part of my career in technology before I spent the later part rebuilding it, and the pattern I see most often is not too little software. It is too much, badly connected. A church management system here, a separate giving platform there, a communications tool, a check-in tool, a calendar that no one trusts, all holding overlapping copies of the same families and none of them agreeing about who those families are.

Map what you actually have. Make the list of every system that holds data about your people or your money, who administers each one, what it costs, and crucially, which systems talk to each other and which do not. The church management system is usually the spine, so look hard at its health. Is the data clean enough to act on, or has it decayed to the point that staff have quietly given up and gone back to spreadsheets? That last symptom is the loudest one. When capable people route around a system, the system is already dead. It just has not been buried.

Red flags worth naming:

• The same person exists three times across your systems with three slightly different spellings, and no one can say which record is the real one.
• Staff maintain private spreadsheets because they do not trust the official system. The shadow systems are where the truth has fled.
• You are paying for tools no one fully uses, and the integrations that were supposed to connect them were never finished or quietly broke and no one noticed.

Diagnostic questions: If a new family attended this weekend, how many separate systems would need to know about them, and would they find out automatically or because a person remembered to type it three times? And: what is the one report leadership keeps asking for that we still cannot produce without heroics?

If this area alone feels overwhelming, that is normal. Sorting out a tangled stack and getting systems to actually talk to each other is the heart of what I do under systems implementation and integration, and it is rarely a job for spare evenings.

Area 4: Volunteer and Ministry Workflow Alignment

A church does not run on staff. It runs on the people who give their Saturdays and their gifts, and the systems that move a person from a first visit to a serving role are operations whether anyone calls them that or not. The audit question here is about flow. When someone raises a hand to serve, what actually happens, and how many of them fall through a gap between the hand going up and a real place to belong?

Trace the journey end to end for one or two ministries. Follow a hypothetical new volunteer from interest to onboarding to background check to first serve to ongoing scheduling. Notice every handoff, because handoffs are where people get lost. Notice how much of it depends on one ministry leader's personal memory and goodwill rather than a repeatable process. Notice whether your screening and background-check practices are consistent across every ministry that works with children and students, or whether they vary by who happens to be leading.

Red flags worth naming:

• People volunteer, never hear back, and quietly conclude they were not needed. The slow leak of willing hands is almost invisible and deeply costly.
• The process for serving lives entirely in a leader's head, which means it walks out the door the day that leader steps back.
• Background-check and child-safety practices are inconsistent across ministries. This is the one area in the entire audit where I will not soften the language. It must be airtight, everywhere, every time.

Diagnostic questions: If I signed up to serve with kids this weekend as a stranger, how long until someone responded, and would I have been properly screened before I was ever alone with a child? And: which of our serving pipelines would simply stop if one specific volunteer leader got sick for a month?

Now look at how decisions themselves move.

Area 5: Communication and Decision-Making Speed

Some churches are slow because they are careful. Many more are slow because no one ever decided how decisions get made, so every choice negotiates its own path from scratch. The cost is enormous and almost never measured: good initiatives die not because anyone rejected them but because they could never get through the fog.

Watch how a real decision travels. Pick something currently in motion and trace it. Who raised it, who weighs in, who actually decides, and how long does each leg take? Look at your meeting load with honest eyes. Look at where information lives and whether staff are drowning in channels, the same message arriving by email and text and in three different apps, which trains everyone to ignore all of them. Look for the decisions that have been pending so long that people have stopped expecting an answer.

Red flags worth naming:

• The same questions resurface in meeting after meeting because nothing was ever truly settled, only discussed.
• Staff cannot tell you who has the authority to make a given call, so they escalate everything upward, and the senior leaders become a bottleneck for choices they should never have to touch.
• Important information is scattered across so many channels that the real answer is whatever was said most recently in the hallway.

Diagnostic questions: For the last significant decision we made, how many days passed between someone first raising it and a clear answer reaching everyone affected? And: what decisions are currently waiting on me that someone closer to the work could make better and faster if I simply told them they could?

Area 6: Facilities, Vendors, and Contracts

Buildings and contracts are where money leaks quietly for years. No single bill is shocking, which is exactly why no one looks. Meanwhile the church renews agreements it forgot it had, pays for coverage it does not need, and defers maintenance that will arrive later as a much larger and much less convenient invoice.

Build the list nobody has: every recurring vendor and contract, what it costs, when it renews, whether it auto-renews, and where the actual signed document lives. You will likely find at least one you cannot fully explain. Look at deferred maintenance honestly, the roofs and units and parking lots whose failure is not a question of if but when. Look at how facility use gets scheduled and whether ministries are quietly fighting over rooms because the calendar is not trusted. Look at your insurance coverage against what you actually own and do.

Red flags worth naming:

• Contracts auto-renew because no one is tracking renewal dates, so you are never actually choosing to continue, only failing to stop.
• There is no real capital plan, so major repairs hit the budget as emergencies and get funded by robbing ministry.
• The signed agreements cannot all be located, which means at renewal or dispute you are negotiating without your own paperwork.

Diagnostic questions: Which contracts will renew in the next ninety days, and did we consciously decide to keep each one? And: what is the single most expensive building failure likely in the next three years, and do we have any plan to pay for it that is not a crisis appeal?

Area 7: Security and Data

I have saved this for last not because it matters least but because it is the area most often ignored until the moment it cannot be. A church holds extraordinary trust: the giving records, the home addresses, the children's information, the pastoral notes about people at their most vulnerable. Guarding that is not an IT chore. It is pastoral care expressed through diligence.

Look at who has access to what, and whether that access ever gets removed when someone changes roles or leaves. Old accounts that were never closed are among the most common and most dangerous gaps I find. Look at how sensitive information is stored and shared, and whether passwords for critical systems are sitting in a shared document or a former employee's memory. Look at your backups, and more importantly, look at whether anyone has ever actually tested restoring from one. An untested backup is a hope, not a plan. Look at how prepared the staff is for the threat that actually reaches churches most: not dramatic hacking but ordinary fraud and phishing, the urgent email that looks like it came from the pastor asking for gift cards or a wire.

Red flags worth naming:

• Former staff or volunteers still have active logins to systems holding member or financial data.
• Critical passwords are shared informally and have not changed in years, so access has quietly spread further than anyone can now trace.
• Backups exist on paper but no one has ever confirmed they can actually be restored, and staff have never been trained to recognize the fraud attempts aimed squarely at them.

Diagnostic questions: If a key staff member left under bad circumstances tomorrow, how confident am I that within an hour every system they could touch is locked? And: if our main database vanished tonight, how recent and how trustworthy is the copy we would actually be able to bring back?

Tallying What You Found

You do not need a sophisticated scoring model. You need an honest count. Go back through the seven areas and, for each red flag that genuinely describes your church, make a mark. Then sort what you found into three plain buckets.

• Trust and safety. Anything touching money handled by one person, child protection, or access to sensitive data. These come first regardless of how many you found, because the cost of being wrong is measured in people and integrity, not dollars.
• Drag. The slow leaks: late reports, unclear ownership, broken integrations, untracked contracts. None of these will sink you this month. Together they are why the whole place feels heavier than it should.
• Latent. The repairs and renewals and capabilities that are fine today and will not be fine in a year or two. The deferred roof. The org design that works at this size but will break at the next.

Now read the pattern, not just the count. A few isolated flags across unrelated areas usually means you have a basically healthy operation with specific gaps to close. The same kind of flag showing up in area after area, ownership unclear everywhere, data untrusted everywhere, points to something deeper than any single fix: a culture that never built the underlying discipline, which is a different and more hopeful problem because it can actually be addressed at the root.

Here is the thing I most want you to hear. If you ran this audit honestly and found a long list, that is not a verdict on you or on the people who came before you. It is the normal state of almost every growing church I have ever examined, including ones widely admired from the outside. Ministry moves fast, the work is good and urgent, and operations get built in the cracks between Sundays. Finding the gaps is not the failure. Refusing to look is.

Naming the disorder is the first act of caring for it.

Where Outside Eyes Earn Their Keep

I have given you a real framework, and I mean for you to use it. But I would be dishonest if I pretended a self-audit is the same as an outside one. It is not, for a reason that has nothing to do with your competence. You cannot see the water you swim in. The workarounds your staff invented years ago now look like normal life. The risk everyone has learned to step around has become invisible precisely because everyone learned to step around it. Insiders audit the church they have made their peace with. An outsider audits the church that is actually there.

That gap is the entire reason the Operational Assessment exists. It is the same seven-area examination you just walked through, run with outside eyes, more depth, and pattern recognition drawn from many churches rather than the single one you know from the inside. It comes in two forms. The Virtual assessment is a focused remote engagement at $1,200. The On-Site assessment is more thorough, conducted in your building and among your people, at $3,500. Both end the same way: a written report you can hand to your board, a prioritized remediation roadmap that tells you not just what is wrong but what to fix first and why, and a live debrief where we sit down together and talk through what it all means and what to do next.

No pressure attached to any of that. If you read this whole piece and decided to run the audit yourself and never call me, I will count that a good outcome, because the church will be stronger for it. But if you would rather not grade your own paper, or you suspect there are things you genuinely cannot see from where you sit, that is exactly what an assessment is for. And if what you find points less to a one-time fix and more to an ongoing need for operational leadership, there are other ways I work with churches, including serving in a fractional operations role, and a simple way to just start a conversation first.

Order in the house of God is not bureaucracy and it is not control. It is the quiet architecture that lets ministry happen without grinding on the people doing it. Order is not administrative. It is an act of faithfulness. When the systems are sound, the staff can stop fighting the building and the software and the confusion, and get back to the work they were actually called to. That is the whole point of any audit worth running.

Every problem has a solution. The first ninety days are for finding both.

Common questions

How do I know if my church needs an operations director?

A few signs are reliable. Decisions pile up waiting on the senior leaders for choices someone closer to the work should make. Reports arrive late or get quietly distrusted. Capable staff are building private spreadsheets because the official systems no longer serve them. And the senior pastor is spending real energy on operational firefighting instead of leading and shepherding. If you ran the seven-area audit and the red flags clustered around unclear ownership and slow decisions, you likely need dedicated operational leadership, whether full-time, part-time, or fractional. The assessment is designed to tell you which.

What is the difference between a business administrator and an executive pastor?

The titles overlap and churches use them loosely, but there is a real distinction. A business administrator is typically focused on the back office: finance, payroll, HR compliance, facilities, the administrative machinery that keeps the church legal and solvent. An executive pastor of operations carries that same machinery but holds it as a pastoral and strategic calling, integrating operations with the church's mission and often sitting in senior leadership. One keeps the systems running. The other treats running the systems well as a form of ministry. Many churches need the first long before they are ready to fund the second.

Can we afford to fix this?

The more honest question is usually whether you can afford not to. Most operational dysfunction is not free. It costs in late or distrusted financials, in staff hours spent fighting tools instead of doing ministry, in volunteers who slip through the cracks and never come back, in contracts that auto-renew unexamined. Much of what an audit surfaces costs little or nothing to fix beyond decision and discipline. The assessment itself is deliberately accessible at $1,200 virtual or $3,500 on-site precisely so that clarity is not gated behind a large engagement. Knowing what is wrong and what to fix first is what protects you from spending money in the wrong order.

How long does an Operational Assessment take?

It depends on the format and the size of your church, but the assessment is intentionally scoped to be a focused engagement rather than a drawn-out project. The Virtual assessment is the faster of the two, conducted remotely. The On-Site assessment takes longer because it includes time in your building and conversations with your people, which is exactly where the things you cannot see from a screen tend to surface. Either way it ends with deliverables in hand: a written report, a prioritized remediation roadmap, and a live debrief. You walk away with clarity, not just a meeting.

Will an outside assessment make my staff feel judged or threatened?

That concern is legitimate and worth taking seriously. Handled badly, an audit can feel like a search for someone to blame. Handled rightly, it is the opposite. I am not there to grade individuals. I am there to examine systems, and almost everything an audit finds is a structural gap rather than a personal failure. Most staff feel relief, not threat, when someone finally names the friction they have lived with for years and treats it as a solvable design problem instead of their fault. The framing matters enormously, and setting that tone is part of the work.

We are a smaller church. Is this only for large or multi-site churches?

No. The principles scale down cleanly. A smaller church has fewer systems and fewer people, but the same questions apply: is money handled with a second set of eyes, is anyone clear on who owns which decision, are children properly screened, can you restore your data if it vanished. Smaller churches often have an advantage, because fixes are simpler to implement when there are fewer moving parts and the whole staff fits in one room. The audit in this article was written to be run by a church of almost any size. The lessons from larger and more complex environments translate down. They do not require you to be large.