TOPIC:

My club membership has a great amount of diversity, yet sometimes I'd go in and be see meetings attended only by people of the same gender and ethnicity. This led me to wonder what the membership dynamics were on a more detailed level. To analyze this, I paired Meeting Attendance Reports from FreeToastHost with my own member data to generate the attached charts, which review membership and attendance based on Gender and BIPOC. I think these reports are very useful - they can inform the VP-PR's marketing strategy and the VP-M's efforts to keep members engaged.
It occurs to me that such reports might be useful for dimensions as well:

• People who participate In-Person vs Remote
• For hybrid clubs Corporate Members vs Public Members
• Student / Professional / Retired
• Age Group
• Length of Membership

With this in mind, I wonder if the FTH3 might want to consider including such optional demographic fields (or perhaps user-defined fields) in its membership database.

Finally, a note: we don't discriminate based on gender or race/ethnicity, that is not what this message is about. Understanding club dynamics goes a long way to assessing the health of a club and charting its future!

Thanks as always for the remarkable FTH3 tool.

Dan

Sorry no, will not be considered.
FTH keeps the minimum personal information as possible and this will not change.

That makes good sense.
Thank you.
Dan

We may be able to do a few enhancements based on information that we already have, but Brian and I are aligned that we want to keep the amount of personal information to a minimum.   Keeping personal information (& the amount we keep) is a very sensitive issue that we have discussed quite a bit and we are very keen to comply with current best practices and prevailing regulations in the world.  (e.g. GDPR)

I'm not a developer, so I am just sharing a related idea... I suppose members have some sort of index numbers in the FTH3 database. Perhaps give users the option to include index numbers in reports so that they could then link them more easily to their own club-specific data? These could, but don't have to be, members' offical TMI index number - just something that is persistant.

(Although I am presently keying off "member name", the names as shown on FTH3 differ in some instances from names by which we refer to people ... nicknames, middle names, references to TMI designations, etc.).