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 .

Add new comment