Rotary Story & Supper Event

What could this idea change?

It creates a welcoming reason for people to connect around a shared interest and leave with a clear next step.

It may suit: Members, guests or community participants who would find the topic useful, and the people hosting the activity.

A simple way to start

1. Write a decision brief for Rotary Story & Supper Event: define which supper and story format should be repeated, the evidence already held, people affected, local authority, fixed constraints, success signals and stop conditions. Who could lead it: Fellowship coordinator and access contact
2. Co-design timing, cost, access, transport, dietary and participation options with a varied member group, and invite without ranking tenure or requiring personal disclosure. Who could lead it: Fellowship coordinator and access contact with the access and privacy contacts
3. Build and test an evening combining a shared meal with one or two voluntary stories; use the Story and Supper Host Blueprint, rehearse the boundary wording, check materials and confirm who can decide, refer, pause or close the activity. Who could lead it: Hosts and safety lead
4. Host the fellowship experience with active welcome, mixed and optional participation, a quiet or early-exit option, safe transport planning and no recruitment or fundraising ambush. Capture only the evidence needed to judge whether the trial achieved its stated aim: make fellowship feel hospitable and purposeful without over-programming it. Who could lead it: Hosts and safety lead
5. Analyse the evidence against the starting point, validate meaning with the people involved, record exceptions and unintended effects, and prepare a simple host blueprint and permissioned follow-up without overstating what the trial proves. Who could lead it: Hosts and safety lead and an independent reviewer

What should we look for?

• After 90 days, review Rotary Story & Supper Event. Look for regular, voluntary contact across the club and early follow-up when someone becomes unexpectedly disconnected.
• Rotary Story & Supper Event produces a simple host blueprint and permissioned follow-up by the promised decision date, with evidence limitations and any participation gaps stated.
• The participant mix crosses existing friendship groups, tenure and attendance patterns, with gaps recorded.
• Access, dietary, transport, cost and communication requests are resolved or honestly explained before the activity.
• Follow-up shows whether new connections continued without creating obligation, unwanted contact or a closed social circle.

Before we say yes

• Does it fit a real local need?
• Can people take part safely and fairly?
• Are the facts, permissions and Rotary branding right?
• Who will lead it, and when will we review it?