# Working with Document Change Requests

QualityDocs Vaults include the *Document Change Request* (DCR) object to support Vault users requesting changes for individual Vault Library documents. In Vaults configured for [Multi-Document Change Control (DCC)](/en/lr/42152/) and [Periodic Review](/en/lr/72024/), *Document Change Requests* can additionally be managed in parallel with *Document Change Control* and *Periodic Review* records.



<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>: This article outlines Veeva’s best-practice recommendations for managing DCRs. As the <em>Document Change Request</em> object is highly <a href="/en/lr/8255861/">configurable</a> to meet your organization’s requirements, some of this information may not apply to you.</p>
    </div>
  </div>
</div>



## Creating a Document Change Request

To create a new change request:

1. Locate the document for which you're requesting a change.
2. In a document tab, the Doc Info page, or search results, open the **All Actions** menu and select the **Create Document Change Request** user action. The label for this action may be different in your Vault.
3. Fill in request details. When creating a request from the document, you don't need to fill in the *Target Document* field. Vault automatically selects the document version you were viewing when you initiated the action.
4. Click **Save**.

You may also be able to create a change request from a custom tab, for example "Change Requests". When creating this way, you must select a specific document (including version) in the **Target Document** field.

## About Document Change Controls

The Multi-Document Change Control (DCC) feature's best-practice [configuration](/en/lr/37406/#dcr-object) includes functionality to automatically link *Document Change Requests* associated with the DCC's documents, as well as manage DCR record status in parallel with the DCC as it moves through its lifecycle. 

See link [Working with Multi-Document Change Control (DCC)](/en/lr/42152/) for details.


### About Non-DCC Document Change Requests 

Vault can automatically close *Document Change Request* records which are not associated with a *Document Change Control*. 

When your Vault is configured according to Veeva recommendation, non-DCC DCRs are inactivated when their associated document reaches its Steady state (for example, *Approved*) or its *Obsolete* state.


## About Periodic Reviews

The QualityDocs Periodic Review feature set can auto-start periodic review workflows and follow-up tasks, and provide clear visibility on triggering *Document Change Control* records as part of the Multi-Document Change Control (DCC) process.

When a document undergoes Periodic Review outside of the DCC process, Vault can automatically inactivate *Periodic Review* records when the related document reaches a destination state.


## Viewing Change Requests from a Document

When enabled, the [Quality Relationships](/en/lr/50533910/) panel includes a **Document Change Requests** section. Once a document is associated with a *Document Change Request*, Vault automatically populates the panel with a link to the record.