Escalate when the file has reached a lender-level decision, not when the team is merely annoyed.
The right escalation happens early enough to prevent wasted work on a blocker that only the lender can really clear, especially when litigation, major repairs, special assessments, delinquency, reserve weakness, or severe path uncertainty are already in view.
Know which issues deserve early escalation.
Know what to send with the escalation.
Avoid spending days collecting around a lender-level problem.
Working on a live file right now?
This page gives general guidance. CondoScreener Pro helps with your specific file. Run the 60-second pre-screen to see the likely lane, what is still unresolved, and what to request first.
Who this is for
Who this is for
When this matters
Short answer
Escalate a condo file to the lender when the next question is fundamentally a lender decision about fundability, conditions, or path viability rather than a normal document-collection problem.
That usually means confirmed litigation, major repairs or safety issues, meaningful special assessment or reserve weakness, severe delinquency, transient-use complications, or a file that has stalled without a clear lender-side priority order.
What the paid Decision Record gives you
The free pre-screen gives the likely lane and a short explanation. The paid Decision Record organizes the file-specific next move: what is still missing, what is still unconfirmed, what to request first, what not to do yet, and what to do today.
Likely lane
Likely waiver-path candidate
Primary blocker
No decisive blocker reported from the submitted answers.
Still missing
Current HOA budget is not on hand.
Still unconfirmed
Project status is still unknown.
Request these first
Condo questionnaire / Form 1076-equivalent
What to do today
Save this result to the file.
File-ready value
Built for the moment when you need a conservative next move before you email the HOA, move the file deeper into lender review, or hand it off internally.
Escalate now or not yet
| Situation | Escalate now? | Why |
|---|---|---|
| Confirmed litigation, major repairs, or major safety issue | Yes | This is lender-level risk, not routine processing |
| Special assessment, severe reserve weakness, or material delinquency | Usually yes | You need to know whether the file is still workable |
| Path uncertainty that could kill the file | Often yes | The lender may need to weigh in before more work is done |
| Routine missing HOA docs with no bigger blocker visible | Not yet | Tighten the doc chase first |
| File aged 10 or more days with unclear priority order | Yes | Silence and drift are reasons to escalate the status directly |
Core answer
The test is simple: can the team solve the issue with normal document collection, or does it need a lender answer about whether the file can still move?
If the next move depends on lender judgment, the file has reached escalation territory.
Core answer
A good escalation is concise and decision-oriented. State the file facts, the specific blocker, what has already been confirmed, and the exact question you need answered.
That gets a better response than a vague note asking for any update.
Core answer
Escalating early can prevent days of document collection on a file that may not be fundable as currently structured.
Even when the lender says the file is still workable, you usually get a clearer condition list and a better request order than you had before.
What usually changes the answer
What people usually miss
Have this exact issue on your file?
This page explains the pattern. The pre-screen tells you the likely lane for your file today, and the Decision Record turns the answer into what to request first, what not to do yet, and what to do now.
Escalation example
A processor learns that the project has a major special assessment and weak reserves, but keeps collecting routine docs for another week before escalating.
What to request first
What not to do yet
Need the next move now?
Use the free pre-screen when you want the likely lane and a short explanation. Use the Decision Record when you need the request-first list, the limiting unknown, and the cleanest note you can save or forward.
Related pages
FAQ
The next question is about lender judgment on a serious blocker, not about routine document collection.
Escalate when it is slow and the reason is unclear or likely lender-level, not just because it has minor normal follow-up.
A concise file note with confirmed facts, the blocker, what has already been done, and the exact decision question.
Want the file-ready version of this guidance?
Run the 60-second pre-screen to see the likely lane, the blocker or limiting unknown, and what to request first. Use the sample Decision Record if you want to see the action-plan version before you buy.
Working on a live file?
Stop guessing the next move. See the likely lane, what is unresolved, and what to request first.