Skip to content

Manage Compliance Reminders

The Compliance Scheduler page allows users to manage items that appear in the weekly Upcoming Compiance Tasks notification. The page is configured as two tabs that each contains a basic data grid with cross-filtering options. See the sections on working with data grids and filtering with charts for more information.

Documents tab

Every reminder item must be linked to a document. Documents are entered, with an optional link to a PDF, on the Documents tab. Click the button at the top of the data grid, which will create an empty row for you to enter a name, description, and (optional) link to the PDF.

To generate a PDF link, send the document to a System Administrator, who will upload the document to AWS and provide back a URL.

Add a new compliance reminder

If necessary, follow the directions in the Documents tab section to add a new compliance document.

Click the button at the top of the data grid, which will create an empty row for you to enter the information. The name and description should provide enough context that it is understandable when displayed in the weekly notification.

The "Group" option is the responsible group within LADWP.

The "Agency" option is the primary agency that originated the compliance document (if multiple agencies are equally valid, choose the one that has primary enforcement responsibility for the specific requirement).

Next, configure how you want to receive reminders.

Configure the reminder schedule

There are three configuration options for setting reminders:

  • Recurrence Type: How often does the compliance requirement recur, or does it only happen once?
  • Reminder Type: How far in advance should the reminder begin to appear in the weekly notification? The reminder will appear every week until the Due Date is past.
  • Due Date: When is the requirement due? Depending on recurrence type, the system will use the day, the day and month, or the full date. This must be left blank for conditional requirements.

Not all permutations of the configurations make sense together. For example, a Recurrence Type set to Monthly should not have a Reminder type of "Annual." Similarly, "Conditional" type requirements generally will not have a due date, unless the compliance document expires after a specific date.

If the Recurrence Type is anything other than "Does not recur," the year is ignored in "Due Date" and the reminder will continue to be sent until the "Completed" box is checked.

If the recurrence type is shorter than the reminder type, you may see multiple instances of the reminder appear in the weekly email. For example, a monthly reminder that begins 6 weeks in advance of the due date (say the 1st of the month) creates an overlap, so beginning on Augst 15th the reminder for September 1 and October 1 would appear in the email.

Manage reminders

Reminders may be edited directly from the data grid (see the section on working with data grids). Generally speaking, if a reminder is no longer needed, check the "Completed" checkbox instead of deleting the record. Completed reminders can be easily filtered using the "Completed" pie chart.