Posted: January 21, 2025 at 9:52 pm
|
Hello, I need advice on how to setup my event. I have a 1 Day Skills Competition taking place with 80 different Skills in 2 Categories – 40 Skills for Secondary students and 40 Skills for Post-Secondary students. Each Skills Competition has a limited number of spots. Individual students register and schools register multiple students in several Skills Competitions at the same time (make 1 payment for multiple students). I am thinking – create 2 events: Secondary and Post-Secondary. In the Secondary event I will create 40 Event Dates and the matching 40 Tickets. I will do the same for post-secondary. I can create the capacity for each Event and set the Ticket quantity for the matching ticket (keep the same). The reason I am thinking this is the way to go is for the schools who want to register multiple students and make 1 payment. Next year, I can then make a copy of the event, then update the dates of the Events and Tickets. The alternative is to create 80 different Events – with 1 Event Date and 1 Ticket. If I do it this way, I don’t think I can have a school register their students at one time to make one payment? This might be easier making 1 Event Date and 1 Ticket; however, I don’t see a way of making a clean table. What are your thoughts? Thank you. Jeff |
|
|
Hi Jeff, So, I’ll start with how I think I would set this up based on the above and that would be this set up:
Becuase then you have small ‘events’ to manage overall and you can direct the relevant users to the correct events. It wont work if those need to share capacities but I’m assuming they don’t. — But let’s dig into this a little more to confirm this.
What makes you think that? EE gives you the option of collect registrant information for either JUST the first ticket (meaning that all of the tickets selected in a single group registration as for that single attendee) or collecting for EACH ticket selected in a group (meaning you you provide the attendee information for each individual ticket selected). With both of those set ups the school can select the tickets and pay in a single transaction, but option 1 means they register each individual student across whichever tickets they need and then pay… so 5 students means running through registration 5 times, each selecting the relevant skills and completing payment. Option 2 can combine that all together, but it means that the teacher registering will need to repeat the attendee information for each student on each skill. For example, if Student 1 is registering for Skill A, B & C and Student 2 is registering for Skills A & D, the teacher inputs Student 1’s info 3 times and Student 2’s info 2 times on the registration form. So I guess the question here is, do you need student information for each skill, and if so, do you want to force the teacher to register each student individually but only have to enter that student details once for all skills they are registering onto… Or combine everything together but the teacher will need to input each students details multiple times?
From the above, I don’t think this works wee as individual Events, its means the teach will need to visit each individual event/skill to add the ticket. In a single event they get to select all of the skills in a single step. |
|
You must be logged in to reply to this support post. Sign In or Register for an Account
