The letter at the front of an impact report is often written last, in a hurry, by someone who has already survived the audit binder. That is when the sentences drift toward triumph. A roof was patched. A cohort finished a certificate. A garden produced tomatoes. All of that may be true. The waitlist for the same roof crew, the two students who left in March, and the blight that took the late crop still belong on the page.
We draft leadership letters after the figures, not before. If the attendance chart shows a dip in the second quarter, the letter has to walk through it. Weather, a bus route cut, a staff medical leave — donors who live in the same county already heard the rumor. Naming it in the letter keeps the rest of the packet from feeling staged.
A mild reservation in the letter is not a confession of failure. It is a record of judgment. “We declined two after-school sites because we could not hire a second coordinator” tells a foundation officer more than a claim that the organization is ready to double. The next ask, if leadership chooses to make one, can point at that sentence instead of a slogan.
We refuse to write letters that invent a deadline for a gift. Sourcelogicbase does not run countdowns, fake remaining seats, or stock language about a matching gift that has not been documented. If a match exists, the letter cites the funder and the end date from the award letter.
Keep the letter on one spread. If leadership wants a longer essay, it can live later in the report beside the program it describes. Donors who skip to the figures should still meet an honest first page.