Overview
A master Calendar does nothing on its own until a Calendar Schedule inherits it. Inheriting applies the Calendar's Patterns, Specifics and Exclusions — with their grace periods and reminders — to the Schedule, so one set of timing can serve many Schedules.
This article covers inheriting a Calendar into one or many Schedules, what carries over, and what removing one does. To create a master Calendar, see Creating a master Calendar.
At a glance |
|
Who can do this | Super Users, the Schedule's Owners or creator, or a Role with Schedules › Modify — and you must be able to view the Calendar |
Where | Schedules › a Calendar Schedule › Edit › Inheritance; for several Schedules, Schedules › Toggle Multiselect › Edit › Bulk change Calendar Inheritance |
Works on | Backend (web). Assignees complete the Checklists in the Mobile app. |
Availability | All organizations |
💡 Why this matters: Inheritance is how one cadence serves many Schedules. Edit the master Calendar once and every Schedule that inherits it follows — no per-Schedule rework when the season changes.
What a Schedule inherits
Every Pattern and Specific on the Calendar becomes slots on the Schedule, with the same deadlines, grace periods and reminders.
The Calendar's Exclusions skip its slots on every inheriting Schedule. The Schedule's own Exclusions also skip inherited slots, on that Schedule only.
Slot times use the Schedule's own Time Zone. A Calendar has no time zone, so 08:00 means 08:00 local time on each Schedule.
The Schedule keeps its own Checklists, targets, assignees, reviewers and compliance settings — none of these come from the Calendar.
A Schedule can inherit several Calendars and still have its own Patterns and Specifics; all the slots combine. The Schedule header shows Inherits from, and the Schedules list has a Calendars column.
⚠️ Heads-up: Inherited slots can only be changed in the master Calendar. Clicking one on the Schedule opens a message naming the Calendar it comes from, with Go to calendar. Each Calendar can also be inherited only once per Schedule.
Inherit a master Calendar
1. Edit the Schedule
Go to Schedules, select the Calendar Schedule and click Edit.
2. Open Inheritance
Click Inheritance in the Schedule's header to open Configure Calendar Inheritance, then click the plus button (Add Calendar).
3. Choose the master Calendar
Search for the Calendar and select it. Calendars the Schedule already inherits aren't offered.
4. Decide on slots already under way
Both boxes are unticked by default, so the Schedule starts with the Calendar's next slot that hasn't started. Tick Include started pattern slots or Include started specific slots to add slots already in progress; they open on the Schedule from the moment you add the Calendar.
5. Add the Calendar
Click Add Calendar. The slots appear on the Schedule straight away.
Inherit into many Schedules
Go to Schedules, click Toggle Multiselect and select two or more Calendar Schedules.
Click Edit, then Bulk change Calendar Inheritance.
Choose an Action — Add, Remove or Replace — and the Calendars. Replace sets each Schedule's inherited Calendars to exactly the ones you choose; left empty, it removes them all. For Add and Replace, choose whether to include started slots.
Save, check the list on Are you sure? and confirm. Only the Schedules you're allowed to modify are changed.
Remove an inherited Calendar
In Configure Calendar Inheritance, click the bin icon next to the Calendar, then Remove Calendar. Remove and Replace in the bulk dialog, and deleting the master Calendar, have the same effect.
🛑 Critical: Removing an inherited Calendar can't be undone. Its slots already started on the Schedule end immediately without creating Missing Results, and all its future slots are deleted. To pause a Calendar for a closure, add an Exclusion instead.
Example: seasonal calendars
Scenario: three rides operate in different seasons, and each ride's daily pre-opening inspection should run only in-season.
Setup: build Spring, Summer, Fall and Winter master Calendars. Each ride's Schedule inherits only the seasons it operates — for example, Spring, Summer and Fall.
Result: each inspection runs only in-season, and a change to the Summer Calendar reaches every ride that inherits it at once.
Best practices
Keep one master Calendar per season or operating pattern, and inherit the combination each Location runs.
Put park-wide closures on the master Calendar as Exclusions, and closures for one site on that site's Schedule.
Tick the include-started options only when you need today's slot, such as when replacing a Calendar mid-day.
Check the Calendars column in Schedules before changing or deleting a master Calendar, to see which Schedules it reaches.
Frequently asked questions
Does inheriting a calendar also include its grace periods?
Yes. Grace periods and reminders are part of each Pattern and Specific, so every inheriting Schedule gets them. Change them on the master Calendar. See Adding Grace Periods to Schedules and Calendars.
If I add a calendar after its slot has started, will today's checklist be issued?
Only if you tick Include started pattern slots or Include started specific slots when you add it. Otherwise the Schedule starts with the Calendar's next slot.
Can I use an exclusion to override a master calendar?
Yes. An Exclusion on the Schedule skips inherited slots on that Schedule only; one on the master Calendar skips them on every inheriting Schedule. Tick Exclude Specific Slots to skip Specifics too. Slots already started aren't affected.
I inherited a calendar, but nothing is active on the schedule. Why?
Check the slots: started ones are only added if you ticked an include-started box, and the Calendar's Patterns may have expired. Then check the Schedule has Checklists, targets and assignees who are Location members — see Verifying a Schedule with Schedule Metrics.