Environmental & Risk Management / Compliance Management / Compliance Program Manager

About Non-Recurring Events

When you create a requirement, you can generate events for the requirement based on the recurring schedule you enter. However, some regulations have requirements that consist of duties that are performed on an ad hoc rather than a predictable recurring basis. These are referred to as non-recurring events.

Non-Recurring Event Examples

The following are examples of events that do not follow a predictable schedule:

Some organizations, such as schools, are required to conduct biannual or annual emergency response drills and fire alarm testing. These aren’t required on specific dates, so organizations typically schedule them for whatever date works best that year. For this type of requirement, you would manually create non-recurring events.
In the US, there are many regulations that require updated certifications and training for people dealing with hazardous materials,such as asbestos. Therefore, for new employees and existing employees, these certifications and training are scheduled as needed, not on a pre-determined recurring schedule.
Some regulations have requirements that are not predictable. For example, a stormwater drain regulation could require drain inspection throughout your property after rainfall exceeds a specified number of inches within a specified number of days. In this case, the inspection would be scheduled as a non-recurring event around the time of the expected heavy rain.

About the Do Not Reschedule? Field

Each event has a Do Not Reschedule? flag associated with it. This flag determines whether the event should be removed when you regenerate events (occurs when this flag is set to No), or whether the event should remain when events are regenerated (occurs when set to Yes). By default, events that are entered manually are set to Yes; events that are generated automatically based on a recurring schedule are set to No. Since non-recurring events do not follow the recurring schedule, it is assumed that you would not want to remove them when the schedule is regenerated. For this reason, non-recurring events generally have the Do Not Reschedule field set to Yes. However, you are able to change this setting if needed.

The Manage Non-Recurring Events task shows only events that have the Do No Reschedule? field set to Yes. If you change this field from Yes to No, for an event that was manually entered, that event is no longer shown in the Manage Non-Recurring Events task. If you change the Do Not Reschedule? field for an event that you generated using a recurring schedule from No to Yes, then that event is shown in the Managing Non-Recurring Events task.

For information on when you might change the Do Not Reschedule field, see Determining if an Event Is Removed When Regenerating Events.

Tasks for Working with Non-Recurring Events

You can work with non-recurring events from any of the tasks for working with events. From the Manage Non-Recurring Events task, you work exclusively with events that have their Do Not Reschedule? field set to Yes. This view includes only events that have an Event Status of Scheduled, In Process - On Hold, or Stopped. See Managing Non-Recurring Events.

You can add non-recurring events from the following tasks:

Manage Compliance Requirements (Events tab)
Manage Non-Recurring Events
Manage All Compliance events