Using OGS: Screening Resolution & Client Selection
This guide is for KYC analysts and compliance reviewers who work with the OGS: Screening Resolution & Client Selection task — the two-stage task for ongoing screening.
Looking for configuration help? This guide covers the analyst workflow only. For Journey Builder setup and downstream ODS configuration, see Configuring OGS: Screening Resolution & Client Selection.
Working a downstream ODS task? If an OGS run has already been resolved and you have received an ODS task triggered by OGS, see Using ODS: Screening Resolution & Materiality instead.
What is the OGS task?
Ongoing Screening (OGS) periodically screens entities against watchlists on a scheduled basis — independently of onboarding or on-demand screening. When a batch run returns hits, the OGS: Screening Resolution & Client Selection task is created for the affected entity.
This task is distinct from the ODS task. Where ODS is triggered per client journey, OGS works at the entity level — a single hit list covers all providers and all clients that share that entity.
The task has two stages.
| Stage | Name | Purpose |
|---|---|---|
| Stage 1 | Screening Resolution | Determine whether each hit is real — at the entity level |
| Stage 2 | Client Selection | Determine which client relationships are affected and should receive a downstream ODS journey |
Separation of concerns: OGS resolves whether a hit is real at the entity level. A downstream ODS task then determines what that hit means for each affected client — including classification data, materiality assessment, and any escalation. These are intentionally separate stages carried out by (potentially) different analysts.
Stage 1 — Screening Resolution
In Stage 1 you review and resolve the hits returned by the OGS batch run. The hit list covers all providers that screened this entity and applies across all clients that share this entity.
At the top of the page, the screened entity's name, search criteria (nationality, date of birth, business and residential address), and aliases are shown in a collapsible panel for reference while working through hits.
What you see
The screening results show the hits returned for the entity across all OGS providers. The layout and interaction are similar to the match resolution experience in ODS — you can view hit details, review provider information, and record a decision for each hit.
Resolving hits
For each hit, open the resolution view and record your decision:
| Decision | When to use |
|---|---|
| Match | You are satisfied this hit relates to the screened entity |
| No Match | You are satisfied this hit does not relate to the screened entity |
| Unresolved | You cannot make a determination at this stage |
Select the reason that best supports your decision and, where required, add comments.
Hit decisions in Stage 1 are recorded at the entity level — they cover the entity across all client relationships. You are not yet making a judgement about which clients are affected; that happens in Stage 2.
Document upload
If your journey has been configured to require supporting documentation, you must upload a document for each resolved hit before you can save the decision. Select the Document Type from the dropdown and upload the file. Uploaded documents can be previewed from within the task.
Action Items panel
The Action Items panel tracks your progress through Stage 1:
- While unresolved hits remain: "Unresolved hits (N) Required"
- Once all hits have a decision: "All screening hits resolved Completed" (shown with a green tick)
An Impacted clients action item only appears in the panel when at least one hit is marked as Match. If no hits are marked as Match, the Impacted clients item is not shown.
Completing Stage 1
Once all hits have been resolved, Stage 1 is complete and Stage 2 becomes available.
Stage 2 — Client Selection
In Stage 2 you identify which client relationships associated with this entity should be notified of the confirmed hit and receive a downstream ODS journey.
Accessing Stage 2
Stage 2 is accessed via the Review button that appears in the Impacted clients action item in the Action Items panel — this item only appears when at least one hit is marked as Match.
The Impacted clients modal
Clicking Review opens the Impacted clients modal:
- Title: "Impacted clients"
- Subtitle: "Follow-up journeys defined through the launchpad task will be triggered for selected clients."
Each client is displayed as a row showing a relationship chain — entity tiles connected by dashed lines, each tile showing entity name, entity type, and relevant badges (e.g. PEP status, ownership percentage).
Selecting clients
All clients are pre-selected (checked) by default. You can uncheck clients that should not receive a downstream ODS journey.
When you uncheck a client, a mandatory "Reason for no follow-up" rich text field appears below that client's row. This reason is required before you can confirm.
The Confirm button triggers the launchpad task.
Think carefully before deselecting a client. If a client is not selected in Stage 2, no ODS task will be created for them from this OGS run. You must provide a reason for no follow-up for each deselected client before you can confirm. If you later determine a client should have been included, the downstream journey will need to be started manually.
Completing Stage 2
Once you have reviewed all clients and made your selections, complete Stage 2. The system automatically hands off to the launchpad.
What happens after Stage 2
After you complete Stage 2, a launchpad task automatically triggers an ODS: Screening Resolution & Materiality journey for each client you selected. No manual intervention is required.
The downstream ODS journey screens only the main entity and applicable related party.
The ODS tasks that are created work exactly like any other ODS task — the analyst follows the standard ODS workflow for match resolution, classification data, and materiality assessment. The one visual difference is that hits from the OGS batch run are highlighted in the ODS screening results table so the analyst can identify their origin.
The ODS analyst does not need to re-resolve the hits. The hit decisions from Stage 1 are available for reference. The ODS analyst's role is to determine what the confirmed hit means for their specific client: capturing classification data, assessing materiality, and completing any required escalation.
Audit
All match decisions, client selections, and document uploads made in the OGS task are captured in Audit.
Impacted Clients Updated: When client selections are confirmed in Stage 2, an "Impacted Clients Updated" row appears in the OGS audit panel. On expand, it lists each client with their Legal Entity ID, whether they were selected (Yes/No), and — for deselected clients — the Reason for no follow-up.
Document events: When documents are uploaded, removed, or updated, distinct labelled rows appear: Document Added, Document Removed, Document Status Updated, Document Archived, Document Unarchived. Each row is expandable with file name, document type, and status details.
Match decisions are also captured in the audit panel.
Permissions
The OGS task uses the standard screening permissions. No new permission types are introduced.
| Permission | What it allows |
|---|---|
| Screening Access | Read-only access to the OGS hit list and Stage 2 client list. You see the eye (view) icon only |
| Screening Edit | Edit access while the task is In Progress. Resolve hits, make client selections, upload documents |
| Read-only after completion | Once the task reaches Completed status, all users have read-only access regardless of their assigned permission |
Glossary
| Term | Definition |
|---|---|
| OGS | Ongoing Screening. A periodic workflow that screens entities against watchlists on a scheduled basis |
| ODS | On-Demand Screening. The downstream task type (ODS: Screening Resolution & Materiality) triggered per client relationship after OGS Stage 2 |
| Entity level | The OGS task resolves hits at the entity level — covering all clients that share the entity — rather than per client relationship |
| Stage 1 — Screening Resolution | The first stage of the OGS task, where the analyst resolves hits from the OGS batch run at entity level |
| Stage 2 — Client Selection | The second stage of the OGS task, where the analyst selects which client relationships should receive a downstream ODS journey |
| Launchpad | An automated task triggered after Stage 2 that starts ODS journeys for each selected client |
| OGS-triggered hit highlighting | Visual highlighting applied to OGS hits in the downstream ODS task so the ODS analyst can identify their origin |