# Configure Schedule Records To simplify managing recurring PVA obligations, SafetyDocs offers automated PVA scheduling, supporting on-time reporting and reducing manual workload. When users create _Scheduled_-type _PVA Obligation_ records, they populate the _Schedule_ field with a specific _Schedule_ record that defines when and how often Vault creates _PVA Activity_ records and report documents for the _PVA Obligation_ record.

Note: If you have a Veeva Safety Workbench license, you may have access to Workbench Report Set scheduling and signal review scheduling. This functionality uses Schedule records to determine the intervals at which to run a Workbench Report Set and generate Workbench Reports and their Excel documents or to create Signal Reporting Periods, respectively.

### Standard Schedules Vault includes the following standard _Schedules_: * _Bi-Annually_: Every two years. * _Annually_: Every one year. * _Semi-Annually_: Every six months. * _Quarterly_: Every three months. * _Bi-Monthly_: Every two months. * _Monthly_: Every one month. * _First Day of the Month_: Monthly on the first day of the month. * _Monthly on the First Selected Day of the Week_: Monthly on the first day of the week that matches the day corresponding to the _Start Date_ of the _PVA Obligation_ or _Workbench Report Set_ using the _Schedule_. For example, if the _PVA Obligation_ has a _Start Date_ of August 1, 2025 (a Friday), this _Schedule_ runs every month on the first Friday. * _Last Day of the Month_: Monthly on the last day of the month. * _Weekly_: Every seven days on the specified days. * _Daily_: Every one day. * _DSUR_: Follows a DSUR schedule of every year. * _PADER_: Follows a PADER schedule of every three months for the first three years, then once a year thereafter. * _PBRER_: Follows a PBRER schedule of every six months for the first two years, then once a year thereafter. ### Schedules and Schedule Components Each _Schedule_ record contains the schedule's name, description, and links to the child _Schedule Component_ records that define its frequency, duration, repetitions, and the order in which Vault runs them. A _Schedule_ with a single _Schedule Component_ runs according to that single _Schedule Component_'s frequency, duration, and repetitions. When a _Schedule_ contains multiple _Schedule Components_, Vault runs the _Schedule Components_ based on their _Order_ field values. This means Vault first runs the _Schedule Component_ with an _Order_ field value of `1` until its full cycle is complete, as defined by its _Periodicity_ and _Number of Repeats_ values. Then, Vault runs the _Schedule Component_ with an _Order_ field value of `2` until its full cycle is complete, and so on. #### Example Schedule with a Single Schedule Component The _Bi-Annually_ _Schedule_ record, which repeats every two years without an end, consists of a single _Schedule Component_ record with the following field values: * _Number of Repeats_ is `0`: This _Schedule Component_ repeats indefinitely. * _Order_ is `1`: As this is the only _Schedule Component_ defined for the _Schedule_, this value doesn't impact its functionality. * _Periodicity (Unit)_ is `Years`: This _Schedule Component_ runs every _x_ years, where _x_ is equal to the _Periodicity (Value)_ field value. * _Periodicity (Value)_ is `2`: This _Schedule Component_ runs every two years, as defined by both this field and the _Periodicity (Unit)_ field value. #### Example Schedule with Multiple Schedule Components {#example-multiple} The _PBRER_ _Schedule_ record consists of two _Schedule Component_ records, which allow Vault to run the schedule every six months for the first two years, then once a year thereafter. Its first _Schedule Component_ record, which runs every six months for the first two years, contains the following field values: * _Number of Repeats_ is `4`: This _Schedule Component_ repeats four times, at the intervals specified in the _Periodicity_ fields. As the _Periodicity_ field values define a repeating interval of every six months, this means Vault runs this _Schedule Component_ for two years. * _Order_ is `1`: When looking at all of the _Schedule Component_ records on the _Schedule_, Vault runs this _Schedule Component_ first. * _Periodicity (Unit)_ is `Months`: This _Schedule Component_ runs every _x_ months, where _x_ is equal to the _Periodicity (Value)_ field value. * _Periodicity (Value)_ is `6`: This _Schedule Component_ runs every six months, as defined by both this field and the _Periodicity (Unit)_ field value. Its second _Schedule Component_ record, which runs once a year indefinitely after the first _Schedule Component_ has reached its end, contains the following field values: * _Number of Repeats_ is `0`: This _Schedule Component_ repeats indefinitely. * _Order_ is `2`: When looking at all of the _Schedule Component_ records on the _Schedule_, Vault runs this _Schedule Component_ second. * _Periodicity (Unit)_ is `Years`: This _Schedule Component_ runs every _x_ years, where _x_ is equal to the _Periodicity (Value)_ field value. * _Periodicity (Value)_ is `1`: This _Schedule Component_ runs every one year, as defined by both this field and the _Periodicity (Unit)_ field value. ## Prerequisites To create _Schedules_, your Admin must enable PVA Scheduling. ## Create Custom Schedules To create a _Schedule_, you must: * [Create the parent _Schedule_][1] * [Create one or more child _Schedule Components_][2] to define how Vault runs the _Schedule_ ### Create Schedules {#create-schedules} To create a _Schedule_: 1. Navigate to **Business Admin > Objects > Schedules**. 2. Select **Create**. 3. In the **Name** field, enter a descriptive name for your _Schedule_. 4. Select **Save**. ### Create Schedule Components {#create-schedule-components} To create a _Schedule Component_: 1. From the _Components_ section of your _Schedule_ record, select **Create**. 2. In the dialog that appears, populate the following fields, then select **Save**:

Field	Description
Number of Repeats	Enter a number between 0 and 100. This is the number of times this Schedule Component will repeat in the schedule. Entering `0` allows the component to repeat indefinitely.
Order	Enter a number between one and 25. For Schedules with multiple Schedule Components, this number determines the order in which Vault runs the Schedule Components.
Periodicity (Unit)	Select a unit from the picklist: Days Weeks Months Years In combination with the Periodicity (Value) value, this determines the period of time between each repeat.
Periodicity (Unit Monthly)	If you selected Months in the Periodicity (Unit) field, you can select an option to define a specific pattern for when this Schedule Component runs: First Day of the Month Monthly on the First Selected Day of the Week Last Day of the Month Note: If you leave this field blank, Vault initiates the monthly Schedule Component on the Start Date defined in the PVA Obligation or Workbench Report Set using the Schedule.
Periodicity (Value)	Enter a number between one and 365. In combination with the Periodicity (Unit) value, this determines the number of time units between each repeat.

[1]: #create-schedules [2]: #create-schedule-components