Templates
Templates allow you to save event configurations for reuse in Schoolea, making it faster and easier to create new events with consistent settings. When you create an event from a template, it copies all the configuration, staff assignments, forms, and reminders from the template.
Templates are ideal when you run similar events regularly, such as parent-teacher conferences each term, weekly tours, or monthly uniform fittings. Rather than manually configuring each event from scratch, you can save your preferred setup as a template and reuse it.
Creating a template
Templates are created from existing events, ensuring that your template reflects a proven configuration that works for your school.
- Configure an event with all your desired settings, including:
- Event configuration (location, booking options, features)
- Staff assignments
- Forms (registration, booking, feedback)
- Reminders
- In the side menu, click Save as Template
- Enter a name and optional description for your template
- Click Save as template
We recommend setting up and running an event first, then saving it as a template once you're happy with the configuration. This ensures your template includes all the settings you need.
Using a template
Once you've created a template, you can use it to quickly create new events.
To create an event from a template:
- Go to the Events page
- Click the Event Templates button
- Find the template you want to use and click Use this template
- Enter a name for your new event
- Click Create Event
The new event will be created with all the configuration from the template, and you'll be directed to set up the specific dates and times for this event.
Events created from templates are independent. Changes to the template will not affect events that were previously created from it.
What gets copied from templates
When you create an event from a template, the following are copied:
- Event configuration: Location, booking length, booking limits, booking buffer, optional features
- Staff assignments: All staff members assigned to the template (deactivated staff are skipped with a warning)
- Forms: Registration, booking, and feedback forms with all questions and settings
- Reminders: All reminder configurations
Templates do not include:
- Event dates and times: You'll configure these when creating the event
- Bookings and attendees: Templates only save configuration, not event data
- Event-specific data: Event code, statistics, or other event-specific information
- Attachments: Use global attachments instead of event-specific ones
Deleting templates
If you no longer need a template, you can delete it:
- Go to the Events page
- Click the Event Templates tab
- Find the template you want to delete
- Click Delete
- Confirm the deletion
Deleting a template does not affect any events that were created from it. Those events will continue to function normally.
Common use cases
Recurring parent-teacher conferences
Save your conference setup as a template, including:
- Booking length (e.g., 5-minute slots)
- All teachers assigned
- Parent booking limits
- Registration and feedback forms
- Reminder timing
When it's time for next term's conferences, create an event from the template and just set the new dates.
Regular school tours
Create a template for your open day tours with:
- Tour capacity limits
- Default location
- Registration form questions
- Tour guide assignments
Use the template each month for consistent tour experiences.
Seasonal uniform shop sessions
Save your uniform fitting configuration including:
- Time slot length
- Booking capacity
- Registration requirements
- Staff assignments
Reuse the template each season when the uniform shop opens.
Tips for effective templates
- Use descriptive names: Name templates clearly (e.g., "Term Conferences - 5 min" or "Saturday Tours")
- Add helpful descriptions: Use the description field to note what makes this template special or when it should be used
- Keep templates updated: If you improve your event configuration, update your template so future events benefit
- Create multiple variations: If you run events with different configurations, create separate templates for each variation