Gift Aid adds 25p to every pound a UK taxpayer gives you. It is the closest thing to free money in fundraising, and it is routinely left on the table, not because donors refuse it but because the declaration was collected badly.
The pattern we see most often: the donation form is a third-party embed, the Gift Aid question sits inside it, the response goes to the payment provider, and the charity's CRM receives a flag and nothing else. No wording, no timestamp, no address that matches the one on the claim. Two years later HMRC asks to see the declaration for a specific gift and there is nothing to show them.
- Your charity's name
- The donor's full name
- Their home address, at minimum house number or name and postcode
- What the declaration covers: this gift, past gifts, future gifts, or all of them
- A clear statement that they want the donation treated as Gift Aid
- Confirmation that they have paid enough UK tax to cover the amount being reclaimed
The tax statement is not boilerplate
The line about having paid enough tax is the part designers most want to shrink, and the part that carries the legal weight. The donor is confirming a personal tax position, and the responsibility for any shortfall is theirs. Hiding it behind a toggle or setting it in nine point grey undermines the whole declaration.
Write it out. Set it at the same size as everything else in the form. If the wording feels too long for the layout, the layout is wrong.
A pre-ticked Gift Aid box is not a declaration. It is a liability with a conversion uplift.
Capture it at the moment of giving
Declarations chased by email afterwards convert at a fraction of the rate, and the follow-up costs staff time on every gift. The declaration belongs on the donation form, immediately after the amount, while the donor is still in the mindset of giving.
That has a design consequence. You now need a real address, not a billing address inherited from a card payment, and you need it without adding four fields to a form you have spent months shortening. A postcode lookup with a manual fallback is usually the answer. It is also the single most common place we find broken accessibility on charity sites.
Store more than a yes
A boolean in the CRM is not evidence. When we build this, every declaration writes a record containing:
- The exact wording shown, and the version of it
- Timestamp and channel: web form, phone, paper, event
- The address as given, separate from any later address changes
- Scope: single gift, or enduring and therefore covering earlier and future donations
- Any subsequent cancellation, with its own date
Keeping the wording matters more than people expect. Declaration text changes over the years. If you cannot show what a donor actually agreed to in 2021, you cannot defend the claim on their 2021 gifts.
Then make the claim boring
If the declaration record is complete, the claim becomes an export rather than a reconciliation exercise. The finance team should be able to produce a claim file without going back to the website, the payment provider or the events spreadsheet, and without anyone deciding by hand which donations qualify.
That is the test worth applying to any donation platform you are considering. Not whether it supports Gift Aid, because they all say they do, but whether it can hand you a defensible record of every declaration, and whether your finance team can claim from it unaided.
