# One Story, Ready to Send

## Turn program notes into a donor update you can stand behind.

A donor is waiting for news. You have attendance figures, a few program notes and a photo you cannot use yet. Here is how to turn what you know into an update—and keep the unanswered question open.

*The organization, people, dates and figures in this example are fictional.*

### Start with the message

**Subject: Your September reading-program update**

Hi Morgan,

You asked how the September reading sessions went. Across six sessions, 42 students took part, with time set aside for reading practice and choosing books.

We can confirm participation from the attendance register. We’re still reviewing the reading assessments, so I don’t yet have a reliable answer about changes in reading ability.

Thank you for supporting the reading program. I’ll write again by October 18 with the assessment findings, or let you know what is still outstanding and when we expect an answer.

Best,
Amina

That message answers what it can, names what it cannot, and gives the donor a date for the next update. It needs neither an unapproved photograph nor an invented success story.

### See where each sentence came from

| Program notes | What belongs in the message | What to leave out |
|---|---|---|
| September register: 42 distinct students attended across six sessions. Program lead verified the count. | “Across six sessions, 42 students took part.” | “42 students attended every session.” The register does not establish that. |
| Session logs record reading practice and book selection. | A concrete description of what students did. | A dramatic scene nobody recorded. |
| Reading assessments are still under review. | “We’re still reviewing the reading assessments.” | “Reading ability improved.” That result is not yet verified. |
| Morgan contributed to the reading program. | “Thank you for supporting the reading program.” | A claim that Morgan’s gift alone paid for every session or produced every result. |
| No photograph has been cleared for this use. | A text-only update. | An unrelated photograph presented as September’s activity. |

The distinction is simple: **what happened, what it means, and what your evidence allows you to say are separate questions.**

### When “stronger” writing becomes a weaker claim

**Draft to reject:**

> Your generosity transformed the lives of 42 children, helping them become confident readers.

**What the records support:**

> Across six September sessions, 42 students took part in reading practice. We’re reviewing the assessments to understand what changed in their reading ability.

The second version gives the donor something concrete to understand. It leaves room for the result when the team can verify it.

### Ask the program team for the missing facts

Use a request someone can answer without planning a new storytelling project:

> Hi Ben—Morgan is waiting for the September reading update. Before I send it, could you confirm:
>
> - Is 42 the number of distinct students across all six sessions?
> - Do the session records support the description of reading practice and book selection?
> - Are the assessments ready to report? If not, when should I check again?
>
> Please link the existing records and correct any wording that goes beyond them. I can send a text-only update; we do not need to wait for a photograph. Could you reply by October 10, or tell me what timing is workable?

Keep participant records and personal details in the location your team already uses to control access.

### Write your version

**Subject:** [Program or question] — [reporting period] update

Hi [name],

You asked [the question, or the update you promised].

During [period], [verified activity or result]. [One concrete detail that helps explain it.]

[What remains unanswered, if anything. Say what you are checking rather than filling the gap with a claim.]

Thank you for [accurate description of the donor’s support]. [Next update or action, with a date you can keep.]

[Name]

Use the opening only when the donor actually asked that question or was promised that update. Otherwise, begin directly with the news. Remove the unresolved-question paragraph when there is no unresolved question.

### If you owe an individual update

A general program report may be useful while you wait, but it does not fulfill a promise about an individual participant. Say so:

> I’m still waiting for the individual update I promised. In the meantime, here is the program news we have verified. I’ll check again on [date] and let you know where things stand.

If permission to share someone’s story is unclear, use content already approved for this audience. A deadline does not supply permission.

### Finish the handoff

For the fictional update above:

| Work | Person responsible | Finish condition |
|---|---|---|
| Check attendance and session description | Ben, program lead | Correct the wording and link the source records. |
| Check relevance and send the approved email | Amina, relationship owner | Save the final version and actual send date. Check for a failed delivery. |
| Follow up on assessments | Amina | Check with Ben on October 16; update Morgan by October 18. |

Sending the participation update completes that message. The assessment question stays open until it is answered or a different next step is agreed with Morgan.

*Further reading: [Jenna Watanabe and Maria Bryan on storytelling and consent](https://www.mariabryan.com/podcast/episode-56). The fictional messages and worksheets here are original Gratona examples.*