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 community action, supported volunteering and controlled use of personal information; they are not an endorsement of the named Project Team Recognition initiative or evidence for any project outcome, contribution or claim.
Primary references consulted
Our Clubs(Rotary International) Used for: Rotary clubs bring people together to connect and take action in their communities.
National Standards for Volunteer Involvement(Volunteering Australia) Used for: Volunteer involvement should be inclusive, supported and connected to clear organisational responsibility.
Chapter 6: APP 6 Use or Disclosure of Personal Information(Office of the Australian Information Commissioner) Used for: Personal information should not be reused or disclosed beyond the understood purpose without an applicable basis.
Candidate District material consulted
These records remain draft evidence and still need a human source decision.
Club Playbook - Theme 2 Candidate record 77 Project Team Shoutouts provides the related end-of-project public-thanks concept. It is not a literal current-title match and does not supply partner closeout, full-role mapping, workload, no-ranking, contributor choice, impact-evidence, correction or record controls.
Theme 2 source-assurance wave
What has been checked
3 current primary pages used by this guide were reopened on 9 August 2026.
3 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
Our Clubs 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: 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.
National Standards for Volunteer Involvement Supports: The 32 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
The club and partner must complete project, outcome, incident, complaint, asset and unfinished-work closeout before public recognition.
Recognition must not rank hours or people, mask workload or safety issues or affect future appointment and membership decisions.
Contributors and partners control whether names, roles, images and claims are used and on which channels.
Beneficiary and confidential details are excluded unless valid authority, dignity and use permissions are documented.
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 Project Team Recognition when valuable contributions are going unnoticed or recognition depends too heavily on the same informal networks.
Projects with a partner-confirmed outcome, role list and closeout record that can identify delivery, support, access, administration and follow-up contributions.
Teams able to choose collective, role-based, named, private, written, meeting or public recognition separately.
A club willing to discuss learning, workload, safety, conflict and incomplete work separately from the appreciation moment.
Before the club starts
A project closeout confirming partner acceptance, outcomes, limitations, roles, incidents, complaints, finances, assets, permissions and unfinished work.
A contribution map that includes less-visible and partner roles without requiring individuals to disclose private or confidential work.
Private recognition choices for each person or team and partner approval for names, representatives, claims, images and public channels.
A no-ranking, no-hours-comparison and no-decision-use rule and a separate route for unresolved workload, safety and conduct matters.
Capacity guide
Likely cost
Low; use thoughtful words and simple tokens rather than expensive gifts.
Lead time
About two weeks to set criteria, preferences and the nomination channel.
People
Two to four people, with project leads supplying timely nominations.
A useful club conversation
Questions worth asking
Who made the project possible before, during and after the visible service activity?
What outcome and limitations has the community partner actually confirmed?
Which workload or safety matter needs action rather than appreciation?
Common traps
Trying Project Team Recognition when Top-contributor awards, hour rankings, surprise speeches, naming beneficiaries, using volunteer lists for publicity or claiming project success before partner sign-off.
Proceeding with Project Team Recognition when A substitute for incident, complaint, partner, finance, impact, workload or project-governance closeout.
Names, images or private roles are published without authority. — Verify every person, partner, role, claim and channel and offer private and team-only options.
A practical 90-day path
Three milestones for Project Team Recognition
When
What the club does
Evidence to keep
Days 1–30: Agree the local design
Complete the operational and partner closeout before announcing success or recognition. Map delivery, preparation, access, administration, partner and follow-up contributions and identify teams or roles that were less visible.
A verified outcome and issue record A complete contribution view
Days 31–60: Run and adjust the first version
Check workload, safety, conflict and incomplete obligations and move them to separate accountable actions rather than covering them with thanks. Ask contributors and partners how they wish to be recognised and verify names, roles, claims, images and channels.
A truthful recognition boundary Contributor-controlled recognition
Days 61–90: Review the evidence and decide
Deliver collective and role-based thanks, describe the partner-confirmed outcome and learning and avoid comparison or hero narratives. Complete unresolved actions, correct public material, close recognition records and carry agreed learning into the next project brief.
Accurate team appreciation Recognition linked to better project practice
Fit it to the club you have
Small club
Use a short team closeout and partner-approved note, naming roles only where people choose and avoiding forced individual awards.
Larger club
Use a standard project closeout, contribution map and permission register across committees and service teams.
Regional or rural club
Protect partner, beneficiary and private-role details that are easy to infer and offer private or team-only recognition.
Metropolitan, hybrid or online club
Include remote coordination, digital, language and access roles and obtain separate permission for posts, recordings and online team lists.
Learn, adapt and know when to stop
Evidence worth keeping
Recognition following partner and operational closeout rather than preceding it.
Delivery, support, partner and less-visible roles represented without hour rankings.
Contributors and partners choosing names, wording, images and channels.
Change course when
Visible members receive credit while partner and support work disappears. — Map the full delivery network and use collective and role-based recognition under each contributor's choice.
The club announces success or impact without partner confirmation. — Require partner sign-off and describe limitations and learning alongside outcomes.
Recognition rewards long hours or masks unsafe workload. — Prohibit hour rankings and require separate workload and safety actions before closeout.
How to put it into practice
Detailed implementation steps for Project Team Recognition
Step
Action
Suggested owner
Timing
Evidence or output
1
Complete the operational and partner closeout before announcing success or recognition.
Project lead and partner contact
At project completion
A verified outcome and issue record
2
Map delivery, preparation, access, administration, partner and follow-up contributions and identify teams or roles that were less visible.
Project and recognition leads
Within one week
A complete contribution view
3
Check workload, safety, conflict and incomplete obligations and move them to separate accountable actions rather than covering them with thanks.
Club board sponsor
Before recognition
A truthful recognition boundary
4
Ask contributors and partners how they wish to be recognised and verify names, roles, claims, images and channels.
Recognition contact
Before publication
Contributor-controlled recognition
5
Deliver collective and role-based thanks, describe the partner-confirmed outcome and learning and avoid comparison or hero narratives.
Meeting or communications lead
At the agreed closeout moment
Accurate team appreciation
6
Complete unresolved actions, correct public material, close recognition records and carry agreed learning into the next project brief.
Project lead and club board sponsor
Within one month
Recognition linked to better project practice
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.
Visible members receive credit while partner and support work disappears. — Map the full delivery network and use collective and role-based recognition under each contributor's choice.
The club announces success or impact without partner confirmation. — Require partner sign-off and describe limitations and learning alongside outcomes.
Recognition rewards long hours or masks unsafe workload. — Prohibit hour rankings and require separate workload and safety actions before closeout.
Names, images or private roles are published without authority. — Verify every person, partner, role, claim and channel and offer private and team-only options.
The club and partner must complete project, outcome, incident, complaint, asset and unfinished-work closeout before public recognition.
Recognition must not rank hours or people, mask workload or safety issues or affect future appointment and membership decisions.
Contributors and partners control whether names, roles, images and claims are used and on which channels.
Beneficiary and confidential details are excluded unless valid authority, dignity and use permissions are documented.
What to measure
After 90 days, review Project Team Recognition. Look for a wider range of contributions being recognised, with consent, and for recipients reporting that the recognition felt appropriate.
Recognition following partner and operational closeout rather than preceding it.
Delivery, support, partner and less-visible roles represented without hour rankings.
Contributors and partners choosing names, wording, images and channels.
Workload, safety and learning actions completed and recognition records closed.
Follow-up: At the 90-day review, compare the recorded measures with the starting point, resolve the listed governance holds and tell participants whether Project Team Recognition 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
Project Outcome and Recognition Readiness Check
Confirm the project is ready for truthful appreciation.
