SpreadRun

UAD 3.6 View and Location Codes: Why UCDP Flags Them

Published October 5, 2026

In UAD 3.6, view and location are not free text boxes. Each is a value from a fixed list in the delivery specification, and the report can carry more than one. When a field is missing, or set to Other with no description, UCDP returns a fatal finding.

What the fields are

  • View Type: one of 29 values, such as Residential, Park, Lake, Mountain, Woods, Highway or Other.
  • Range of View: Full, Partial, Seasonal or Other.
  • Site Influence: what the old forms called location. It is also a value from a list, with Other for anything not covered.

What triggers a finding

  • UAD1361 (subject) and UAD1450 (each sales comparable): the view type must be included. Fatal.
  • UAD1364: provide the range of view. Fatal.
  • UAD1328 (subject) and UAD1769 (each sales comparable): the site influence must be included. Fatal.
  • UAD1362, UAD1365, UAD1451, UAD1329 and UAD1770: when you pick Other, describe it. Fatal.
  • UAD1363 (primary view indicator), UAD1366 (impact on value and marketability) and UAD1330 (site influence proximity) are Warnings.

A value that is not on the list is a different problem. The delivery specification lists the supported values for each field, so typed text or an old UAD 2.6 abbreviation does not meet the specification. We found nothing in the UCDP user guide that says which status that produces, so we will not guess. Treat it as something to fix before the report goes out.

What UCDP does

Only lenders and their agents can submit to UCDP. Appraisers cannot register. So findings reach you through the lender or AMC, from the Submission Summary Report (SSR). In the published compliance rules, a Fatal finding makes the submission status Not Successful, and a Warning does not stop a Successful status. To get to Successful, every fatal finding has to be resolved, which usually means correcting the data and sending a new file.

Note the wording. These findings make a report Not Successful. Rejected is a different UCDP status for packages that could not be processed at all. See Not Successful vs Rejected.

How to fix it

  1. In the site section of your software, pick at least one view type and a range of view for the subject.
  2. Pick at least one site influence for the subject, and a view and site influence for every sales comparable.
  3. Wherever you chose Other, fill in the description.
  4. If your software let you type a value, replace it with one from the list.

About the validator: it checks every view, range and site influence value against the supported list, and it runs the Other description rules. The four "must be included" rules (UAD1361, UAD1450, UAD1328 and UAD1769) are among the ones it does not run yet, and every report lists them.

Rules quoted from Appendix H-1, URAR Compliance Rules v1.5. Values from Appendix A-1, URAR Delivery Specification.

Check the whole file, not just this field. The SpreadRun UAD 3.6 validator runs the delivery specification checks and 585 of the 728 published URAR compliance rules on your XML or ZIP and lists every finding with its rule ID and location. $1.00 per completed report from prepaid credits, with a free test on the page. Check a report

A PASS is not UCDP acceptance. UCDP also runs the rules the validator does not, GSE proprietary checks and its own system checks.

More UAD 3.6 fixes

Sources: UCDP General User Guide (February 2026), UCDP FAQ, and the URAR Delivery Specification (Appendix A-1) and Compliance Rules (Appendix H-1) on the Uniform Appraisal Dataset page. SpreadRun is not affiliated with or endorsed by Fannie Mae or Freddie Mac. This is general information, not legal advice.