
Letter of explanation conditions look simple but cause endless resubmits. Here is how processors can request, review, and clear LOEs on the first pass.
Few loan conditions look easier on paper than a letter of explanation. The underwriter wants the borrower to explain something, the borrower writes a few sentences, and the condition clears. In practice, LOE conditions are one of the most common reasons files bounce back to processing. The letter is vague, unsigned, answers the wrong question, or raises a new issue the underwriter now has to chase.
This guide covers why letter of explanation conditions come up, what underwriters actually need to see, and a simple workflow processors can use to get LOEs right the first time.
A letter of explanation (LOE) is a short written statement from the borrower that explains something in the file the underwriter cannot verify from documents alone. It does not replace documentation. It gives context so the underwriter can decide whether the item affects the borrower's ability or willingness to repay, and whether more paperwork is needed.
LOE conditions can show up at initial underwriting, after a resubmission, or late in the file when updated documents reveal something new. That last case is the dangerous one, because it lands when the closing date is already close.
Most letter of explanation conditions fall into a handful of buckets:
Knowing the trigger matters, because each one needs a different kind of answer. A good processor can often predict LOE conditions before underwriting even issues them.
An LOE that clears on the first pass usually has the same traits:
Before you contact the borrower, read the underwriter's exact wording. Note every item, date, and amount it references. If the condition is unclear, ask the underwriter for clarity now rather than after the borrower has written something that misses the point.
Borrowers struggle with open-ended requests. Instead of "please send an LOE for your credit," give them the specific items and a simple structure: what happened, when, the amount if relevant, and whether it created any new debt. We cover this approach in more depth in our guide to writing loan condition requests borrowers complete the first time.
Ask for the backup at the same time as the letter. A large deposit LOE should arrive with the source document, like a transfer statement, gift letter, or bill of sale. Collecting both together prevents the most common LOE resubmit: "explanation received, please provide documentation."
Run a quick check before the letter goes to underwriting. Is every item addressed? Is it signed and dated by every required borrower? Do the details match the statements and credit report? Did the borrower mention anything new? Two minutes of review here can save a full underwriting turn.
When a file has several LOE items, treat each one as a separate condition with its own status. One letter covering four topics is fine to submit, but tracking it as a single line item hides which pieces are still missing. Splitting them out makes it obvious when three are done and one is stuck.
LOE conditions rarely take long to write. They cause delays because they cycle. A vague letter comes back with a follow-up condition. The follow-up asks for documentation. The documentation shows something new, which triggers another letter. Each loop can cost days, and late in the file it can push you toward a rate lock extension.
The fix is front-loading: anticipating likely LOEs at submission, requesting them with specific prompts, and reviewing them before they reach underwriting. Processors who do this consistently see fewer surprises between conditional approval and clear to close.
Conditionly is loan condition tracking software built for mortgage processors. Each letter of explanation can be tracked as its own condition, with a clear owner, status, and due date, so you can see at a glance which LOEs are requested, received, under review, or cleared. Loan officers get visibility without pinging you for updates, and nothing slips through when a file gets busy.
If LOE back-and-forth is slowing your pipeline, start a free trial of Conditionly and see every open condition in one place.