Sign Up
A reconsideration of value (ROV) happens when a borrower, loan officer, or reviewer challenges the conclusion in a valuation report — arguing the value is too low, the comparables were wrong, or relevant information was missed. Appraisals get most of the regulatory attention around ROVs, but evaluations are not exempt from the same scrutiny, and institutions should treat them with the same rigor.
The core risk in an ROV situation isn't that the original value was wrong — valuation is inherently an estimate, and reasonable professionals can differ. The real risk is not being able to show your work. If a preparer can't reproduce which comparables were considered, why others were excluded, and what data supported the final number, a challenge becomes very difficult to defend.
This is where the difference between a spreadsheet-based process and a structured software platform becomes concrete. A manual process typically preserves the final report but not the reasoning path that led to it — which comparables were pulled, how they were scored against each other, and what the preparer saw at the time. A platform that captures comparable data, scoring, and preparer decisions as part of the evaluation record gives you that reasoning path automatically.
A sound ROV process should include a documented path for the request to be submitted, an independent review by someone who wasn't involved in the original evaluation, and a written outcome — either an adjustment with supporting rationale, or a documented basis for standing by the original conclusion.
Institutions that treat every evaluation file as though it might eventually be challenged tend to have the strongest files overall, since the discipline required to survive an ROV request is the same discipline that produces defensible reports in the first place.
Sign Up
Sign Up for EvaliBLOG
Contact Us
Request a Demo
AI Use & Transparency