Predicted risk bands
How customers are distributed across the fixed reference bands.
How to read these bands
These bands describe relative predicted risk. They are not action thresholds and do not change queue selection.
PORTFOLIO INSIGHTS
A clear view of predicted risk and review capacity for your customer portfolio.
Upload a prediction-time CSV, set your review capacity, and score the full portfolio.
AT A GLANCE
Summary of model estimates for the full uploaded portfolio.
How customers are distributed across the fixed reference bands.
These bands describe relative predicted risk. They are not action thresholds and do not change queue selection.
How the requested capacity translated into the queue.
Interpretation: Predicted probabilities summarize model estimates, not observed outcomes or expected losses. Portfolio patterns are descriptive and do not show that an intervention will change outcomes.
COHORT EXPLORATION
Filter scored customers and compare descriptive groups.
Every filter applies to the full scored portfolio. Counts below show the filtered denominator.
Fixed 10 percentage-point bins; shares use the filtered cohort.
Descriptive summaries for the filtered cohort.
| Group | Customers | Share | Mean risk | Selected |
|---|
For numeric fields, groups use quartile boundaries from the full portfolio.
Customers are ordered from highest to lowest predicted risk. The table shows a page at a time.
| Rank | Customer ID | Predicted risk | Risk band | Review status | Details |
|---|
Interpretation: Filtered groups describe this uploaded portfolio. They do not establish causes, treatment effects, or fairness conclusions. Encoded input values are shown as supplied; category codes are not given inferred labels.
CAPACITY DECISION
How your review capacity shaped the ranked customer list.
A consistent selection rule determines who enters the review list.
These totals explain why customers entered the review list or remained outside it.
| Queue outcome | Customers |
|---|
Unused capacity can occur when a full tied score group cannot fit. The queue never splits that group or exceeds its target.
Compare customer profiles under the current review capacity.
Summaries use the full uploaded portfolio, regardless of filters in Explore portfolio. Each measure shows the median, middle half of values, full range, and available and missing record counts.
Average bill and payment amounts are calculated per customer across the six supplied monthly fields. Small groups are shown with their exact count; individual records can have more influence in a small group. These descriptive differences do not show causes, outcomes, or intervention effects.
Customers are listed from highest to lowest predicted risk.
| Rank | Customer ID | Predicted risk | Selection reason | Details |
|---|
Interpretation: This view explains a model-ranked review policy under the requested capacity. It does not recommend an intervention or estimate the effect of reviewing a customer.
PORTFOLIO PATTERNS
What appears in this uploaded portfolio, alongside patterns the model used on validation data.
Summaries describe the uploaded rows. They do not represent future behavior or outcomes.
Share of customers in each input code, across the full portfolio.
Codes are shown as supplied. Their integer values are not relabeled as payment outcomes here.
Monthly distribution across all uploaded customers.
| Month | Median | Middle half | Range | Records |
|---|
Monthly distribution across all uploaded customers.
| Month | Median | Middle half | Range | Records |
|---|
Global permutation importance from the validation cohort.
Mean Average Precision decrease after shuffling each feature.
How to interpret: These validation results describe how the model performed when a feature was shuffled. They do not show that a feature causes default or explain an individual customer's score. Engineered features can share information with their source fields, so their importance values should not be added together.
Upload a customer file above to see the portfolio summary and review-capacity breakdown.