Skip to main content

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: Use the search field to filter cards by project name or table.
Only projects with at least one run show review status details. Projects with no runs show First full run instead.

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): Hub actions: 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:
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.

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 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.
Last modified on October 10, 2026