Most benevolence funds start the same way: someone in genuine need asks the pastor for help, the pastor says yes, and money moves from a designated account with no form, no second signature, and no record beyond a line in the checkbook. It works, until it doesn't. The second request comes in for a different amount with no obvious reason why. A board member, months later, asks who approved what and why one family got more than another. Nobody remembers, because nobody wrote it down.
None of this means your church has been careless. It means the fund has been running on one person's judgment instead of a policy the church agreed to in advance. The fix is not complicated, and it does not require a lawyer or a finance committee retreat. It requires a short written document that answers four questions before anyone is standing in your office asking for rent money: who qualifies, how much can be given, who has to approve it, and what gets written down afterward. The rest of this walks through building that document.
Start with why a policy protects the person asking, not just the church
It is easy to think of a benevolence policy as a defensive document — something that protects the treasurer from a lawsuit or the board from an awkward question. That is part of it, but not the better part. A clear policy also protects the person asking for help. Without one, whether someone receives assistance depends on who happens to answer the phone, how the request is worded, and how the pastor is feeling that week. A written policy means the member who is too proud to ask twice, or too unfamiliar with church culture to phrase the request the way a longtime member would, gets evaluated against the same standard as everyone else.
It also protects the fund itself. A benevolence account with no limits and no criteria tends to drift toward whoever asks most often or most persuasively, which is rarely the same thing as whoever needs it most. A policy is what keeps the fund available for the family who only asks once, in November, after they have already tried everything else.
Define who qualifies, in plain terms
The single most useful sentence in a benevolence policy is the one that says who it is for. Some churches restrict the fund to members only. Many extend it to regular attenders, and some deliberately open it to anyone in the community who asks, treating it as an outreach ministry rather than a members-only benefit. There is no universally correct answer here — it depends on your church's size, your fund's balance, and how you think about the line between benevolence and evangelism. What matters is picking one and writing it down, so the answer does not change depending on who is asking or who is answering.
Beyond the who, name the kinds of need the fund is meant to cover: rent or mortgage arrears, utility shutoff notices, emergency car repair needed to get to work, funeral costs, medical bills not covered by insurance. Most policies also name what the fund does not cover — recurring monthly support, debt that predates the request, or requests tied to a pattern of need that a one-time gift will not actually solve. Naming the exclusions is not unkind. It is what lets you say yes quickly to the requests that fit and refer the ones that don't to something better suited, like ongoing pastoral care or a local assistance agency.
A starting template you can adapt
A policy this size does not need to be long. A single page, reviewed once a year, covers most small churches:
- Eligibility. Who the fund serves — members, regular attenders, or anyone in the community — and any documentation the request should include, such as a past-due notice or a repair estimate.
- Categories covered. A short list of need types the fund is meant for, and a short list of what it is not meant for.
- Per-request limit. A maximum dollar amount for a single request, and a maximum any one household can receive in a twelve-month period, so one long-running need doesn't quietly absorb the whole fund.
- Approval chain. Who can approve a request under the limit alone, and what threshold requires a second signature or a board vote.
- Payment method. A preference for paying the landlord, utility company, or provider directly rather than handing over cash, with an exception process for when that isn't practical.
- Recordkeeping. What gets written down for every request — date, amount, category, approver, and a brief note — and who is allowed to see it.
Set a limit before you need one
A dollar limit does two things at once: it caps the church's exposure to any single request, and it gives the person approving the request a number to point to instead of a judgment call made on the spot. A common structure is a per-request cap — say, three hundred dollars — that one person can approve alone, with anything above that requiring a second approver or a vote at the next board meeting. Add a rolling twelve-month cap per household on top of that, so a family in an extended crisis is redirected toward a more sustained form of care rather than repeated one-time gifts that never quite add up to a real solution.
The specific numbers matter less than having any at all. A church of sixty people and a church of two hundred and fifty will land on different figures, and that is fine — set the limit at whatever the fund's actual balance can sustain across a full year of ordinary requests, not the number that sounds generous in the moment.
Decide who approves, and build in a second set of eyes
The approval chain is where most unwritten benevolence practices quietly fall apart, because it is usually one person — almost always the pastor — making every call alone. That is not inherently a problem, but it puts the pastor in the position of being the only person who can explain any given decision months later, which is an uncomfortable spot even for a pastor who has done nothing wrong. Requiring a second signature above a certain amount, or requiring any request from a board member's own family to go to the full board regardless of size, closes off the two situations that generate the most awkward questions.
This does not need to slow down genuine emergencies. Keep the under-the-limit approval fast and single-signature so a Friday afternoon utility shutoff can be handled the same day. Reserve the slower, two-signature or board-vote path for the requests large enough, or unusual enough, that a pause to confirm is worth the delay.
Write down what happened, every time
A policy is only as good as the record that shows it was followed. For every approved request, keep the date, the amount, the general category of need, who approved it, and a line of context — enough that someone reviewing the fund a year later can confirm the policy was applied consistently, without keeping details a person shared in confidence that have nothing to do with the amount given.
SundayBridge keeps a discreet case record for exactly this kind of thing — a pastoral care case with comments and history that stay visible only to the people who need to see them. Logging a benevolence request there gives you a dated, attributable record of who asked, who approved it, and what was given, without mixing it into a public prayer list or a shared spreadsheet anyone with access can open.
Track the fund itself, not just individual requests
A policy also needs a way to see the fund's balance and giving trend over time, not only the requests coming out of it. If your church treats benevolence as a designated fund that people give toward specifically, watching that giving line alongside general fund contributions tells you whether the account is growing, shrinking, or roughly flat against the pace of requests — the same kind of pattern you would want to notice in giving trends more broadly. That visibility is what lets the board decide, ahead of a crisis, whether the current limits still make sense or need revisiting.
Reviewing that pattern is worth building into a weekly or monthly admin rhythm rather than only noticing it when the fund is unexpectedly empty. A five-minute look at the balance once a month is enough to catch a fund quietly running low well before someone in real need is told there is nothing left.
Revisit the policy once a year, not once
The policy you write this year will not fit forever. A church that grows from eighty to a hundred and fifty people, or moves through a season with an unusual number of medical crises, will eventually outgrow the limits it started with. Set a fixed point — the same board meeting each year, or whenever you review the annual budget — to ask whether the per-request cap, the household cap, and the approval chain still match how the fund is actually being used. A policy that is reviewed on purpose stays useful. One that is written once and forgotten becomes exactly the kind of unwritten practice it was meant to replace.
If a written policy is new territory for your church, it can help to see how this fits alongside your other financial habits — how you track giving that respects the giver and how a directory your team actually trusts keeps the people involved in a benevolence decision straight, especially when the same few names tend to be the ones asking, approving, and recording.
The point of a benevolence policy is not to make your church stingier or more bureaucratic. It is to make the same decision the same way every time, so the person answering the phone on a hard day has something to stand on besides their own best guess.