Evaluation Summary: Overview – Alloy

❗️ PII data in an article is all fake for demonstration purposes

Evaluation summaries are comprehensive pages that present key information and data about an entity and its evaluation through a Workflow. A Journey Application can have multiple evaluation summaries that make up the entirety of the Journey Application, if the Journey had multiple Workflows.

Evaluation summaries can have information such as matched data sources, triggered rules (tags), fraud scores, decision reason codes, watchlists, credit reports, and other relevant metadata depending on which data services were configured in the Workflow.

This information is designed to help reviewers quickly understand the outcome and reasoning behind an evaluation, such as why an application was approved, denied, or sent for manual review.

Conditional Display of Evaluation Cards

Evaluation summaries dynamically display data cards based on the information returned during an evaluation. This logic helps reduce visual clutter and ensures reviewers focus on relevant results. Most data cards are shown only if data is returned that would populate that card, however there are select cards that will always be visible outlined below:

If no data is returned for a given card, the entire card is hidden, rather than displaying an empty or partially empty panel.
The following cards will always appear in an evaluation, even if no data is returned:
- Matched Data
- Tags
- Other Data (this card remains visible to allow configuration or data entry, even when empty)
The Watchlist and Credit data cards are vendor specific and will always be displayed if a Watchlist or Credit vendor module is included in the workflow, regardless of whether those modules return data.

This behavior ensures that evaluations only surface cards with meaningful results and the required context and configuration entry points remain available.

Evaluation Summaries

Evaluation summaries pages may contain the following data cards:

Matched Data
Tags
Diligence
Returned Reason Codes
Data Sources
Other Data
Credit
Watchlist

Matched Data

This table includes the data sources verifying each piece of the applicant’s information.

Matched data sources are in green and non-matched in gray (shown below). This section shows if a data source could match that element, such as address, to the entity.

Please note that whether a piece of data is matched may or may not be connected to the reason an evaluation was decisioned to Manual Review, Denied, or Approved. For that reasoning, see the next section, Tags.

Diligence

Fraud Scores are listed in the Diligence Section.

These scores reflect the thresholds where the data sources see risk, and not necessarily the rules in the Workflow. To see how the scores affect the outcome, refer to the workflow configuration.

Returned Reason Codes

The Returned Reason Codes table displays the reason codes returned whether or not they were used in decisioning.

Data Sources

The Data Sources table displays the data sources used to decision on the applicant.

A data source paired with a green circle and white checkmark indicates that the data source was executed.

A data source that did not execute is paired with a gray circle and white minus symbol.

In the event of a service failure, an icon will be paired with the data source. When this occurs, you can click on the data vendor and see if there were any errors returned. If the error is temporary, Alloy recommends that the evaluation is rerun.

Other Data

The Other Data section can be used to surface metadata fields contained in the raw response (JSON).

For instance, the Other Data section can be customized if your organization wants to see specific vendor attribute information.

To learn more on how to surface information in the Other Data section of the Evaluation Summary page, please check here.

Watchlist

The Watchlist data card appears whenever a Watchlist data vendor module is run in the workflow.

Credit

The Credit data card appears whenever a Credit-specific vendor module is run in the workflow.