# Configuring Expected Document Lists (EDLs)

In Clinical Operations Vaults, [Expected Document Lists (EDLs)](/en/lr/31833/) help you plan your TMF and more accurately report on TMF completeness. An EDL defines a checklist of the trial records expected (and those specifically not expected) for a specific study, study country, study person, study organization, study product, or site.

EDLs are available on all Vaults. To learn about platform EDL features, see [Working with EDLs](/en/lr/32749/). This article provides configuration details for features that are only available in Clinical Operations Vaults.

## Configuring Reference Sites {#configuring-reference-sites}

[Reference Sites](/en/lr/31833/#reference-sites) allow users to update Expected Documents across multiple sites without having to bulk update each individual Expected Document.

To enable Reference Sites in your Vault:

* Ensure that the desired users have the appropriate permissions to mark a _Study Site_ record as a Reference Site.
* Configure a workflow on the site object and add a step with the System Action **Update Related Expected Documents**. When you do so, you must select a scope for the update:
    * **All sites in same study**: the action will update _EDL Items_ at all sites in the same study as the reference site.
    * **All sites in same study country**: the action will update _EDL Items_ at sites only in the same study country as the reference site.
* Add a user action on the site lifecycle to trigger the new workflow.

<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>: You can only run the <em>Update Related Expected Documents</em> action on <em>Sites</em> which have the <em>Reference Site</em> field set to <em>Yes</em>.</p>
    </div>
  </div>
</div>



## Managing EDL Bulk Update Options

<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>: It is recommended to use Reference Sites instead of bulk updating.</p>
    </div>
  </div>
</div>



After modifying the _Requiredness_ or _\# Expected_ fields on an _EDL Item_ for one site or for one country, you can bulk update these [fields for all sites/countries](/en/lr/31833/#bulk-update) in the same study or for all sites in the same study country.

To remove this option from the dialog, navigate to **Admin > Settings > General Settings** and select the **Hide Update Related EDL Items in the Same Study for Bulk Updates** checkbox. You can add this option back to the dialog by clearing this checkbox.

## Configuring the Create Expected Documents Action

You can configure the [_Create Expected Documents_](/en/lr/31833/#product-specific) action as an event action or entry action on the following lifecycles:

  * _Study Person Lifecycle_
  * _Selected Study Organization Role Lifecycle_
  * _Study Product Lifecycle_

## Configuring Milestone Items with EDLs

[_Milestone Item_](/en/lr/31833/#milestone-relationship) records connect an _EDL Item_ to a _Milestone_. Users can set a _Milestone Item_ record to _Inactive_ when an _EDL Item_ will not be used for a _Milestone._ Setting a _Milestone Item_ to _Inactive_ indicates that this version of the _EDL Item_ is not applicable for this _Milestone_.

To allow users to set _Milestone Items_ to _Inactive_, navigate to **Admin > Configuration > Objects > Milestone Item**. Click **Edit** and select the **Milestone Item Lifecycle** from the **Lifecycle** drop-down. You must then [add a user action](/en/lr/59885/#user-actions) on the lifecycle's _Active_ state to **Change State to Inactive**.

## Synchronizing _Requiredness_ with _# Expected_

You can configure Vault to automatically update the _# Expected_ field when the _Requiredness_ field is updated. Without this option enabled, you will need to update _# Expected_ manually. To enable:

1. Navigate to **Admin > Settings > General Settings > Expected Document List (EDL) Options**.
2. Check the box next to **Synchronize Requirediness and # Expected**.

When this setting is enabled:

* Setting _Requiredness_ to Required will update _# Expected_ to 1 if its current value is 0
* Setting _Requiredness_ to Not Required will update _# Expected_ to 0 if its current value is greater than 0

## Updating _Requiredness_ and _# Expected_ Based on EDL Matching

Vault can automatically update the _Required_ and _# Expected_ fields based on the EDL Match Job. This is an additional feature that an Admin can enable on top of _Synchronize Requiredness and # Expected_. Without this option enabled, you will need to update any _# Expected_ field values greater than 1 manually. To enable:

1. Navigate to **Admin > Settings > General Settings > Expected Document List (EDL) Options**.
2. Check the box next to **Update Requiredness, # Expected Based on EDL Matching**. 

<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>: You must first enable <em>Synchronize Requiredness and # Expected</em> before you enable <em>Update Requiredness, # Expected Based on EDL Matching</em>.</p>
    </div>
  </div>
</div>



When this setting is enabled:

* When the number of matched documents increases to more than zero, Vault updates the _Required_ field value to **Required** if the previous value was anything other than **Required**.
* When the number of matched documents is greater than the value in the _# Expected_ field, Vault updates the _# Expected_ field with the number of matched documents. You may also use the bulk action **Set # Expected to # Actual** to update the _# Expected_ field with the number of documents matched to the Expected Document if the _# Expected_ field is less than the _All Document Count_ field.

<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 automatically increases the <em># Expected</em> field as more documents are found by the EDL Match Job, but it does not reduce the <em># Expected</em> field if documents unmatch. Users can still update the <em># Expected</em> field manually.</p>
    </div>
  </div>
</div>



### Syncing _# Expected_

Vault can also automatically keep the _# Expected_ in sync with the total number of matched documents. This feature adds the _Auto-Manage # Expected_ (yes/no) field to Template EDL Items. To indicate that Vault should manage the _# Expected_ for EDL Items based on the Template EDL, select the **Auto-Manage Expected #** checkbox.

When users create EDL Items based on these Template EDLs, Vault copies the _Auto-Manage # Expected_ field value to the EDL Item. On specific EDL Items, users can perform the **Enable Auto-Manage # Expected** or **Disable Auto-Manage # Expected** actions to enable or disable this functionality.