The approval chain nobody talks about (until it breaks)

What we thought we were building

We designed the Request to Purchase workflow assuming churches wanted speed. Four signatures, each one routing to the right person. Unit head flags the need. Pastor in charge vets it against strategy. Finance pastor checks the budget. Resident pastor gives final sign-off. On paper, it looked clean. Linear. Efficient.

In practice, it exposed something we hadn't anticipated. In charismatic churches running 500 to 3,500 members across multiple service units, the real problem isn't the number of approvers. It's that finance and pastoral leadership often don't share the same information about what the church actually needs.

A unit might request new chairs because attendance hit capacity. The finance pastor sees cost. The pastor in charge sees member experience. The resident pastor sees something else entirely, because they're thinking about the whole branch strategy six months out. Without a process that forced these conversations, decisions got made in silos. With our four-stage chain, the friction became impossible to ignore.

The moment we realised it wasn't broken, it was just honest

That Lagos pastor's complaint shifted something for us. They weren't asking us to remove approvals or speed things up. They were saying, 'We needed to buy the sound system. Your process made us actually talk to each other about whether we could afford it right now, or whether we were spending money we didn't have.'

Once they went through the full chain, the resident pastor realised the equipment budget had been committed three months earlier for a different project. The unit head hadn't known. The finance pastor had flagged it weeks ago but it never reached the person making the decision. The 4-stage chain didn't slow things down. It revealed that things had already been slowed down by bad communication.

They bought the equipment. But on the back of an actual conversation, not a spreadsheet that lived in someone's email.

Why four stages matter in a megachurch, not in a small one

A 200-member branch doesn't need a 4-stage approval. The pastor probably knows every equipment purchase anyway. But at 800 members, with four service units running across different venues, the resident pastor can't know everything. Neither should they.

The structure exists because of how these churches actually work. Unit heads understand their teams and what keeps them running. Pastors in charge connect individual units to the overall mission. Finance pastors guard sustainability. Resident pastors hold the vision for where the branch is heading.

Without a process that brings all four into the same conversation, you get three problems. One: money gets spent on things that made sense locally but don't fit the bigger picture. Two: good ideas never get funded because finance didn't know they were coming. Three: trust erodes, because people feel decisions are being made without them.

The four stages aren't bureaucracy. They're the shape of how your leadership actually works, made visible and deliberate instead of hidden in ad hoc conversations after service.

What changed when we stopped seeing it as a speed problem

Once we understood that approvals are really conversations, we built the flow to make those conversations easier, not faster. Each stage now shows context. Why is this being requested? What's the budget impact? Where does it sit against other priorities the resident pastor has mentioned?

We added one thing that seemed small but changed everything: notes. A unit head can explain what they're seeing on the ground. A pastor in charge can flag risks. The finance pastor can show the three-year giving projection and what it means for this purchase. The resident pastor can respond directly rather than approving or rejecting into a vacuum.

A church in Abuja told us this meant their finance pastor stopped feeling like a 'no machine.' They were actually part of the decision, not just the gatekeeper. And the resident pastor got real data about what the branch needed, instead of guesswork.

The requests that revealed your real priorities

Six months in, something unexpected happened. Churches started using the request history to see what they actually cared about. One branch realised 60% of their approved spending went to audio visual, almost nothing to children's ministry. Not because they didn't value children's work. Because requests just never happened in that unit.

The 4-stage chain, sitting in the system, became a way to audit not just spending but intention. It forced the question: if we're approving sound equipment three times a year but never seeing a request for children's resources, what's actually happening? Is the children's pastor resourced enough to think big? Is there a bottleneck we don't see?

One resident pastor used this data in a leadership meeting. It shifted their budget allocation the following year. Not because the system told them to. Because the system made it impossible to pretend they were spending what they thought they were spending.