Jump to content

Membership Officer - Tracking: Difference between revisions

From Mensa Wiki
BethWeiss (talk | contribs)
m Related: created wow, cleaned up page
BethWeiss (talk | contribs)
m Added rest of wow and example fields
Line 7: Line 7:
* The system is quick to maintain
* The system is quick to maintain
* Another volunteer could understand it easily  
* Another volunteer could understand it easily  
| best   =  
| best =
* Track only information that supports action
* Keep notes brief and useful
* Use a system that can be maintained consistently
* Review tracking regularly
* Make it easy for another volunteer to understand
| pitfalls =
| pitfalls =
* Tracking more information than you use
* Creating overly complex systems
* Letting tracking become a task in itself
* Failing to update information consistently
* Storing information that is not relevant to membership work
}}
}}
== Purpose ==
== Purpose ==
Line 23: Line 33:
|-
|-
| New Members || Who joined and when they were contacted || Ensures timely welcoming   
| New Members || Who joined and when they were contacted || Ensures timely welcoming   
|-
| Outreach || Basic record of messages sent || Avoids missed or duplicate contact 
|-
|-
| Responses || Whether a member replied or engaged || Helps prioritize follow-up   
| Responses || Whether a member replied or engaged || Helps prioritize follow-up   
Line 55: Line 63:
* Be easy to understand   
* Be easy to understand   
* Take only a few minutes to maintain   
* Take only a few minutes to maintain   
Member information should be handled responsibly and shared only with those who need it for legitimate Local Group purposes.
== Example Tracking Fields ==
A simple tracking sheet might include:
{| class="wikitable"
! Member
! Joined
! Contacted
! Response
! Follow-Up Needed
! Notes
|-
| Jane Smith
| 6/1/2026
| 6/5/2026
| Yes
| No
| Interested in games
|}


== Basic Workflow ==
== Basic Workflow ==
Line 60: Line 90:
=== Weekly or Monthly ===
=== Weekly or Monthly ===


# Review new member report  
* Review new member report  
# Send welcome messages
* Send welcome messages
# Update tracking sheet  
* Update tracking sheet  
# Review responses  
* Review responses  
# Identify follow-up opportunities
* Identify follow-up opportunities


=== Ongoing ===
=== Ongoing ===
Line 89: Line 119:


== When to Simplify ==
== When to Simplify ==
 
The system should support your work — not create more of it.  If tracking feels like a burden:
If tracking feels like a burden:


* Reduce the number of fields   
* Reduce the number of fields   
* Focus only on new members   
* Focus only on new members   
* Remove anything you’re not using   
* Remove anything you’re not using   
The system should support your work — not create more of it.
== What Success Looks Like ==
*


== Related ==
== Related ==
* [[Membership Officer - Member Communication]]
* [[Managing Membership Outreach]]
* [[Managing Membership Outreach]]
* [[Making It Personal]]
* [[Responding to Members]]
* [[Responding to Members]]
* [[Membership Officer - Templates and Samples]]
* [[Membership Officer - Templates and Samples]]

Revision as of 06:35, 1 June 2026

Words of Wisdom

Track only what helps you take action. If you’re not using the information, you don’t need to track it.

What Success Looks Like

  • You know which new members have been contacted and with what information
  • Follow-ups happen when appropriate
  • Information is easy to find
  • The system is quick to maintain
  • Another volunteer could understand it easily

Best Practices

  • Track only information that supports action
  • Keep notes brief and useful
  • Use a system that can be maintained consistently
  • Review tracking regularly
  • Make it easy for another volunteer to understand

Common Pitfalls

  • Tracking more information than you use
  • Creating overly complex systems
  • Letting tracking become a task in itself
  • Failing to update information consistently
  • Storing information that is not relevant to membership work

Purpose

Provide a simple, sustainable way to track membership-related activity so nothing important is missed.

Tracking supports consistency, follow-up, and continuity — without creating unnecessary complexity.

What to Track

Focus on a few key areas:

Area What to Track Why It Matters
New Members Who joined and when they were contacted Ensures timely welcoming
Responses Whether a member replied or engaged Helps prioritize follow-up
Follow-Up Who may need a second touch Supports connection without overdoing it
Notes Brief, useful context (interests, preferences) Keeps interactions personal

What NOT to Track

Avoid overcomplicating your system:

  • Detailed interaction histories
  • Every message sent
  • Complex metrics or scoring systems
  • Information you won’t use

Keep it light and actionable.

Simple Tracking System

A single spreadsheet is usually enough.

You do not need specialized tools.

Your system should:

  • Be easy to update
  • Be easy to understand
  • Take only a few minutes to maintain

Member information should be handled responsibly and shared only with those who need it for legitimate Local Group purposes.

Example Tracking Fields

A simple tracking sheet might include:

Member Joined Contacted Response Follow-Up Needed Notes
Jane Smith 6/1/2026 6/5/2026 Yes No Interested in games

Basic Workflow

Weekly or Monthly

  • Review new member report
  • Send welcome messages
  • Update tracking sheet
  • Review responses
  • Identify follow-up opportunities

Ongoing

  • Add new members to your tracking list as they are added
  • Update responses when they happen
  • Keep notes short and useful

Using Tracking to Support Personalization

Tracking helps you:

  • Remember previous interactions
  • Avoid repeating the same message
  • Suggest relevant events or connections

Using Tracking to Support Continuity

A simple system ensures:

  • Someone else can step into the role if needed
  • Work is not lost between volunteers
  • Processes remain consistent over time

When to Simplify

The system should support your work — not create more of it. If tracking feels like a burden:

  • Reduce the number of fields
  • Focus only on new members
  • Remove anything you’re not using