The first benevolence request rarely waits for a good time. Someone’s car breaks down two days before payday, or a family’s power gets shut off on a Friday afternoon, and whoever answers the phone has to decide something right then — how much, from where, approved by whom, remembered by whom later. If the church has never written down the answers to those questions, the person answering the phone is inventing policy under pressure, and the next person who answers will invent a different one.
A benevolence fund policy is not a theological statement about generosity. It is a short, boring document that settles five or six practical questions in advance, so that generosity does not depend on which board member happens to pick up. Most small churches can write one in an afternoon. The hard part is not the writing. It is deciding, calmly, what you would actually want to happen before you are standing in front of someone who needs help now.
Start with who can say yes, and for how much
Every benevolence policy needs an approval ladder, even a short one. The simplest version most small churches land on: the pastor (or a designated staff member) can approve a request alone up to a set dollar figure, and anything above that needs a second signature — a treasurer, a deacon, or a short vote at the next board meeting. The number itself matters less than picking one. A church of 80 might set the solo-approval line at $150; a church of 250 might set it at $400. Either is defensible. No line at all is not.
Write down what happens when the usual approver is out of town or is the one asking. Name a backup, by role, not by name, so the policy does not need rewriting every time there is a staff change.
Define what the fund is for, and what it is not
Rent, utilities, a car repair that’s keeping someone employed, groceries, a funeral cost — most churches can agree on those without much debate. Where policies actually earn their keep is the harder cases: an ongoing rent shortfall that looks less like an emergency and more like a monthly bill, a request tied to a dispute the church has no way to verify, or help for someone the church has never met. You do not need to solve every edge case in advance. You do need one sentence that tells the approver what the fund is for — typically some version of “short-term help with an unexpected, verifiable need” — and a line about what falls outside it, such as recurring monthly support, which usually belongs to a longer pastoral care conversation rather than a single disbursement.
Decide who is eligible before someone asks who isn’t
Some churches restrict the fund to members. Many do not, on the reasoning that a benevolence fund that only helps people already inside the church misses the point of having one. Either choice is fine. What is not fine is discovering the disagreement in the moment a visitor asks for help and two board members give opposite answers. Say plainly whether the fund serves members only, regular attenders, or anyone the church can verify a real need for, and whether a first request from someone the church has never met needs a different level of approval than a request from a longtime member.
Write the confidentiality rule down, not just the intention
Everyone agrees benevolence should be handled discreetly. The policy’s job is to say exactly who sees a recipient’s name and who sees only a total. A workable pattern: the approver and the treasurer know who received help, because the treasurer has to be able to account for every dollar. The rest of the board sees a summary — count of requests, total disbursed, rough categories of need — by month or quarter, with names available only on request and only for a stated reason, such as an audit. Whatever you pick, put it in the policy itself, not in a shared understanding that only exists until someone new joins the board and asks a reasonable question at the wrong moment.
This is also where it helps to be honest about who can see what in whatever system your church keeps records in. Most church software, including SundayBridge, runs on a single login for the whole church rather than restricted staff roles, so a volunteer with access to the giving records can technically see everything else too. Your written policy, not the software, is what actually keeps a recipient’s name out of the wrong conversation — decide who is trusted with access before you decide what the software can restrict, because for many small-church tools it cannot.
Keep records that satisfy the board without over-collecting
A benevolence case needs enough written detail that the approver, six months later, can explain to the board or an auditor why the money went out: the date, the amount, a one-line description of the need, and who approved it. It does not need bank statements, medical records, or a running narrative of the family’s life. Over-collecting creates a file that is more sensitive to lose than it is useful to keep. A pastoral care log with a short note and a date does the job that a folder of financial documents does not need to do.
Practically, this tends to split into two records that live in two different places: the disbursement itself gets logged as a transaction so the treasurer can reconcile the fund total, and the pastoral context — why, what was discussed, whether there’s a follow-up — gets kept as a discreet case note the pastor can find later without digging through a spreadsheet. If you’re rethinking how giving and pastoral notes end up scattered across different tools, this look at recording giving without exposing the giver covers the same instinct from the giving side.
Set a renewal rule and revisit it on a schedule
Policies that never get reread quietly stop matching reality. The dollar limits from five years ago may no longer reflect what a car repair or a month of rent actually costs. Put a review date on the policy itself — once a year, often alongside the annual budget conversation — and assign it to a specific meeting rather than leaving it to whoever remembers. If your church already has a rhythm for the small recurring admin tasks that fall through the cracks, a weekly or monthly admin rhythm is a natural place to hang an annual policy review, rather than inventing a separate process for it.
Decide how a request gets recorded against a household, not just a person
Benevolence requests often come from one member of a family but affect the whole household, and a policy that only tracks individuals can miss that a second request three months later is really the same family asking again under a different name. Deciding in advance whether you track need against the household or the individual affects both your repeat-request rule and your confidentiality rule. If your records currently blur that line, the distinction between household and individual records is worth settling before you write the repeat-request clause into your benevolence policy.
Put the whole thing on one page
A benevolence policy that runs four pages will not get read at the moment it matters. The version that actually gets followed fits on one page: who can approve what amount, what the fund is and is not for, who is eligible, who sees a name versus a total, what gets written down, and when the board revisits the numbers. Everything past that is detail the approver can work out case by case, which is exactly what a good policy leaves room for — not because the details do not matter, but because the six decisions above are the ones that are genuinely hard to make well under pressure, and everything else is easier to improvise once those are settled.