# How Expectedness Rolls Up to Case Expectedness and Listedness Vault uses _Expectedness_ records to populate the _Expectedness_ and _Listedness_ fields on a _Case_. How Vault populates these fields depends on the _Datasheets_ available, and whether the _Case_ is associated with a _Study_. The following section provides more information on the auto-calculation logic for _Study Cases_ and non-Study Cases. The _Listedness (Status)_ and _Expectedness (Status)_ fields become "Auto-Calculated" when Vault automatically populates these fields. Users can [override the field values][1] manually. ### Expectedness Roll-Up Evaluation The following illustrations show the auto-expectedness process for a Case using the Product, Study, or Study Product Datasheets: **Non-Study Case** Expectedness from Core Product Datasheet See an [explanation of the steps][2] below. **Study Case** Expectedness from Study Datasheet See an [explanation of the steps][2] below. **Multi-Product Clinical Trial Study Case** Expectedness from Study Product and Study Core Datasheets See an [explanation of the steps][2] below. 1 **Expectedness Generation** Vault generates _Case Assessment Expectedness_ records for each relevant _Datasheet_: * **Non-Study Cases**: For each product _Datasheet_ (product family, product core, or local) related to _Case Products_. * **Study Cases**: Based on the following _Datasheets_, when configured: * Study product * Study core * Product (product family, product core, or local) related to _Case Products_
2 **Case Assessment Listedness and Expectedness** To automatically populate the **Expected** and **Listedness** fields on a Case Assessment, Vault looks at the Case Assessment's **Expectedness** records using the following logic: To populate the **Listedness** field on the Case Assessment:
Case Report Type Auto-Population Logic
Non-Study Case

If there is an Expectedness record corresponding to the Product's Core or Product Family Datasheet, this rolls up to populate the Listedness field on the Case Assessment.

If there are no Expectedness records, the Listedness field is not automatically populated.
Study Case

If there is an Expectedness record corresponding to the Study Core Datasheet, this Expectedness rolls up to populate the Listedness field on the Case Assessment.

If there is no Study Product or Study Core Datasheet, but there is an Expectedness record corresponding to the Product's Core or Product Family Datasheet, this value rolls up to the Listedness field.

If there are no Expectedness records, the Listedness field is not automatically populated.
To populate the Expected field on the Case Assessment:
Case Report Type Auto-Population Logic
Non-Study Case

Vault evaluates all Expectedness records under the Case Assessment to set the Expected field, using the following logic:

  • Unexpected: If one (1) or more Expectedness records are set to No or blank
  • Expected: If all Expectedness records are set to Yes
Study Case

If there are Expectedness records, Vault roll-up for Study Products is as follows:

  • Based on the Study Product Datasheet, if one exists, otherwise,
  • Based on the Study Core Datasheet, if one exists, otherwise,
  • Based on the most conservative of the Product Core Datasheet and Local Datasheet, if one exists

If there is no Study Product or Study Core Datasheet, Vault evaluates all Expectedness records under the Case Assessment to set the Expected field as follows:

  • Unexpected: If one (1) or more Expectedness records are set to No or blank
  • Expected: If all Expectedness records are set to Yes
3 **Case Listedness and Expectedness** At the _Case_-level, for both study and non-study _Cases_, both the _Listedness (Core)_ and _Case Expectedness_ fields are synced with the primary _Case Assessment_. Unless the _Case_ fields are [overridden][1], any time the primary _Case Assessment_ changes, Vault updates the associated _Case_-level fields to match. ## Study Product Placeholder Expectedness Roll-Up Evaluation If your Admin has enabled Datasheet Expectedness for Blinded Study Products, for double-blinded clinical trial study _Cases_ without _Study Arms_, Vault generates _Case Assessment_, _Case Assessment Result_, and _Expectedness_ records based on each _Datasheet_ associated with _Study Product Placeholders_ on the blinded _Case_. Vault rolls up the most conservative _Expected_ value across all _Expectedness_ records, including overridden values, to the _Expected_ field of the associated _Case Assessment_. For example, if there are multiple _Expectedness_ records and only one (1) has _Expected_ set to _No_, Vault rolls up _No_ to the _Case Assessment_ regardless of the _Datasheet_ type. ## Override Case Expectedness or Listedness There are two ways to update the Case Expectedness or Listedness fields: * Edit the field on the primary Case Assessment to override the calculated expectedness. The associated **(Status)** field updates to "Overridden" on the Case Assessment but remains Auto Calculated on the Case.
This will automatically update the associated field at the Case-level, because the Case fields are synced with the primary Case Assessment.
* Edit the field directly on the Case to override the value, and prevent Vault from syncing the value with the primary Case Assessment. The associated **(Status)** field updates to "Overridden" on the Case.
### How-To Video: Overriding Auto-Expectedness Evaluations Watch our quick video tutorial on Overriding Auto-Expectedness Evaluations. [1]: #override-expectedness [2]: #expectedness-eval-illustration-steps