How to Use Events: Six Common Scenarios Explained

Springnest Events is flexible by design, which means the right approach depends on the type of events you run. Whether you're managing a recurring series, promoting destination events, or dealing with a schedule that changes week to week — the approach is different each time.

This article covers six common scenarios. Find the one that fits your situation, and you'll know exactly what to do.

You're hosting an event that repeats on known dates, and the details — title, description, images — are the same each time. You want a single event page that shows all the dates, and you want it to automatically move to Past Events once the final date has passed.

Example: A winter market running every Sunday for four months. A school holiday kids programme with five set dates.

Create one event and assign all the dates to it using the Dates section in the event editor. Add each date individually using the structured date picker.

Recommended approach:

One event with multiple dates keeps your Events page clean and focused. Your event appears as a single card on the index — all dates are listed on the event's own page.

Note:

Dates must be added one by one. There is no bulk date import. This is intentional — each date is a discrete entry that Springnest uses to manage the event's lifecycle and Past Event status.

Once all structured dates have passed, the event automatically moves to Past Events and is removed from the upcoming index. No manual action required.

Your event happens regularly, but the theme, lineup, or content changes each time. You want each occurrence to have its own page, its own description, and its own featured image.

Example: You host a live music night every month, but the artist and theme change each time. A monthly guest chef dinner with a different menu and chef each evening.

Create a separate event for each occurrence, with its own title, description, and date.

Tip on naming:

Include the specific detail in the title — not just the event series name. A page full of cards all titled "Live Music Night" is confusing for visitors and harder to manage. Instead, use: Live Music Night – The Cape Trio, 14 June or Guest Chef Dinner – Chef Ané Meyer.

Tip on admin effort:

This approach gives you full creative control, but it does take more time to maintain. Plan for regular content updates — one new event to create and publish each cycle. If this feels like too much overhead, Scenario 1 may be a better fit, even if the details vary slightly.

Note:

This approach also applies if you simply want more cards on your Events index page. Each event you create appears as its own card. Some properties prefer this to make the page feel more active. That's a valid choice — just go in with the expectation that more events means more admin.

You're hosting a recurring event, but the dates aren't fully confirmed in advance. The schedule is weather-dependent, booking-dependent, or just irregular by nature.

Example: A guided sunset hike that runs when conditions allow. A pop-up dining experience with dates confirmed month by month.

Create one event and assign structured dates as they are confirmed. When dates change or are cancelled, edit the event and update accordingly.

Note:

Expect to revisit this event regularly. Managing a shifting schedule means your event is an ongoing task, not a set-and-forget one. Build that into your routine.

If an event date is cancelled after it's been published:

• Remove the date from the event if it's no longer happening.

• Or leave it and add a note in the description — e.g. "This event is subject to weather conditions. Check back or contact us to confirm."

You run an ongoing event that has no planned end. You want it to appear on your Events page as a permanent or semi-permanent fixture — not something that disappears into Past Events after a date passes.

Example: A free walking tour every Tuesday and Thursday. Complimentary sunset drinks every evening during the season.

Create one event and use the Open Date Text field instead of structured dates. Describe the schedule in plain language — for example: Every Tuesday and Thursday or Daily during the summer season.

Important trade-off:

Events using open date text opt out of automatic lifecycle management. The event will not move to Past Events automatically — you are responsible for hiding or deleting it when it's no longer running. Keep this in mind when the season ends or the event is discontinued.

Note on ordering:

Events appear in the order they were created, or in the order you manually arrange them in Admin. Events with open date text are no exception — they sort by their position in your manual order, not by date.

You're not just showcasing your own events — you want your website to serve as a guide to what's happening in your area. The goal is to attract visitors searching for local experiences, and to give your guests a reason to visit your site before and during their stay.

Example: A wine estate that lists the region's food and wine festivals. A bush lodge that highlights nearby conservation events, stargazing evenings, and local market days.

Create a series of events, each representing a destination happening. Create them in the order you want them to appear, or arrange them manually in Admin using drag-and-drop.

Tip on ordering:

Events are displayed in the order they were created, with no automatic date-based sorting. If you want events to appear in a specific sequence — for example, in rough date order, or grouped by type — either create them in that order or reorder them manually in Admin. Drag-and-drop reordering is available from the Events List.

Tip on Event Types:

Use Event Types to categorise your destination events, especially if you're covering a range of experiences — food, music, outdoor, family, etc. This helps visitors navigate and filter what's relevant to them.

Tip on venues:

Each event gets its own venue field. For destination events, always assign a venue with a Google Maps address so guests know exactly where the event is happening — it won't be on your property.

Note on SEO:

Each event has its own URL and its own SEO settings — title, meta description, and custom slug. This is what makes a destination events strategy work from a search perspective. A well-written event page for a local festival can rank independently and bring new visitors to your site. Fill in the SEO section for every event you publish.

You run events at your property, but there are also things happening in your area that your guests would genuinely benefit from knowing about — a neighbouring property's festival, a local market, a seasonal happening nearby. You want to feature both on your Events page.

This can work well, but only if it's done with clarity. Visitors will not automatically understand which events are yours and which are not.

Consider this approach if:

• You host a small number of your own events, and local events meaningfully add value for your guests

• The nearby events are closely tied to why guests choose your property (e.g. a surf lodge near a major surf competition, a wine estate adjacent to a regional harvest festival)

• You're willing to invest in keeping the content accurate and up to date

1. Create Event Types to clearly label your events — for example: On-site and Local & Nearby, or Hosted by Us and In the Area.

2. Assign a venue to every event. For off-site events, the venue name and Google Maps address removes any ambiguity about where the event is happening.

3. For off-site events, add a short note in the event description to set expectations — e.g. "This is an external event not hosted by us. Visit the organiser's website for tickets and details."

4. Link to the organiser's website so guests have an authoritative source for the details.

Note:

Do not assume visitors will interpret the distinction on their own. If your Events page mixes on-site and off-site events without clear labelling, you will get enquiries and confusion. The steps above are not optional if you go this route — they are what makes the strategy work.