Assign, Manage, and Work on Stewardship Tasks

The Stewardship task queue displays data stewardship tasks — assigned to a data steward, or unassigned — across Person, Provider, and Organization entities. You can assign tasks to a data steward individually or in bulk.

Access and assign tasks

To view the task queue, open Launchpad and select Stewardship. The queue lists tasks in a table with columns including Status, Category, Match score, Source, NativeID, Created date, Assignee group, Assignee, Resolution, and Identity name. By default, tasks are sorted by created date with the most recent shown first, 20 per page. You can filter the queue by entity type, domain, and other criteria, and your filters and sort order persist as you page through results.

Assign individual tasks

1. On the task queue, select a task.

2. From the Assign selected menu, select the data steward.

Assign tasks in bulk

1. On the task queue, click Bulk assignment.

2. Choose the tasks to assign, either by selecting them directly or by saved filter or custom filter.

3. Select the responsible data stewards and set the assignment parameters. When you select multiple data stewards, tasks are assigned one at a time to each selected steward until none remain.

4. Click Save.

Data stewardship task types

The task queue includes tasks from the categories below. These categories work the same way across Person, Provider, and Organization entities, with one exception: Applied Overlay and Rejected Overlay tasks are currently supported for the Person entity only.

Potential Match – Cross Source

• Description — Two identities were compared with a resulting similarity score above the Manual Review threshold but below the Automatic Match threshold.

• Record source — The two identities' records came from different sources.

• Result — Verato does not automatically link the identities under a single LinkID, but flags them as a close potential match. A data steward can review the identities to assess whether they represent the same person.

Potential Match – Same Source

• Description — Two identities were compared with a resulting similarity score above the Manual Review threshold but below the Automatic Match threshold.

• Record source — The records came from the same source.

• Result — Verato does not automatically link the identities under a single LinkID, but flags them as a close potential match. A task in this category may include records from several sources, but it always includes at least two distinct identities (each with its own LinkID) that have records from the same source.

Match – Same Source

• Description — Two identities were compared with a resulting similarity score at or above the Automatic Match threshold.

• Record source — The records came from the same source.

• Result — Verato automatically links the two identities under a single LinkID. Because this involves duplication within a single source, a data steward should be aware of the outcome and determine whether any action is needed in the originating source system.

Prevented Match – Same Source

• Description — Two identities were compared with a resulting similarity score at or above the Automatic Match threshold.

• Record source — The records came from the same source, but the entity is configured to prevent automatic matches within records from the same source — either for all sources or for specific sources.

• Result — Verato prevents the automatic link. As with Match – Same Source, a data steward should be aware of the outcome and determine whether any action is needed in the originating source system.

Applied Overlay (Person entity only)

• Description — Created when a postIdentity update to a Person entity's Source and NativeID combination triggers overlay detection — a substantial change in demographic values on an existing record, such as when one person's information is submitted under a Source and NativeID that already holds a different person's data — and the overlay detection action configured for that trigger is set to Task.

• Result — The update is allowed to proceed: the new demographic values are stored, and a task is created so a data steward can review the change and confirm whether it was legitimate or needs to be corrected.

Rejected Overlay (Person entity only)

• Description — Created when a postIdentity update to a Person entity triggers overlay detection and the overlay detection action configured for that trigger is set to Reject with Task.

• Result — The update is rejected: the new demographic values are not stored. A task is created so a data steward can review the rejected update and decide whether it should be applied after all.

Automatic task cleanup

Updates, deletions, linking or unlinking, and merging or unmerging actions can change the grouping of records in a task in a way that makes the task unnecessary. Verato regularly reviews and closes outdated tasks, reducing the number of tasks a data steward needs to review.

A task is eligible for automatic cleanup under the following conditions:

• Potential Match – Cross Source, Potential Match – Same Source, and Prevented Match – Same Source — The task isn't in progress and isn't currently assigned to a data steward, and the task has only one LinkID.

• Match – Same Source — The task isn't in progress and isn't currently assigned to a data steward, and the task has a single record (Source and NativeID) that shares the same source as the trigger record.

• Applied Overlay and Rejected Overlay (Person entity only) — The task isn't in progress and isn't currently assigned to a data steward, and the record that triggered the overlay was deleted or merged.

Configure data stewardship parameters

Task creation, the Manual Review threshold, and the Automatic Match threshold are configurable per entity. Not all task categories are created by default:

• Potential Match categories are created by default.

• Match – Same Source and Prevented Match – Same Source are not created by default.

• Applied Overlay and Rejected Overlay (Person entity only) are not created by default — enabling them requires setting the corresponding overlay detection action (Task or Reject with Task) for the Person entity.