Schedules
Overview
Schedules are reports or other deadlines imposed on a regulated entity as a condition of a permit, compliance action, or environmental project. They broadly apply to either submitted reports (for example, an annual emissions summary report) or notifications (for example, informing the agency when construction begins or ends).
Schedules are added to a source record during the drafting process and are linked to forms that the regulated entity can complete and submit through nVIRO. Submissions are then routed to the appropriate workgroup or user for review, allowing the agency to approve, reject, or request resubmission of revised versions.
Schedule Groups
Related schedules are organized into schedule groups, and each submission version is tied to a specific schedule, as shown in the diagram below.
Schedule Types
Schedule behavior is determined by the schedule type associated with the source record. The schedule type defines which form is used, whether late submissions create a violation (and whether a grace period applies), and whether the schedule requires agency approval.
Schedule types are configured by system administrators. For more information, see the Schedule Types page.
Schedule Due Dates
Each schedule is configured with one of the following due-date behaviors:
As Needed (One Time): Has no set due date, so it is never late. Once received, it is not required again. For example, a schedule could be created to allow a regulated party to notify the agency when construction begins.
As Needed (Recurring): Has no set due date, so it is never late. The regulated party may need to submit it many times—for example, each time a specific event occurs.
Recurring schedules may be set to Allow Single Draft, where submitting the schedule creates the next instance and ensures only one draft exists at a time, or Allow Multiple Drafts, where starting a draft creates a new schedule instance.
Specific Due Date: Has a specific due date and is late if not submitted on time.
Triggered Due Date: Becomes available only after another schedule is received or processed. The triggered schedule has no due date until the trigger event occurs. For example, receipt of a “Construction Begun Notification” schedule could trigger the availability of a “Construction Completed Notification” schedule.
Calculated Due Date (Recurring): Automatically creates recurring instances of the same schedule at a set interval. For example, each progress report could become due 30 days after the previous one is received.
For schedules with due dates, whether a late submission creates a violation is determined by the schedule type. For more information, see the Schedule Types page.
A schedule with a Triggered due date can only be added if at least one schedule already exists in the form set or schedule group. Users may need to save the form set or schedule group to proceed.
Trigger Events
Trigger events must be defined for schedules with Triggered or Calculated due dates. A trigger event can be the Achieved Date, Received Date, or Decision Date of the preceding schedule, which must belong to the same schedule group.
A fourth option, Received Date Override, is available but should be used with caution. A schedule that relies on this trigger is only created if an override date is entered on the triggering schedule.
Recurring Schedules
Schedules can repeat on a set interval, such as the 30th day of each month, using a Specific or Triggered due date. Recurring schedules can be configured for a fixed number of occurrences or set to continue indefinitely as long as the parent record is active.
For Extended or Expired permits, recurring schedules are generated nightly for any schedules due within six months of the current month. For example, the schedule for an annual report due on 7/15/2025 would be created on 1/1/2025.
Schedule Evaluations and Violations
Every schedule has an associated evaluation record that tracks any violations related to the schedule, such as automatically generated late violations or other violations recorded by the reviewer.
Schedule Statuses
Schedule statuses are divided into three main categories—Draft, Active, or Closed—which drive system behavior. The specific statuses within each category are configurable, and some implementations may include additional statuses not listed below.
Status Category | Status | Description | Notes |
|---|---|---|---|
Draft | Not Available | The schedule has not been made available yet. | A schedule may not be available if the trigger event has not occurred yet or the parent record is not yet active. |
Active | Not Submitted | The schedule is active but has not been submitted. | Schedules in this status may be linked to a Draft submission. |
Active | Received | The schedule is active and has been submitted, but the submission has not been reviewed by the agency. | The linked submission is in In Process status at this time. |
Active | Approved, | The schedule is active and has been submitted, and the submission has been reviewed by the agency. | The status displayed reflects the agency’s decision after reviewing the submission. External users may revise and resubmit schedules in these statuses. |
Closed | Not Approved - Closed | The schedule was submitted and reviewed, and the agency decided not to approve it. Because the deficiency cannot be corrected through a revision, the schedule is closed. |
|
Closed | Closed | The schedule is closed because the parent record was deactivated. | This applies to unsubmitted schedules that either had no due date or had a due date after the deactivation. The only exception is permit schedules, which are shared across revisions. Schedules remain active when a permit is superseded by a revision. |
On this page
Related Content