E-122 · A 90-day try-out

A club plan for Project Team Recognition

Use this as a starting point. Cross out what does not fit, add what is missing and make it your club's own.

Where this idea came from

Playbook entry
E-122 · Project Team Recognition
Theme
Theme 2: Engagement & Belonging · Subtheme 7: Recognition & Celebrations
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 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

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

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

1. Is this worth trying here?

What we hope will change: Use Project Team Recognition to make recognition timely, genuine and fair across visible and behind-the-scenes contributions.

2. Our 90-day try-out

What our club will do for Project Team Recognition
StepWhat we will doWho could lead itOur dateHow we will know it is done
1Complete the operational and partner closeout before announcing success or recognition.Project lead and partner contactAt project completionA verified outcome and issue record
2Map delivery, preparation, access, administration, partner and follow-up contributions and identify teams or roles that were less visible.Project and recognition leadsWithin one weekA complete contribution view
3Check workload, safety, conflict and incomplete obligations and move them to separate accountable actions rather than covering them with thanks.Club board sponsorBefore recognitionA truthful recognition boundary
4Ask contributors and partners how they wish to be recognised and verify names, roles, claims, images and channels.Recognition contactBefore publicationContributor-controlled recognition
5Deliver collective and role-based thanks, describe the partner-confirmed outcome and learning and avoid comparison or hero narratives.Meeting or communications leadAt the agreed closeout momentAccurate team appreciation
6Complete unresolved actions, correct public material, close recognition records and carry agreed learning into the next project brief.Project lead and club board sponsorWithin one monthRecognition linked to better project practice

3. Checks before we start

Things our club needs to check
QuestionWhat it means for usWho will checkDone?
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.

4. What changed?

What we will keep an eye on
What mattersWhere we are nowWhat we hope to seeHow we will checkWho
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.

After 30 days

Is it reaching the right people? Is anything unsafe, unfair or harder than expected?

After 60 days

Make one useful change based on what people have told you.

After 90 days

Compare with where you started. Decide whether to change it, continue it 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.

Open supporting document
02

Project Contribution and Choice Map

Notice the complete team without ranking effort or exposing private roles.

Open supporting document
03

Team Recognition and Learning Closeout

Deliver accurate thanks and carry learning into future projects.

Open supporting document

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.

Worksheets for your club

Open them online, print them or change them to suit the way your club works.

01

Criteria rubric

Use this worksheet to recognise people's contributions fairly and ask before sharing their story.

Open worksheet
02

Safety and approval check

Use this worksheet to notice problems early, make the idea safer and know who needs to say yes or help.

Open worksheet