Articles

How do you recalibrate a PD model to a new default rate?

One number added to the intercept repairs the level. Solving it from the averages misses, and solving it from the change in bad rates double counts.

To recalibrate a logistic PD model to a new default rate, add one constant to every applicant's log-odds of default and solve for the constant that makes the average predicted PD equal the observed rate. On 2,400 SME applications where the card predicts 7.90 per cent and 12.625 per cent defaulted, the solve gives a shift of 0.5623 in log-odds, or 16.22 scorecard points. Computing it from the averages gives 0.5214 and falls short; computing it from the change in cohort bad rates gives 0.7622 and overshoots.

Worked in full in Machine Learning for Finance by Julian R. Sterling, with every figure reproduced in a free workbook.See the book on Amazon →

The assumptions

The model is the SME scorecard of Machine Learning for Finance, scaled at 20 points to double the odds, a factor of 28.8539. It was developed on 2015 to 2019, where 6.32 per cent of loans went bad. The out-of-time cohort, 2020 to 2021, holds 2,400 applications and 303 bads: 12.625 per cent. Poured into the ten score bands fixed on the development sample, the card says this:

Out of time, ten fixed development bands, worst band first
BandApplicationsBadsObservedPredictedGap, pts
135511331.83%22.22%9.61
23155116.19%10.90%5.29
33084213.64%7.82%5.82
42853311.58%5.96%5.62
5246187.32%4.77%2.55
6203157.39%3.87%3.52
7219135.94%3.11%2.83
8179105.59%2.47%3.12
916274.32%1.86%2.46
1012810.78%1.20%−0.42
All2,40030312.625%7.90%4.72

The ranking survived: bad rates still fall almost band by band. The level did not. The card expects 189.6 bads and 303 arrived. That is the case for recalibration rather than rebuilding.

Step 1: why a shift in log-odds

A logistic model predicts log-odds of default as an intercept plus weighted characteristics. Adding a constant s to the intercept moves every applicant's log-odds by s, multiplies every applicant's odds of default by es, and moves every score by s × factor points. The order of applicants does not change, so Gini, KS and the area under the curve are untouched. Only the level moves, which is exactly what is wrong.

Scaling the PDs instead, by the ratio 12.625 / 7.90 = 1.598, is tempting and wrong: it is linear in probability, breaks above 100 per cent for any PD over 62.6 per cent, and over-corrects the riskiest band.

Step 2: solve the shift by Newton's method

The condition is that the average of the shifted PDs equals the target. It has no closed form, because the average of logistic curves is not a logistic curve, but Newton's method converges in three or four steps. Each step adds the remaining gap divided by the average of p(1 − p), which is the slope of the mean PD with respect to the shift.

Find s such that Σ nb × 1 / (1 + e−(logit(pb) + s)) / N = 12.625%

Newton step: sk+1 = sk + (target − mean PD(sk)) / mean[p(1 − p)]

Excel, band PDs in C, counts in B, shift in F1: =SUMPRODUCT(B2:B11,1/(1+EXP(-(LN(C2:C11/(1-C2:C11))+F1))))/SUM(B2:B11), then Goal Seek F1 to 0.12625

Newton's method on the ten bands
StepShiftMean PDSlope
00.00007.90%0.0684
10.690513.97%0.1091
20.567112.67%0.1011
30.562312.625%0.1008

The shift is 0.5623 in log-odds. It multiplies every applicant's odds of default by 1.7546 and is worth 0.5623 × 28.8539 = 16.22 points. The banded solve treats every applicant in a band as having the band's average PD. Solved on all 2,400 individual scores, the same method gives 0.573620, or 16.55 points; the difference is the averaging, not the method.

What it repairs, and what it does not

Gap between observed and predicted, before and after the shift, percentage points
BandObservedPredicted afterGap beforeGap after
131.83%33.39%9.61−1.56
216.19%17.67%5.29−1.48
313.64%12.95%5.820.69
411.58%10.01%5.621.57
57.32%8.08%2.55−0.76
67.39%6.59%3.520.80
75.94%5.33%2.830.60
85.59%4.25%3.121.33
94.32%3.21%2.461.11
100.78%2.08%−0.42−1.30

The largest under-prediction falls from 9.61 points to 1.57. Six bands are still under-predicted, the two worst bands are now slightly over-predicted, and the best band's over-prediction widens. One parameter fixes the average; it cannot fix the shape. If the shape matters for pricing or provisioning, a two-parameter fix (intercept and slope on the score) is the next step.

What if the target rate is different?

Shift needed for other target default rates, from a mean predicted PD of 7.90%
TargetNewton shiftPointsShift from averagesMean PD it reaches
8.00%0.01440.420.01367.99%
10.00%0.27707.990.25879.85%
12.625%0.562316.220.521412.22%
15.00%0.782422.570.721314.31%

The shortcut, logit(12.625%) − logit(7.90%) = −1.9345 + 2.4559 = 0.5214, falls short at every target in the table, and by more the further the target moves. Here it leaves 9.8 bads unexplained.

The common mistake

The more damaging error is computing the shift from the two cohorts' observed bad rates: odds of 0.1445 out of time against 0.0674 in development, a ratio of 2.1430 and a shift of 0.7622. That double counts. The out-of-time population already scores lower, which is why the card predicts 7.90 per cent rather than the development 6.32; part of the rise is already in the scores. Applied anyway, the 0.7622 shift predicts 14.77 per cent, 51.5 more bads than arrived, and moves the scale by 21.99 points instead of 16.22. Always solve against the mean predicted PD of the population you are calibrating, never against the old sample's bad rate.

The shift has a policy consequence. An applicant at the old cut-off of 550 had a predicted PD of 10.16 per cent; after recalibration the same score means 16.56 per cent. To keep the same risk appetite the cut-off has to read 566.22. What leaving it alone cost is worked in what an unchanged score cut-off costs.

Takeaway

The solve on all 2,400 individual scores, with each Newton step a live formula, is in the free workbook for this case.

Questions readers ask

Why not just multiply every PD by the ratio of observed to predicted?

Because probabilities cannot be scaled linearly without breaking at the top. Here the ratio is 1.598, and a band predicted at 22.22 per cent would go to 35.5, while a PD of 70 per cent would exceed 100. A shift in log-odds keeps every PD between 0 and 1 and preserves the ranking exactly: the Gini and KS of the card do not move.

Does recalibration change the Gini or AUC of a scorecard?

No. Adding the same constant to every log-odds moves every score by the same number of points, here 16.22, so the order of applicants is unchanged and every ranking measure is identical. Recalibration fixes level, not discrimination. If the ranking has also decayed, the model needs re-estimating, not a shift.

How many points does an intercept shift move a scorecard cut-off?

Multiply the shift by the factor, PDO divided by ln 2. At 20 points to double the odds the factor is 28.8539, so a shift of 0.5623 in log-odds is 16.22 points. A cut-off of 550 would have to read 566.22 to keep the same predicted PD; on the full 2,400 individual scores the exact shift is 0.573620, or 16.55 points.

Read the whole case

This article is one calculation from Machine Learning for Finance. The book takes the same case from first principles to the decision, chapter by chapter, and every figure it prints is a live formula in the free companion workbooks.

Get the book on Amazon →Free companion files

Also on Amazon UK · Amazon Germany · Amazon France · Amazon Canada

Also on this site

Reading guide: corporate finance, valuation and markets → · All 681 articles →

If this book helped, or didn’t, a few lines on Amazon are worth more than they look: they are what the next reader goes on. Write a review. The workbook stays free either way.