> 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 programme. It covers a set of tables and names a **Programme 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 and verify a record

1. Open the record as a [Form](/command/the-portal/content-types.md#form).
2. Read the **Data quality** tile at the top. It shows the verdict and, if relevant, a note such as the number of gaps.
3. Click the tile to open **Data quality details**.
4. Read **Quality dimensions**, the **Evidence** (when it was assessed and verified, the next review, the source) and **What to fix**, which lists each open gap and who is responsible.
5. In **Verification**, click **Verify** on a field, or **Verify all**.
6. Click **Reassess now**, or **Save & reassess** if you fixed values.

Each field in **Verification** shows its state, for example:

| State                                               | What to do                           |
| --------------------------------------------------- | ------------------------------------ |
| **Value missing**                                   | Fill the field, then verify it.      |
| **Never verified**                                  | Confirm the value is right.          |
| **Changed since verified**                          | Confirm the new value.               |
| **Review overdue**, **Due today**, **Due tomorrow** | Confirm the value is still right.    |
| **Verified**                                        | Nothing to do until the next review. |

If the tile says **Not assessed**, click **Assess now**.

### See quality next to the data

* In a [Table](/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](/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 **Programme 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 straight away.

## 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](/command/the-portal/content-types.md#scenario).
* [Command Dialog](/command/features/command-dialog.md) can tell you which data is missing for records you own.
* Authoring needs the editor role. Others see the settings read-only.

{% 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 details**.
{% endhint %}

## Related

* [Measures](/command/features/measures.md)
* [Scoring](/command/features/scoring.md)
* [Tasks, Notifications and Approvals](/command/the-portal/tasks-and-notifications.md)


---

# 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.