The Event Creator, the designer, the visionary powerhouse of the Academic branch
Core Responsibilities
- Coming up with, evaluating, and designing Academic Events
- Thinking of a diverse range of ideas and fleshing them out
- What topic does this address, what ideas does this cover, and what can be tied into this event, what is the educational value
- Evaluating those ideas, to ensure feasibility and engagement
- Thinking about the attendees, how would it be run, are we capable of doing that event justice the way it’s been formulated, would it be a good fit
- Designing the flow and step-by-step of each event
- Really envisioning each step of that particular event, how would it play out, what would happen, how would it run
- Not the exact logistics, but the stages of the event and things, not just leaving the running to the AEO to deal with, since that’s not their duty
- Sorting the behind-the-scenes logistics, with the relevant CMs
- Sorting out the funding
- Including bringing in any external services if necessary, e.g. catering, hosting, equipment, etc., this doesn’t include sponsors (that’s for OO)
- Getting approval from the Chair (for new/bigger events)
- AC and AEO are synergetic roles, so if one starts to wane (out of necessity), the other should try to cover while necessary
Desired Attributes
- Full of ideas, and adaptable to change and SM desires
- Must be willing to listen to what the SMs want, since this is their society
- Must also have lots of ideas of what things to do and how to execute them
- Diverse thinking, must be more than willing to consider which other societies pose interesting collaborative opportunities
- An adequate understanding of Cybersec and what events and event topics would even be suitable for this area, especially with workshops
Committee Connections
Chair: The AC would need to make sure the Chair OKs event ideas and propositions, because the Chair should be keeping track of what SMs liked and what they didn’t, but also just generally, the Chair is also free to add and flesh out ideas
Treasurer: It’s up to the AC to OK the overall costs and logistics drawn up by the AEO (and AC) with the Treasurer, to make sure that the event is financially viable
Tech Officer: The infrastructure for an event may require the aid of the TO. Since it’s the AC’s job to design the event and to handle the ‘back-end’, working with the TO is the AC’s job, if the TO is required for an event
Secretary: To make sure that they’re aware of this event as it’s being planned, partially also because the Secretary should help in reaching out to any external services that may be needed
Puzzlemaster: Cos what fun is an event without any puzzles? :D
Editor/Publicity Officer: To make sure that the word is spread about this event and to ask any pre-planning questions, to see what the SMs would like from this event, or when they’d like this event to be run, etc.
Outreach Officer: The OO will likely receive/send propositions for events for companies, the AC will need to know about such events, to see if anything needs to be designed or if it’s a straightforward event that doesn’t require much on our side
Academic Events Officer: Well, I mean… The AC and AEO should work together to make sure an event is both logistically and holistically well-planned
Notes
- Probably a bit more work than CC, probably comparable to AC, depends how many ideas the AC comes up with, so the first couple years will probably be harder as event templates are created, then later ACs will mostly be able to reuse those (but innovation, because new ideas are good and fun :D)