# Create an Expected Schema Check

Source: https://userguide.qualytics.io/data-quality-checks/expected-schema/how-tos/create-a-check/

*Requires the Data Observability (DO) module.*

Step-by-step tutorial for creating an Expected Schema check on a container. For what each property means and how the rule evaluates the data, see the [How It Works](https://userguide.qualytics.io/data-quality-checks/expected-schema/deep-dive/how-it-works/) page.

> **Note: Permission Required**
>
> You need the **Author** team permission on the datastore to create an Active check, or **Drafter** to create it as a Draft. See the [Permissions](https://userguide.qualytics.io/data-quality-checks/expected-schema/deep-dive/permissions/) page for the full matrix.

> **Tip: Show me how**
>
> The app can walk you through this. Click **Show me how**  in the check creation form's header, or press `H` while it is open, and the **Add a Check** walkthrough highlights each step while you fill in the real form.

## Field reference

The **Authored Check Details** form is organized in the sections below. Fill them in as you follow the [Steps](https://userguide.qualytics.io/data-quality-checks/expected-schema/how-tos/create-a-check/#steps).

### Target

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Associate with a Check Template** | No | Toggle | Leave it off for this rule. The toggle replaces the **Rule Type** dropdown with a **Template** dropdown, and Expected Schema is not offered as a template rule type, so no template can supply it. |
| **Rule Type** | Yes | Option | The validation logic to apply. Select **Expected Schema** for this check. |
| **Table / File** | Yes | Option | The table or file whose structure is asserted. Locked after the check is saved. |
| **Custom Anomaly Description** | No | Toggle | Has no effect on this rule. The option replaces the message on Record Anomalies, and Expected Schema emits a Shape Anomaly only. |

> **Tip: Create the table or file from the form**
>
> If the table or file you need does not exist yet, click **Add Computed Table**  next to the **Table / File** field while it is empty (**Add Computed File** on a file-based datastore). Once saved, the new one is selected and pinned to the top of the list with a  icon until you close the form. The button appears only with the **Author** or **Editor** team permission on the datastore, and not when you add a check from Explore.

### Properties

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Fields** | Yes | Option | The fields the container must carry, picked from the container's field list. This is the declaration the check compares the container against; the type each one is checked against comes from the field's profile. |
| **Allow other fields** | Yes | Text | Whether columns that are not declared are tolerated. On, extras pass; off, the container must hold exactly the declared set. |

### Ownership

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Owner** | Yes | Option | The user responsible for the check. Already filled in with the check creator. |
| **Anomaly Assignee** | No | Option | The user automatically assigned to anomalies the check produces. |

### Metadata

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Description** | Yes | Text | A plain-language description of what the check enforces. Supports Markdown formatting: click the field to open the Markdown editor. Click the **Apply suggested description**  button for a suggestion based on the rule type. |
| **Tags** | No | Option | Tags applied to the check for filtering and organization. |
| **Additional Metadata** | No | Key-value | Custom key-value pairs, typically links to catalog entries, tickets, or governance records. |

> **Info: No Filter Clause and no Pass Criteria section**
>
> Expected Schema reads the container's structure rather than its rows, so the form shows neither a **Filter Clause** input nor a **Coverage** slider.

> **Tip: Let AgentQ fill in the form**
>
> When [AgentQ](https://userguide.qualytics.io/agentq/getting-started/) is configured for your deployment, the **Check Assistant** panel in the check form can author the check for you: describe the rule in plain language (for example, "the orders extract must have order id as an integer and status as text") and it proposes a configuration you can apply to the form. Review the filled-in fields, then Validate and Save as usual.

## Steps

**Step 1**: Select the source datastore from the left menu, then click the **Checks** tab.

**Step 2**: Click **Add** in the top-right corner and select **Check** from the dropdown. The **Authored Check Details** form opens.

> **Warning: No tables available**
>
> On a datastore that has no tables yet, for example one that was just added and has not been synced, the form shows a **No tables available** warning (**No files available** on a file-based datastore) that reads **Run a Sync on this datastore before adding checks.** instead of the check fields. When you open the form from the datastore page and you can run operations on the datastore, the warning also offers a **Run Sync**  button, which closes the form and opens the Sync dialog. Add the check once the Sync finishes. The warning does not appear when you add a check from a check template.

**Step 3**: Select **Expected Schema** in the **Rule Type** dropdown.

**Step 4**: Fill in the required fields and any optional ones you need. Every field is described in the [Field reference](https://userguide.qualytics.io/data-quality-checks/expected-schema/how-tos/create-a-check/#field-reference) above.

**Step 5**: Click **Validate** to test the rule against the selected data without saving it. A success message confirms the rule can run on that data. If validation fails, see [Troubleshooting](https://userguide.qualytics.io/data-quality-checks/expected-schema/troubleshooting/#validation-fails-when-creating-the-check).

**Step 6**: Click **Save**. A success message confirms that the check was created.

*Last updated: November 10, 2026.*
