**Source URL:** https://safety.veevavault.help/en/lr/679956/index.md

# Generate a QC Checklist

After a data entry task is complete, <a href="/en/lr/01173/#about-case-data-entry-review">a quality control (QC) task is assigned</a> to the appropriate participants to ensure there are no errors on the _Case_.

If a _Case_ meets certain _Creation Rule Criteria_, Vault may generate a _Checklist_ [during _Case_ processing][1] and [after _Case_ closure][2]. You may also be able to [manually trigger QC _Checklist_ generation][3] for a _Case_ in _QC_ state. QC _Checklists_ provide guidance and specific field verifications when performing a QC task for a _Case_. These _Checklists_ leverage <a href="/en/lr/49033/">Vault _Checklist_</a> functionality. 

The following list describes the relevant terms: 
* **In-process _Checklist_**: Used to perform QC during _Case_ processing.
* **Post-closure** **_Checklist_**: Used to perform QC after the _Case_ is closed and the _Process Completion Date_ is set. These _Checklists_ are scheduled periodically.

## Prerequisites

To use QC _Checklist_, your Admin must <a href="/en/lr/679958/">enable QC _Checklist_ generation</a> and <a href="/en/lr/679957/">configure QC _Checklist Creation Rules_</a>.

## How Vault Generates In-Process QC Checklists {#in-process-checklists}

Vault generates an in-process QC _Checklist_ when a _Case_ enters the lifecycle state specified by the <a href="/en/lr/679957/#rule-phase">_Rule Phase_</a> of the _Checklist Creation Rule_.

Vault runs through the _Checklist Creation Rules_, using <a href="/en/lr/679957/#qc-checklist-terms">_Checklist Creation Rule Criteria_ and sampling</a>, and chooses the first one the _Case_ meets successfully. Using this rule, Vault determines which _Checklist_ design to use for the _Case_ and generates a QC _Checklist_ tailored specifically for the _Case_. Vault also creates a _Case Checklist Rule Assignment_ record where you can see which _Checklist Creation Rule_ was used to generate the _Checklist_.

A QC _Checklist_ is not generated in the following instances:

* Vault does not find a successful _Checklist Creation Rule_.
* The _Locked By_ field is blank on the _Case_ object. Depending on your Admin's configuration, this field may be labeled _Assigned To_.

## How Vault Generates Post-Closure QC Checklists {#post-closure-checklists}

Vault generates a post-closure QC _Checklist_ after a _Case_ is closed (the _Process Completion Date_ is set). Vault identifies closed _Cases_ at 
<a href="/en/lr/679958/#set-post-closure-qc-interval-setting">an interval set by your Admin</a>. For example, if they set the _Post-Closure QC Interval_ setting to `Weekly`, Vault performs a search for closed _Cases_ once a week and generates a _Case Checklist Rule Assignment_ for every identified _Case_.

Your Admin can also manually trigger post-closure QC _Checklist_ generation in the Admin area of Vault for ad-hoc generation and testing purposes. For more information, see <a href="/en/lr/679958/#manually-test-post-closure-qc-checklists">Enable QC Checklist Generation</a>.

Similar to in-process _Checklist_ generation, Vault considers all post-closure _Checklist Creation Rule Criteria_ and sampling rates.

### Managing Post-Closure QC Checklists

Manage post-closure _Checklists_ using the _Case Checklist Rule Assignment_ records. Vault assigns in-process _Checklists_ based on your Admin's configuration. You must assign post-closure _Checklists_ before they are created. 

To generate and assign a post-closure QC _Checklist_, set the appropriate user on the _Assigned To_ field in the _Case Checklist Rule Assignment_ object.

<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 does not generate <em>Checklists</em> for <em>Cases</em> that are superseded.</p>
    </div>
  </div>
</div>



## Generate QC Checklists

If <a href="/en/lr/679958/#execute-checklist-rules-user-action">configured by your Admin</a>, you can manually trigger QC _Checklist_ generation for _Cases_ in the _QC_ state. Contact your Admin for details.

To manually trigger QC _Checklist_ generation:
1. Navigate to the **Cases** tab and select a _Case_.
2. From the **All Actions** menu, select **Execute Checklist Rules**.

Vault displays a message when the action is finished executing.

<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>: If the <em>Case</em> from which this action was run is <a href="/en/lr/01170/">locked</a> to another user, Vault assigns the generated <em>Checklist</em> to this user instead of the user who ran the action.</p>
    </div>
  </div>
</div>



## Respond to Checklists

For information on responding to QC _Checklists_, see <a href="/en/lr/49033/#responding-to-checklists">Working with Checklists: Responding to Checklists</a>.

## Access Checklist Responses

To access QC responses, navigate to the **Checklists** section and then select the _Checklist_. You can use the QC comments to perform corrective actions on the _Case_. 

[1]: #in-process-checklists
[2]: #post-closure-checklists
[3]: #generate-qc-checklists