> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/features/data-governance.md).

# Data Governance

Know whether your data is good enough to rely on, with a quality verdict on every governed record, field-level verification and steward digests.

Data Governance tells you whether the data behind your roadmaps, scores and recommendations is good enough to rely on. It checks the fields that matter for completeness, correctness and currentness, gives every governed record a plain verdict, and shows who is responsible for closing each gap.

## What it is

Every governed record is judged on three dimensions:

| Dimension        | The question it answers                                                                  |
| ---------------- | ---------------------------------------------------------------------------------------- |
| **Completeness** | Is the field filled in?                                                                  |
| **Correctness**  | Is the value valid, not just present? For example an allowed choice or a real reference. |
| **Currentness**  | Has someone confirmed the value recently enough to trust it?                             |

The result is a verdict on the record's form:

| Verdict              | Meaning                                                |
| -------------------- | ------------------------------------------------------ |
| **Trusted**          | The data can be relied on.                             |
| **Use with caution** | Some gaps. Check them before relying on the data.      |
| **Do not rely**      | Serious gaps. Fix them first.                          |
| **Partly assessed**  | Only part of what should be checked has been assessed. |
| **Not verified**     | The values have not been confirmed by a person.        |
| **Not assessed**     | No assessment has run yet.                             |

An administrator decides what is governed:

| Concept            | What it is                                                                                                                                                                    |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Charter**        | A governance program. It covers a set of tables and names a **Program steward**. A charter is **Standing**, or a **Campaign**: a time-boxed drive with a deadline and a goal. |
| Table in a charter | For each table, which records are in scope, who the steward is, and what has to be true.                                                                                      |
| **Rules**          | The checks for each table, such as a field must be filled, must hold an allowed value, or must be re-reviewed within a number of days.                                        |

## When to use it

* **As a record owner:** check and confirm the data on your records.
* **As a steward:** close the gaps your digest lists.
* **As an analyst:** see quality next to the data before you rely on it.
* **As an administrator:** decide which data matters and how it is checked.

## How to

### Check a record's data quality

The **Data quality** section of a Form shows everything about one record's data quality in one place: the verdict, the score for each dimension, and every governed field.

1. Open the record as a [Form](https://docs.ins-pi.com/command/the-portal/content-types.md#form).
2. Click the **Data quality** tile at the top. The Form scrolls to the **Data quality** section. The small arrow beside the tile (**Data quality details**) opens a summary instead.
3. Read the head row: the verdict, then the charter, how much of the record could be judged (for example **96% of checks · 10 fields**) and when it was last checked.
4. Read the table. Each dimension, **Completeness**, **Correctness** and **Currentness**, heads its own column with its score, and each row is a governed field.

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2Fgit-blob-c26645dc2461b336d8829aceb53f40645300eff5%2Fcommand-form-data-quality-panel.png?alt=media" alt="The Data quality section of a Form, with the verdict and facts on top and the governed fields in a table, one column per dimension, each headed by its score."><figcaption><p>The Data quality section of a Form</p></figcaption></figure>

The section has these parts:

| Part         | What it shows                                                                                                                                                                                                                                                                                      |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Head row     | The verdict and its facts. When more than one charter governs the record, tabs on the left: **All charters**, which pools them, then one tab per charter with its own score. When the verdict is **Not verified**, a link such as **3 fields unconfirmed** highlights the fields still to confirm. |
| Column heads | The score for **Completeness**, **Correctness** and **Currentness**. A dimension no rule checks shows **n/a**, and a field it does not check shows a dash.                                                                                                                                         |
| Field table  | Each governed field with its **Value** and its result for each dimension. The **Currentness** cell also shows its verification state. Click a field's name to see each rule's result and which charter checks it.                                                                                  |

Above the table:

* **Show** chooses **Needs attention** or **All fields**. **Needs attention** opens on the first four fields that need you, with a line to show the rest.
* **Sort** orders the rows by **Needs attention**, **Field name** or **Verification due**.
* **Search fields** finds a field by name.

If nothing matches, **Clear view** resets them.

### Verify fields

1. In the **Data quality** section, find the field in the table.
2. Click **Verify** in its **Currentness** cell to confirm the value is right, or **Verify all** at the top to confirm every field that is due. In a narrow section, **Verify all** and **Reassess** sit in the **⋮** menu (**More data quality actions**).
3. Click **Reassess** to score the record again.

Rows keep their place while you verify. Click **Re-sort** to sort them again.

Each field's verification state tells you what to do, for example:

| State                                                               | What to do                                                                                                                            |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Nothing to verify**                                               | The value is missing. Fill the field with **Edit**, then verify it.                                                                   |
| **Unconfirmed · 30 d left**                                         | Nobody has confirmed the value yet. Its review period counts from the day the record was created. Confirm it before the days run out. |
| **Never verified**                                                  | Nobody has confirmed the value, and its review period has run out. Confirm it now.                                                    |
| **Changed since verified**                                          | Confirm the new value.                                                                                                                |
| **Overdue · 12 d**, **Due today**, **Due tomorrow**, **Due in 5 d** | Confirm the value is still right. A review shows as due within its last 14 days.                                                      |
| **Verified · 200 d left**                                           | Nothing to do until the next review.                                                                                                  |

If the section says **Not assessed yet**, click **Assess now**.

### Fix values in the section

1. In the **Data quality** section, click **Edit**. Each value in the table becomes a field you can change, and every governed field is shown.
2. Change the values. A field you cannot change shows a lock and the reason, for example that the value belongs to a related record.
3. Click **Commit** at the top of the section to save, or **Discard** to drop your changes. The badge on **Commit** counts your changes.

Command scores the record again after you commit. While it catches up, the section says **Updating the scores after a recent change…**. If the scores are still behind, click **Reassess**.

**Edit** appears only when you have rights to change at least one governed field. On a Command Form, it waits until you save or cancel the Form's own edits. **Verify** waits until you commit or discard.

### Use it on the ServiceNow form

When your administrator has switched form visualization to Command, the **Data Quality** section of the record's ServiceNow form shows the same panel. You read, verify, edit and reassess it there as on a Command Form.

* Click **Open this record in Command** to open the record's Form in Command.
* Commit or discard your data quality changes before you save or leave the ServiceNow form. Until you do, the form's own buttons pause and say why.
* After you commit, the form reloads to show the new values. If the form has unsaved changes of its own, it asks first.

### See quality next to the data

* In a [Table](https://docs.ins-pi.com/command/the-portal/content-types.md#table), open **Columns** and choose **Data Quality**: **Overall**, **Completeness**, **Correctness** or **Currentness**, for all charters or one.
* On a [Dashboard](https://docs.ins-pi.com/command/the-portal/content-types.md#dashboard), add the **Data quality** widget for a population's quality and coverage.

### Set up governance (administrators)

1. Open **Global Settings > Data Governance** and click **Add charter**.
2. Give it a **Charter name**, a **Program steward**, and choose **Standing** or **Campaign**. For a campaign set **Starts**, **Due** and a **Goal %**.
3. Add a table. On **Settings**, set the conditions that select the records in scope and, optionally, a **Steward** and a **Notification policy**.
4. On **Rules**, click **Add check** and choose what you are checking (a field, a relationship, a measure or a lifecycle) and what you expect.
5. On **Scores**, review how the table's result is scored.
6. Click **Recompute** to assess right away.

To show the **Data quality** section on a Form, add the **Data quality** widget to a section of the form layout in **Global Settings > Forms**. Add it to the top band too if you want the **Data quality** tile.

## Good to know

* Stewards receive a periodic digest of open gaps, by email, in-app notification or both, as set in the notification policy.
* A value from a trusted operational source can count as verified without a manual review. A hand-typed value still needs one.
* A charter can also check planned data in a [Scenario](https://docs.ins-pi.com/command/the-portal/content-types.md#scenario).
* [Command Dialog](https://docs.ins-pi.com/command/features/command-dialog.md) can tell you which data is missing for records you own.
* Changing Data Governance settings needs the Command Admin role. Others see the settings read-only, with the reason.
* When several charters govern a record, its verdict is the worst of theirs: one charter with an overdue review makes the record **Do not rely**, even if the others are fine. Each charter's tab shows its own verdict.
* **Not governed** means no charter covers the record's type, so there is no score to show. It is not a failing score.
* **Data quality unavailable** means the score could not be read. Command shows no score rather than a wrong one; click **Try again**.
* The score is not the legacy Data Quality percentage. The same record can read 57% in the legacy view and 84.6 in Data Governance, because each one measures it with different rules.

{% hint style="info" %}
Data-quality gaps are not created as tasks in **My Tasks**. Stewards work from the digest and from the record's **Data quality** section.
{% endhint %}

## Related

* [Measures](https://docs.ins-pi.com/command/features/measures.md)
* [Scoring](https://docs.ins-pi.com/command/features/scoring.md)
* [Tasks, Notifications and Approvals](https://docs.ins-pi.com/command/the-portal/tasks-and-notifications.md)
* [Retire legacy Data Governance](https://docs.ins-pi.com/command/get-the-app/upgrade-v260-to-v261/path-c-retire-some-features/data-governance.md), for switching ServiceNow forms to the Command view


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ins-pi.com/command/features/data-governance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
