Why did this file suddenly get pushed into full review?
Usually because a blocker fact was discovered or clarified. Common reasons: project status turned out to be "newly converted" not "established," litigation or delinquency surfaced, occupancy type wasn't what was initially stated, or key documentation gaps became apparent during initial review. The file probably always belonged in full review — the discovery just happened mid-process instead of at intake.
Why it's not always simple
Files don't always have all their facts confirmed at intake. A project that looked straightforward at day 1 often reveals complications by day 10 when deeper due diligence happens. The question isn't usually "how did we get in wrong," but "why didn't we discover this earlier."
The bigger issue: the file didn't "suddenly" become a full-review candidate — it probably always was. The review path didn't change, the understanding of the file did.
What people usually miss
People often feel surprised when a file moves to full review mid-process, as if something went wrong. What usually gets missed:
- The blocker that triggered full review was probably discoverable at intake if asked systematically
- Files don't change lanes — the determination of lane just gets clarified
- The "sudden" push to full review is a sign that intake questions weren't thorough enough
- Asking about blockers systematically upfront prevents surprises later
- Full review isn't a punishment; it's the correct path if blockers exist
- The delay comes from the discovery, not from the path change
The real problem: incomplete intake questioning leads to mid-process discoveries that should have been known upfront.
Example
A processor starts a file with preliminary assessment that it qualifies for limited review. Everything seems straightforward through day 8. But when the HOA questionnaire is reviewed, it reveals active litigation and a 22% delinquency rate. Suddenly the file is in full review. The processor feels like something went wrong, but actually, the litigation and delinquency were always there — they just weren't discovered until the questionnaire was reviewed. If project blockers had been systematically confirmed at intake (via a phone call asking specifically about litigation and delinquency), the file would have been in full review from the start, and the two-week discovery delay wouldn't have happened.
If this is a real file
If a file gets moved to full review mid-process, don't be frustrated — focus on getting the information needed for full review. The file is now on the correct path based on the actual facts.
If you want to understand what the actual blocking factor is for your file and make sure you've uncovered all relevant facts, you can run a 60-second pre-screen.