Sustainability & Risk / Compliance / Compliance Program Manager
Sustainability & Risk / Compliance / Contract Manager

Non-Recurring Events (Concept)

Note: You can generate events for both contract terms and compliance program requirements. The information in this topic applies to events generated for both contract terms and requirements.

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:

Events for Future, Proactive Compliance Projects

You might have a need to enter events for compliance-related work that you assess needs to be done, but it is discretionary. For example, a compliance manager might assess that all ramps should be repaved in a year or so, but there is no immediate ADA compliance issue. For these events, a compliance manager could create manual, non-recurring events that are not immediately scheduled. These events could be managed in a similar manner to the Projects application by setting the Event Status to Budgeted or Planned before you actually schedule the work. This could be done for small, informal projects for which you don't need the full features of the Projects application, or if you do not have a license for the Projects application.

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:

See Also

Adding and Editing Events for a Requirement or Contract Term.

Managing Events: Overview