Ava reads every appraisal.
Automated underwriting.
Ava is the review engine inside Dwelling Blocks, built to be the best appraisal review and the easiest one to put in front of your underwriters: no setup project, no form mapping, rules written in plain language. It reads a report the moment it arrives, the form, the addenda and the photos, checks it against your rules, and returns a pass, fail or inconclusive on every rule with the reasoning attached. It runs on every report placed through the platform, or on its own on any appraisal from any source, so an underwriting desk can put it to work without changing how orders are placed.
Form reports 2,140 sq ft. Sketch addendum totals 1,986 sq ft. Difference is 7.8%, above the 5% tolerance in this rule. Ask the appraiser to reconcile the GLA or correct the sketch.
What Ava does
Reads the whole report.
The form, the addenda, the attachments and the photos, on the redesigned URAR and on every legacy form still in circulation. Nothing about a report's layout has to be described first.
Applies your rules, written the way you would say them.
"Include three high-quality photos of the kitchen." "Comparable sales must have closed within the last 90 days." Each rule is scoped by product, state or channel, so a Texas requirement never fires on a California order, and each one carries the message the appraiser sees when it fails.
Returns a decision on every rule, with the reasoning.
Pass, fail or inconclusive. A fail comes with what was found and what to do about it. An inconclusive means Ava could not confidently find what the rule asks for, and it blocks on purpose: a review that guesses when it cannot read something is worse than one that says so.
Photo 19 shows the water heater from the front. The strapping is not visible from this angle and the addendum does not mention it. Ava cannot confirm or rule out compliance. Held for a person.
Holds the report until it is fixed or explained.
A blocking item is cleared by a revised report or by an acknowledgment with an explanation for the reviewer. Nothing moves to the next step before then. When every rule passes, which is what most reports do, the report moves on without anyone opening it.
Runs before submission, not after.
Appraisers on the network see Ava's findings before the report goes anywhere, so the revision request that used to cost a week never gets sent.
Kitchen photos: 2 found, rule asks for 3. Add one showing the range, sink and cabinetry.
What Ava never does
It does not change a value. The opinion of value belongs to the appraiser. Ava checks the report; it does not write it.
It does not decide alone. Every fail and every inconclusive is cleared by a person, either the appraiser with a revision or a reviewer accepting the explanation, and the record shows who cleared what and why.
It does not guess. When it cannot read something, it says so and routes the report to a person.
It does not run a rule you have not turned on. New rules start in draft, and nothing fires until you make it active.
Built for a regulated shop
Your model risk, compliance and audit teams will ask what Ava does, what it never decides, and how a decision can be reviewed after the fact. The answers are above, and the record backs them up.
Every finding carries its reasoning, so a reviewer, an internal auditor or an examiner can see why a report was held.
A complete audit trail on every report: which rules ran, which version, what was found, who cleared it and when.
Rules are versioned. Model updates ship on a schedule with release notes, and a new version can be run against your own recent reports before it goes live on your pipeline.
A person can override any finding, and the override is part of the record.
See "What trains Ava" below. The short version: your reports and your rules are yours.
The same SOC 2 Type II controls as the rest of the platform. Model documentation for your model risk review is available under NDA.
What trains Ava, and what does not.
Lenders ask this before anything else, so here it is plainly.
Ava is trained on the appraisal data that flows through Dwelling Blocks' own network and on data our customers have agreed to contribute, de-identified. A customer's reports, rules and review results are never used to build features for another customer without that customer's written agreement. Your rules are yours, your findings are yours, and nothing you upload is shared with anyone but you and the vendors on your own orders.
Ava on its own
You do not have to move your ordering to use Ava. Connect it to your LOS or your current ordering platform over the API, or stand it up for an internal review desk and upload the reports you already receive. Your rules, your reports, your results, with the same statuses and the same reasoning as a review inside the platform. It is the fastest way to put a consistent review on every appraisal a lender, an AMC or an investor touches, whatever platform placed the order.
your rules applied
results out
back to the source
Ava during the UAD 3.6 transition
Where you stand on 3.6 →The redesigned URAR is a report your reviewers have never read. Ava reads it as it is: the dynamic sections, the structured fields, the addenda and the photos. Your existing rules apply to the new report without a re-mapping project. Put Ava on every report through the transition, so a reviewer who is still learning the new form is not the last line of defense.
The model behind it
Ava runs on models built and tuned for one job, reading appraisal reports, and on the data that only a platform in the middle of the transaction has: more than 1,000 transactions a day across every property type and every state, with the revisions and the outcomes attached, so the model knows not just what a report says but what happened to it next.
Our own collateral model, trained on that data, is in development and will ship the way every Ava release does: versioned, documented, and run against your reports before it touches your pipeline.
Questions
Adding Ava is the easiest implementation your team has ever done.
Nothing about your ordering or payments has to change. Inside the platform, Ava is already on. On its own, one API call sends a report and the findings come back, whatever platform placed the order. Rules are written the way an underwriter would say them, there is no form mapping, and we run it beside your current review until you are satisfied. If it is not right, you have lost nothing.
How switching works →See Ava on your own reports.
Send us three rules and a report, and we will show you what comes back.