Starting point
- Portfolio or sub-portfolio list with stable identifiers.
- Prior internal value or BPO that acts as the comparison point.
Exception logic
- High spread: consensus range is too wide to rely on without manual review.
- Divergence: AVMLens consensus differs materially from the current internal mark.
- New risk: flood, environmental, or infrastructure factors create a pricing narrative the prior file did not capture.
Result
- The analyst receives a smaller, higher-signal exception queue instead of reopening every property.
- Each flagged property carries a concrete reason, not just a red status indicator.
- Teams can document why a property was escalated or left alone.
Why teams care
- Less wasted review time: analysts focus on outliers and drift, not stable rows.
- Better audit trail: the reason for escalation is tied to actual evidence fields.
- Cleaner handoff: export-ready results flow into existing servicing or risk workflows.