E-157 · Detailed guide · Theme 2

Suggestion Box System

Use Suggestion Box System to give members a safe, visible route for ideas and concerns to lead to an answer or improvement.

Where this idea came from

Playbook entry
E-157 · Suggestion Box System
Theme
Theme 2: Engagement & Belonging · Subtheme 10: Feedback, Voice & Improvement
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 member suggestions, information collection, safe referral and visible improvement; they are not an endorsement of the named Suggestion Box System or authority to collect, identify, disclose, retain or decide any member matter.

Primary references consulted

  • Engage emerging leaders (Rotary International)
    Used for: Rotary encourages clubs to ask members what they want and describes a stop, start and continue box as a way to hear positive and negative suggestions.
  • Chapter 3: APP 3 Collection of solicited personal information (Office of the Australian Information Commissioner)
    Used for: A form or invited complaint can involve solicited personal information, and collection purpose, notice, third-party arrangements and reasonable expectations matter.
  • Better Practice Complaint Handling Guide (Commonwealth Ombudsman)
    Used for: Accessible feedback systems need clear processes, confidentiality, impartial referral, timely response and a way to use insights for improvement; the guide is adapted as general system-design evidence, not as a legal standard for clubs.

Candidate District material consulted

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

  • Club Playbook - Theme 2
    Direct connected-Drive inspection on 9 August 2026 confirmed candidate record 95 Suggestion Box (Physical or Digital): an always-open physical or digital suggestion route with quarterly review and feedback loops. The title is not a literal current match, and the candidate does not supply collection, triage, complaint, safeguarding, privacy, conflict, response, retention or deletion 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
  • Engage Emerging Leaders
    Supports: Member-centred discovery, mentoring, feedback, emerging-leader support and club-health review principles during renewal.
    Does not establish: That a person is ready for office, should be selected, has consented to a role or that a proposed renewal pathway will work locally.
  • Chapter 3: APP 3 Collection of solicited personal information
    Supports: Data-minimisation, collection-purpose, proportionality and consent safeguards where the Privacy Act and APP 3 apply.
    Does not establish: Whether a particular Rotary club is an APP entity or whether a proposed renewal survey, diagnostic or member record is lawful in its actual circumstances.
  • Better Practice Complaint Handling Guide
    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: The club's local need, legal position, capability, cost, safety, accessibility, suitability, likely effectiveness, authority to act or approval of the initiative.

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 gives the club a clearer view of people's experiences before decisions are made, including feedback that informal conversations can miss.

It may suit: The people whose experience the club needs to understand, especially voices that are not often heard.

Use it when

  • Consider Suggestion Box System when feedback is collected informally, repeatedly raised or rarely followed by a clear response.
  • A club that hears useful ideas informally but loses them between conversations, meetings and board agendas.
  • Members who prefer a written, asynchronous or lower-pressure contribution route alongside meetings and direct conversations.
  • A small pilot with a named review team, clear triage rules, more than one access method and a monthly feedback loop.

Before the club starts

  • A board-approved scope defining what the box accepts, what it does not accept, who reviews it, the review frequency and the response standard.
  • A triage and referral protocol for complaints, safety matters, harassment, safeguarding, privacy, financial concerns and urgent operational issues.
  • An honest collection notice covering identification, access, use, reporting, storage, retention, deletion and the limits of confidentiality or anonymity.
  • Equivalent physical, digital and assisted submission options, an accessible response channel and a named independent reviewer for conflicts involving the usual review team.

Capacity guide

Likely cost
Low; use existing survey, meeting and communication channels where possible.
Lead time
About two weeks for one complete listening and response cycle.
People
Three to five people, including a decision owner, feedback coordinator and action owners.

A useful club conversation

Questions worth asking

  1. What would make someone use this route instead of staying silent, and what would make them distrust it?
  2. Which submissions must leave the suggestion workflow immediately, and who can transfer them safely without losing the person between systems?
  3. What will members see each month so they know ideas are considered even when the answer is no or not yet?

Common traps

  • Trying Suggestion Box System when An unattended box, an anonymous accusation channel or a substitute for confidential complaint, safeguarding, grievance or emergency pathways.
  • Proceeding with Suggestion Box System when Promising anonymity when handwriting, metadata, free-text detail, access logs or a small membership could reveal the contributor.
  • A reviewer has a conflict or can identify and disadvantage a contributor. — Require conflict declarations, recusal and an independent review route, and separate contributor identity from decision material wherever practical.

A practical 90-day path

Three milestones for Suggestion Box System
WhenWhat the club doesEvidence to keep
Days 1–30: Agree the local designMap how members currently raise ideas and concerns, where contributions are lost and which matters need a separate responsible pathway rather than the suggestion system. Design the physical and digital entry points, plain-language notice, optional contact choice, access controls and accessible alternatives with a small, varied member test group.A channel map and suggestion-system scope Tested submission routes and collection notice
Days 31–60: Run and adjust the first versionAgree triage categories, acknowledgement and response times, conflict arrangements, urgent escalation and the information that may appear in an aggregate member update. Run a 90-day pilot, check every channel on the published schedule, acknowledge contactable submissions and transfer matters that belong in a safer or more formal process.An approved triage, referral and response protocol A controlled submission and referral register
Days 61–90: Review the evidence and decideRecord each suggestion as accept, explore, refer, decline or out of scope, add the reason, owner and due date, and publish a de-identified response without exposing a contributor or third party. At 90 days, review reach, timeliness, referrals, unresolved items, privacy and access issues and delivered improvements, then change, continue or close the system and dispose of data as promised.A you suggested, we responded update A pilot decision and data close-out record

Fit it to the club you have

Small club

Use an external or district-level reviewer when handwriting, context or relationships could make contributors obvious, and publish themes only when they cannot identify a person.

Larger club

Use a small trained review panel, one controlled register and service standards by category so multiple entry points do not create duplicate or inconsistent responses.

Regional or rural club

Offer paper, telephone and supported submission routes, protect people whose issue could be recognisable in a close community and avoid requiring travel or reliable internet.

Metropolitan, hybrid or online club

Use an accessible mobile form with keyboard operation and a plain-text alternative, restrict platform metadata and keep the digital channel connected to an equally influential non-digital route.

Learn, adapt and know when to stop

Evidence worth keeping

  • Every submission is checked on schedule and recorded as acknowledged, transferred or decided within the published service standard.
  • Every accepted or exploratory suggestion has an owner, next step and due date, and overdue actions are visible to the board.
  • Members receive a regular de-identified response showing what was suggested, what will happen, what will not happen and why.

Change course when

  • A suggestion is actually a complaint, safety issue or request for support and is left in a low-priority queue. — Train reviewers to triage rather than investigate, publish separate responsible routes and transfer urgent or protected matters immediately under the approved protocol.
  • The box collects identifiable or sensitive detail without a necessary purpose or secure handling plan. — Minimise fields, state the actual privacy level, restrict access, avoid unnecessary free text and apply documented retention and deletion dates.
  • Members stop contributing because decisions disappear or only popular ideas receive attention. — Publish service standards and a complete decision-category summary, including declined and deferred suggestions with understandable reasons.

How to put it into practice

Detailed implementation steps for Suggestion Box System
StepActionSuggested ownerTimingEvidence or output
1Map how members currently raise ideas and concerns, where contributions are lost and which matters need a separate responsible pathway rather than the suggestion system.Member experience lead and secretaryWeeks one and twoA channel map and suggestion-system scope
2Design the physical and digital entry points, plain-language notice, optional contact choice, access controls and accessible alternatives with a small, varied member test group.Design lead, privacy reviewer and member testersWeek twoTested submission routes and collection notice
3Agree triage categories, acknowledgement and response times, conflict arrangements, urgent escalation and the information that may appear in an aggregate member update.Board sponsor and review teamBefore launchAn approved triage, referral and response protocol
4Run a 90-day pilot, check every channel on the published schedule, acknowledge contactable submissions and transfer matters that belong in a safer or more formal process.Suggestion review teamWeekly during the pilotA controlled submission and referral register
5Record each suggestion as accept, explore, refer, decline or out of scope, add the reason, owner and due date, and publish a de-identified response without exposing a contributor or third party.Decision owner and communications leadMonthlyA you suggested, we responded update
6At 90 days, review reach, timeliness, referrals, unresolved items, privacy and access issues and delivered improvements, then change, continue or close the system and dispose of data as promised.Board sponsor and independent checkerEnd of the pilotA pilot decision and data close-out record

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.
  • A suggestion is actually a complaint, safety issue or request for support and is left in a low-priority queue. — Train reviewers to triage rather than investigate, publish separate responsible routes and transfer urgent or protected matters immediately under the approved protocol.
  • The box collects identifiable or sensitive detail without a necessary purpose or secure handling plan. — Minimise fields, state the actual privacy level, restrict access, avoid unnecessary free text and apply documented retention and deletion dates.
  • Members stop contributing because decisions disappear or only popular ideas receive attention. — Publish service standards and a complete decision-category summary, including declined and deferred suggestions with understandable reasons.
  • A reviewer has a conflict or can identify and disadvantage a contributor. — Require conflict declarations, recusal and an independent review route, and separate contributor identity from decision material wherever practical.
  • The board must approve the system scope, service standards, reviewers, conflicts, referral paths, information handling, response format and pilot review before launch.
  • Complaints, safeguarding, safety, harassment, financial concerns, privacy incidents and requests for personal support must use the responsible process and not be decided through the suggestion register.
  • The publicly writable candidate source remains unapproved and cannot become controlled source evidence until a source owner supplies a controlled snapshot or changes the integrity boundary.

What to measure

  • After 90 days, review Suggestion Box System. Look for representative participation, published themes, named actions and a report back on what changed, what did not and why.
  • Every submission is checked on schedule and recorded as acknowledged, transferred or decided within the published service standard.
  • Every accepted or exploratory suggestion has an owner, next step and due date, and overdue actions are visible to the board.
  • Members receive a regular de-identified response showing what was suggested, what will happen, what will not happen and why.
  • Unmanaged urgent matters, lost referrals, unauthorised access, misleading anonymity claims and unresolved privacy incidents remain at zero.

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

Suggestion System Scope and Service Standard

Define what the system can receive and the response members can rely on.

Open supporting document
02

Submission Form and Collection Notice

Collect only necessary information while explaining choice, use and privacy limits.

Open supporting document
03

Triage and Safe Referral Guide

Move each submission to the right process without asking the contributor to start again.

Open supporting document
04

Suggestion Decision and Action Register

Maintain an accountable record from receipt to decision and delivery.

Open supporting document
05

You Suggested, We Responded Update

Close the feedback loop without exposing contributors or private matters.

Open supporting document
06

Access, Retention and Deletion Log

Control who handled submission information and confirm disposal at the promised time.

Open supporting document

Related playbook entries

  • E-156
  • E-158

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.