> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reviewing Match results

> Review, approve, and reject Match groups after a run — For Review, Reviewed, Unmatched, pairs, and search.

## Overview

After a Match project run completes, potential matches must be reviewed so stewards can confirm which records belong together, reject incorrect clusters, and prepare golden records for write-back.

This process applies to party data (for example customers or contacts) and to operational data (for example materials or accounts), depending on the table configured on the project.

***

## Match review page

You can see review status across projects on **Match → Review**.

The page title is **Match review**. Each card displays:

| Element | Description |
| - | - |
| **Name** | Project name (opens the project overview) |
| **Table** | Source table (and scoring mode when set) |
| **Status** | Latest run status |
| **Review status** | Counts for **for review** versus **reviewed**, with a ring chart |
| **Match review** | Opens the latest run’s results hub |
| **Overview** | Opens the project page |
| **Run delta** | Starts a delta run when a prior run exists |
| **First full run** | Shown when the project has no runs yet |

Use the search field to filter cards by project name or table.

<Note>
  Only projects with at least one run show review status details. Projects with no runs show **First full run** instead.
</Note>

***

## Run results hub

Each run has a results hub. Open it from:

* **Match → Review** → **Match review** on a project card
* **Match → Projects** → **Run** / **Delta**, or **Full run** / **Run delta** on the project page
* A run row under the project’s **Runs** section

The hub navigation (exact labels):

| Tab | Purpose |
| - | - |
| **Results** | Hub summary (counts and shortcuts) |
| **For Review** | Groups awaiting steward decision |
| **Reviewed** | Groups no longer pending |
| **Unmatched** | Records that did not enter a multi-member group |
| **Pairs** | Pair-level score comparisons |
| **Duplicates** | All groups for the run |
| **Uniques** | Unique / singleton-oriented results |
| **Clusters** | Large clusters that may need careful review |
| **Search** | Search across the run |

Hub actions:

| Action | Purpose |
| - | - |
| **Write back approved** | Upsert approved goldens (see [write-back](/match/write-back)) |
| **Match review** | Jump to **For Review** |
| Overflow | **Export groups CSV**, **Export goldens CSV**, **Execution history** |

On the **Results** hub, summary cards include **For review**, **Reviewed**, **Unmatched**, and **All groups** (opens **Duplicates**).

***

## Group records

A **group** is a set of potential matching records from the run.

Common information shown for groups includes block key, member count, score, and status (`pending`, `approved`, `rejected`, `merged`).

### Reviewing a group

1. Open **For Review** from the run hub.
2. Select a group to open its detail page.
3. Compare **members** side by side (field values and scores).
4. Take steward actions as needed.
5. Click **Approve group** when the cluster is a true match, or **Reject** when it is not.
6. Use **Skip** (when available) to move to the next pending group without deciding yet.

### Actions on members and goldens

Depending on group state, the group detail panel may offer:

| Action | Effect |
| - | - |
| **Approve group** | Marks the group approved and can advance to the next pending group |
| **Reject** | Marks the group rejected |
| **Unmatch** | Removes a member from the group as a potential match |
| **Set as master** | Designates which member is treated as master in the UI |
| **Edit golden** / **Save golden** | Adjust golden field values after approval |
| **Regenerate golden** | Rebuild golden values from survivorship rules |

<Note>
  Exact availability of master, unmatch, edit-golden, and regenerate actions depends on group status. Use the actions shown on the group detail page for your run.
</Note>

***

## Pair results

The **Pairs** tab shows side-by-side comparisons with overall and per-field scores. Use pairs when you need to understand why two records scored as they did, including overlap-style projects when an overlap table is configured.

***

## Unmatched records

The **Unmatched** tab lists records that did not join a multi-member group. Review them when you expect matches that blocking may have missed—then adjust blocking on the [project](/match/projects) and run again.

***

## Searching records

Use the run **Search** tab to find records across the run’s result set and navigate to the relevant group detail.

***

## Related articles

* [Match overview](/match/overview)
* [Match projects](/match/projects)
* [Match advanced settings](/match/advanced-settings)
* [Golden records and write-back](/match/write-back)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.