| 1 | Ask the local or international partner whether a story night is useful, who should shape it, which audience and purpose they support and what benefit or risk the telling creates for them. | Project lead and partner liaison | Eight weeks before the event | A partner-approved story purpose and representation boundary |
| 2 | Build a simple evidence timeline from community assessment through delivery and review, showing partner decisions, contributions, outputs, outcomes, limits and current responsibilities. | Project evidence lead and partner representative | Six weeks before the event | A verified project timeline and evidence note |
| 3 | Audit every proposed image, quotation, name and case detail against the consent, dignity, privacy and rights basis for this specific audience and remove anything that cannot be confirmed. | Story editor and privacy reviewer | Four weeks before the event | A cleared asset and consent register |
| 4 | Co-write the story with partners, using people-first language, naming local assets and leadership, stating evidence limits and avoiding before-and-after claims that cannot be supported. | Partner representative and story editor | Two weeks before the event | A partner-approved accessible presentation |
| 5 | Present the project through shared decisions, evidence and learning, invite moderated questions and use a reflection prompt about partnership quality rather than praise for the club. | Event host and project partners | During the event | A respectful project account and de-identified learning themes |
| 6 | Send partners the final material and audience themes, correct any issue, close media permissions, and assign one improvement to the club's next international partnership or project review. | Project lead and club sponsor | Within ten business days | Partner closeout, correction record and one owned partnership improvement |
