Population Stability Index (PSI) & CSI Explained

Population Stability Index (PSI) and CSI: Monitoring Scorecard Stability

A credit scorecard is a snapshot. It captures how borrowers looked and behaved on the day it was built, while customers, products, policies and the economy keep moving. When the live population drifts far enough from the development sample, scores stop meaning what they used to. The population stability index (PSI) and the characteristic stability index (CSI) are the two standard checks for catching that drift early. This guide explains how both work, how to read them, and how to build them into routine scorecard monitoring.

Why scorecards drift

Drift rarely has a single cause. The most common sources are:

  • Acquisition changes: a new marketing channel, partner or product brings in different applicants.
  • Policy changes: a revised cut-off or eligibility rule changes who applies or who is approved.
  • Economic shifts: inflation, interest rates or unemployment change borrower behaviour and incomes.
  • Seasonality: festive or year-end periods can temporarily change the mix of applicants.
  • Data issues: a system change, new data source or coding error alters how a variable is captured.

Telling these apart is the real job of monitoring, and it starts with a measure that is easy to calculate.

What Is the Population Stability Index (PSI)?

The population stability index (PSI) is a statistic that measures how much a score or variable distribution has shifted between two samples, usually the model development population and a recent population. A higher PSI means a larger shift, which suggests the scorecard may now be scoring customers unlike those it was built on.

The PSI formula

Split the score range into bins, using bin edges fixed at development. For each bin, compare the share of the recent (actual) population with the share of the reference (expected) population, then sum across bins:

PSI = Σ (Actual% − Expected%) × ln(Actual% / Expected%)

Each bin’s term is never negative, because the difference and the logarithm always share the same sign. The total is zero when the two distributions match and grows as they diverge.

How to calculate PSI step by step

  1. Choose the reference (expected) population, usually the development sample.
  2. Define the score bins on that population, often 10 to 20 bands, and freeze the edges.
  3. Apply the same edges to the recent (actual) population and calculate each bin’s share as a proportion.
  4. For each bin, calculate (Actual − Expected) × ln(Actual / Expected).
  5. Add the bin terms to get the PSI, then compare it with your thresholds.

Worked example

Take a five-band score distribution. The expected column is the development sample; the actual column is last month’s applications. In the formula, use proportions (0.14, not 14), or the result is inflated 100-fold.

Score bandExpected %Actual %Actual − Expectedln(Actual / Expected)PSI term
Below 58010%14%0.040.33650.0135
580–61915%18%0.030.18230.0055
620–65925%26%0.010.03920.0004
660–69930%26%−0.04−0.14310.0057
700 and above20%16%−0.04−0.22310.0089
Total100%100%0.0340

 

The total PSI is about 0.034, which sits in the stable range. The population has shifted slightly towards riskier score bands, but not enough to act on by itself. Notice that the two lowest bands gain share while the top two lose it. A pattern like that is worth watching over several months, because a single stable reading can hide a slow trend.

Population Stability Index Interpretation Thresholds

Most lenders read PSI against three bands. These are industry rules of thumb, not statistical laws, so treat them as triggers for review rather than automatic verdicts.

PSI valueInterpretationTypical response
Below 0.10Stable: no significant shiftContinue routine monitoring
0.10 to 0.25Moderate shiftInvestigate drivers with CSI and monitor more closely
Above 0.25Significant shiftEscalate, review performance, consider recalibration or redevelopment

 

Your own PSI thresholds may differ. Bin count, sample size and portfolio type all affect the value, and many institutions set limits in their model risk policy.

What Is the Characteristic Stability Index (CSI)?

The characteristic stability index (CSI) applies the same logic to a single scorecard variable, such as age band, income band or months on book. It compares how that variable’s attributes are distributed today with the development sample.

PSI tells you the population has moved. CSI tells you which characteristics moved it. That is why the two are used together.

AspectPSICSI
What it measuresShift in the final score distributionShift in one characteristic’s distribution
LevelWhole scorecardIndividual variable
BinsScore bandsAttribute bins of each variable
Key questionHas the overall population changed?Which variable is driving the change?
Typical useHeadline early-warning alertDiagnosis and root-cause analysis
FormulaΣ (Actual% − Expected%) × ln(Actual% / Expected%)Same formula, applied per characteristic

 

A quick CSI example

Suppose applicants under 25 rise from 12% to 20% of the population, the 25 to 40 group moves from 48% to 46%, and the over-40 group falls from 40% to 34%. Applying the formula to each age band gives terms of about 0.041, 0.001 and 0.010, so the CSI for age is roughly 0.05. Almost all of it comes from the under-25 band, which points straight to the source of the shift.

One caution: some practitioners weight the CSI by the points assigned to each attribute, which expresses drift as an average change in score points. Pick one definition, document it, and apply it consistently.

Scorecard Implementation and Monitoring

PSI and CSI only protect you if they run on a schedule with clear rules. A practical set-up for scorecard monitoring:

  1. Fix the baseline. Choose the reference population, usually the development sample, and freeze the bin edges. Never re-bin on new data.
  2. Set the frequency. Monthly is common for high-volume retail portfolios; quarterly can suit smaller ones. Match it to volume and policy.
  3. Define thresholds. Write amber and red limits (for example 0.10 and 0.25) into your monitoring policy.
  4. Track PSI and CSI together. Calculate the score PSI first, then CSI for every scorecard variable, ranked by contribution to the shift.
  5. Build a dashboard. Show PSI over time with threshold lines, the top drifting characteristics, and bin-level distribution charts.
  6. Pair stability with performance. Track Gini or KS, bad rates by score band and calibration as outcomes mature. Stability alone does not prove accuracy.
  7. Act when drift appears. First rule out data or pipeline errors. Then check for business changes such as a new channel, policy or cut-off. Use CSI to find the drivers, review performance, and decide whether to monitor, recalibrate or redevelop. Record the decision and escalate under your governance process.

Where volumes allow, run the same reports by segment, such as product, channel or region. A stable overall PSI can hide a large shift inside one segment that is offset by another. Keep a short written log of each review, including the PSI values, the explanation for any amber or red reading, and the decision taken. This trail is what validators and auditors will ask to see.

Data drift versus concept drift

PSI and CSI detect data drift: the inputs or scores look different from before. They cannot detect concept drift, where the link between characteristics and default changes while the distributions stay the same. Model drift in practice is often a mix of both, which is why stability reports should always sit next to performance reports.

Common Mistakes in PSI/CSI Monitoring

  • Re-binning on new data. Bins must stay fixed at development edges, or the comparison is meaningless.
  • Reading PSI as performance. A stable PSI does not guarantee the score still rank-orders risk.
  • Applying thresholds mechanically. A 0.12 caused by a known campaign is different from a 0.12 with no explanation.
  • Using the wrong baseline. Comparing approved customers with all applicants, or mixing segments, creates false alarms.
  • Ignoring empty or tiny bins. A zero share makes the logarithm undefined. Merge sparse bins or apply a small floor value.

FAQs

What is a good PSI value?

A PSI below 0.10 is generally read as stable, 0.10 to 0.25 as a moderate shift worth investigating, and above 0.25 as a significant shift. These are widely used rules of thumb rather than statistical laws, so check your own institution’s model monitoring policy for the limits that apply to your portfolio.

What is the difference between PSI and CSI?

PSI measures how the overall score distribution has shifted, while CSI measures the shift in a single scorecard variable. PSI tells you that the population has changed; CSI helps you find which characteristics caused it. Analysts usually track PSI as the headline alert and use CSI for diagnosis.

How often should PSI be calculated for a scorecard?

Monthly is common for high-volume retail portfolios, and quarterly can be enough for smaller or slower-moving ones. The right frequency depends on application volume, how quickly the portfolio changes, and your model risk policy. Calculate it more often after policy changes, new acquisition channels or major economic shocks.

Can a scorecard have a low PSI and still perform poorly?

Yes. PSI only shows whether the population looks the same, not whether the score still ranks risk correctly. The relationship between characteristics and default can change even when distributions are stable. That is why PSI should be reviewed alongside Gini or KS, bad rates by score band and calibration checks.

Learn to Build Scorecards Hands-On

Understanding the difference between an application vs behavioural scorecard is the first step. Building one, from binning and WOE to validation and cut-off strategy, is where the skill really develops. If you want to learn this end to end, with real-world case studies and tools used in banks, explore our Credit Risk Scorecard course.

 

Explore Dexlab Analytics’ Credit Risk Modeling certification program to build PD, LGD, and EAD models from scratch, work through IFRS 9 ECL frameworks, and learn model validation techniques used by practicing risk teams.


.

 

November 11, 2026 3:27 pm Published by

, , , , , , , , , , , , , ,

Comments are closed here.

...

Call us to know more

×