For appraisers & QC teams · UAD 3.6 · URAR

The knowledge hub for UAD 3.6.

Learn the new appraisal format, ask a grounded copilot, and validate your report — before UCDP. Practical guides, a plain-English glossary, all 728 compliance rules, and an AI that checks your actual file and cites every answer.

Grounded in the official spec · every answer cites its source · files processed in memory, never stored.

UAD 3.6 Copilot
grounded · cited
Why is site value required when I use the cost approach?
When the cost approach is used, the estimated site value becomes required — missing it is a Fatal edit that blocks your UCDP submission.
UAD1229 Cost approach & site value
…or upload a report and it checks it against every rule.
FreeThe UAD 3.6 fatals cheat sheet

The fatal edits that bounce a URAR at UCDP — with plain-English fixes. Grab the printable one-pager.

Get it free →

Real reports, not screenshots

Learn from the official sample reports

All 12 published URAR scenarios — with real values, characteristics, the delivered photos, and the actual report PDF. The clearest way to see how the new format actually looks.

All 12 sample reports →

The copilot

One place to learn it and check it

The copilot has read the entire hub. Ask anything about UAD 3.6 in plain language and get an answer that links its sources — or upload a report and it validates it against the schema and 728 rules, then tells you how to fix what it finds.

  • Grounded in the hub — it cites, it doesn’t guess
  • Use-type aware — subject vs. comparable rules, done right
  • Ask, learn, and validate in a single chat
Validation report
Attention required
2
Fatal
3
Warning
valid
Schema
FatalUAD1001

Provide the address line for the subject property.

FatalUAD1229

Provide the ‘Opinion of Site Value’.

“Explain how to fix these →” — and the copilot walks you through each one.

Why a hub

The new format is a lot — and UCDP is unforgiving.

UAD 3.6 replaces the familiar forms with one dynamic, data-first report and hundreds of conditional, context-sensitive rules. It’s easy to get wrong, and every Fatal edit sends the report back through the chain.

Context-sensitive rules

The same field can allow different values for the subject versus a comparable. The hub explains it; the copilot checks it.

Hidden conditional requirements

Use the cost approach and site value becomes required. Learn these chains here — before UCDP fires them back.

A brand-new vocabulary

MISMO, ValuationUseType, cardinality, subschema. The glossary puts every term in plain English.

How the check works

Three layers, mirroring what UCDP does

When you validate a report in the copilot, it runs the same class of checks the portal applies — deterministically, and before you submit.

01

Schema

Your report is checked against the GSE UAD 3.6 subschema — structure, containers, and allowed enumerations.

02

Conformance

Every data point is checked against the Delivery Specification: required/conditional fields, formats, and use-type-specific values.

03

Compliance

The published UAD Compliance Rules run — 728 completeness, validity, and reasonableness edits, tagged Fatal or Warning.

Privacy by design

Your report never touches our disk

Appraisal packages carry borrower PII, addresses, and an opinion of value. So when you validate one, it’s processed entirely in memory and discarded the moment your report is generated. Nothing is stored, shared, or used to train anything.

  • In-memory processing — no file written to disk
  • Discarded immediately after your report returns
  • Self-hosted deployment available for stricter teams
upload report
→ read into memory
→ validate (schema · conformance · compliance)
→ return findings
✗ never written to disk
✗ never retained

Get comfortable with UAD 3.6.

Ask the copilot, browse the hub, or validate a report — free to start, no account required.

Or get UAD 3.6 updates and early access as the hub grows: