Reconsideration of Value: Building an ROV Process That Stands Up

For most of the industry's history, a borrower who believed an appraisal missed the mark had no formal path — maybe the loan officer forwarded a few sales to the appraiser, maybe not. That era is over. Since late 2024, a borrower-initiated reconsideration of value has been a defined process with required disclosures, expected turn times, and a paper trail — and lending operations are discovering that "we handle ROVs when they come up" no longer survives contact with an exam.

The good news: a defensible ROV process is not complicated. It just has to actually exist, in writing, and produce records.

What is a reconsideration of value?

A reconsideration of value (ROV) is a formal request to the appraiser to re-examine the value conclusion based on specific information — typically overlooked comparable sales, factual errors in the report, or evidence of prohibited bias. Under the aligned policies Fannie Mae, Freddie Mac, and HUD published in 2024 (Fannie Mae's ROV initiative page collects the requirements), lenders must give borrowers a disclosed, standardized path to request one: the borrower is informed of the process at application and again when the appraisal is delivered, gets one borrower-initiated ROV per appraisal, and the request goes to the appraiser with a documented outcome. The GSE requirements apply to loans with application dates on or after October 31, 2024; the banking agencies' 2024 interagency guidance sets parallel expectations for institutions generally.

Two years in, examiners aren't asking whether you have a policy. They're asking to see it work.

The anatomy of a defensible ROV workflow

Strip away the compliance language and a workflow that stands up has five parts. Disclosure at the two required moments — application and appraisal delivery — using language a borrower can actually act on. A structured intake that captures what the borrower is contesting and caps submitted comparables at a manageable number, so the appraiser receives a reviewable request rather than a grievance. A routing rule that gets the request to the appraiser (never to someone who'll pressure the appraiser — appraisal independence applies with full force inside an ROV). A response standard — the appraiser addresses each item and either revises the report or explains why not, within the turn time you disclosed. A closeout record — request, materials, response, outcome, dates — filed where an examiner can find it. Name an owner for the queue and a service-level clock, and the five parts run themselves.

The whole thing fits on two pages of procedure. What examiners keep finding instead: disclosure text that exists but describes no actual mechanics, ROVs handled in email threads no one retained, and — the one that draws findings — loan officers "screening" requests before they reach the appraiser.

Where lenders get tripped up

The most common failure isn't malice; it's informality. An ROV resolved with a phone call leaves nothing to show an examiner, and nothing to defend the lender if the borrower later alleges the challenge was ignored. Close behind: treating the one-ROV limit as a reason to slow-walk the first request, missing your own disclosed turn times, and letting the process differ borrower to borrower — inconsistency is itself a fair-lending exposure. We covered how examiners test the wall between production staff and appraisers in Appraisal Independence in 2026; the ROV path is where that wall gets stress-tested hardest, because it's the one moment the process invites communication about value.

One more trap worth naming: the ROV that succeeds. When an appraiser revises a value after reconsideration, that's the system working — but it should trigger a quiet quality note, not just a relieved closing. Which brings us to the upside.

What a good ROV response looks like

The appraiser's obligation in a reconsideration of value is responsiveness, not surrender. A defensible response addresses each item the borrower raised — each proposed comparable accepted or rejected with a stated reason, each claimed factual error corrected or refuted — and lands in one of three places: the value changes, the value holds with strengthened support, or the report is corrected without a value change. All three are legitimate outcomes; what matters is that the reasoning is in writing.

Lenders should hold the no-change response to the same documentation bar as the revision, because the file that says "reviewed, no change" with nothing behind it is the one that looks like a rubber stamp in an exam. And the lender's role throughout is transmission, not translation — the borrower's request goes to the appraiser as submitted, and the appraiser's answer comes back as written.

ROV data is panel intelligence you already paid for

Every ROV your process produces is a structured record: which appraiser, what was challenged, what happened. Aggregated by appraiser and by market, that file answers questions panel managers otherwise guess at. An appraiser who draws reconsiderations at triple the panel rate — or whose values move every time they're challenged — is flagging themselves. A market where ROVs cluster is telling you where comps are thin and scrutiny should be higher. Lenders who treat the ROV file as a compliance archive are leaving the second half of its value unread. These are the same appraiser-level patterns Fannie Mae's Appraiser Quality Monitoring program watches for at national scale — your ROV file is the panel-sized version of it.

That's the reframe worth leaving with: the reconsideration of value process was imposed as a consumer protection, and it is one. Run well, it's also the cheapest quality-control instrument a lending operation owns — evidence, borrower goodwill, and panel insight from a process you were required to build anyway. The lenders who struggle with ROVs treat them as challenges to be survived. The ones who don't treat them as data.