How to actually ask a lender for an exception — and get one.

When a file does not exactly fit within a lender's guidelines, it gets assessed to see if the risk is worth an exception to the guidelines — meaning a lender is weighing whether the deviation is minor and well-mitigated enough to justify approving outside standard policy. A file that's off on one dimension, with everything else strong, is a realistic exception candidate; a file that's off on several dimensions at once generally isn't.

It also matters how far outside policy the file sits. A ratio that's marginally over a threshold reads very differently to an underwriter than one that's well beyond it, even if both are technically “an exception.” The closer a file already is to standard policy, the more realistic the exception request.

Relationship history can also factor in, particularly at a lender the brokerage sends consistent, well-packaged volume to. That's not a guarantee of approval, but a lender is generally more willing to extend judgment to a broker whose past submissions have been accurate and well-documented than to one it doesn't know well.

That track record isn't built overnight, which is one more reason a wasted or overreaching exception request has a cost beyond the single file — it's spending down exactly the kind of accumulated trust that makes a legitimate future request more likely to succeed.

A brokerage that keeps a simple internal record of which exceptions were requested, at which lender, and what the outcome was, ends up with a genuinely useful reference for future files — both for gauging a specific lender's realistic appetite and for avoiding a repeat of a request that's already been tried and declined.

Exceptions often need further approval from the head office or command chain, which may require extra time for consideration — a front-line underwriter frequently can't grant one alone. That escalation is worth planning for in the closing timeline rather than discovering it after a client has been given a date.

This is also why an exception request usually shouldn't be submitted at the last possible moment before a closing deadline — the extra sign-off layer means an exception simply takes longer than a standard approval by design, and a broker who leaves no room for that reality risks putting a client's closing date at real risk.

Different lenders structure this sign-off chain differently — some have a formal exceptions committee that meets on a set schedule, others route an exception through a senior underwriter's individual discretion on a rolling basis. Knowing which model a given lender uses helps set a realistic expectation for how long the decision will actually take.

Generally yes — a quick conversation with the lender's BDM about whether a specific deviation is realistically exception-able saves a formal submission that was never going to be approved. See who to call when a file stalls for the broader escalation logic this fits into.

This conversation doesn't need to name the client or share full file details to be useful — a general, anonymized version of the scenario is often enough for an experienced BDM to give a realistic read on whether it's worth the formal request, which protects client confidentiality while still getting a useful answer before committing time to a full submission.

A BDM's pre-submission read isn't a guarantee — the actual underwriter or exceptions committee still makes the final call, and a favourable early signal can still result in a decline once the full file is reviewed. It's a feasibility check, not a pre-approval, and worth treating as exactly that when setting a client's expectations.

Specificity and restraint: naming the exact deviation, showing the concrete mitigant, and not stretching the request to cover more than the one thing that genuinely needs flexibility. A request that asks for a single, well-justified exception is far more likely to succeed than one that quietly bundles several unrelated deviations together.

It helps to write the request the way an underwriter would want to defend it internally — because that's effectively what's being asked of them. A senior underwriter or head-office reviewer signing off on an exception often has to justify that decision within their own organization, so a request that hands them a clear, well-supported rationale is doing part of their job for them.

Comparable precedent helps too, where it genuinely exists: if a similar exception has been approved before, for that lender or in the broader market, referencing that pattern briefly can reinforce that the request is reasonable rather than unprecedented — without overstating how directly comparable the two files actually are.

• →Asking for an exception without naming what specifically is being requested
• →Bundling multiple unrelated policy deviations into a single request
• →Skipping the BDM feasibility check and submitting formally on a long-shot file
• →Overselling the mitigants rather than presenting them plainly and letting the underwriter draw their own conclusion
• →Repeating a request that was already declined without adding new, material information

Treadstone's fulfillment associates build exception requests with the specific mitigating documentation a lender's sign-off chain actually needs, instead of a general appeal for flexibility.