July, August, September 2026 Updates

Explore new Q3 2026 updates including Occurrence Schedules, an enhancement to Scheduling in Event Manager that lets a single schedule request hold more than one schedule, each with its own time, location, resources, and repeat pattern.

Occurrence Schedules: One Request for Events That Vary

Real events rarely fit into one neat time slot. A camp breaks for lunch and picks back up in a different room. A season practices on two days at one time and a third day at another. Until now, each of those variations needed its own schedule request. With Occurrence Schedules, one schedule request can hold more than one schedule, and each schedule carries its own time, location, resources, and repeat pattern.

What's New

With Occurrence Schedules, you can:

• Add more than one schedule to a single request using the new "add new schedule" button
• Book time slots with a gap between them, such as a morning session and an afternoon session, on one request
• Use different buildings and resources at different times within the same request
• Schedule occurrences that overlap on purpose within the same request, without conflict errors (conflict detection still applies between separate requests)
• Combine different repeat patterns on one request, such as Monday and Wednesday at one time and Friday at another
• Collapse each schedule section to see just the key details
• Edit individual occurrences on their own, the same as before
• Choose how automated work requests are generated when a custom field is set to create them, either once per occurrence or once per day, grouping same-day occurrences on that request that share the same buildings and resources

Resources are counted by location. Occurrences in the same location share one set of resources, and occurrences in separate locations are treated as having their own sets.

Why It Matters

Scheduling a complex event used to mean chopping it into pieces. Camp with a lunch break? Two requests. Season that practices at different times on different days? Also two. Every extra request was one more thing to build, one more approval to track, and one more chance for something to slip. Now the whole event lives on one request.

For teams that generate work requests from scheduling, batching by day means your custodial crew gets one ticket for the sessions on that request that share the same space and resources, instead of one for every session. 

And if you only book one-off events or simple weekly repeats? Carry on. Nothing changes, aside from one new button you are free to ignore.

Learn More

Learn more about building a schedule request with multiple schedules in our Occurrence Schedules Article.