Who to call when a file actually stalls.

A Business Development Manager represents the lender's relationship with the brokerage: positioning products, explaining policy and rate-sheet nuance, and providing pre-submission guidance on whether a story file is likely to fit. A BDM generally doesn't sit inside the adjudication queue and, in most cases, can't personally move a specific file through underwriting any faster once it's already submitted.

That doesn't make a BDM powerless once a file is submitted — a good one can flag urgency internally, ask an underwriter for a status update on the broker's behalf, or clarify why a condition was issued. What a BDM generally can't do is override an underwriter's independent judgment on a specific file, which is exactly why the two roles need to be approached differently depending on the problem.

A BDM is also usually the best source of context that never makes it onto a rate sheet: which underwriters on the team tend to be more comfortable with a particular file type, what's changed recently in how the lender is reading a certain scenario, or where the lender's appetite has quietly tightened or loosened since the last time a broker submitted a similar deal.

That informal knowledge compounds over a relationship built over multiple files rather than a single transaction, which is part of why brokerages that maintain steady, well-managed lender relationships tend to get faster, more useful answers than ones treating every lender interaction as a one-off.

Once a file is in adjudication and stuck — a specific condition unclear, a document that was submitted but not showing as received, or a decision overdue against the lender's stated turnaround — the underwriting desk itself, not the BDM, is usually the contact who can actually resolve it.

Some lenders route broker communication through a dedicated underwriting support line or processing desk rather than the underwriter directly, which is worth learning for each lender in advance — escalating correctly within a given lender's own structure is just as important as knowing whether to call the BDM or the underwriter in the first place.

A useful test before escalating: is this a problem the underwriter can actually resolve by hearing from the broker again, or is it simply a matter of the file being in a queue that needs to run its course? Escalating a file that's genuinely just waiting its turn rarely speeds anything up and can read as unnecessary pressure; escalating a file with a specific, resolvable blocker almost always gets a useful response.

Having the file's reference number, the date it was submitted, and the exact document or condition in question ready before making contact also speeds up the exchange considerably — the underwriter can act immediately instead of spending the first few minutes of the call just locating the file.

When brokers make reasonable requests, the answer should arrive promptly and match what the BDM said policy would allow — inconsistent exception handling between a BDM's pre-submission read and the underwriter's actual decision is where trust in a lender relationship erodes fastest. A broker who gets burned by that mismatch a few times starts routing volume elsewhere, which is exactly the outcome a strong BDM relationship is meant to prevent.

There's a real difference between a firm, specific follow-up — “this file has been in queue three days past the stated turnaround, can you confirm status” — and a vague or frequent one that reads as impatience rather than a legitimate concern. Lenders generally respond well to brokers who escalate selectively and specifically, and less well to brokers who chase every file the same way regardless of whether it's actually behind.

Keeping escalation proportional to the actual problem — genuinely overdue, a real document discrepancy, a time-sensitive closing — protects the broker's credibility for the file that truly needs it.

It also helps to give the contact being escalated to a clear, easy way to help: a specific question, a specific document reference, a specific date. An escalation that simply says “any update?” puts the burden on the lender contact to figure out what's actually being asked; a specific escalation gets a specific, faster answer.

Document the right contact per lender per scenario once, rather than re-deciding it under pressure every time a file stalls. That's a natural extension of a broader lender exception process — knowing who to sound out before formally requesting an exception saves a wasted submission.

A simple internal reference — lender name, BDM contact, underwriting desk contact, and preferred escalation channel — kept current and shared across the team saves exactly the kind of time that gets lost re-discovering the same information under pressure on a future file.

Reviewing and updating that reference periodically matters too — BDMs move roles, underwriting desks reorganize, and a contact list built once and never revisited tends to quietly go stale exactly when it's needed most, on the file that's actually stuck.

Treadstone's fulfillment associates maintain lender-by-lender escalation contacts as part of the pipeline management they run for brokerages, so a stalled file gets routed to the right person immediately instead of starting with a guess.