# Using PromoMats Standard Metrics PromoMats Standard Metrics allow Vault users to keep track of key metrics about their PromoMats content. Standard Metrics track information that answers the following questions: * What types of material have been developed? * What is the average approval time for a piece of material? * How many review cycles does it take for content to be approved? * What is the average time content spends in review? * What is the approximate cost to create content across various content types? PromoMats Standard Metrics are populated in the _Standard Metrics_ section of a document's [_Doc Info_](/en/lr/9753/) page. Vault automatically records a new set of metrics for each _Steady_ state the document enters. ## Fields for Standard Metrics The _Standard Metrics_ section includes the following fields. ### Content Information Fields When you [add a PromoMats document](/en/lr/15085/), you can fill in these fields. * **Global Content Type**: Assigns a universally accepted content type to a document. * **Content Creation Currency**: Assigns a unit of currency to use for _Content Creation Cost._ * **Content Creation Cost**: The amount paid by the customer for the development of the promotional item. This cost should not include media buy, print production, or reviewer time costs. You must select a _Content Creation Currency_ before you set this field. Admins can set default values for these fields. If default values exist, Vault automatically displays them when you create the document. You can select new values for these fields from the picklist. ### Date Fields {#date-fields} Vault automatically populates these fields as documents move through review workflows, enter certain [state types](/en/lr/58172/#lifecycle-states) (_In Review_ and _Steady State_), and reach a major version. Vault does not calculate values for these fields for documents that have not reached a major version. Date fields are available for use in report types that include documents. * **Initial In Review Date**: The date the document entered the _In Review_ state for the first time. * **Initial Steady State Date**: The date the document entered the _Steady_ State and reached a major version for the first time. * **Days to Enter Review:** The time (in days) between the lowest minor version within the major version (for example, document v1.1) and the _Initial In Review Date_. * **Days in Review**: The time (in days) between the _Initial_ _In Review Date_ and the _Initial Steady State Date_. * **Number of Review Cycles**: The cumulative number of times a document enters the _In Review_ state before the _Initial Steady State Date_. * **Days to Approval**: The cumulative time (in days) between the lowest minor version within the major version (for example, document v1.1) and the _Initial Steady State Date_. Vault calculates a set of metrics for each _Steady_ state version of a document. When a document moves out of a _Steady_ state and from a major version to a minor version, for example, from version 1.0 to version 1.1, the date fields become blank, and Vault calculates them again when the document enters an _In Review_ state. You can see values for previous major versions by selecting **Version History** from the **Actions** menu.
Because Vault calculates a day as 24 hours, it is possible for the _Days to Enter Review_, _Days in Review_, and _Days to Approval_ fields to have a value of zero. For example, if Lisa changes a document's state to _In Review_ at 4:00 PM on Thursday, and Ken changes the document's state to _Approved_ at 9:00 AM on Friday, the _Days in Review_ value for the document is zero. Vault includes weekend days when calculating _Days to Enter Review_, _Days in Review_, and _Days to Approval_. ## Copying Standard Metrics Documents When you select the **Make a Copy** action on a document: * If the _Global Content Type_ on the source document is set to "Not Specified", the _Global Content Type_ on the copy will appear blank, even if there is a mapped _Global Content Type_ value. When you click **Save**, Vault automatically updates the value to "Not Specified". * If you select the _Copy Fields_ checkbox and the source document's _Global Content Type_ is an active value, the copy will have the same _Global Content Type_ value. * If you clear the _Copy Fields_ checkbox, Vault does not copy the _Global Content Type_ from the document and instead populates the mapped default _Global Content Type_ on the copied document upon **Save**. If there is no mapped _Global Content Type_, it defaults to "Not Specified". * Vault does not copy values for _Content Creation Cost_ and _Content Creation Currency_. If the default _Content Creation Currency_ for your Vault is a currency, for example _Canadian Dollars_, the _Content Creation Currency_ value on the copy will match the source document, and the _Content Creation Cost_ will be blank. If the default _Content Creation Currency_ for your Vault is "Decline to Provide", the _Content Creation Currency_ and _Content Creation Cost_ default to "Decline to Provide" on the copy. ## Reclassifying Standard Metrics Documents Vault does not update values for _Global Content Type_, _Content Creation Currency_, and _Content Creation Cost_ fields when you reclassify a document, even if default values are configured for these fields on the new document type. ## Durations {#duration-fields} Vault can determine the length of time a document spent in four (4) standard processes: * **Time in Content Creation**: The total time it takes for a piece to be created or updated after review. This is the total time the piece spends with the content creator (internal or agency), and does not include [placeholders](/en/lr/15087/) or planning states. * **Time in Quality Check**: The total time a piece spends in quality check with the content owner or project manager before it is submitted for review and approval. * **Time in Review and Approval**: The total time a piece of content spends in the review and approval process. This includes the time a content owner or project manager spends assessing the workflow outcomes. * **Time in Regulatory Submission**: The total time for a piece to be prepared for submission to the Local Health Authority and the time the piece spends with the Health Authority when applicable. This is the time after review and approval and before the piece is _Approved for Use_. Admins can add lifecycle states to these processes. You can access this information through Pulse. To view durations metrics, use the _Standard Metrics Durations with Documents_ report type to create and run the following reports: * _Standard Metrics in the Previous 12 Months_ * _Standard Metrics in the Last 12 Months_ * _Standard Metrics by Country in the Last 12 Months_ * _Standard Metrics Durations in the Previous 12 Months_ * _Standard Metrics Durations in the Last 12 Months_ * _Standard Metrics Durations by Global Content Type in the Last 12 Months_ * _Standard Metrics Durations by Country in the Last 12 Months_ * _Standard Metrics Durations by Product in the Last 12 Months_ You can also view this information using the _Veeva Standard Duration Metrics_ [dashboard components](/en/lr/8934/).