For most charities the Christmas appeal is the biggest fundraising moment of the year. The creative gets months of attention. The data behind it often gets a fortnight, and usually a busy one.
That imbalance is where the avoidable problems come from. Rarely anything dramatic: a supporter who receives two packs, a segment bigger than the print run, a Gift Aid declaration nobody checked until the thank you letters were going out. Each is small on its own. Together they cost money, goodwill, and a good deal of everyone’s December.
Appeal data is genuinely plannable, though. If your pack is posting in mid-November, the next four weeks decide how the whole thing runs. Here is a way to use them.
Week one: get the list right before you segment it
Segmentation built on an unclean list spreads the problem across every segment, so this comes first.
Start with exclusions. Work through your opt-outs, mail preference flags, gone-aways and deceased records, and check each one is actually suppressing. In Raiser’s Edge NXT, BeaconCRM, or Access Charity CRM, that usually means confirming the flag(s) you rely on is the one your selection query reads, not a similar field somebody set up two years ago for a different purpose.
Then look at addresses. Anything that came back undelivered from last year’s appeal should already be flagged. If those returns went into a pile rather than the database, this is the week to process them. It is cheaper to fix a hundred addresses now than to post a hundred packs that will not arrive.
Finally, run a duplicate check on the appeal population, not a full deduplication project. One household receiving two packs is the complaint you are most likely to get, and the easiest to prevent.
Week two: agree the segments and write the criteria down
By the end of this week you want the segments agreed with fundraising and the logic recorded in plain English, before anyone writes a query.
Most charities run some version of: regular givers, active cash donors by recency and value, lapsed donors worth reactivating, high value supporters for a personalised pack, and legacy prospects who need a different tone. The exact cut matters less than everyone agreeing what each segment means and how big it should be.
Write the criteria down. “Donors who gave twice or more in the last 24 months, excluding regular givers and anyone already in the major donor segment” is the kind of sentence that saves an argument later, and means the selection can be rebuilt next year or run by someone else if you are away.
Agree the volumes now too. If fundraising has budgeted for 8,000 packs and the criteria produce 11,500 records, that is a conversation for this week, not the day before the data is due at the mail house.
Week three: build the selection and check it properly
Run the selection, then check it against something other than itself. Three questions catch most problems. Do the volumes match what you agreed in week two, and if not, do you know why? Does every record have the fields the pack needs, salutation, address lines, postcode, and any personalisation the creative relies on? Do the segments add up to your total, with nobody twice and nobody who should have been suppressed?
Then read a sample by eye. Pull thirty records at random and look at them as a person would, not as rows. A missing salutation, an address starting with a comma, a title reading “Mr Mr”, these show up to a human immediately and not at all in a record count.
Build your exclusion report at the same time: how many were suppressed and why. Ten minutes now lets you answer “why did we only mail 8,000?” with a number rather than a guess.
Week four: hand over cleanly, and get ready for the money coming back
The handover is mostly discipline. Agree the file format with your mail house before you send it, confirm what they need for postal sorting, and send a test file first if you have not worked with them recently. Also remember the compliance and governance piece with any new agency. Keep a copy of exactly what you sent, so when a query comes back in December you can check the real file rather than rerunning the selection and hoping it matches.
The part that gets missed is the other direction: the income your appeal generates needs somewhere to go.
Check your campaign, appeal and fund codes exist in the CRM and that whoever processes donations knows which to use. Make sure online giving is coded to match, whether that is Engaging Networks, your website forms or a JustGiving page, so you are not reconciling by hand in January. Confirm your Gift Aid process can cope with a spike in declarations. Agree who is thanking supporters and how quickly, and check the thank you template pulls the right name.
Appeal reporting is straightforward when the codes were right on the way in, and a fortnight of work when they were not.
What this buys you
None of it is complicated. It is mostly deciding things in a calm week in September rather than a frantic one in November. The charities that find Christmas manageable are not the ones with the cleanest data. They are the ones who cleaned the list before segmenting, agreed the volumes before building the selection, and set up the income coding before the first donation arrived.
If you would like a second pair of eyes on your appeal selection, or help with the coding and reporting before the pack goes out, contact ADA about Christmas appeal data support. We can work alongside your team for the weeks it matters, and leave you with a process you can run yourself next year.