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 Rotary belonging, purpose-limited personal information and valid consent; they are not an endorsement of the named Birthday Recognition Moments initiative or this locally designed delivery model.
Primary references consulted
Enhancing Belonging and Engagement at Rotary(Rotary International) Used for: Rotary seeks a culture where each person is valued and differences are respected.; Recognition should support belonging without requiring conformity to one social practice.
Chapter 6: APP 6 Use or Disclosure of Personal Information(Office of the Australian Information Commissioner) Used for: Personal information generally should be used for its collection purpose unless a valid exception applies.; A membership record should not automatically authorise public birthday use or a new communications channel.
Chapter B: Key Concepts(Office of the Australian Information Commissioner) Used for: Consent should be informed, voluntary, current and specific.; An individual should understand the particular use and be able to change their decision.
Candidate District material consulted
These records remain draft evidence and still need a human source decision.
Club Playbook - Theme 2 Candidate record 39 Birthday & Milestone Acknowledgements is a related but non-literal concept for current E-063 Birthday Recognition Moments and contributes cards, meeting mentions and newsletter or social acknowledgement. It does not supply opt-in, data-minimisation, channel, non-celebration, fairness, photo or governance 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
Enhancing Belonging and Engagement at Rotary Supports: Belonging, accessibility, respectful participation and equitable access principles for renewal and club experience. Does not establish: That a particular meeting model, membership pathway, leadership process or club culture is inclusive without testing with affected people.
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.
Australian Privacy Principles Guidelines: Chapter B, Key Concepts Supports: The 8 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
The club board must approve the recognition standard, minimum data, access roles, budget, alternatives and annual review before the register is used.
No membership-system date, age, image or contact detail may be used for birthday recognition without a current, specific member choice.
A private or meeting acknowledgement does not authorise a public post, tagged image or disclosure of age.
Members must be able to decline, correct or stop recognition without explaining their reason or losing an equivalent form of care.
Still an internal draft: source interpretation, local suitability, accessibility, governance and editorial approval remain open checks.
Why a club might use this
It makes a wider range of contributions visible and strengthens the club's culture of appreciation.
It may suit: Members and volunteers whose contributions may be recognised, and the people nominating or celebrating them.
Use it when
Consider Birthday Recognition Moments when members attend club activity but have few chances to know one another well.
A club seeking a light-touch recognition practice and willing to ask each member whether, when and how they want to be acknowledged.
A secretary or recognition lead able to restrict access, review choices regularly and remove information promptly.
A club prepared to offer an equivalent private or non-birthday recognition route for people who do not celebrate or disclose birthdays.
Before the club starts
A fresh opt-in form offering no acknowledgement, private message, meeting mention or approved public channel, with month-and-day only unless more is genuinely needed.
A restricted register naming the purpose, data custodian, access list, review date, correction route and deletion process.
A consistent low-cost recognition standard and an equivalent alternative for members who do not celebrate birthdays.
A host and communications brief that prohibits age guesses, unapproved photographs, personal anecdotes and pressure to explain a private choice.
Capacity guide
Likely cost
Low to medium; set a clear per-person ceiling and always include a no-cost option.
Lead time
Two to four weeks for each activity.
People
Three to six people, including a host, organiser and accessibility contact.
A useful club conversation
Questions worth asking
Have we asked what each member wants, or are we relying on an old date and an assumed preference for public attention?
What is the least information the club needs to deliver the chosen acknowledgement?
How will we recognise care fairly when someone does not celebrate or disclose a birthday?
Common traps
Trying Birthday Recognition Moments when A public birthday calendar, age reveal, surprise party or social post based only on a membership database field.
Proceeding with Birthday Recognition Moments when A popularity contest, gift obligation or collection of money that treats different spending as a measure of how much a member is valued.
A meeting mention becomes a public post, photograph or tagged profile without a separate decision. — Record channel-specific choices, recheck before publication and seek new permission for images, tags or another audience.
A practical 90-day path
Three milestones for Birthday Recognition Moments
When
What the club does
Evidence to keep
Days 1–30: Agree the local design
Agree the modest recognition options, data needed, budget and alternative route, then remove any age-based or compulsory element. Ask every member privately to opt in, select the channel and correct the date, explaining that no response means no birthday acknowledgement.
An approved recognition and privacy standard Current member recognition choices
Days 31–60: Run and adjust the first version
Store only the information needed, restrict access to named roles and schedule a monthly check without exporting the register to broad calendars or chat groups. Prepare the chosen message or meeting mention within the standard budget, verify the current choice and exclude age, private stories, images and tags unless separately approved.
A restricted upcoming-recognition list A person-approved acknowledgement
Days 61–90: Review the evidence and decide
Deliver the acknowledgement in the chosen channel without inviting teasing, gift pressure or public discussion of the person's choice. Provide an easy correction or stop route, update the register immediately and review fairness, missed acknowledgements and data access each year.
A respectful recognition moment A corrected register and annual fairness review
Fit it to the club you have
Small club
Use a restricted month-and-day list and one consistent private or meeting option, resisting the assumption that close familiarity replaces consent.
Larger club
Use role-based access, a monthly approval check and automated reminders that reveal no date beyond the authorised recipients.
Regional or rural club
Be especially careful where a birthday, household detail or absence can be linked easily across community networks.
Metropolitan, hybrid or online club
Give online members the same private and visible choices, and do not post in permanent chat channels merely because a meeting mention would have been temporary.
Learn, adapt and know when to stop
Evidence worth keeping
Current opt-in and channel choice recorded for every member acknowledged, with no response treated as no permission.
Only the minimum date and contact information retained and accessible to named roles.
Recognition delivered consistently within the agreed budget, including an alternative for people who do not celebrate birthdays.
Change course when
The club exposes a full birth date, age or other information that increases privacy or identity risk. — Collect month and day only where sufficient, restrict the register, never announce age and remove broader calendar exports.
A member who dislikes birthdays, has a difficult association or follows a different practice is pressured to explain. — Make all options voluntary, provide an equivalent alternative and treat no acknowledgement as an ordinary private choice.
Recognition varies by popularity, wealth, office or who remembered to organise it. — Use one approved standard, a named owner, monthly checks and an exception log reviewed for fairness.
How to put it into practice
Detailed implementation steps for Birthday Recognition Moments
Step
Action
Suggested owner
Timing
Evidence or output
1
Agree the modest recognition options, data needed, budget and alternative route, then remove any age-based or compulsory element.
Club board and recognition lead
Before the annual consent cycle
An approved recognition and privacy standard
2
Ask every member privately to opt in, select the channel and correct the date, explaining that no response means no birthday acknowledgement.
Secretary
Annually and at member induction
Current member recognition choices
3
Store only the information needed, restrict access to named roles and schedule a monthly check without exporting the register to broad calendars or chat groups.
Data custodian
Monthly
A restricted upcoming-recognition list
4
Prepare the chosen message or meeting mention within the standard budget, verify the current choice and exclude age, private stories, images and tags unless separately approved.
Recognition lead
One week before the birthday
A person-approved acknowledgement
5
Deliver the acknowledgement in the chosen channel without inviting teasing, gift pressure or public discussion of the person's choice.
Host or communications lead
At the chosen time
A respectful recognition moment
6
Provide an easy correction or stop route, update the register immediately and review fairness, missed acknowledgements and data access each year.
Secretary and club sponsor
After feedback and annually
A corrected register and annual fairness review
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.
Collect only necessary data, state its purpose and retention, restrict access and provide a practical correction or withdrawal route.
The club exposes a full birth date, age or other information that increases privacy or identity risk. — Collect month and day only where sufficient, restrict the register, never announce age and remove broader calendar exports.
A member who dislikes birthdays, has a difficult association or follows a different practice is pressured to explain. — Make all options voluntary, provide an equivalent alternative and treat no acknowledgement as an ordinary private choice.
Recognition varies by popularity, wealth, office or who remembered to organise it. — Use one approved standard, a named owner, monthly checks and an exception log reviewed for fairness.
A meeting mention becomes a public post, photograph or tagged profile without a separate decision. — Record channel-specific choices, recheck before publication and seek new permission for images, tags or another audience.
The club board must approve the recognition standard, minimum data, access roles, budget, alternatives and annual review before the register is used.
No membership-system date, age, image or contact detail may be used for birthday recognition without a current, specific member choice.
A private or meeting acknowledgement does not authorise a public post, tagged image or disclosure of age.
What to measure
After 90 days, review Birthday Recognition Moments. Look for repeat participation, new connections across existing groups and members choosing to organise the next activity together.
Current opt-in and channel choice recorded for every member acknowledged, with no response treated as no permission.
Only the minimum date and contact information retained and accessible to named roles.
Recognition delivered consistently within the agreed budget, including an alternative for people who do not celebrate birthdays.
Corrections, stops, missed acknowledgements, teasing or privacy concerns resolved and included in the annual review.
Follow-up: At the 90-day review, compare the recorded measures with the starting point, resolve the listed governance holds and tell participants whether Birthday Recognition Moments 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
Member Birthday Recognition Choice Form
Let each member choose whether and how the club acknowledges their birthday.
