> ## Documentation Index > Fetch the complete documentation index at: https://docs.dash360.com/llms.txt > Use this file to discover all available pages before exploring further. # Risk Quality Check Report > Audit the completeness of your Risk Register at a glance: a Yes/No grid showing which fields are filled in on every risk, so you can find and fix data gaps before running analysis. Risk Quality Check Report ## Overview The Risk Quality Check Report is a **completeness audit** of your Risk Register. It lists every risk in the project as a row and, for each field that matters, shows a simple **Yes** or **No** indicating whether that field has been filled in. Green **Yes** means the field is populated; red **No** means it is missing. This makes it easy to spot data gaps before they undermine analysis: a risk with no probability, no cost impact, or no activity mapping will not contribute correctly to the Monte Carlo on the [Risk Analysis](/user-guide/risk/risk-analysis) page, and this report surfaces exactly which risks need attention and in which fields. **URL:** `/Risk/RiskQualityCheckReport/Index` ## Prerequisites * A project must be selected (use the **Project:** picker at the top of the report). * The project's Risk Register should contain risks; the report has one row per risk. * Your account needs access to the Risk module to open the report. *** ## How to read the report Each row is one risk (identified by its **Risk ID**). The **Edit** icon and **Risk ID** are fixed to the left as you scroll. Each remaining column is a field from the Risk Register, and the cell shows whether that field is filled in for that risk: * **Yes** (green): the field is populated with a usable value. * **No** (red): the field is empty or unset. A field counts as **Yes** only when it holds a real value. For most text fields that simply means "not blank", but a few have stricter rules: * **Category**, **Type**, **Owner**, **Assignee**: a record must actually be linked (not just typed). * **Activities**: the risk must be mapped to at least one schedule activity. * **Probability**, **Cost Most Likely**, and **Schedule Impact** (Risk and Mitigated Risk): the value must be present **and non-zero**, since a zero there usually means "not estimated yet". * **Trigger Date**, **Start Date**, **Finish Date**, **Last Reviewed Date**: an actual date must be set. Scan a column to find every risk missing that field, or scan a row to see everything still open on a single risk. There is no "right" number of Yes values; some fields (such as a Trigger Date or a mitigation plan) legitimately do not apply to every risk. Use the report to confirm the fields you care about are complete, not to force every cell green. ## Editing a risk from the report Each row has an **Edit** (pencil) icon fixed on the far left. Click it to open the full Add or Edit Risk form for that risk without leaving the report. When you save, the grid reloads automatically so the Yes/No columns reflect your change; a field you just filled in flips from red **No** to green **Yes** right away. This lets you fix data gaps in place: scan for the red cells, edit the risk, and confirm the column turns green. ## Columns checked The report checks the same fields you enter on the [Add or Edit a Risk](/user-guide/risk/risk-register#add-or-edit-a-risk) form, grouped here for reference. ### Identification and classification | Column | "Yes" means | | --------------------- | ----------------------------- | | **Title** | A title is entered | | **Description** | A description is entered | | **Category** | A Risk Category is linked | | **Type** | A Risk Type is linked | | **Status** | A status is set | | **Classification** | Threat or Opportunity is set | | **Handling Strategy** | A response strategy is chosen | ### Dates and time-phasing | Column | "Yes" means | | ---------------- | -------------------------------- | | **Trigger Date** | A trigger date is set | | **Start Date** | A start date is set | | **Finish Date** | A finish date is set | | **Spread Type** | A time-phasing profile is chosen | ### Mapping and people | Column | "Yes" means | | ------------------- | ---------------------------------------------------- | | **WBS** | A WBS element is associated | | **WBS Description** | The WBS description is present | | **Work Packages** | At least one impacted work package is set | | **Activities** | The risk is mapped to at least one schedule activity | | **Owner** | An owner is assigned | | **Assignee** | An assignee is assigned | ### Risk and Mitigated Risk Each impact field is checked twice: once for the **Risk** (pre-response) values and once for the **Mitigated Risk** (post-response) values. These two labels are configurable per project and default to "Risk" and "Mitigated Risk", so your column headers read, for example, **Risk Probability** and **Mitigated Risk Probability**. | Column (Risk and Mitigated Risk) | "Yes" means | | -------------------------------- | -------------------------------------------- | | **Probability** | A non-zero probability is set | | **Cost Distribution Method** | A distribution method is chosen | | **Cost Min** | A minimum cost is entered | | **Cost Most Likely** | A non-zero most-likely cost is entered | | **Cost Max** | A maximum cost is entered | | **Schedule Impact** | A non-zero schedule impact (days) is entered | | **Response** | The narrative response is entered | | **Mitigation Plan** | A mitigation plan is entered | | **Mitigation Status** | A mitigation status is entered | ### Other | Column | "Yes" means | | ---------------------- | -------------------------------------------- | | **Consequence** | A consequence narrative is entered | | **Mapping Mode** | A mapping mode (Relative or Absolute) is set | | **Last Reviewed Date** | The risk has been reviewed at least once | ### Custom fields If your project defines custom (notebook) fields on the Risk Register, each one is added as its own column and checked the same way: **Yes** when a value has been entered for that risk, **No** when it is blank. ### Showing the underlying value Every checked field also has a hidden **"… Value"** column (for example, **Title Value** or **Risk Cost Most Likely Value**) that shows the actual stored value rather than Yes/No. These are hidden by default; turn them on with the **column chooser** (the icon above the grid) when you want to see what is actually entered, not just whether something is. *** ## Grid features The report is a full data grid, so you can slice it to focus on the gaps that matter: | Feature | Description | | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------- | | **Search** | Free-text search across the grid | | **Filter row** | Per-column filter inputs directly under the headers (for example, filter a column to **No** to list only the risks missing that field) | | **Header filter** | Click a column header's filter icon to pick values | | **Group panel** | Drag a column header to "Drag a column header here to group by that column" to group rows (for example, group by Status) | | **Column chooser** | Show or hide columns, including the hidden "… Value" columns and custom-field columns | | **Reorder, resize, and fix columns** | Rearrange and pin columns; the Edit icon and Risk ID are fixed to the left by default | | **Paging** | Page through large registers (25, 50, 100, or 200 rows per page) | *** ## Exporting Click the **Download** icon in the page header and choose **Export as Excel**. The file is saved as `RiskQualityCheckReport.xlsx` with the Yes/No color coding preserved (green Yes, red No) and the orange header styling, so the audit is easy to read and share outside the application. ***