M-T1-PS-25 · Detailed guide · Theme 1

Rotary Storytelling Podcast

Establishes a club-owned, season-based podcast that combines narration, interviews and field audio to tell a coherent range of local service stories.

Where this idea came from

Playbook entry
M-T1-PS-25 · Rotary Storytelling Podcast
Theme
Theme 1: Attraction & Visibility · Subtheme PS: Public Storytelling
Source material
Existing checked Theme 1 guide
Linked playbook entry
M-T1-PS-25 · Rotary Storytelling Podcast

Why a club might use this

Creates an accessible long-form channel for local voices and project learning with stable show notes, transcripts and enquiry routes.

Use it when

  • Local listeners, volunteers, partners, members and supporters who prefer recurring audio storytelling. Use when the club has at least six genuinely different episode ideas and a clear listener promise.

Before the club starts

  • A season bible covering audience, format, editorial scope, episode mix, release rhythm and success measures.
  • Owned hosting and account access plus recording, editing, transcript, music, backup and archive workflows.
  • Guest, field-recording, rights, accessibility, evidence, complaints and safeguarding release gates.

Capacity guide

Likely cost
$
Lead time
2-4 weeks
People
3-5 members

How to put it into practice

Detailed implementation steps for Rotary Storytelling Podcast
StepActionSuggested owner
1Design the season arc and test its listener promise against six distinct episode briefs.Showrunner
2Assign hosts and producers and complete research, guest and field-recording plans for the pilot pair.Series Producer
3Record narration, interviews and approved location sound using consistent technical and consent standards.Recording Lead
4Edit the pilot episodes, verify claims, clear rights and prepare transcripts and useful show notes.Editorial and Accessibility Lead
5Launch the season, manage feedback and actions, and decide renewal only after an end-of-season review.Publisher and Audience Lead

Controls and safeguards

  • Keep the feed, hosting account, source files and passwords under documented club ownership with a succession plan.
  • Apply episode-level consent, evidence, music, archive, accessibility and safeguarding checks even when a format becomes routine.
  • High — a recurring feed compounds consent, rights, account-ownership and correction failures across a whole season.

What to measure

  • Episodes released against the season plan

Follow-up: Send guests final links and correction routes, resolve listener actions, archive each production package and hold a documented renewal decision after the season.

Related playbook entries

  • M-T1-PS-05
  • M-T1-PS-19
  • M-T1-PS-14

Before your club says yes

Does the idea fit?

Talk with the people it is meant to serve and check that the need is real.

Who can say yes?

Name the person or group that can approve the work, spending and any safety arrangements.

Are people protected?

Check privacy, consent and safety. Collect only the information you genuinely need.

Can everyone take part?

Check the language, format, place, technology and cost for barriers.

Are the facts and permissions right?

Check names, claims, images, quotations, partner references and Rotary branding.

How will we learn?

Note where things stand now, check in at 30, 60 and 90 days, and decide what to do next.