Season 1 curriculum
Paid trackGuideline Decoder12 min · Janice

Lesson 2 · Guideline decoder

Which Exceptions Are Real?

Show the difference between a request an AE can champion and a request that does not address the actual credit or eligibility risk.

Scenario

Three files have exception requests: one has compensating factors, one has a missing-document issue, and one asks the lender to ignore the actual risk.

Learner Outcome

The member can package an exception request with facts, mitigants, and a specific ask.

Skool summary

The lender-side view of exceptions: what gets championed, what dies quickly, and how to ask so your AE can actually help.

1

The exception test

A real exception request does three things: it identifies the exact rule or overlay, explains why the file is still a good risk, and offers compensating evidence. A weak request says the borrower is nice, the Realtor is upset, or the deadline is close.

2

Exception lanes

Classify the ask before sending it: eligibility exception, overlay exception, documentation exception, operational exception, credit-risk exception, or compliance/fair-lending hard stop. Some lanes can be packaged. Some are not 'ask harder' situations.

3

What Janice needs

Give the AE a clean package: guideline reference, borrower facts, risk factors, compensating factors, prior performance if relevant, document proof, and the exact decision needed. Do not make the AE reconstruct the file from a thread.

4

Champion script

Say: 'I am not asking you to ignore the issue. I am trying to classify it. Is this baseline ineligibility, investor overlay, channel policy, missing documentation, or a possible exception path? If it is exceptionable, here are the mitigants and the narrow decision I am asking for.'

Homework

  • Rewrite one exception request using the package template.
  • Add a fallback path so the request is not all-or-nothing.