A message calendar built from the supporter's inbox, not the team's campaign list

A nonprofit's calendar is usually four calendars: fundraising, advocacy, programme communications and events, each owned by a different team and each internally sensible. None of them describes what actually happens to a supporter, which is that some weeks they hear nothing and other weeks they get an emergency appeal on Monday, a petition on Tuesday, a newsletter on Wednesday and an event invitation on Thursday, all from the same organisation. The team sees four reasonable campaigns. The subscriber sees an organisation that cannot decide what it wants.

Four teams, four sensible calendars, one supporter receiving all of them. Nobody in the building was looking at the fourth view.

1. 01

   The unit of planning is the message received, not the campaign sent

   One row per send per segment, ordered by date, is a longer document and the only one that shows collisions. A campaign-level calendar hides them by construction, because two campaigns can be a fortnight apart on the plan and still land in the same inbox on the same morning.

2. 02

   Suppression rules belong in the calendar, not only in the platform

   Written next to the row they apply to — sustainers excluded from this appeal, recent donors from that one, advocacy-only subscribers from both — the rules get reviewed by the people planning the sends instead of living inside a saved segment nobody opens.

3. 03

   December has to be planned in August

   Year-end sending is where the inbox is most crowded and the rows have the least slack, and it is usually the part of the calendar written last. The calendar locks the year-end rows first and fills the rest of the year around them.

4. 04

   Advocacy and fundraising are different asks and the calendar has to see them as different

   A petition and an appeal ask different things of the same person, and the order between them matters. Marking each row with its ask type makes an otherwise invisible pattern visible: how often a supporter is asked for money immediately after being asked for a signature.

Sector giving rose **5.0%** while donor counts fell **3.6%** for a fifth straight year (Fundraising Effectiveness Project, full-year 2025) — a retention problem. Over-mailing a shrinking donor base accelerates it, which is exactly what the inbox-view calendar is built to prevent.

The workbook holds one row per message per segment: date, segment, ask type — appeal, advocacy, newsletter, event, stewardship — the owning team, the subject line, the suppression rules in plain language, and the link to the built email. A second view sorts those rows by segment and date: the subscriber's view, and the one used in planning meetings. Year-end is locked first. Collision rules are explicit: no two asks of any type to a segment inside a defined gap, and no appeal within a defined window of an advocacy send to that segment. Rows breaking a rule are flagged in the sheet rather than argued about in a meeting.

1. 1

   Week 1

   Segment definitions

   Segments named and defined once, then used by every team

   Owner: OmniFlow + organisation

2. 2

   Week 1

   Year-end lock

   December rows placed before any other planning begins

   Owner: OmniFlow + fundraising

3. 3

   Weeks 2–3

   Calendar build

   All planned sends entered as one row per message per segment, both views live

   Owner: OmniFlow

4. 4

   Week 3

   Collision rules

   Gaps agreed in writing, flags applied in the sheet rather than by memory

   Owner: OmniFlow + team leads

5. 5

   Ongoing

   Monthly review

   Subscriber view reviewed together; flagged rows resolved before builds start

   Owner: All teams

This entry makes no performance claim. It documents a planning structure and the problem it exists to make visible: a year that looks reasonable from four desks and looks relentless from one inbox.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

The first version was a single sorted sheet with no separate subscriber view, on the assumption that a filter would do the same job. It did not — a filter is something someone has to remember to apply, and in a meeting nobody applies it. The subscriber view is now the tab the file opens on, and the campaign view is the one you have to click to.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work