A family asking for help with a camp fee should not have to explain themselves twice, and nobody at the event should be able to tell who paid what. That is the standard worth designing to, and most of it comes down to where the amount is stored and who is able to read it.
Decide the rule before you look at software
Sliding-scale and scholarship schemes go wrong when the rule is invented one application at a time. Settle it in writing first.
- What the scheme covers: the registration fee only, or travel, kit and spending money as well.
- How an amount is decided: a published band by household size and income, a set number of assisted places, or a discretionary decision by one named person.
- Whether any evidence is asked for at all, and what is done with it once the decision is made.
- Who approves, who may read an application, and who is simply told the place is confirmed.
- What happens if the family's circumstances change, or if the child does not attend.
- How the fund is topped up, and what to do when it runs out before the applications do.
The last of those is the rule most schemes lack, and it is the one that makes a hard decision fair rather than arbitrary.
At checkout
The workable pattern is plain. The family applies privately, one named person approves an amount, and the amount is applied to the booking so the family sees the price they are actually being asked to pay. They pay it the same way as everybody else, at the same point in the same form.
What matters as much is what they never experience: a separate route through the site, a different form, a conversation at the desk on arrival, or a code they have to say out loud in front of other people. Where codes are used, make each one single use or tied to a household, so that one forwarded message cannot empty the fund.
Who can see the amount
This is the part rented platforms handle worst, because they offer a few fixed roles and an office works around them by printing a list that shows everything.
- A cabin or group leader needs the attendee, the allergy, the medication and the emergency contact, and nothing whatever about money.
- Somebody helping at the desk for one weekend needs less again: who is expected, and whether they have arrived.
- The treasurer needs the size of the fund and what has been drawn from it.
- Only the approver, and the person they answer to, should be able to see that a named household received an amount.
- Rosters, cabin lists, name badges and printed check-in sheets should carry no price at all.
Test it the way it will fail. Open a roster from a volunteer account and see whether an assisted place is distinguishable from any other. Then export the same roster and look again, because exports are usually where the extra columns come back.
The records behind the fund
A scheme still has to be accountable. Keep the application, the date, the amount approved and the name of the person who approved it, and keep them somewhere the roster cannot reach. A yearly total of places given and money spent is what a trustee or a treasurer needs, and it can be produced without naming anybody.
The same household often exists twice over in the office. They give through one product and registered through another, nothing joins the two, and so nobody can see that the family asking for help has been giving quietly for years. Joining those records is a large part of why an office starts looking at owning the system rather than renting it.
Add a year of registration fees, the database band and the share taken on giving into the software bill calculator first. Our page on what churches, conferences and camps rent and what can be rebuilt covers how scholarships, rooming and consent records fit together, and the guide to renting versus owning software sets out when a small programme should stay exactly where it is.