Not automatically. Full review is required only when the fact pattern or risk profile actually forces it.
A lot of condo files get routed into full review because no one has enough confidence to keep the simpler lane alive. That is not the same thing as proving the file really belongs in the heavier path.
See what usually forces full review.
Separate real full-review signals from default routing.
Know what to confirm before accepting the heavier lane.
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
A condo needs full review when the project facts, blocker disclosures, or documentation weakness make a simpler lane unavailable or not credible enough to trust.
That usually comes down to project status, occupancy and LTV fit, transient-use risk, litigation, delinquency, reserve weakness, safety issues, insurance quality, and whether the current questionnaire and financial support actually answer the right questions.
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.
Full-review signals
| If this is true | It usually means | Best next move |
|---|---|---|
| Project status is new, newly converted, or still unclear | The simpler lane weakens or disappears | Get status clarified in writing now |
| Litigation, delinquency, safety, or major reserve issues are present | Project-level risk increases | Surface the blocker before more work is done |
| Transient-use or hotel-like restrictions appear | Heavier scrutiny becomes more likely | Confirm the use restriction directly |
| Questionnaire, budget, or insurance support is weak | Confidence drops even if the file looked clean | Request stronger support before accepting the lane |
| Master-association complexity or lender overlay applies | The forcing factor may be structure or overlay | Ask what fact is actually forcing full review |
Core answer
Teams often use full review as a safety blanket when the file feels uncertain. That is understandable, but it is not the same as a real lane determination.
The better question is what fact is actually forcing the heavier path. If no one can name that fact, the file may be in full review because of uncertainty rather than because the condo truly requires it.
Core answer
Full review is usually forced by one of two things: real project-level risk or unresolved facts that make the cleaner lane too fragile to trust.
Core answer
Before you accept full review as final, make sure the lane-setting facts are actually confirmed and not just vague. That means naming the blocker, seeing the support, and deciding whether the issue is a true forcing fact or just missing clarity.
A file can still belong in full review after that exercise. The point is to know why, not to guess.
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.
Full-review example
A broker assumes a condo file needs full review because the project feels complicated and the lender intake team labels it that way.
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
Yes. A file can end up there because of uncertainty or weak support even when the real forcing fact has not been identified clearly.
They use it as a default when key lane-setting facts are still unresolved.
Yes. You still need the documents that prove why the lane is heavier and what the next request should be.
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.