Building a story pipeline your field team actually feeds

Every communications director has sent the email: "Does anyone have any good stories?" It rarely works, and it is not because field staff don't care. It is because story collection has never been anyone's actual job.

Why chasing fails

Field staff are managing programs, crises, and people. A request for stories arrives as an extra favor with no deadline, no format, and no consequence for ignoring it. Meanwhile the comms team, having no reliable supply, ends up recycling the same three stories until donors stop noticing them.

The principle: if something is important and it depends on someone remembering, it will fail. Build the structure instead.

The five components

1. A submission form that takes four minutes

Not a document. A form — on a phone, in the field. Ask for only what you genuinely need:

Name and age (and whether the name can be used publicly)
The situation before
What changed, and what specifically caused the change
One quote in the person's own words
One or two photos
Consent confirmation, captured at submission

2. A monthly target per site

One story per site per month. Written into the site leader's role description and reviewed like any other responsibility. This is the step that converts stories from favor to expectation.

3. Consent captured up front

Consent is established at submission, not chased later. For organizations working with children, this is non-negotiable: written permission, clear boundaries on identifying details, and annual re-verification. Build it into the form so it cannot be skipped.

4. A tagged bank, not a folder

Store stories tagged by theme, program, country, and outcome type. When a year-end appeal needs a story about education in Uganda, someone should find it in thirty seconds rather than send another email.

5. A deployment rhythm

Channel	Frequency	Story type
Social	2× per month	Short, visual, single moment
Monthly email	1× per month	Fuller narrative with outcome
Quarterly impact report	1 per quarter	Strongest story paired with data
Major donor communication	As needed	Matched to that donor's interest

What makes a story actually work

Donors remember one story, one number, and one moment. Not fourteen talking points. The strongest structure is almost always:

A specific person, named or anonymised, in a specific place
The situation before — concrete, not abstract
The intervention — what your organization actually did
What changed — and one number that shows it was not a one-off
What it means — the future that is now possible

Avoid the dignity trap. Stories that emphasize helplessness may raise money in the short run and cost you credibility over time — with the community you serve and increasingly with donors. Show agency. The person in the story should be the one who acted; you helped.

Your first 30 days

Build the form. Use whatever you already have — a simple online form is enough.
Brief site leaders and write the monthly expectation into their role.
Set up the tagged bank. A shared drive with a naming convention beats no system.
Collect for one month before publishing anything, so you start with a buffer.

Where this sits in the Flourishing Framework™. Marketing & Communications work only holds when the layer beneath it is solid. The free Flourishing Index shows you which layer is actually constraining you — in six minutes. Take the Index →

A note on sources

This guide describes practitioner method rather than published research. The frameworks here — moves management, story pipelines, decision-rights matrices, and role scorecards — are standard practice in professional fundraising and organizational development, refined through our own work running an international organization. Where we cite statistics elsewhere in this library, we name the source. Where we don't, we're telling you it's practice.