Event Structure

There are three basic event structures that are used most often in Slate. 

Event Models At a Glance

A. Use Form Fields on main campus visit template to determine if a prospective student will participate in additional activities while visiting campus.

B. Use Related Events on main campus visit template to allow the prospective student to register for additional events on the same day without submitting additional registration forms.

C. Use separate event registration forms for different on-campus activities.

A combination of the models above may also be used.

Event Structure A - Use Form Fields

mceclip2__3_.png

This event structure is often used to allow registration for multiple on-campus activities that occur on the same day on a single registration form. The main event’s registration limit is sufficient for all of the possible activities.

Institutions that use this structure need to know if the registrant intends to participate in the other on-campus activities. Typically there are only a few, if any, follow-up questions.

Use Form Fields on the main campus visit template to determine if a prospective student will participate in additional activities while visiting campus:

mceclip1__6_.png

  Best Practice: When to Use Structure

Institutions that decide to use Event Structure A typically have these event characteristics:

  • 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.
Event Structure B - Use Related Events

mceclip3__3_.png

Use Related Events on the main campus visit template to allow the prospective student to register for additional events on the same day without submitting multiple registration forms. Maintain a distinct registration limit for the different activities. This structure allows separate constituent event communications.

mceclip4__3_.png

  Best Practice - When to Use Structure B

Institutions that decide to use Event Structure B typically have these event characteristics:

  • The additional on-campus activities have set registration limits that differ from 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.

If event processes require administrative setup specific to one of the related events, add Internal Only fields to the form for that related event's template.

Important!

Do not delete the basic fields that are pre-populated on the form.

  Automated Communications

Upon Registration-type communications for the Campus Visit template are sent to registrants. Upon registration communications are never sent for related event registrations.

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.

Event Structure C - Use Separate Forms

mceclip0__5_.png


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.

mceclip1__7_.png

  Best Practice: When to Use Structure C

Institutions that decide to use Event Structure C typically have these event characteristics:

  • Complex registration forms that cannot be accommodated elegantly on a single registration form.
  • A constituent event requires a complex 'upon registration' communication.
Event Structure D - Use a Combination

mceclip4__4_.png

A hybrid event structure may be used:

mceclip5__3_.png

Was this article helpful?
9 out of 9 found this helpful