---
title: "Nonprofit supporter newsletter planner"
type: "skill"
url: "https://useaiblocks.com/skills/plan-a-nonprofit-supporter-newsletter"
updated: "2026-10-28"
first_published: "2026-10-25"
job: "Write emails that get read"
tested: true
licence: "MIT"
source: "https://github.com/sector-skills/nonprofit-skills/tree/7d8a2ca9d471fc975d0e9ccd02fcdd66520fd1c8/nonprofit-skills-library/skills/communications-marketing/nonprofit-email-newsletter"
instructions: "https://useaiblocks.com/skills/plan-a-nonprofit-supporter-newsletter/SKILL.md"
---

# Nonprofit supporter newsletter planner

> Share nonprofit news and reader groups. Get a newsletter plan, draft and issue checks.

Share your news, reader groups and voice guide. Plan each issue and draft a template. Get a newsletter plan and checks.

Free skill for the job "Write emails that get read" · Level: intermediate · Thinking: medium · Tested · Updated 2026-10-28

## Links

- Page: https://useaiblocks.com/skills/plan-a-nonprofit-supporter-newsletter
- Instructions (SKILL.md): https://useaiblocks.com/skills/plan-a-nonprofit-supporter-newsletter/SKILL.md
- All files (zip): https://useaiblocks.com/skills/plan-a-nonprofit-supporter-newsletter.zip
- JSON version: https://useaiblocks.com/skills/plan-a-nonprofit-supporter-newsletter.json
- In your AI: connect https://useaiblocks.com/mcp and ask "Use AI Blocks to get plan-a-nonprofit-supporter-newsletter"

## What it does

Share your news, reader groups and voice guide. Plan each issue and draft a template. Get a newsletter plan and checks.

## What you give it

- Your nonprofit goals, approved news and stories, voice guide, reader groups and realistic content supply.

## What you get

- A reusable newsletter draft, reader-specific content rules, a content calendar and an issue checklist.

## Example: what goes in and what comes out

### What goes in

- Your nonprofit goals for the newsletter
- Approved news items and stories
- Your voice guide or brand messaging
- How you want to group readers, such as donors, volunteers and general readers
- How much news you can really share each month

### What comes out

- **Newsletter template**: A reusable layout with subject line, opening note, lead story, quick updates, spotlight, dates and footer.
- **Reader group rules**: What each reader group should see, such as general readers, donors, volunteers, board and lapsed readers.
- **Subject line and send guidance**: Short, specific subject lines, a steady send day and list clean-up habits that protect inbox delivery.
- **Content calendar**: A rolling plan for the next 4 to 8 weeks, built on the news you can really supply.
- **Issue checklist**: Checks for links, personal tags, mobile view and the unsubscribe link before each send.

## Use it when

- You want to plan a nonprofit supporter newsletter.

## Skip it when

- You want an email that asks for gifts: use a fundraising appeal email, not this newsletter plan.
- You need to set up lists or tags in your email tool: ask whoever runs your donor database or email tool.
- You want social posts or donation page copy: write those as separate pieces of work.

## How to use it

1. Download the complete skill folder and add it to your AI tool, or copy the instructions into a chat.
2. Provide the inputs listed here and ask your AI to follow the skill.
3. Review the result and any missing facts before using it.

## What to do next

- [Nonprofit giving page writer](https://useaiblocks.com/skills/nonprofit-donation-page-writer): Write the landing page

## Sources and credits

- From sector-skills: https://github.com/sector-skills/nonprofit-skills/tree/7d8a2ca9d471fc975d0e9ccd02fcdd66520fd1c8/nonprofit-skills-library/skills/communications-marketing/nonprofit-email-newsletter, shared under the MIT licence (original name: nonprofit-email-newsletter).
- [nonprofit-email-newsletter skill](https://github.com/sector-skills/nonprofit-skills/tree/7d8a2ca9d471fc975d0e9ccd02fcdd66520fd1c8/nonprofit-skills-library/skills/communications-marketing/nonprofit-email-newsletter), sector-skills: Original instructions and supporting files, with attribution and the MIT licence. Display copy describes the task.

## Instructions (SKILL.md)

## Nonprofit Email Newsletter

<!-- needs: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. -->
### Before you start
Use the material below to do this job. If facts or tool access are missing, explain what you can finish and what must wait.

**What you need** (use your own material or the linked skill):
- **A buyer brief**, made by the [Buyer brief writer](https://useaiblocks.com/skills/buyer-brief-writer): who it's for, how much they already know, and what will move them.
- **A brand guide** (yours): a printable brand guide: voice, look, do and don't, with examples.
- **Source text** (yours): a long source in full: an article, a video or talk transcript, or notes from a book, with its title, author and link.

**Recommended steps before this one** (optional; do each once, then reuse what it makes):
1. **A buyer brief** with the [Buyer brief writer](https://useaiblocks.com/skills/buyer-brief-writer). Bring customer words. It uses your brand brain.
2. This one.

How to start:
1. **Look first.** Use what they've already attached, pasted or put in their about-me note. In a coding assistant with file access, look in the project too for these by name.
2. **Check what's missing.** Look for a buyer brief, a brand guide, source text. They can attach files, paste the details, or share a file path your assistant can read. Offer the linked skills above when they help prepare that material. Ask only for missing facts that change the result. If they ask you to start with what they have, complete the parts you can and mark the gaps.
3. **Do the job.** Follow the skill below with the facts and tools you have. Mark each gap with `MISSING:` where it belongs and never invent a fact to fill it.
<!-- /needs -->

### When to Use This Skill

Use this skill for the recurring, relationship-oriented e-newsletter — the update-focused email that
keeps supporters informed between fundraising asks. Typical triggers: designing or refreshing a
newsletter template, setting cadence (monthly vs. quarterly), segmenting the list by audience type,
planning a rolling content calendar, or diagnosing poor open/click rates.

**Boundary — the critical distinction to make explicit every time:** A newsletter's job is
relationship maintenance and information sharing; an appeal email's job is to generate a gift. If the
email's primary CTA is "donate now," it belongs to `nonprofit-annual-appeals`, not this skill, even if
it's sent through the same list. This skill may include a *soft, secondary* giving mention (e.g., a
small "support this work" link in the footer) but should not be structured around an ask. Segmentation
*tooling and CRM setup* is `nonprofit-donor-crm`; this skill defines segmentation *strategy* for
newsletter content only. Social content is `nonprofit-social-media`. Donation page copy itself is
`nonprofit-donation-page-copy`.

### Standard Deliverable: Newsletter Template Structure

A reliable recurring structure (readers learn to expect and scan it, improving engagement over time):

1. **Subject line + preview text** — see subject-line guidance below.
2. **Opening note** (2-4 sentences from the ED or a rotating staff voice) — sets the theme for this
   issue, not a generic "hello."
3. **Lead story** — one program update, milestone, or outcome, with a photo and a short pull-quote if
   available (source finished narratives from `nonprofit-storytelling` when featuring a beneficiary).
4. **Quick-hit updates section** — 2-4 short items (upcoming events, a new hire, a media mention, a
   volunteer need) as a scannable bulleted or card list, not full paragraphs.
5. **Spotlight** — rotate between volunteer, donor, staff, or partner spotlights issue to issue so no
   single audience type is neglected.
6. **Upcoming dates/CTA block** — event registrations, volunteer sign-ups; a small "ways to give"
   link, kept secondary in visual weight to informational content.
7. **Footer** — standard boilerplate (from `nonprofit-brand-messaging`), social links, unsubscribe/
   preference-center link (required for CAN-SPAM compliance).

### Segmentation Strategy (Content Logic, Not Tooling)

Decide *what each segment should see*, then hand the technical list-building to `nonprofit-donor-crm`:

- **General subscribers** (signed up via website, no gift/volunteer history): broadest program-update
  content, low ask frequency, focus on building affinity before conversion.
- **Active donors:** can include slightly more outcome/ROI-of-your-gift framing ("here's what your
  support funded this quarter") without becoming a full appeal.
- **Volunteers:** prioritize volunteer opportunity content and volunteer spotlights; deprioritize
  financial asks, which can feel redundant to their time-based contribution.
- **Board/major stakeholders:** may warrant a distinct, higher-frequency or more detailed version
  (sometimes a separate "board update" is more appropriate than folding them into the general list).
- **Lapsed/inactive subscribers:** consider a distinct re-engagement newsletter track or sunset
  policy rather than lowering overall list deliverability by continuing to mail unengaged addresses.

### Subject Line and Deliverability Practices

- Keep subject lines under ~50 characters and specific ("3 kids, 1 summer, 1 big win" beats "Our
  July Newsletter") — specificity consistently outperforms generic labels on open rate.
- Avoid spam-trigger patterns: excessive punctuation/caps, "free," multiple dollar signs — these hurt
  inbox placement even for legitimate nonprofit senders.
- Maintain list hygiene: remove or suppress hard bounces and long-term non-openers (e.g., no opens in
  12+ months) periodically — a bloated, unengaged list drags down sender reputation and can push
  future sends (including appeal emails) into spam folders for everyone.
- Send consistently on the same day/time pattern (e.g., first Thursday monthly) — consistency builds
  subscriber expectation and modestly improves open rates over erratic scheduling.
- Always include a working unsubscribe link and honor opt-outs promptly — a legal requirement (CAN-SPAM)
  and a deliverability factor (spam complaints from ignored unsubscribes damage sender reputation).

### Step-by-Step: Building or Running the Newsletter Program

1. Set cadence based on real content supply, not aspiration — a promised weekly newsletter with only
   monthly program updates worth sharing produces filler content and declining engagement; monthly or
   biweekly is realistic for most small-to-mid nonprofits.
2. Define the segment list and what differs per segment (per the strategy above); confirm the CRM/
   ESP can actually execute the planned segmentation before committing to it editorially.
3. Build the template structure once as a reusable layout; resist redesigning it every issue.
4. Maintain a rolling content calendar 4-8 weeks out, pulling from the same content pipeline as
   social media and the annual report so stories are captured once and reused across channels.
5. Draft using the org's messaging house voice; keep the CTA block visually secondary to information.
6. QA every issue: test links, check personalization tags render correctly, and preview on mobile
   (most nonprofit email opens are on mobile devices).
7. Send, then review open rate, click rate, and unsubscribe rate by segment; watch for a rising
   unsubscribe rate as an early signal of ask-creep or declining relevance.
8. Periodically clean the list (bounce and long-term non-opener suppression) on a set schedule (e.g.,
   twice yearly) rather than only reactively after a deliverability problem appears.

### Common Failure Modes

- **Ask creep:** the "newsletter" slowly becomes another appeal channel, fatiguing the list and
  blurring the metric picture for both channels — if this is happening, split into two distinct
  sends/tracks.
- **One-size-fits-all content** sent identically to donors, volunteers, and cold subscribers, missing
  relevance gains from minimal segmentation effort.
- **Irregular cadence** that trains subscribers not to expect (or open) the email.
- **No content pipeline coordination** with social/annual report teams, causing duplicated effort or,
  worse, stale content because "someone else already covered that story."
- **Ignoring list hygiene**, letting deliverability quietly degrade until even appeal emails
  (a much higher-stakes send) land in spam.
- **Overloading each issue** with too many CTAs (donate, volunteer, register, follow us, read this) —
  newsletters with a single primary CTA per issue outperform multi-ask emails on click-through.

### Practitioner vs. Advisor Framing

- **As the practitioner** (communications staff): use the template structure as a locked format and
  the segmentation strategy to brief whoever manages the CRM/ESP; track unsubscribe rate as an early
  warning metric for ask creep.
- **As an advisor/consultant**: when a client says "our newsletter isn't working," first check
  whether it has quietly become an appeal channel (a strategy misdiagnosis) before recommending
  template or subject-line fixes (tactical fixes) — the two problems require different
  recommendations and conflating them wastes an engagement's early diagnostic phase.

<!-- next: written by tools/add-needs.mjs for AI Blocks; not part of the original skill. Edit that tool, not this section. -->
### After this
When you've handed it back, suggest what they could do next in one short question. It's a suggestion: if they're done, that's fine. Offer these, and say they can type their own:
- **Write the landing page** with the [Nonprofit giving page writer](https://useaiblocks.com/skills/nonprofit-donation-page-writer). It takes the draft.
If they pick one and that skill is added here, carry straight on with what you just made. If not, give the link and say what to bring.
<!-- /next -->
