Most benevolence forms are not written once. They are written once and then edited eight times, each edit added after a specific Tuesday when something went wrong — a check written to the wrong person, a request that turned out to duplicate one from three months earlier, a board member who asked, after the fact, why no one had checked whether the family had already gotten help from the county. Each edit made sense at the time. Together, they can turn a one-page form meant to help someone in a hurry into something that reads like a loan application.
The fix is not more questions. It is fewer, better ones — a set where every field earns its place by changing what happens next: whether the request gets approved, how much, paid to whom, and how fast. This is the short list, the longer list of questions that only sometimes belong, and the list of questions worth cutting even though they feel responsible to ask.
The test: does this question change the decision?
Before adding any field to a benevolence application, ask what decision it feeds. “What is the amount requested” changes the decision directly — it is compared against a policy cap and a fund balance. “How long have you attended this church” usually does not change anything at all; it just sits on the form because someone once worried about people who are not members asking for help, without the church ever actually deciding to turn non-attenders away.
A field that does not change a decision does one of two things instead: it slows the person down for no reason, or it sits there collecting an answer nobody reads. Neither is neutral. Every extra field is a small tax on someone who is often filling this out at the worst moment of their week.
The questions that always belong
These earn their place on almost every benevolence form, regardless of size or how formal your process is:
- Name and how to reach them — phone, email if they have one, and the best time of day. A crisis often comes with an unreliable phone or a shift schedule that makes calling back harder than it sounds.
- What the need is, in one or two sentences — rent due Friday, a car repair blocking a job, a utility shutoff notice. Ask for the specific thing, not a life story.
- The exact amount requested — a number, not a range, so it can be checked against a policy cap or a fund balance without a follow-up question.
- Who gets paid — the landlord, the utility company, the pharmacy — kept as its own field, separate from the amount. Funds paid directly to a biller are on much firmer ground than cash handed to an individual, both practically and often legally.
- Whether they have asked anyone else for help with this same need — a county program, another church, a relative. This is coordination, not suspicion; its purpose is to keep one bill from being paid twice by two different sources that never talked to each other.
Five fields, none of them optional, all of them feeding a decision someone is about to make.
The questions that only sometimes belong
These are reasonable, but only for certain funds or certain request sizes. Adding them by default, on every request regardless of amount, is where forms start to feel heavier than they need to.
- Household income or monthly expenses — defensible for an ongoing rent subsidy or a repeat-request fund that needs to weigh ability to pay over months. Not defensible for a one-time $75 gift card.
- Documentation — the bill, the notice, the estimate — worth requiring above a dollar threshold your church sets in advance, and worth waiving below it. A $500 rent request should come with the actual notice. A $40 grocery request usually should not have to.
- How they heard about the fund, or who referred them— useful if your church tracks where requests come from to decide where to focus outreach, but not something the decision to help hinges on.
- Whether they attend the church — worth asking as a fact, not a filter, unless your church has actually decided the fund is members-only. If it has not decided that, do not let the form quietly decide it by making the question feel like a gate.
The questions worth cutting
These show up on a lot of benevolence forms because they feel thorough. Almost none of them change what happens next, and all of them add friction:
- A full narrative field asking someone to “explain in detail the circumstances that led to this request.” One or two sentences tells you what you need; a long open text field either gets a one-word non-answer or an unbounded outpouring that is hard on the person writing it and does not change the decision.
- Employer name and job title, unless your fund is specifically weighing a repayment plan. It rarely changes the amount approved and can read as judgment about whether someone “deserves” help based on their work.
- A required references section — two people who can vouch for the applicant. This is more appropriate for a background check than a request for a $200 utility payment, and it delays an urgent request behind phone calls to strangers.
- Multiple signature or witness lines for small requests. A single approver's name and date is enough for anything under your fund's emergency threshold; save layered sign-off for the larger, recurring cases where it actually matters.
None of these questions are wrong to ask in every context — a fund making a $3,000 commitment over six months is a different conversation than a fund covering a $60 electric bill. The mistake is asking the large-request questions of every request, by default.
Ordering the questions matters as much as the list
Put contact information first — it takes seconds and asks nothing hard. Follow with the need, in the person's own words, then the amount and payee. Save anything that could feel invasive, like income or documentation, for after the form has already established what is being asked for and why. A form that opens with a person's financial picture before it has said hello reads very differently from the same questions asked in the right order.
If a question needs a sentence of explanation to not feel like an accusation — “we ask this so we don’t accidentally pay a bill twice,” for instance — put that sentence right above the field. People fill out forms more openly when they understand why a question exists, not just that it does.
Where the answers need to live afterward
A short list of good questions still needs somewhere to go once the form is filled out. If completed applications end up as loose paper or scattered PDFs, the pattern-spotting that made a short question set worthwhile — noticing that three requests in six months all came from the same household, or that shutoff notices cluster every July — never actually happens, because nobody can see the requests side by side. A record your team actually trusts matters here as much as the wording of any single question.
SundayBridge keeps pastoral care cases — benevolence requests included — on one record with comments and history, so the answers to these questions stay attached to the person's file rather than living only in a folder or one staff member's memory. It does not write the check or process the payment; that part still runs through however your church handles disbursements today.
Review the question set once a year, not once ever
Forms drift the same way records do. Set a yearly reminder, alongside whatever other recurring admin work your office already tracks, to sit down with whoever handles benevolence and ask, of every field on the form: has this changed a decision in the last twelve months? If the honest answer is no for three years running, cut it. If your records need a broader cleanup anyway, the benevolence form is a good place to start, since it is usually the shortest one in the building and the easiest to get right in an afternoon.