CR031 - Event Registration

Suggestion:

"Change systems and processes to link event registration with member data so that a richer understanding of attendees can be analysed by Member Group committees."

Category on Overview Diagram
MEMBERSHIP

Instructions:
Please complete Add New Comment section fields as requested below:

FIELD REQUESTED INPUT
Your name:
WILL BE PUBLISHED
With your name !
Email:
WILL NOT BE PUBLISHED
With your email – this will not be made public
Homepage
WILL NOT BE PUBLISHED
LEAVE BLANK
Subject
WILL NOT BE PUBLISHED
LEAVE BLANK
Comment
WILL BE PUBLISHED
Please type JUST ONE these three response options on the first line.

AGREE
DISAGREE
REFER

REFER is to be used to either get more information, or if you like the principal, but have concerns about the implementation.

Then from the second line onwards please add any personal comments if you would like to.
 

Comments

AGREE. There is no need to to

AGREE. There is no need to to supply supply personal details but it would be useful to link attendance to that it can be access via data segmentation, e.g. answer question as to how many people working in a particular area (university, schools, insurance, telecomms etc) have attended a meeting. Or even just to know the area of work of regular attendees - subjects could then be geared towards this.

DISAGREE I agree with Julian

DISAGREE I agree with Julian Kunkel. Branch and SG events should be drop-in to encourage attendance. A register can be taken during the meeting if needed. (And please change 'principal' to 'principle' in the header).

REFER

REFER
As long as it doesn't fall foul of GPDR. Remember that Branch Committees (and, I assume, SG Committees) are not permitted access to BCS PII .

REFER

REFER
you can't track the data of non-members, I would suggest that contravenes GDPR. We have about 200 signed up to our non-members list, made up from people who have attended events previously, and who have asked to be kept informed of future events. They have not expressly opted in to having the BCS store any of their data, other than their email address (??and name??)

Refer

Refer

I suspect this would contravene GDPR unless there is explicit consent. Where there is consent then the data should be kept so that it can be analysed.

DISAGREE

DISAGREE
The vast majority of members are never seen at events. Dicing and slicing the 10% who do doesn't gain anything. And as an active branch with a varied programme, we rarely see the same face twice.

AGREE

AGREE

It would be helpful to know what age groups are attending, for instance. Are we appealing enough to younger members and students? What ones were particularly well attended by women? This would help us run more events that appealed to different demographic to our very male and stale (middle-aged) SG membership.

Refer

Presumably it is dependent on the platform used, so people opt in to their data being used for analysis. As long as there is resource in place to effectively analyse the data - what events work, which ones don't, what times seem to be best; or are there gaps we are not filling. If it can be used to create more inclusive events, whilst committing to protecting data then why not.

AGREE - the data provided can

AGREE - the data provided can be suitably anonymised and segmented. I am looking at a lot of this for a small country community and where there is insufficient members of a particular category it is either omitted or swapped with a neighbouring area on a random basis. If we know the types of people that book and attend we can focus on what interests them, and also look at what we might do to attract the rest. Signing in sheets are worse than useless.

Add new comment