The four gatekeepers: how Request to Purchase approval actually works in Ekklesia

Why churches need more than one person saying yes

Most churches handle purchases the way they handle everything else: a committee meeting, a WhatsApp thread that goes seventy messages deep, and then someone buys the thing anyway because nobody was sure who had final authority.

The problem isn't that pastors and administrators are careless. It's that charismatic and Pentecostal churches, especially mid-sized branches with 200 to 3,500 members, operate at a scale where one person can't see all the moving parts. The Sunday school coordinator needs chairs. The maintenance team needs paint. The media unit needs equipment. Without a structured path for approval, you end up with overlapping purchases, missing budget alignment, and no audit trail.

Ekklesia's Request to Purchase workflow routes every purchase through four deliberate stages. It's not bureaucracy for its own sake. It's the people who already care about your church's health, watching out for each other.

How the four-stage chain actually moves a purchase forward

A service unit head (say, the children's ministry coordinator) submits a request to purchase materials. The form captures what they're buying, how much it costs, and why. That request lands with the unit's pastor-in-charge first. They know the ministry. They can ask: Do we actually need this? Can we use what we already have? Is the price reasonable?

If approved, it moves to the finance pastor. This is the stage where budget reality meets desire. The finance pastor sees the church's cash position, upcoming commitments, and planned giving patterns. They might approve it as is, send it back with a note about timing, or flag it as something to revisit in the next planning cycle.

Finally, the request lands with the resident pastor. They're the ones accountable to the board and the larger membership for how resources are stewarded. For smaller purchases, they often rubber-stamp what's come before. For anything substantial, they're reading the full chain: What did the unit head need? What did the pastor-in-charge think? What did the finance pastor's numbers say?

Each stage is visible. Each person sees the request, the previous approvals, and any notes. Nobody has to chase WhatsApp messages to find out whether someone already said no.

The detail that changed everything: the audit trail

During beta testing with a 600-member branch in Accra, we discovered something we hadn't anticipated. A donation had been flagged as suspicious by their finance team. It turned out someone had submitted a purchase request that looked legitimate but wasn't. Within minutes, the finance pastor could pull the full history: who submitted it, when each person approved or queried it, and what comments had been left at each stage.

That didn't solve the underlying problem, but it meant the church could act. They reviewed their governance, tightened access controls, and actually understood where the gap had been.

The audit trail does more than catch problems. It creates accountability quietly. When people know that every approval is recorded, dated, and visible to the people above them, behaviour changes. Not out of fear. Out of clarity. Everyone knows the standards.

When the system helps you say no

We've watched finance pastors use the 4-stage workflow to have conversations they couldn't have had before. One finance pastor told us that she'd previously been known as 'the person who says no.' She wasn't. She was the person who had to manage cash with nobody else seeing the picture. Once Request to Purchase was in place, she could show unit heads the actual numbers: 'We've got £12,000 committed over the next four weeks. Your purchase costs £2,500. If we do this now, we won't have emergency funds for the roof repair that's coming in month two.'

Suddenly it wasn't her saying no. It was the math, visible to everyone.

The other thing that shifts is the volume of requests that get refined before they reach approval. Unit heads, knowing their pastor-in-charge will see the request, tend to think more carefully. Is this urgent? Is this the best price? Do we need all of this, or just part of it? That filtering happens naturally when the request isn't disappearing into an inbox.

The feature nobody mentions until they've used it: routing

Most church management software treats approval like a single pathway. Ekklesia routes based on role and unit. The children's ministry coordinator's request goes to their pastor-in-charge, not to a generic pastor inbox. The finance data is only shown to people with finance access. Comments stay visible to the approval chain without spilling into general chat.

This matters more in larger branches, where a resident pastor might oversee five or six unit heads. Without routing, they'd drown in notifications. With it, they only see requests that are stuck, queried, or substantial. The routine approvals move quietly through the chain.

We built this because we watched churches struggle. You can't just drop a process onto a WhatsApp culture and expect it to work. The system has to make the right path easier than the wrong one.

What changes once you have visibility

Something unexpected happened at a 2,100-member branch in Port Harcourt six months in. The finance pastor realised that three different units were trying to buy similar equipment. She flagged it during the finance review stage and looped in the resident pastor. Within a week, they'd consolidated the purchase with a supplier, saved 18%, and built relationships between ministries that had been siloed.

The 4-stage approval workflow didn't invent that solution. But it made the information available to someone who could act on it.

That's the real return. It's not about making approvals harder. It's about giving the people who care about your church's health the information they need, when they need it, in a form they can actually use.