Event Structure
- 29 Feb 2024
- 2 minute read
- Print
- DarkLight
- PDF
Event Structure
- Updated 29 Feb 2024
- 2 minute read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
There are three basic event structures that are used most often in Slate. This article helps you choose the right option (or combination of options) for your needs.
Prerequisite skills
Event structures
📃 One form, multiple fields
Use form fields on the main event template to determine if a registrant will participate in additional activities.
🔗 Related events
Use related events on the main template to allow the registrant to register for additional events on the same day without submitting additional registration forms.
📚 Multiple forms
Use separate event registration forms for different on-campus activities.
🛠️ Use a combination
Mix and match the above options to fit your needs.
📃Option 1: One form, multiple fields
Using form fields lets registrants use a single registration form to register for more than one on-campus activity occurring on the same day.
✅ Good for:
Multiple events on the same day
Need to know whether registrants will participate in other events activities
You’re only asking a few follow up questions
The registration limit of the main event is sufficient for the other on-campus activities
The registration form for the main event is sufficient to capture the information needed, with very few exceptions.
❌ Be aware:
Events must happen on the same day
Main event’s registration limit must be sufficient for all possible activities
Example: Campus Visit
Use form fields on the main campus visit template to determine if a prospective student will participate in additional activities while visiting campus:
📖 Further reading:
🔗 Option 2: Related events
Use related events on the main event template to allow registration for additional events on the same day without submitting multiple registration forms.
✅ Good for:
Your on-campus activities have registration different registration limits than the main event
The registration form for the main event is sufficient to capture the information needed for the other on-campus activities, with very few exceptions
The additional on-campus activities require significant changes to the communication plan
You want to send separate constituent event communications
❌ Be aware:
Do not delete the basic fields that pre-populate the form
Maintain distinct registration limits for the different activities
Add Internal Only fields to the form to related event templates if that event requires specific administrative setup
📬 Automated communications
Upon Registration communications for the Campus Visit template are sent to registrants.
Communications for related events that use any other triggers, including 'Upon Update' or 'Hours before event,' are all sent for any registrants, regardless of which registration form was submitted.
Upon Registration communications are never sent for related event registrations.
📚 Option 3: Multiple forms
This event structure is used for more complex on-campus events, where a single registration form would become cumbersome to collect all of the required information for each activity.
Prospective students can be directed to Event Landing Pages where each of the on-campus events are listed. Communication plans can be used to market additional events to encourage registrants to sign up for those other activities.
✅ Good for:
Complex registration forms that cannot be accommodated elegantly on a single registration form.
A constituent event requires a complex 'upon registration' communication.
🛠️ Option 4: Use a combination
If your events require a little bit of everything, mix and match the above options to suit your needs.
Example: Campus visit with overnight option
In this example, a single form houses the campus visit. On that form is a related event selector for class visits with options for each major. A separate form collects information regarding an optional overnight visit.
Was this article helpful?
