Configure Schedule Records | Veeva Vault Help

Depending on your Veeva Safety Suite application licenses, you can use standard Schedules or create custom Schedules to schedule recurring:

Prerequisites

To create Schedules, you must:

Update schedule-related object layouts
Set the Safety Scheduler Job to active

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 record 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 of 1 until its full cycle is complete, as defined by its Periodicity and Number of Repeats. Then, Vault runs the Schedule Component with an Order of 2 until its full cycle is complete, and so on.

Example Schedule with a Single Schedule Component

The Bi-Annually Schedule, which repeats every two years without an end, consists of a single Schedule Component 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).
Periodicity (Value) is 2: This Schedule Component runs every two years, as defined by both this field and the Periodicity (Unit).

Example Schedule with Multiple Schedule Components

The PBRER Schedule consists of two Schedule Components, which allow Vault to run the schedule every six months for the first two years, then once a year thereafter. Its first Schedule Component, 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 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 Components 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).
Periodicity (Value) is 6: This Schedule Component runs every six months, as defined by both this field and the Periodicity (Unit).

Its second Schedule Component, 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 Components 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).
Periodicity (Value) is 1: This Schedule Component runs every one year, as defined by both this field and the Periodicity (Unit).

Create Custom Schedules

To create a custom Schedule, you must:

Create the parent Schedule
Create one or more child Schedule Components to define how Vault runs the Schedule

Create Schedules

To create a Schedule:

Navigate to Business Admin > Objects > Schedules.
Select Create.
In the Name field, enter a descriptive name for your Schedule.
Select Save.

Create Schedule Components

To create a Schedule Component:

Expand the Components section of the Schedule, then select Create.
In the dialog that appears, populate the applicable fields, then select Save.

Schedule Component Fields

The following fields may be available:

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 record 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.