Giving Tuesday Is December 1: How a Small Nonprofit Can Turn Its Impact Report Into a 5-Minute Audio Update Donors Actually Finish (AI Podcast, 2026)

1) Why audio suits donor updates

Donors who give once a year rarely read the annual report. They do open short messages from an organization they trust. A spoken update is a thank-you with a number in it, and it can be played while someone walks the dog or does the dishes.

It also helps a small team. You probably do not have a producer or a voice actor. An AI podcast workflow lets one person produce a clean episode from a document they already have. We make no claim here about open rates or donation lift; track plays and replies against your last email.

This post is about stewardship (thanking and reporting), not asking. If you want the video side of fundraising, see our guide on AI voice for fundraising and donor videos.

2) Start with a one-page source

The audio is only as good as the page it comes from. Write one page with these parts:

• Three numbers you can prove: people served, meals, hours, trees, whatever your measure is.
• One story with permission (see below).
• One thing that is not finished, so the update is honest.
• One specific next step for Giving Tuesday.

Upload that page to the SpeakSay AI podcast tool and generate the episode from it. Do not upload donor lists, addresses or anything private.

3) The five-minute structure

Keep the ask to a single sentence. The episode is a thank-you first. People notice when an update turns out to be an appeal.

4) Handle stories and names with care

Stories about the people you serve are the most powerful part and the riskiest. Get these things settled before you write them in:

1. Written permission from the person, in a form they understand, for audio use as well as print.
2. No identifying details unless they asked for them. First names can be enough, or none.
3. A check with the person, or a trusted representative, that the audio version still feels right.

Do not use a synthetic voice to speak as a beneficiary or to "re-enact" their words. Use the host voices to tell the story in the third person, or use their own recording with permission. Label the episode as AI-generated narration in the show notes and spoken intro.

5) Make the episode

1. Generate the episode from your one-page source.
2. Listen for numbers, names and place names, and fix any that are wrong. Our pronunciation guide shows how.
3. Check that the story section says only what the page says. If the host adds details, remove them.
4. Even out the loudness with the free audio normalizer before sending.
5. Add a written transcript below the player.

6) When and how to send it

• Around November 24 to 27: send the update as a thank-you before the appeal wave. Link the audio and a transcript, with no donation button on the same email if you can avoid it.
• On December 1: a short reminder pointing to the same audio, with your ask.
• In the week after: a thank-you message with the result, and the audio if you want to share the final number.

Treat these dates as a plan, not a promise. Check your own list's habits.

7) Pre-send checks

• Every number matches your records.
• Every story has written permission.
• The episode says it uses AI-generated narration.
• A transcript is linked for people who cannot play audio.
• A real person from your team has listened to the whole episode.

8) FAQ

It falls on the Tuesday after Thanksgiving, which is December 1, 2026.

For reporting and thanks, many small teams find it acceptable when it is labeled. Use a human voice for anything personal, such as a message from your director.

Five minutes or less. If you need more, split it into two episodes.

Only if your own data policy allows it and the donor expects it. Generic thanks are safer for a mass send.