# Managing Monitoring Schedules

Vault allows you to manage _Monitoring Events_ across multiple _Sites_ using _Monitoring Schedules_. Events can be manually scheduled or applied in bulk from an approved _Monitoring Scheduling Template_.


## **Configuration**

To configure _Monitoring Schedules:_

1. Add the **Site Monitoring Schedule** to the _Study Site_ object.
2. Add the **Monitoring Schedule Templates** page layout section to the _Study_ or _Study Country_ objects, as needed.
3. Add the **Create Monitoring Schedule Items from Template** [user action](/en/lr/43127/#assigning_actions_to_an_object) to the _Monitoring Schedule_ object.
4. Optional: Add a workflow step to run the **Create Monitoring Schedule Items from Template** system action.
5. Configure the appropriate **Object Lifecycle** steps or workflows for approving a _Monitoring Schedule Template_ and related _Monitoring Schedule Template Items_.
6. Configure the appropriate **Object Lifecycle** steps or workflows for approving a _Monitoring Schedule_ and related _Monitoring Schedule Items_.
7. Optional: Add the **Monitoring Schedule Site Parameter** to the _Study Site_ object page layout.

## **Monitoring Scheduling Templates**

You can create _Monitoring Schedule Templates_ on _Study_ and _Study Country_ records. Each template includes a list of _Monitoring Schedule Template Items_ and is associated with a _Monitoring Schedule Parameter_. For example, if you wish to have risk-based schedules, you can create High Risk, Medium Risk, and Low Risk _Monitoring Schedule Parameters_.

Each _Monitoring Schedule Item_ has the following fields:

* _Name_
* _Milestone Type_
* _Monitoring Event Type_
* _Monitoring Visit Method_
* _Recurring_ (Yes/No)
    * _Recurring Frequency_: If the previous field is **Yes**, enter the number of days after which the event recurs.
* _Application Role_ and _Study Team Role_: These two fields determine the CRA assigned when the _Monitoring Event_ is created.
* _Sequence_: This field is required prior to approving a monitoring schedule and must be unique for all related items in a _Monitoring Schedule_.  If multiple valid _Monitoring Schedule Items_ are eligible to create _Monitoring Events_, the highest sequence number determines the recurring frequency.
* _Minimum Window_
* _Maximum Window_

## Site Monitoring Schedules

Approved _Monitoring Schedule Templates_ with corresponding _Monitoring Schedule Template Items_ can be applied to a site's _Monitoring Schedule_ via a workflow step or user action, depending on the configuration.

If a Monitoring Schedule Template is approved for both a _Study_ and _Study Country_, the _Study Country's_ template is used.  If it is only present for the Study, the _Study's_ template is used. If configured, the Monitoring Schedule Parameter is also used to determine the correct Monitoring Schedule Template to apply. 

Once the site's _Monitoring Schedule_ moves to its Approved lifecycle state, Vault then creates _Monitoring Events_ directly from the site's _Monitoring Schedule Items_. Vault automatically uses the specified _Monitoring Event Type_ and _Milestone Type_.  The _Days from Initiation_ field specifies the time period for the initial expected _Baseline Start Date_. If the event is recurring, subsequent _Baseline_ dates are set based on the _Recurring Frequency_.  The _Minimum_ and _Maximum Dates_ allow you to define the expected time frame for a _Monitoring Event_ and can be used for reporting purposes.

If your organization uses custom _Monitoring Event Types_, you can add them to your _Monitoring Schedules_ and _Monitoring Schedule Templates_. Vault will automatically create the custom _Monitoring Events_ with matching _Milestone Types_ once you have [configured the event types and corresponding milestones](/en/lr/42837/#custom-monitoring-event-types).

## **CRA Assignment**

Adding the _Application_ and _Study Team Roles_ allows automatic matching to assign a CRA to the _Monitoring Event_. If a _Study Person_ is both defined and active for the _Study Team Role_ on the _Study Site_, _Study Country_, or _Study_ and if the _End Date_ is either blank or greater than the _Baseline Visit Start Date_, the _Study Person_ will populate in the _Monitoring Event_ created from the item. Vault first evaluates the _Study Site_, then the _Study Country_, and then the _Study_ when attempting to assign the CRA.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault only assigns the CRA if one and only one <em>Study Person</em> is assigned to the role. In other words, if there are multiple <em>Study Persons</em> assigned to the same role, Vault does not default the CRA.</p>
    </div>
  </div>
</div>




## **Monitoring Event Schedule Parameter**

The _Monitoring Schedule Parameter_ field is available to ensure the _Site_ uses the correct schedule when set on a _Study Site_. For example, you can specify additional _Monitoring Events_ for a _Site_ that requires more frequent visits by ensuring the _Monitoring Schedule Parameter_ matches the desired template.
