Schedules
Define your recurring cycles once, such as "every quarter", and use them for policy reviews, evidence reviews, trainings, vendor assessments and automated checks.
A schedule is a named cycle, such as Quarterly access review or Annual policy review. Other features use it to know when something is due again. When you change the schedule, every feature that uses it follows the new cycle.
To import, archive or delete schedules, see Collections. Scripts and integrations: see API below.
Add a schedule
- Open Collections, then Schedules, and choose Add schedule.
- Enter a Name that says the cycle, for example
Monthly patch review. Add a Description if you want. - Under Pattern, open Select a schedule pattern and choose a cycle, for example Last Friday of month. The rule appears under Rule, and Next dates shows when the cycle falls next.
- Choose Create.
The cycles you can define
A pattern fills in the controls below it. To define a cycle the patterns do not cover, change the Frequency, the Interval and the days, months or time of day the controls offer. The Rule field shows the result and is read-only. The rule follows RFC 5545, the standard that calendar programs use. Times are in your organization's time zone, which an owner or admin sets under Settings.
A cycle has one of these shapes. Interval works with every one of them.
| Cycle | Example rule |
|---|---|
| Every N minutes, optionally only between two hours. With an hour window the interval must divide the day: 1, 2, 3, 4, 6, 8 or 12 hours, or a number of minutes below 1440 that divides it, such as 5, 10, 15, 20, 30 or 45. The first run of each day is the window's first hour. | FREQ=MINUTELY;INTERVAL=30 |
| Every N hours, optionally only between two hours. With an hour window the interval must divide the day: 1, 2, 3, 4, 6, 8 or 12 hours, or a number of minutes below 1440 that divides it, such as 5, 10, 15, 20, 30 or 45. The first run of each day is the window's first hour. | FREQ=HOURLY;BYHOUR=9,10,11,12,13,14,15,16,17 |
| Every N days, optionally at one time of day | FREQ=DAILY;BYHOUR=9;BYMINUTE=0 |
| Every N weeks on the weekdays you choose | FREQ=WEEKLY;BYDAY=MO,FR |
| Every N months on a day of the month, or on the first to fourth or last weekday | FREQ=MONTHLY;BYDAY=-1FR |
| The 31st of each month, the last day in shorter months | FREQ=MONTHLY;BYMONTHDAY=31 |
| Every N years in the months you choose, on a day or a weekday | FREQ=YEARLY;BYMONTH=1;BYMONTHDAY=15 |
| Every N weeks, months or years, on the day the cycle starts | FREQ=MONTHLY;INTERVAL=3 |
A time of day is an hour and a minute together. A cycle has no end date, and the form does not offer an end or a number of repeats. If a rule is refused, the form says why under This rule cannot be saved.
See what uses a schedule
- Open the schedule.
- On the Detail tab, Related Data lists what uses it:
- assets and vendors;
- policies, records, evidence and record categories;
- assignments;
- integration checks and automation actions.
Check this list before you change or delete a schedule. A change applies to all of them.
Watch out: processes that use the schedule are not in this list. Check Processes before you delete a schedule. A process whose schedule was deleted keeps its next due date.
Reference
| Field | Required | Notes |
|---|---|---|
| Name | yes | 2 to 255 characters. |
| Description | no | |
| Rule | yes | One RFC 5545 rule, chosen in the form with a Pattern or the controls below it. |
| Slug | yes | Made from the name. See Collections. |
Where schedules are used
| Feature | What the schedule sets |
|---|---|
| Policies, records, evidence | The review cycle and the next review date |
| Trainings and policy assignments | How often people must repeat it |
| Record categories | How often a new entry is due |
| Processes | When the next run is due |
| Assets | The retention period |
| Vendors | How often the vendor is assessed again |
| Integration checks and actions under Automations | When they run |
Policies, records and evidence count the next review date from their last review. Each feature's guide says what counts as a review.
A monthly or yearly cycle counted from the 29th, 30th or 31st falls on the last day of a shorter month: a monthly cycle from 31 January is due on 28 February, 31 March and 30 April. A monthly rule with BYMONTHDAY=31 works the same way.
Integration checks and actions count from Monday 1 January 2001, 00:00 in your organization's time zone. When the rule names no day, monthly ones run on the 1st of each month, weekly ones on Mondays, quarterly ones on 1 January, April, July and October, and yearly ones on 1 January. A rule that names a day, such as the last Friday of the month, runs on that day.
When you delete a schedule
- Policies, records and evidence that used it lose their review cycle and their next review date.
- A recurring assignment stops recurring. People who completed the current cycle stay completed.
- Assets, vendors, record categories and processes keep no schedule. A vendor's next assessment date that was already set stays.
- devguard refuses the delete while an integration check uses the schedule, even a draft or archived one. The message names the checks. Move them to another schedule first.
- A schedule that runs an automation action cannot be deleted either, but the error does not say why. Related Data lists the actions.
The list can be filtered by Frequency and Last updated.
CSV columns
The template from Download CSV template has these columns. Leave slug empty to make it from the name.
slug,name,description,ruleSet
quarterly-access-review,Quarterly access review,,FREQ=MONTHLY;INTERVAL=3API
The calls are the same for all collections; see the Collections API. The path is /schedules/.
| Field | Type | Required |
|---|---|---|
organizationId | string | on create |
name | string, 2 to 255 characters | yes |
slug | string, lowercase with hyphens | yes |
ruleSet | string, an RFC 5545 rule in one of the shapes above | yes |
description | string | no |
{
"organizationId": "<organization id>",
"name": "Quarterly access review",
"slug": "quarterly-access-review",
"ruleSet": "FREQ=MONTHLY;INTERVAL=3"
}The API refuses a rule outside these shapes and returns the reason. It stores an accepted rule in its canonical spelling, which may differ from what you sent. The same check runs in the form, the CSV import, the template import and the AI.
How is this guide?