E-050 · Detailed guide · Theme 2

International Project Story Night

Use International Project Story Night to remove avoidable barriers so people from different backgrounds can belong and contribute on fair terms.

Where this idea came from

Playbook entry
E-050 · International Project Story Night
Theme
Theme 2: Engagement & Belonging · Subtheme 3: Cultural Inclusion & Belonging
Source material
Current playbook index title and category plus an internally authored detailed-guide draft

Initiative-specific development wave

How this draft was developed

These sources support general principles for community-led service, ethical project communication, dignity, consent and privacy; they are not an endorsement of the named International Project Story Night initiative or this locally designed delivery model.

Primary references consulted

  • Rotary Community Corps (Rotary International)
    Used for: Rotary Community Corps members identify community needs and plan and carry out projects with local Rotary clubs.; Community involvement in design, implementation and oversight strengthens sustainability and impact.
  • Code of Conduct Requirements for Ethical Communications (Australian Council for International Development)
    Used for: Development communications should be truthful, accurate and respectful and protect privacy and dignity.; Images and messages should respect people's values, history, religion, language and culture and remain authentic to context and consent.
  • Chapter 6: APP 6 Use or Disclosure of Personal Information (Office of the Australian Information Commissioner)
    Used for: Personal information generally should not be used or disclosed for a new purpose without consent or another valid basis where the Australian Privacy Principles apply.; A project consent does not automatically cover a later public story, recording or fundraising use.

Candidate District material consulted

These records remain draft evidence and still need a human source decision.

  • Club Playbook - Theme 2
    Related records 38 Club Story Circle Night, 75 Service in Action Reel and 94 Post-Project Reflection Rounds support Rotary storytelling, project highlights and reflection. None is a literal International Project Story Night record or supplies this guide's partner-authority, dignity, evidence and renewed-consent controls.

Theme 2 source-assurance wave

What has been checked

  • 3 current primary pages used by this guide were reopened on 9 August 2026.
  • 6 attributed source claim(s) were mapped to their bounded use in this initiative.
  • Candidate District material remains separate and does not establish this result.
See each source's scope and limit
  • Rotary Community Corps
    Supports: The 11 attributed Theme 2 claims attached to this source, limited to the implementation elements and supporting documents named in each initiative-level claim mapping.
    Does not establish: That the initiative is endorsed by Rotary International or District 9510, that it is permitted by the club's governing documents, that members want it, that it suits the local club, or that it will achieve the intended outcome.
  • Code of Conduct Requirements for Ethical Communications
    Supports: The 6 attributed Theme 2 claims attached to this source, limited to the implementation elements and supporting documents named in each initiative-level claim mapping.
    Does not establish: The club's local need, legal position, capability, cost, safety, accessibility, suitability, likely effectiveness, authority to act or approval of the initiative.
  • Chapter 6: APP 6 Use or Disclosure of Personal Information
    Supports: The 21 attributed Theme 2 claims attached to this source, limited to the implementation elements and supporting documents named in each initiative-level claim mapping.
    Does not establish: Whether the Privacy Act or another duty applies to this club, whether consent is informed and valid, whether collection or publication is authorised, or whether the proposed safeguards are sufficient in the actual circumstances.

What still needs a person to confirm

  • Confirm the member, prospective-member, past-member and community needs, preferences and consent that the local design assumes.
  • Confirm which privacy, safeguarding, incorporated-association, charity, work health and safety, food, liquor, copyright, licensing, screening and other duties apply to the club and the activity.
  • Test accessibility, cultural safety, belonging, language and alternative participation routes with affected people and recognise First Nations cultural authority rather than inferring suitability from the guide.
  • Confirm every local fact, starting point, cost, role, current service contact, measure, stopping condition and platform capability before the club decides to proceed.
  • Confirm the authority and current scope of each primary source, resolve login-gated or moved-page references and keep any candidate District material attributed and unapproved until its source decision is made.

The source-verification release gate remains closed.

Checks still on hold

Still an internal draft: source interpretation, local suitability, accessibility, governance and editorial approval remain open checks.

Why a club might use this

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.

Use it when

  • Consider International Project Story Night when language, custom, access or club habits may be narrowing who feels able to participate.
  • A completed or established international project with a current local partner, an agreed purpose for sharing and enough evidence to distinguish output, outcome and learning.
  • A project team willing to discuss changes, limitations and community leadership as well as achievements.
  • A small forum where partner voice can be included directly or through material approved for this audience and use.

Before the club starts

  • A partner-approved story purpose, audience and format, including who should speak, what the club may say and what should remain private or local.
  • A project evidence pack covering community assessment, partner roles, dates, outputs, outcomes, limitations, finances at an appropriate level and unresolved commitments.
  • A consent and rights review for every identifiable person, quotation, image, recording, document, logo and piece of sensitive information proposed for use.
  • An accessible presentation, a correction route and a host prepared to stop paternalistic, stereotyped or intrusive questions.

Capacity guide

Likely cost
Low to medium, depending on venue access, interpreting, transport and adapted materials.
Lead time
About four weeks for listening, co-design and a practical trial.
People
Four to six club members plus community advisers or participants who choose to contribute.

A useful club conversation

Questions worth asking

  1. Which decisions and capabilities belonged to the community or local partner, and how are they visible in this account?
  2. What do the available measures show, and what outcome or causal claim would go beyond the evidence?
  3. What should our club change in the way it assesses, partners, communicates or follows through on international projects?

Common traps

  • Trying International Project Story Night when A fundraising appeal built around identifiable hardship, children, health, trauma or crisis imagery without a current ethical and consent review.
  • Proceeding with International Project Story Night when A victory presentation that omits partner decisions, community assets, project limitations, failed assumptions, financial context or evidence quality.
  • Questions expose private details, undermine partners or reopen conflict about the project. — Moderate questions, define topics out of scope, let speakers pass and transfer grievances or safeguarding issues to an appropriate private pathway.

A practical 90-day path

Three milestones for International Project Story Night
WhenWhat the club doesEvidence to keep
Days 1–30: Agree the local designAsk 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. Build a simple evidence timeline from community assessment through delivery and review, showing partner decisions, contributions, outputs, outcomes, limits and current responsibilities.A partner-approved story purpose and representation boundary A verified project timeline and evidence note
Days 31–60: Run and adjust the first versionAudit 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. 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.A cleared asset and consent register A partner-approved accessible presentation
Days 61–90: Review the evidence and decidePresent 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. 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.A respectful project account and de-identified learning themes Partner closeout, correction record and one owned partnership improvement

Fit it to the club you have

Small club

Use one project and a 20-minute partner-approved story followed by a structured conversation. If direct partner participation is not practical, use only material cleared for this audience.

Larger club

Use a moderated panel with local and international partner roles balanced, a shared evidence slide and a single question route that prevents competing or intrusive narratives.

Regional or rural club

Plan for low-bandwidth partner participation, share questions and accessible files early, and do not record simply because time-zone or connectivity makes live attendance difficult.

Metropolitan, hybrid or online club

Provide captions, accessible documents and equal speaking support, disable automatic recording and agree the platform, audience, chat, screenshot and later-use boundaries with partners.

Learn, adapt and know when to stop

Evidence worth keeping

  • Project stories with documented partner approval, community leadership, evidence limits and current consent for every identifiable asset.
  • Participants able to name a partner or community decision and one evidence-based outcome without using a rescue narrative.
  • Accuracy, dignity, privacy, rights, accessibility or harmful-question issues identified and corrected promptly.

Change course when

  • The account centres the club as rescuer and portrays communities mainly through deficit, hardship or gratitude. — Give partners editorial authority, show local assets and decisions, use dignified language and balance the club's contribution with community leadership and agency.
  • Old consent is treated as permission for a new audience, platform, fundraising purpose or identifiable case story. — Review each asset for this use, obtain fresh specific permission where required and remove or de-identify content whose consent, safety or rights basis is uncertain.
  • Outputs are presented as outcomes or broad impact claims without suitable evidence and attribution. — Use a verified timeline, label output, outcome, observation and inference separately, state limitations and let partners correct the account.

How to put it into practice

Detailed implementation steps for International Project Story Night
StepActionSuggested ownerTimingEvidence or output
1Ask 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 liaisonEight weeks before the eventA partner-approved story purpose and representation boundary
2Build 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 representativeSix weeks before the eventA verified project timeline and evidence note
3Audit 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 reviewerFour weeks before the eventA cleared asset and consent register
4Co-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 editorTwo weeks before the eventA partner-approved accessible presentation
5Present 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 partnersDuring the eventA respectful project account and de-identified learning themes
6Send 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 sponsorWithin ten business daysPartner closeout, correction record and one owned partnership improvement

Controls and safeguards

  • Check the idea with the people affected and confirm its purpose, owner and practical limits before putting it into use.
  • Protect member choice and privacy, make participation accessible, and do not infer belonging or satisfaction from attendance alone.
  • Confirm venue, accessibility, safety, incident, cancellation and follow-up arrangements for the actual audience and setting.
  • The account centres the club as rescuer and portrays communities mainly through deficit, hardship or gratitude. — Give partners editorial authority, show local assets and decisions, use dignified language and balance the club's contribution with community leadership and agency.
  • Old consent is treated as permission for a new audience, platform, fundraising purpose or identifiable case story. — Review each asset for this use, obtain fresh specific permission where required and remove or de-identify content whose consent, safety or rights basis is uncertain.
  • Outputs are presented as outcomes or broad impact claims without suitable evidence and attribution. — Use a verified timeline, label output, outcome, observation and inference separately, state limitations and let partners correct the account.
  • Questions expose private details, undermine partners or reopen conflict about the project. — Moderate questions, define topics out of scope, let speakers pass and transfer grievances or safeguarding issues to an appropriate private pathway.
  • The club sponsor and project partners must approve the story purpose, evidence, representation, consent, privacy, copyright, accessibility and question controls before promotion.
  • Community or partner leadership must be visible and no person or place may be portrayed mainly through need, dependency, trauma or gratitude for the club.
  • Every identifiable image, quotation and case detail needs a valid basis for this audience, channel and purpose; previous project consent must not be treated as unlimited.

What to measure

  • After 90 days, review International Project Story Night. Look for a broader range of voices being heard, identified barriers being addressed and voluntary feedback showing a stronger sense of belonging.
  • Project stories with documented partner approval, community leadership, evidence limits and current consent for every identifiable asset.
  • Participants able to name a partner or community decision and one evidence-based outcome without using a rescue narrative.
  • Accuracy, dignity, privacy, rights, accessibility or harmful-question issues identified and corrected promptly.
  • One improvement applied to a subsequent community assessment, partnership agreement, project review or communication.

Follow-up: At the 90-day review, compare the recorded measures with the starting point, resolve the listed governance holds and tell participants whether International Project Story Night will change, continue or stop.

Made for this initiative

Tailored supporting documents

These working documents use the decisions, safeguards and evidence needs of this initiative. Complete them with the people affected and keep the agreed version with the club's project record.

01

International Project Story Authority and Purpose Brief

Confirm that partners support the story, audience and division of speaking and editorial authority.

Open supporting document
02

Project Evidence, Consent and Asset Register

Keep every claim, image and quotation traceable and suitable for the intended use.

Open supporting document
03

Partner-Centred Story Night Run Sheet and Follow-Up

Guide respectful delivery and ensure partner corrections and club learning are completed.

Open supporting document

Related playbook entries

  • E-049
  • E-051

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.