An exception request asks an underwriter to approve a file outside standard policy — a ratio slightly over the cap, a credit score just under threshold, a document substituted for the usual one. Underwriters grant these regularly, but almost always on the strength of compensating factors that offset the specific policy gap, not because the broker asked nicely or the client's story was sympathetic.
A poorly structured request — one that restates the problem without offering a mitigant — usually gets declined even when a genuinely approvable version of the same file exists. Here's how to build the version that gets read seriously.
What compensating factors actually move an underwriter?
An exception request needs to pair the specific policy gap with a specific offsetting strength — not a general assurance that the borrower is reliable. The factors that consistently carry weight:
- →Lower loan-to-value than the program minimum requires, giving the lender more equity cushion against the risk being waived.
- →Verified liquid assets or net worth well beyond what the file otherwise suggests.
- →A documented, short-term reason for the gap — a one-time expense that inflated debt ratios temporarily, for example — rather than an ongoing pattern.
- →Strong payment history on file, especially on a similar-sized obligation, when the request concerns credit rather than ratios.
- →A clear, credible path back inside policy at renewal, for a shorter-term or B-lender exception.
A request built around one or two of these, specific and evidenced, is far more likely to succeed than a request built around several vague ones.
What typically gets an exception request declined?
The most common failure: restating the problem instead of solving it. “The client's ratio is a little high but they're a good client” gives an underwriter nothing concrete to approve against. “The ratio is 2 points over policy, offset by a 65% LTV and $40,000 in verified liquid reserves” gives them something they can actually put in an approval file.
Requests also fail when they're submitted without the supporting documentation already attached — asking an underwriter to grant an exception on the promise that evidence will follow is a much weaker position than presenting the evidence with the ask.
How should an exception request actually be formatted and submitted?
Keep it short, specific, and evidence-first — one paragraph stating the exception being requested, one paragraph on the compensating factor with the supporting number, and the document attached. Send it as its own clearly labeled item within the submission, or as a distinct follow-up on an existing file, rather than burying it inside general deal notes where it's easy to miss.
The Deal Notes Submission Cover Note Template covers the broader submission structure this exception request sits inside.
What does a working exception request actually look like?
Exception request template “Requesting an exception to [specific policy — e.g., maximum TDS of 44%] for [borrower name/file #]. Current TDS is calculated at [X%], [Y] points over policy. Compensating factor: [specific, evidenced factor — e.g., LTV of 65% vs. program maximum of 80%, and $[amount] in verified liquid reserves per attached statement]. Supporting documentation attached: [list]. Requesting approval to proceed on this basis.”
Adapt the bracketed fields to the specific policy gap and lender — a credit-score exception pairs differently than a ratio exception, and a B-lender underwriter weighs different compensating factors than an A-lender one, but the structure — name the gap, name the mitigant, attach the evidence — holds across lender tiers.
Where does fulfillment support fit into exception requests?
Building a strong exception request means having the compensating-factor documentation already organized before the request goes in — not scrambling for it after an underwriter asks. Treadstone's fulfillment associates build that evidence trail into the file from intake, and Treadstone's AI underwriting support flags where a file is close enough to policy that a well-built exception request is worth the ask.