A Donation Website: Which Appeal Purpose Must Stay With Each Contribution?

Before commissioning a donation website, decide whether visitors are supporting the organisation's work generally or a particular appeal. Carry the approved purpose from the public page into the contribution record and the finance handoff. A campaign label that staff can rename later is not enough to preserve what a donor was told.

This is a website requirements guide, not a determination of charitable status, permission to fundraise or tax deductibility. The official example below concerns charities in England and Wales. Organisations elsewhere need advice for their own jurisdiction; translating the website does not transfer English and Welsh rules to another country.

Agree the promise before building the form

Imagine an independent community organisation raising money for a reading room. Does its page ask people to support that room alone, or use the room as an example of its wider work? These are different promises even if the same payment provider processes both contributions.

Ask the responsible trustees and advisers to approve the wording and its financial treatment before the developer creates selectable appeals. Avoid treating a photograph, page heading or free-text donor message as a reliable substitute for an agreed purpose. Decide how staff handle a message requesting a narrower use than the form offers. A software default should not silently accept or discard that request.

The Charity Commission's guide to trustee duties, applicable to England and Wales, makes the distinction explicit. It says that an appeal for any or all of the charity's purposes should say so. For a specific project or aim, it describes the money as a restricted fund that must not be merged with the rest of the charity's income and must be spent on what the appeal said.

Preserve the wording that accompanied the contribution

A useful custom brief should require an appeal identity and an approved wording version, not just today's campaign name. Record which version accompanied a contribution, alongside the existing payment reference. Changing next month's public explanation should not overwrite the explanation associated with earlier donations.

Specify what the donor sees before confirming and what the acknowledgement repeats. If several translated pages describe the same appeal, review them for the same scope of purpose. A German version promising only the reading room and an English version promising general support would not be harmless editorial variation.

Keep access proportionate. Staff preparing a finance export may need the appeal reference and treatment, while not every website editor needs donor correspondence. Define the actual roles with the organisation rather than copying unrestricted access from an ordinary content management screen.

These are proposed record and interface requirements. The cited guidance supports the importance of the stated purpose; it does not prescribe this particular database design or certify a custom payment integration.

Decide how surplus and changed plans reach a human decision

The same Commission passage recommends including a secondary purpose covering insufficient funds, surplus funds or changed plans. Have the responsible people settle appropriate wording before launch. Do not let the developer invent fallback terms or assume that a general donation button automatically authorises every later use.

For the website, distinguish closing an appeal to new contributions from deciding what may happen to existing money. If the reading room cannot proceed, the first action might be to pause the public form and open a review task. The application should show the original purpose and relevant wording, not offer a casual bulk action called “move to general funds”.

This article does not specify the legal process for changing purposes, contacting donors or returning money. Those outcomes require the appropriate substantive review. Build the ability to record an authorised decision and its basis after that review, rather than encoding an unsupported universal refund or transfer rule.

Make the finance handoff reconstructable

Agree an export that keeps contribution, appeal version and payment reference connected. A payment total grouped only by month may be useful for reconciliation but cannot explain which purpose accompanied each contribution. Likewise, a page progress counter should not be presented as unrestricted cash available to spend.

Ask how corrections are recorded without erasing the original association. If an appeal was linked incorrectly because of a website defect, staff need evidence of the donor-facing page and a reviewed correction, not an invisible rewrite that makes the history look clean. Keep the accounting treatment with qualified finance staff; a website category is not itself a complete set of accounts.

Accept the purpose trail with realistic examples

Using invented donors and a payment test environment, demonstrate a general-support contribution, a specific-appeal contribution and a contribution made before an approved wording update. Close the appeal and verify that earlier records remain understandable. Try an old direct link, a changed language and a donor note asking for a different use.

Check the public promise, acknowledgement, restricted staff views and agreed export together. Record unresolved policy questions instead of marking them passed because the card payment worked. Bring the approved appeals and finance handoff to your website or app project discussion. The useful deliverable is a traceable purpose from appeal to review, not merely another fundraising counter.