A benevolence request form asks the person in front of you what they need. A benevolence policy tells the person behind the desk what to do about it. The two get confused constantly, because a church usually writes the form first — it is the more obvious document — and never quite gets around to the second one, which is the wording that actually governs the decision. If your church fields a request most weeks, that gap shows up fast: two people get different answers to the same kind of need, and nobody can point to why.
What follows is not a philosophy of benevolence. It is wording: the specific clauses a policy needs, written out in a form you can copy, adapt to your own numbers, and bring to a board meeting for a vote. Treat each section below as a paragraph in the same one-page document, not as a separate memo.
Open with a one-sentence purpose clause
Every policy needs a sentence that says why the fund exists before it says how it works. This is the clause you read aloud to a board member who asks “why did we say yes to that one and no to the other?” A workable version: “The benevolence fund exists to provide short-term financial assistance to members and neighbors facing an unexpected hardship, at the discretion of the approving leader named in this policy, subject to the limits and confidentiality provisions below.” Nothing in that sentence promises help to everyone who asks — it promises a process, which is the thing a policy can actually guarantee.
Write the eligibility clause narrowly, not broadly
Vague eligibility wording — “anyone in genuine need” — sounds generous and decides nothing. A usable clause names what the fund covers and, just as importantly, what it does not:
- Covers — specific, one-time hardships: utility shutoff notices, a car repair needed to keep a job, a temporary rent shortfall, emergency medical costs not covered by insurance.
- Does not cover — ongoing monthly expenses, debts to another person or business, or requests already declined once within the stated repeat-request window (see below).
- Open to — state plainly whether the fund serves members only, or members and the wider community, since this single line changes how often the fund gets asked.
This is also the clause that should point to the intake form rather than duplicate it. A line like “requests are submitted using the church's benevolence request form and reviewed against the eligibility criteria above” keeps the policy from re-listing fields the form already asks for.
Set an approval limit with an actual number in it
This is the clause that saves a bivocational pastor from having to decide, alone, at 4:45 on a Friday, whether $400 is too much. Name a figure a single leader can approve without a second signature, and a threshold above which a second approver or a short board vote is required. A common structure for a church of sixty to two hundred and fifty people:
- Up to $150: pastor or designated staff member approves alone, notifies the treasurer within a week.
- $150–$500: pastor plus one board member or deacon, by phone or email, no meeting required.
- Above $500: brought to the next board meeting, or to an emergency vote by phone if the need cannot wait.
Adjust the numbers to your own fund balance, but do not leave the clause without any number at all — a policy that says “reasonable amounts” instead of a figure has not actually decided anything, and the next disagreement between two approvers will be about the word “reasonable,” not the request.
Write the confidentiality clause before you need it
Decide, in the wording itself, who sees a recipient's name and who sees only a total. A workable version: “The identity of benevolence recipients is known only to the approving leader and the treasurer. The board receives a quarterly summary showing the number of requests, total disbursed, and general categories of need, without names, unless a specific case requires full board review.” This single clause is usually the one that keeps a well-meaning board member from asking, in an open meeting, exactly who received help last month — because the policy already told them that is not how it works here.
Address repeat requests explicitly
A policy silent on repeat requests will get its first exception made within a year, and that exception quietly becomes the real policy whether anyone voted on it or not. Name a limit and an escalation path instead: “The fund assists the same household no more than twice in a rolling twelve-month period without board review. A household with an ongoing crisis beyond this limit may be referred to the board for a longer-term plan, rather than declined outright.” That second sentence matters as much as the first — it gives the approving leader somewhere to send a genuine ongoing need instead of a flat no.
Name who records the outcome, and where
Every approved request needs a paper trail: date, amount, approver, and a brief category of need, kept somewhere more permanent than a sticky note or a treasurer's memory. A short clause covers this: “Every approved request is logged with date, amount, approving leader, and general category, kept in the church's giving and pastoral-care records.” SundayBridge keeps this kind of note attached to a household's own record in giving and in pastoral care, so a future treasurer or pastor can see the history without asking around — but the wording above should still hold if your church ever records it a different way.
Adopt it with a date, and put a review date on the calendar
A policy is a draft until a board votes on it. Close the document with an adoption line: “Adopted by the board on [date]; reviewed annually each [month].” The review date matters more than it sounds like it should — a fund balance changes, a congregation grows or shrinks, and a $150 approval limit that made sense three years ago can be quietly too low or too high by the time anyone thinks to revisit it. Reviewing the policy once a year is a small addition to the kind of weekly admin rhythm that keeps a church's records from drifting out of date without anyone deciding that on purpose.
Keep the form and the policy pointing at each other
Once both documents exist, the last job is making sure they agree. If your records still live across a mix of paper forms, a shared drive, and whoever's memory is longest, this is a good moment to bring them into one place a new pastor or treasurer can actually find. The form collects the request; the policy decides it. Neither one replaces the other, and a church that has only written one of the two has, in practice, written half a process.