> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/tabulations/reviewing-the-tab-spec-mapping.md).

# Reviewing the Tab Spec Mapping

{% embed url="<https://www.youtube.com/watch?v=eLzGpcaA3CU>" %}

When you build with a tab spec, Metaforms matches each row of the spec to your data. The build then pauses at **Mapping review**, step 4 of 5, so you can check the matches before any tables are built.

If you have no tab spec, ask the Tabulation Agent to draft one from your data. Its draft goes through the same review. See [Using the Tabulation Agent](https://help.metaforms.ai/tabulations/using-the-dialing-agent-for-quick-table-setup.md).

The review opens in the agent panel on the right, and the main area shows **Review pending**.

![Review pending in the main area, with the review in the agent panel](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Fgit-blob-8881cf5bd6a05cac3916cf019719716fe2a624d7%2Ftabulations-mapping-review-pending.png?alt=media)

To review in the wider main area, click **Review here instead**.

![The review in the main area](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Fgit-blob-2c44def53f720180731ffecec8da58799367dd69%2Ftabulations-mapping-review-tray.png?alt=media)

### Check each spec row

Each row shows the spec row, the variable it was matched to, and why. **Accept** is already selected on every row, so you only need to act on the rows you want to change.

* **Accept** keeps the proposed match.
* **Skip** leaves the row out. You can add a reason in "Why skip this row? (optional)".
* **Remap** points the row at something else. Under "Remap to one of these", enter variable names separated by commas, or a family stem, but not both.

![A skip reason box and a remap row](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Fgit-blob-55bb5152660cf82dbaacf527870314b9d2f42ebc%2Ftabulations-mapping-skip-remap.png?alt=media)

A remap row needs a value. Until it has one, the row shows "Name the variables or a family stem to remap to." and the build buttons stay disabled.

A skipped row keeps its place in the deck with a **skipped** badge. It has no numbers, and in the exported file it is a short block that gives your reason.

### Confirm the weight

If the build proposes a weight, **Confirm** or **Decline** it.

### Check the banner

Below the rows, **Proposed banner** shows the columns the spec asks for, with their letters.

![The proposed banner](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2Fgit-blob-6d04abde0c7aa6f0c7bab3e53ea166bb1f4ce169%2Ftabulations-mapping-banner.png?alt=media)

### Approve and build

If the review proposes banners, choose one of these:

* **Approve & build with this banner**, or **Approve & build with these N banners** when there are several, accepts them.
* **Build with Total only** declines them.

If it proposes no banners, click **Approve & build tables**.

The build then continues to Tables.


---

# 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://help.metaforms.ai/tabulations/reviewing-the-tab-spec-mapping.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.
