Beyond the Beaten Path

The Client

Our applicant, whom we will call Daniel, is a 41-year-old employed professional with a stable job of six years and a healthy deposit saved from bonuses. On paper he is exactly the kind of borrower a lender should want.

He approached a High Street provider directly, confident that his salary and deposit would carry the day. The application was declined within minutes, with no explanation beyond a reference to their lending criteria.

The Complication

Several years earlier, Daniel had a default registered against a mobile phone account. The amount was modest, a little over £600, and it arose when he moved house and the final bill was sent to his old address.

He never saw it. By the time it caught up with him it had already been registered. He paid it in full the moment he understood what had happened, so the default was marked as satisfied, and that was more than four years ago.

To a human being, the picture is obvious. A responsible person, a trivial sum, a genuine administrative mix-up, settled promptly, and a clean file ever since. To a High Street scorecard, none of that nuance exists.

The system saw the word default, applied a rule, and produced a fail. It did not ask how big, how old, whether it was satisfied, or why it happened.

How We Assessed the Options

The first thing to explain to Daniel was the difference between a credit score and a credit search.

The High Street relies heavily on an internal scorecard, a numerical model that turns a file into a single accept-or-decline verdict. A default, even a small satisfied one, can drag that score below the threshold on its own. It is not that Daniel was judged to be a poor risk in any considered sense; he simply failed an automated gate before any person looked at the case.

Getting a mortgage with adverse credit often means broadening your lender search radius. Away from the High Street sits a different kind of lender, one that uses manual underwriting.

Here a real (human) underwriter reads the file, sees the size of the default, notes that it is satisfied, checks how long ago it was, and reads the explanation of what caused it.

The same facts that the scorecard treated as a red flag become, in that context, a well-evidenced one-off with a clear and innocent cause.

The key variables an underwriter actually weighs are worth setting out plainly, because they are exactly the details a scorecard ignores:

• The size of the default. A £600 satisfied item is treated very differently from a £6,000 one.
• How long ago it was registered. An entry from over four years ago carries far less weight than a recent one, and it will drop off the file entirely at six years.
• Whether it is satisfied. A settled default shows the borrower put the matter right, which reads very differently from one still outstanding.
• The reason behind it. A genuine administrative error, evidenced and explained, is not the same as a pattern of missed commitments.

Identifying the Right Route

Our role at Drake is to identify the right home for a case like Daniel’s rather than to keep firing applications at the High Street and watch them bounce.

Repeated declines are not harmless; each one leaves a ‘hard search’ on the credit file and can make the next lender more cautious still.

By understanding at the outset that this was a scorecard problem and not an affordability problem, we could point the case straight at a lender whose underwriting was built to consider exactly these circumstances.

We helped Daniel prepare a short written explanation of the default, gathered the evidence showing it was satisfied, and set out his clean conduct in the years since.

Presented properly to a manual-underwriting lender, the case looked entirely different from the bare data the scorecard had rejected.