Rotary District 9510Membership HubLegendary Clubs PackageE-132

E-132 · Detailed guide · Theme 2

Rotary Reconnect Web Page

Use Rotary Reconnect Web Page to offer former members a respectful way to reconnect without assuming that they want to rejoin.

Where this idea came from

Playbook entry
E-132 · Rotary Reconnect Web Page
Theme
Theme 2: Engagement & Belonging · Subtheme 8: Past Member Re-Engagement
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 voluntary Rotary rejoining routes, accessible web content and controlled personal-information practices; they are not an endorsement of the named Rotary Reconnect Web Page or authority for any pathway, form, visitor or membership decision.

Primary references consulted

  • Rotary Clubs (Rotary International)
    Used for: Rotary provides voluntary routes for people whose circumstances have changed to rejoin a former club or find another club.
  • Web Content Accessibility Guidelines (WCAG) (Australian Government Architecture)
    Used for: Australian Government digital guidance adopts WCAG as the standard for accessible web content.
  • Read the Australian Privacy Principles (Office of the Australian Information Commissioner)
    Used for: Where the Australian Privacy Principles apply, personal information, direct marketing and correction require transparent and controlled practices.

Candidate District material consulted

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

  • Club Playbook - Theme 2
    Candidate record 82 Digital “Reconnect With Rotary” Hub provides the related landing-page concept with project, event and email-update routes. It is not a literal current-title match and does not supply site-relationship, content ownership, pathway verification, accessibility, privacy, form, analytics, security, response-service, expiry or unpublish 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
  • Rotary clubs
    Supports: The 12 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.
  • Web Content Accessibility Guidelines (WCAG)
    Supports: The 3 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.
  • Read the Australian Privacy Principles
    Supports: The 2 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 makes follow-up more caring and consistent, while leaving people in control of how they respond.

It may suit: Former or less-connected members, and the club members reaching out to them.

Use it when

  • Consider Rotary Reconnect Web Page when past members may value news, friendship or a limited service opportunity but have not been offered a suitable route back.
  • A club with several current reconnect options, named response owners, realistic service standards and a content custodian who can remove stale opportunities.
  • A short page with structured headings, plain language, meaningful links, keyboard access, readable contrast and equivalent telephone or offline routes.
  • Forms that collect only what is necessary for a selected request and state purpose, access, retention, correction, withdrawal and expected response.

Before the club starts

  • A page charter defining audience, relationship to the district and club sites, permitted pathways, response owners, privacy, analytics, accessibility, brand, security and review dates.
  • A verified pathway register for social events, project interest, club updates, rejoining questions and contact choices, each with accurate conditions, capacity, owner and expiry.
  • A minimum-data form design with separate purposes, no preselected consent, no automatic mailing-list addition and a tested correction, withdrawal and deletion process.
  • A current brand and accessibility proof, privacy and security review, non-digital equivalent, broken-link check, publishing approval and emergency unpublish contact.

Capacity guide

Likely cost
Low; mainly personal contact, event access and simple alumni communications.
Lead time
About three weeks to check records, prepare options and make first contact.
People
Three to five people, including a records contact, connector and relevant activity hosts.

A useful club conversation

Questions worth asking

  1. What can a former member do from this page without creating an account, revealing a history or entering a recruitment process?
  2. Which promises depend on a real person responding, and can that service standard be met?
  3. What would we remove today if the club could no longer support it accurately or safely?

Common traps

  • Trying Rotary Reconnect Web Page when A public directory of former members, testimonial wall, lead-generation funnel, automatic newsletter enrolment, cookie-heavy campaign page or substitute for the district membership site.
  • Proceeding with Rotary Reconnect Web Page when Listing inactive projects, unsupported rejoining promises, private contacts, unapproved Rotary marks or links that depend on a personal social-media account.
  • Forms, analytics or third-party embeds collect more information than visitors expect. — Minimise fields and tools, document purpose and retention, restrict access and remove any tracking or embed that cannot meet the approved privacy and security boundary.

A practical 90-day path

Three milestones for Rotary Reconnect Web Page
WhenWhat the club doesEvidence to keep
Days 1–30: Agree the local designApprove the page purpose, audience, site relationship, pathways, non-recruitment boundary, brand, privacy, analytics, accessibility, security and content ownership. Verify each offered pathway with its owner, conditions, participant limit, next step, response time and expiry and remove anything the club cannot currently support.A controlled reconnect-page charter A current reconnect pathway register
Days 31–60: Run and adjust the first versionDraft a short page around visitor questions, with clear choices for social, service, updates, rejoining and no further contact and no claim that one route suits everyone. Build the page and forms with semantic structure, keyboard access, readable contrast, meaningful links, clear errors, minimal data, no preselection and equivalent telephone or offline action.A human, choice-led page draft An accessible functional page
Days 61–90: Review the evidence and decideTest every pathway, form, notice, response, account permission, device view and failure case with former-member and accessibility testers and fix all blocking issues. Publish under approved ownership, monitor response service and errors, review content monthly, remove expired pathways and complete correction, withdrawal, retention and annual governance checks.A passed content, access and response test A current, supported and governed page

Fit it to the club you have

Small club

Use one concise district-site page with two or three verified routes and a telephone contact, rather than building a separate platform the club cannot maintain.

Larger club

Use pathway owners, a content workflow, role-based publishing, expiry automation and a shared response dashboard without combining enquiry purposes.

Regional or rural club

Prioritise telephone, local-event, travel and low-bandwidth information and do not expose home addresses or private community contacts.

Metropolitan, hybrid or online club

Provide search-friendly structured content and accessible online options, but minimise third-party embeds, trackers, account requirements and uncontrolled social-media handoffs.

Learn, adapt and know when to stop

Evidence worth keeping

  • Every published pathway carrying a current owner, conditions, response time and expiry date.
  • Keyboard, screen-reader, contrast, zoom, error, mobile, low-bandwidth and non-digital checks completed at launch and after material change.
  • Enquiries receiving the selected response within the published service standard without automatic cross-enrolment.

Change course when

  • The page becomes a recruitment funnel that combines unrelated choices. — Use separate plain-language pathways and forms, no preselected consent and no membership follow-up unless the visitor selects that route.
  • Stale projects or events create false expectations. — Require owners and expiry dates, run monthly checks and automatically unpublish or visibly close unsupported pathways.
  • The digital experience excludes people or hides important conditions. — Meet the approved accessibility standard, test with users, publish conditions before forms and provide equivalent telephone and offline action.

How to put it into practice

Detailed implementation steps for Rotary Reconnect Web Page
StepActionSuggested ownerTimingEvidence or output
1Approve the page purpose, audience, site relationship, pathways, non-recruitment boundary, brand, privacy, analytics, accessibility, security and content ownership.Digital lead and club board sponsorEight weeks before launchA controlled reconnect-page charter
2Verify each offered pathway with its owner, conditions, participant limit, next step, response time and expiry and remove anything the club cannot currently support.Content custodian and pathway ownersSix weeks before launchA current reconnect pathway register
3Draft a short page around visitor questions, with clear choices for social, service, updates, rejoining and no further contact and no claim that one route suits everyone.Content designer and former-member adviserFive weeks before launchA human, choice-led page draft
4Build the page and forms with semantic structure, keyboard access, readable contrast, meaningful links, clear errors, minimal data, no preselection and equivalent telephone or offline action.Web editor and accessibility checkerThree weeks before launchAn accessible functional page
5Test every pathway, form, notice, response, account permission, device view and failure case with former-member and accessibility testers and fix all blocking issues.Independent testers and response ownersBefore launchA passed content, access and response test
6Publish under approved ownership, monitor response service and errors, review content monthly, remove expired pathways and complete correction, withdrawal, retention and annual governance checks.Content custodian and club board sponsorMonthly and annuallyA current, supported and governed page

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.
  • The page becomes a recruitment funnel that combines unrelated choices. — Use separate plain-language pathways and forms, no preselected consent and no membership follow-up unless the visitor selects that route.
  • Stale projects or events create false expectations. — Require owners and expiry dates, run monthly checks and automatically unpublish or visibly close unsupported pathways.
  • The digital experience excludes people or hides important conditions. — Meet the approved accessibility standard, test with users, publish conditions before forms and provide equivalent telephone and offline action.
  • Forms, analytics or third-party embeds collect more information than visitors expect. — Minimise fields and tools, document purpose and retention, restrict access and remove any tracking or embed that cannot meet the approved privacy and security boundary.
  • The club must approve the page purpose, relationship to district and club sites, pathways, response capacity, brand, privacy, analytics, accessibility, security and ownership.
  • A visitor's selected enquiry cannot authorise automatic newsletter, project, social, membership or publicity follow-up.
  • No former-member directory, testimonial or identifiable story may appear without a separate current authority and publication process.
  • Every pathway and form must have an owner, service standard, expiry and tested correction, withdrawal, retention and unpublish route.

What to measure

  • After 90 days, review Rotary Reconnect Web Page. Look for respectful reconnections made with consent, chosen next steps and follow-up that honours people who decline further contact.
  • Every published pathway carrying a current owner, conditions, response time and expiry date.
  • Keyboard, screen-reader, contrast, zoom, error, mobile, low-bandwidth and non-digital checks completed at launch and after material change.
  • Enquiries receiving the selected response within the published service standard without automatic cross-enrolment.
  • Broken links, stale content, access failures, corrections, withdrawals and retained form data resolved by their due dates.

Follow-up: At the 90-day review, compare the recorded measures with the starting point, resolve the listed governance holds and tell participants whether Rotary Reconnect Web Page 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

Reconnect Page Charter and Pathway Register

Define the page boundary and keep every reconnect option current and owned.

Open supporting document
02

Accessible Reconnect Page Content Map

Turn visitor questions into a concise, usable and equivalent set of actions.

Open supporting document
03

Reconnect Page Test and Operations Log

Prove that the page, forms and human responses keep working after launch.

Open supporting document

Related playbook entries

  • E-131
  • E-133

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.