S-037 · Detailed guide · Theme 5

Monthly Member Report

Use Monthly Member Report to use member information to understand patterns and improve support without reducing people to statistics.

Where this idea came from

Playbook entry: S-037 · Monthly Member Report
Theme: Theme 5: Digital, Data & Systems · Subtheme 3: Member Analytics
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 digital, data and systems, accessibility, privacy, safety, systems or responsible governance; they are not an endorsement of Monthly Member Report, a finding that it suits any club or approval of its local design.

Primary references consulted

Engage emerging leaders (Rotary International)
Used for: Rotary encourages clubs to assess club health, ask members what they want, take suggestions seriously, support leadership and provide relevant service and learning experiences.
Enhancing Belonging and Engagement at Rotary (Rotary International)
Used for: Rotary identifies belonging, respect, accessibility and equitable access to opportunities, networks and support as central to participation and thriving.
Chapter 3: APP 3 Collection of solicited personal information (Office of the Australian Information Commissioner)
Used for: Personal-information collection should be lawful, fair, proportionate and minimised, with additional controls for sensitive information; each club must confirm how privacy law applies to it.
Chapter 11: APP 11 Security of personal information (Office of the Australian Information Commissioner)
Used for: Entities covered by the Privacy Act must take reasonable steps to protect personal information and destroy or de-identify it when it is no longer needed, subject to lawful retention requirements.

Candidate District material consulted

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

Theme_4_All_80_Initiatives_Complete
The exact current-title crosswalk establishes a candidate legacy record for later comparison. No legacy code, unsupported claim or unchecked operational detail was copied into this draft; current official privacy, security, accessibility and governance controls take precedence.

Theme 5 source-assurance wave

What has been checked

4 current primary pages used by this guide were reopened on 9 August 2026.
4 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, feedback, engagement and follow-up principles.
Does not establish: The accuracy of local data, the quality of a particular survey or a decision to automate member contact.
Enhancing Belonging and Engagement at Rotary
Supports: Belonging, accessibility and equitable participation principles for digital member experiences.
Does not establish: That a particular digital workflow is inclusive, accessible or suitable without testing with affected people.
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 collection is lawful in its actual circumstances.
Chapter 11: APP 11 Security of personal information
Supports: Security, access, retention and disposal safeguards where the Privacy Act and APP 11 apply.
Does not establish: That a club's controls are reasonable, that the Privacy Act applies or that a particular retention period is correct.

What still needs a person to confirm

Confirm which privacy, records, safeguarding and other legal duties apply to the club and this local design.
Confirm current ClubRunner or other platform features, permissions, licence settings and supplier instructions in the club's actual account.
Test accessibility and alternative participation routes with affected members rather than inferring conformance from the guide.
Confirm every local fact, starting point, measure, cost, owner and claim before the club decides to proceed.
Resolve any candidate District-source provenance and approval decision without treating the candidate as controlled authority.

The source-verification release gate remains closed.

Checks still on hold

The current Theme 5 index controls the code and title. The exact-title legacy Digital candidate is recorded only as attributed, unapproved evidence and does not replace current identity, controls or source authority.
The connected Drive refresh returned an internal error on 9 August 2026. No unseen file was inferred or promoted; the 7 August intake, duplicate decisions, quarantines, rights boundaries and public-write permission hold remain in force and no sharing was changed.
Before local delivery, the club must approve the decision, participant choices, access arrangements, privacy and records plan, role boundaries, referral or escalation routes, resource limit and the specific control for this boundary: analytics must not rank member worth, predict individual departure or infer sensitive characteristics from thin or biased data.
Formal human review has not started. Monthly Member Report remains an internal initiative-specific draft until all 1,000 initiatives reach the Full-Corpus Review Build and every source, editorial, local-suitability, accessibility and governance gate is resolved.

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

Why a club might use this

It makes everyday club work easier to understand, maintain and hand over.

It may suit: Members who use or maintain the club's information, communications and digital tools.

Use it when

Consider Monthly Member Report when leaders need a clearer picture of participation, retention or workload and have authority to use the relevant data.
A club where the club has a defined user need, accountable owner, current platform information, proportionate data plan and a safe way to test and reverse the change.
A club with a real need for responsible member analytics and capacity to support a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date.
A 90-day trial of Monthly Member Report with a starting point, named participants, a resource ceiling and a scheduled continue, adapt or stop decision.

Before the club starts

A board-approved brief naming which club decision requires aggregated evidence and what interpretation limits will be published, the local authority, people affected, fixed constraints, resource ceiling, decision date and stop conditions.
A starting-point record and participant plan suited to a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date, with accessible information, voluntary choices and a supported alternative route where needed.
Named delivery, evidence and decision owners, including a person authorised to pause Monthly Member Report when a safeguard, permission or boundary is not met.
A proportionate check of governing documents, privacy, information security, accessibility, conflicts, safeguarding, work health and safety, records, finance and referral duties for the actual local design.

Capacity guide

Likely cost: Low if existing reporting tools are sufficient
Lead time: 4–6 weeks
People: A sponsor, data steward and member with analysis skills

A useful club conversation

Questions worth asking

Whose experience, authority, access or safety could be missed if Monthly Member Report is designed only by regular attendees, confident digital users or current leaders?
What would make a completed delivery and evidence pack supporting a continue, adapt or stop decision credible enough for the club's decision, and what would still remain uncertain?
What local adaptation would still respect this boundary: Analytics must not rank member worth, predict individual departure or infer sensitive characteristics from thin or biased data.

Common traps

Trying Monthly Member Report when A club with no open decision, no accountable owner, no capacity to act on a completed delivery and evidence pack supporting a continue, adapt or stop decision or no safe way to pause the trial.
Proceeding with Monthly Member Report when Monthly Member Report must not be used for collecting more data because it is possible, using live sensitive data for training, automating formal judgement or deploying an unowned system without privacy, security, accessibility and recovery controls. Analytics must not rank member worth, predict individual departure or infer sensitive characteristics from thin or biased data.
A volunteer-built workflow becomes unowned, inaccurate or impossible to recover. — Name a service owner, document dependencies, keep tested backups and rollback steps and schedule a maintenance decision.

A practical 90-day path

Three milestones for Monthly Member Report
When	What the club does	Evidence to keep
Days 1–30: Agree the local design	Write the decision brief for Monthly Member Report: define which club decision requires aggregated evidence and what interpretation limits will be published, the starting evidence, people affected, local authority, resource limit, success signals and stop conditions. Identify users and non-users, map access and digital-confidence barriers, explain data use and permissions and retain an equivalent human or non-digital route where essential participation is involved. Apply this specifically to Monthly Member Report and record which relevant experiences or users are still missing.	An approved decision and boundary brief A participant, access and information-handling plan
Days 31–60: Run and adjust the first version	Build and test a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date for Monthly Member Report; complete the Monthly Member Report Initiative Delivery Blueprint, rehearse the boundary wording and confirm who may decide, refer, pause, recover or close the work. Use synthetic or minimised test data, least privilege, versioned configuration, accessible instructions, exception handling and a rollback; do not expose live credentials or private member information. Capture only the evidence needed to judge whether Monthly Member Report advances responsible member analytics.	A tested initiative delivery blueprint and delivery pack A controlled activity and evidence record
Days 61–90: Review the evidence and decide	Compare the evidence with the starting point, validate meaning with affected participants or users, record gaps and unintended effects and prepare a completed delivery and evidence pack supporting a continue, adapt or stop decision without overstating what the trial proves. Make and record the authorised continue, adapt, refer, scale or stop decision for Monthly Member Report; explain the reason, complete every action, close unnecessary records and schedule the 90-day follow-up.	A completed delivery and evidence pack supporting a continue, adapt or stop decision A published participant response, closed action register and next-step decision

Fit it to the club you have

Small club

Choose the smallest maintainable system, use shared role-based administration rather than one person's account and retain printable or telephone alternatives. Apply this specifically to Monthly Member Report, a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date and the club's actual capacity.

Larger club

Separate data, platform, content and approval roles, use staged permissions and keep a shared change and incident register. Apply this specifically to Monthly Member Report, a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date and the club's actual capacity.

Regional or rural club

Design for variable connectivity, older devices and limited local support, with offline continuity and clear escalation to a trusted specialist. Apply this specifically to Monthly Member Report, a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date and the club's actual capacity.

Metropolitan, hybrid or online club

Test across devices, assistive technology and channels, provide captions and accessible documents and keep equivalent controls for remote users. Apply this specifically to Monthly Member Report, a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date and the club's actual capacity.

Learn, adapt and know when to stop

Evidence worth keeping

Monthly Member Report produces a completed delivery and evidence pack supporting a continue, adapt or stop decision by the promised decision date, with evidence limitations, participation gaps and unintended effects stated.
People affected can explain the purpose, their choices, the boundary and how to raise an access, privacy, safety or governance concern.
The trial shows whether responsible member analytics improved from the recorded starting point without shifting hidden workload, risk or exclusion elsewhere.

Change course when

The club proceeds with Monthly Member Report without respecting this boundary: analytics must not rank member worth, predict individual departure or infer sensitive characteristics from thin or biased data. — Put the boundary in the brief and participant information, give the delivery lead stop authority and move any excluded matter to its responsible process.
The system excludes members or creates a single digital path for essential participation. — Test with varied users, provide accessible instructions and retain an equivalent supported alternative.
Permissions, integrations or exports expose more personal information than the purpose requires. — Minimise fields, use least privilege, test permissions, control exports and review access after the trial.

How to put it into practice

Detailed implementation steps for Monthly Member Report
Step	Action	Suggested owner	Timing	Evidence or output
1	Write the decision brief for Monthly Member Report: define which club decision requires aggregated evidence and what interpretation limits will be published, the starting evidence, people affected, local authority, resource limit, success signals and stop conditions.	Board sponsor and information owner	Week one	An approved decision and boundary brief
2	Identify users and non-users, map access and digital-confidence barriers, explain data use and permissions and retain an equivalent human or non-digital route where essential participation is involved. Apply this specifically to Monthly Member Report and record which relevant experiences or users are still missing.	Board sponsor and information owner with the access and privacy contacts	Weeks one and two	A participant, access and information-handling plan
3	Build and test a bounded 90-day initiative with a clear outcome, participant choices, safeguards and decision date for Monthly Member Report; complete the Monthly Member Report Initiative Delivery Blueprint, rehearse the boundary wording and confirm who may decide, refer, pause, recover or close the work.	System lead, privacy contact and access tester	Before the trial	A tested initiative delivery blueprint and delivery pack
4	Use synthetic or minimised test data, least privilege, versioned configuration, accessible instructions, exception handling and a rollback; do not expose live credentials or private member information. Capture only the evidence needed to judge whether Monthly Member Report advances responsible member analytics.	System lead, privacy contact and access tester	Weeks three to eight	A controlled activity and evidence record
5	Compare the evidence with the starting point, validate meaning with affected participants or users, record gaps and unintended effects and prepare a completed delivery and evidence pack supporting a continue, adapt or stop decision without overstating what the trial proves.	System lead, privacy contact and access tester with an independent reviewer	Within seven days of the trial	A completed delivery and evidence pack supporting a continue, adapt or stop decision
6	Make and record the authorised continue, adapt, refer, scale or stop decision for Monthly Member Report; explain the reason, complete every action, close unnecessary records and schedule the 90-day follow-up.	Service owner and independent reviewer	By day 90	A published participant response, closed action register and next-step decision

Controls and safeguards

Check the idea with the people affected and confirm its purpose, owner and practical limits before putting it into use.
Name the system and data owners, restrict access, provide an accessible alternative and document how errors or failures will be recovered.
The club proceeds with Monthly Member Report without respecting this boundary: analytics must not rank member worth, predict individual departure or infer sensitive characteristics from thin or biased data. — Put the boundary in the brief and participant information, give the delivery lead stop authority and move any excluded matter to its responsible process.
The system excludes members or creates a single digital path for essential participation. — Test with varied users, provide accessible instructions and retain an equivalent supported alternative.
Permissions, integrations or exports expose more personal information than the purpose requires. — Minimise fields, use least privilege, test permissions, control exports and review access after the trial.
A volunteer-built workflow becomes unowned, inaccurate or impossible to recover. — Name a service owner, document dependencies, keep tested backups and rollback steps and schedule a maintenance decision.
The current Theme 5 index controls the code and title. The exact-title legacy Digital candidate is recorded only as attributed, unapproved evidence and does not replace current identity, controls or source authority.
The connected Drive refresh returned an internal error on 9 August 2026. No unseen file was inferred or promoted; the 7 August intake, duplicate decisions, quarantines, rights boundaries and public-write permission hold remain in force and no sharing was changed.
Before local delivery, the club must approve the decision, participant choices, access arrangements, privacy and records plan, role boundaries, referral or escalation routes, resource limit and the specific control for this boundary: analytics must not rank member worth, predict individual departure or infer sensitive characteristics from thin or biased data.
Formal human review has not started. Monthly Member Report remains an internal initiative-specific draft until all 1,000 initiatives reach the Full-Corpus Review Build and every source, editorial, local-suitability, accessibility and governance gate is resolved.

What to measure

After 90 days, review Monthly Member Report. Look for a defined question, information suited to that question, clearly noted limitations and decisions that can be explained without exposing individuals.
Monthly Member Report produces a completed delivery and evidence pack supporting a continue, adapt or stop decision by the promised decision date, with evidence limitations, participation gaps and unintended effects stated.
People affected can explain the purpose, their choices, the boundary and how to raise an access, privacy, safety or governance concern.
The trial shows whether responsible member analytics improved from the recorded starting point without shifting hidden workload, risk or exclusion elsewhere.
Every accepted action has an owner, due date and completion evidence, and the club records a reasoned continue, adapt, refer, scale or stop decision.

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

Monthly Member Report User Need and System Boundary Brief

Define the user problem, information flow and excluded uses.

Open supporting document

Monthly Member Report Data Inventory and Purpose Map

Link every field and transfer to a necessary purpose.

Open supporting document

Monthly Member Report Privacy, Consent and Notice Check

Make information handling and choices clear before collection or publication.

Open supporting document

Monthly Member Report Access and Permission Matrix

Apply least privilege and accountable access reviews.

Open supporting document

Monthly Member Report Accessible User Test Script

Test the real task with varied users and alternatives.

Open supporting document

Monthly Member Report Configuration and Change Register

Maintain a reviewable record of settings, integrations and releases.

Open supporting document

Monthly Member Report Incident, Exception and Recovery Card

Give volunteers a safe response route when the workflow fails or data is exposed.

Open supporting document

Monthly Member Report Handover, Backup and Maintenance Plan

Keep the service operable beyond one volunteer.

Open supporting document

Monthly Member Report Member Analytics Delivery Check

Test whether Monthly Member Report genuinely advances responsible member analytics within the subtheme boundary.

Open supporting document

Monthly Member Report Initiative Delivery Blueprint

Turn the initiative title into a locally authorised and testable club design.

Open supporting document

Monthly Member Report Evidence, Decision and Close-Out Record

Bring the evidence, limitations, participant response and final decision for Monthly Member Report into one accountable record.

Open supporting document

Related playbook entries

S-036
S-038

Supporting worksheets

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.

We have checked this

Who can say yes?

Name the person or group that can approve the work, spending and any safety arrangements.

We have checked this

Are people protected?

Check privacy, consent and safety. Collect only the information you genuinely need.

We have checked this

Can everyone take part?

Check the language, format, place, technology and cost for barriers.

We have checked this

Are the facts and permissions right?

Check names, claims, images, quotations, partner references and Rotary branding.

We have checked this

How will we learn?

Note where things stand now, check in at 30, 60 and 90 days, and decide what to do next.

We have checked this