Exports Guide

Exports let your team create downloadable XLSX workbooks from screening profiles and potential matches without changing any live screening records. Access: Requires the Admin role or above. In the sidebar, go to Screening > Export. Use this guide when you need to:

• export potential matches for analytics, calibration, or operational reporting
• export profiles for visibility, customer operations, or audit sampling
• include associated profiles for a potential-match export
• control whether PII columns are included in a workbook
• understand how exported match scores, scoring thresholds, and News geography settings affect the data you are analyzing
• review export history and download completed workbooks

​

How Exports Work

Every export follows the same high-level sequence:

1. define the primary scope with the screening query builder
2. review the live preview table
3. continue from the scope step to lock a durable snapshot
4. optionally add an associated profile export stage when the primary scope targets potential matches
5. add a clear export name and rationale
6. queue the export and download the workbook from Export history after it completes

​

Key Concepts

​

Scope And Snapshot Locking

The scope step shows a live preview so you can confirm the cohort before a workbook is queued. When you continue from the scope step, Minerva locks a durable preview snapshot. That snapshot matters because:

• the export worker uses the same selected rows you reviewed
• the workbook is generated from the locked export snapshot
• history and per-row job items refer back to the same stage definition
• associated profile stages derive from the locked match snapshot, not from a later live re-query

​

Export Stages

An export job can contain:

• a primary match export stage
• a primary profile export stage
• an optional associated profile export stage when the primary stage targets potential matches

Each stage has a single export_selection action. This is what makes exports different from Bulk Actions: the job records selected rows for workbook generation and does not call downstream profile or match mutation endpoints.

​

PII Controls

PII is controlled per export stage.

• If a match stage opts into PII, the match sheet can include fields such as name, gender, nationality, occupation, organization, dates, locations, and aliases.
• If a profile stage opts into PII, the profile sheet can include fields such as name, date of birth, contact details, address, nationality, occupation, and organization.
• If one stage on a sheet includes PII and another does not, the workbook keeps the sheet rectangular but leaves PII cells blank for stages that did not opt in.

Use the smallest PII scope that supports the purpose of the export.

​

Workbook Output

Completed export workbooks include:

• a Summary sheet with job, requester, stage, status, and count metadata
• one or more Matches sheets for exported potential matches
• one or more Profiles sheets for exported profiles
• per-row status, error, processed time, and deep links back into Minerva

For match exports, workbook columns can include identifiers, review status, entity type, source flags, sanctions/PEP/News source names, match score, PEP level, media URLs, client risk rating, score details, billable tag, timestamps, and the screening view URL. For profile exports, workbook columns can include identifiers, profile status, monitoring state, archive state, profile type, flags, assignee, allowlist window, last screened time, timestamps, and the profile view URL.

​

Example Use Cases

​

1. Potential Match Export For Analytics

Use this pattern when you need to analyze unresolved potential matches across feeds, sources, review queues, or score bands. This example shows:

• a potential-match export scoped to unresolved Sanctions, PEP, and News hits
• a created-at window for a recent operational period
• the live preview table analysts use before locking the snapshot
• PII left off for an analytics-oriented workbook

Common analytics questions include:

• Which feeds are creating the most unresolved volume?
• Which sources are producing high-confidence versus borderline matches?
• Which profile cohorts need more review capacity?
• How did a scoring or source configuration change affect incoming volume?

​

2. Associated Profile Export For Visibility

Use this pattern when match-level analytics need profile-level context. When the primary scope targets potential matches, Minerva can add an associated profile stage. The associated stage exports the unique profiles referenced by the locked match snapshot, and you can apply an additional profile query before queueing. This example shows:

• a locked potential-match snapshot
• an associated profile stage turned on
• an additional profile query for active monitored profiles
• a profile preview table before workbook submission
• PII left off for the associated profile stage

Use this for visibility workflows such as reconciling match volume to active customer profiles, reviewing monitored profile exposure, or preparing workload summaries without changing any records.

​

3. Profile Export For Audit Sampling

Use this pattern when you need a profile workbook for audit, quality assurance, or internal control evidence. This example shows:

• a profile-scoped export for accepted monitored active profiles
• a review step with a specific export name and rationale
• PII included for the primary profile export stage
• snapshot counts and a human-readable scope summary before queueing

Use a precise rationale. It appears in export history and helps future reviewers understand why the workbook was created.

​

Export History And Workbooks

Export history shows queued, processing, completed, partial, and failed export jobs. The history table supports sorting, requester search, status filtering, and workbook availability filtering. Open an export to review:

• job status and identifiers
• selected, processed, succeeded, failed, and skipped counts
• each stage and its progress
• exported row snapshots for each stage
• workbook availability and download action

​

Understanding Scores In Exports

Minerva match scores are normalized from 0.00 to 1.00.

• 1.00 means the compared evidence is effectively exact.
• Values closer to 1.00 are stronger matches.
• Values closer to 0.00 are weaker matches.
• In the app preview table, scores are displayed as percentages for readability.

When available, export workbooks can also include score details such as field-level criteria match evidence. These labels should be read as: The overall match score is not a simple average of the visible labels. The screening engine weighs available evidence such as name, aliases, date of birth, location, identifiers, source data, and feed-specific signals.

​

Pre-Resolution vs Post-Resolution Thresholds

Exports show the records that passed the current screening and configuration logic. They do not change score thresholds themselves, but they are useful for calibrating those thresholds. Pre-resolution thresholds decide whether raw source candidates are strong enough to enter entity resolution. Minerva has feed-specific pre-resolution thresholds for Sanctions, PEP, and News. Post-resolution thresholds decide whether a resolved candidate remains in the final returned result set after entity resolution clusters related records. How to tune with exports:

1. Export a stable cohort before changing configuration.
2. Group by feed, source, review status, and score band.
3. Raise a feed-specific pre-resolution threshold when weak raw candidates from that feed are creating avoidable volume.
4. Lower a feed-specific pre-resolution threshold when plausible raw source records appear to be missing before entity resolution can evaluate them.
5. Raise the post-resolution threshold when resolved matches are still too broad after clustering.
6. Lower the post-resolution threshold when entity resolution is grouping relevant evidence but the final visible set is too narrow.
7. Re-export the same cohort after the change and compare volume, score distribution, and analyst review outcomes.

​

News Geography Bias And Export Analysis

The News data filter controls geography bias before news articles reach the Minerva engine. It changes the article pool returned by the News source; the downstream model can only score articles that were retrieved. Use exports to inspect the impact of News geography bias by comparing:

• total News match volume before and after a setting change
• News source names and media URLs for the same profile cohort
• match score distribution for News hits
• how often News-only matches appear without corroborating Sanctions or PEP evidence
• analyst outcomes for common-name subjects versus subjects with strong location evidence

​

Best Practices

• Start with a narrow query that captures the intended cohort.
• Use created-at or last-screened windows for repeatable analytics.
• Choose PII only when the workbook purpose requires it.
• Add associated profiles when match analysis needs profile context.
• Use clear export names and rationales so history remains audit-ready.
• Compare exports before and after score-threshold or News geography changes.
• Download completed workbooks from Export history rather than refreshing the create flow.

​

Related Guides

• Screening Guide
• Match Scoring Guide
• Bulk Actions Guide
• Alert Suppression Guide