Objective

In addition to recurring events, a requirement might also have non-recurring, ad hoc events that do not follow a predictable schedule. For example, 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.

To avoid fines and penalties, and to present documentation in the event that accidents occur, you must have a record of all requirements and their completion. The Compliance Program Managers needs to account for non-recurring events for those requirements that have them. See About Non-Recurring Events.

Solution

The Compliance application enables you to manually add events that do not follow a predictable, recurring schedule. A requirement can have non-recurring events in addition to events that follow a recurring schedule.

Procedure

1. To add a non-recurring event, access the Manage Non-Recurring Events task. From this task, you can also update information for single or multiple non-recurring events. See Managing Non-Recurring Events.
2. Alternately, if you need to adjust information for the non-recurring event, including rescheduling it, you can do so from the Schedule Compliance Events task. From this task, you can work with both recurring and non-recurring events. See Rescheduling Compliance Events.