--- title: "Event Structure" slug: "event-structure" updated: 2026-03-26T17:57:08Z published: 2026-03-26T17:57:08Z canonical: "knowledge.technolutions.net/event-structure" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt > Use this file to discover all available pages before exploring further. # Event Structure Planning an [event in Slate](/v1/docs/events-overview)? There are a few ways do it. This article helps you choose the right **event structure** for your needs. ## Event structures Your event can likely be managed by one of the following: 1. [One form, multiple fields:](/v1/docs/event-structure#option-1-one-form-multiple-fields) Use form fields on the main event template to determine if a registrant will participate in additional activities. 2. [Related events:](/v1/docs/event-structure#option-2-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. 3. [Multiple forms:](/v1/docs/event-structure#option-3-multiple-forms) Use separate event registration forms for different on-campus activities. You can also use a [combination](/v1/docs/event-structure#option-4-use-a-combination) of these. ## Option 1: One form, multiple fields [Form fields](/v1/docs/form-fields-unmapped-fields) let registrants use a single registration form to register for more than one on-campus activity occurring on the same day. [![mceclip2__3_.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/idun3dxuxuyqlqwqxwfyamceclip2__3_.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/idun3dxuxuyqlqwqxwfyamceclip2__3_.png) #### 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: [![mceclip1__6_.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/iyarcyxstucissepwenswwmceclip1__6_.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/iyarcyxstucissepwenswwmceclip1__6_.png) ## Option 2: Related events Use [related events](/v1/docs/related-events) on the main event template to allow registration for additional events on the same day without submitting multiple registration forms. [![mceclip4__3_.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/fzpqt0cjkweqdrasjl7jamceclip4__3_.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/fzpqt0cjkweqdrasjl7jamceclip4__3_.png) #### 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. > [!WARNING] > 📝 *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. ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/jfbde0ameqmndtolgybdqmceclip0__5_.png) 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. ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/5ik4hpft0mqeo1anpficqmceclip1__7_.png) #### 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. ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/fqiliz59eoqoxymtrzaqqmceclip4__4_.png) #### 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. ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/xku8dco1iemp9rcxo6yc5amceclip5__3_.png) ## Up next: Creating an event template Now that you’ve decided on an event structure, you can [create an event template](/v1/docs/event-templates).