Uniform Appraisal Dataset: UAD 3.6 reporting.

What is the Uniform Appraisal Dataset (UAD 3.6)?

The Uniform Appraisal Dataset (UAD) standardizes appraisal information for Fannie Mae and Freddie Mac. UAD 3.6 aligns with the MISMO 3.6 Reference Model and supports the redesigned Uniform Residential Appraisal Report (URAR): a report whose content responds to the property and assignment data.

For product teams, this makes the data model and report conditions central to the implementation. Read the Freddie Mac UAD overview.

UAD 2.6 and UAD 3.6: what changes?

Legacy form numbers give way to a dynamic URAR, with discrete and repeatable information driving the report. Software teams should review field mapping and report generation rather than treating the transition as a change to a PDF template. See the official UAD 3.6 FAQs.

UAD 3.6 implementation dates

The transition uses the UCDP submission date, not the appraisal’s effective date. Confirm pipeline handling against the joint GSE timeline and current FAQs.

Fannie Mae guidelines for UAD 3.6 workflows

Fannie Mae publishes a Selling Guide Supplement for UAD 3.6. Use the applicable policy together with the technical specifications; the supplement is not a replacement for checking the full requirements of the assignment.

For measurement workflows, the supplement addresses above- and below-grade areas, finished and unfinished areas, and separate reporting of certain additional spaces. Where ANSI Z765-2021 applies, scan or sketch output must meet the standard. Do not assume an interior room-area total is the reportable dwelling area.

Our implementation approach: preserve the original geometry, allow reviewed classifications and corrections, and make the calculation trail available to the responsible reviewer.

Freddie Mac guidelines for UAD 3.6 workflows

Use Freddie Mac’s UAD resources alongside its Single-Family Seller/Servicer Guide and applicable Purchase Documents. Freddie Mac explicitly states that its FAQs do not replace those requirements.

The UAD FAQs explain that UAD 3.6 separates restricted appraisal updates and completion reports. Associated reports must match the original submission’s UAD version; UCDP does not allow mixed standards under one Document File Identifier.

Our implementation approach: retain the original submission version and identifiers, then make the correct follow-up report path visible to your users.

What should the inspection app collect?

The assignment and applicable specification determine the requirements. A good field workflow makes relevant details easy to record without presenting every possible field for every property.

• Room and component detail: the GSE inspection tips highlight kitchen and bathroom updates and condition, ceiling information, and separate ADU details.
• Observed defects: link the affected feature and location to a description, supporting photo and the required follow-up information.
• Evidence in context: keep the observation tied to the right dwelling, unit, outbuilding or other report section.

These are examples, not a complete checklist. Use the joint GSE Inspection and Reporting Tips and Appendix F-1 for field-level guidance.

Make photo requirements part of the workflow

The June 2026 Photo and Image Requirements job aid distinguishes required, conditionally required and optional images. Requirements vary with report sections and property details. Build the photo checklist from those conditions, and let reviewers identify missing evidence before report preparation.

A practical software implementation checklist

This is Appcodie’s proposed engineering approach, to be agreed with your appraisal and compliance teams:

1. Map the workflow first. Define the assignment types, responsible roles, review steps and target integrations.
2. Version the requirements. Record the specification release and policy references used for each implementation.
3. Preserve the data structure. Map identifiers, allowed values, repeating groups and conditional fields to the authoritative specification.
4. Design understandable validation. Tell the user which field or exhibit needs attention and why, with a path to correct it.
5. Test real scenarios. Cover room edits, multiple levels, missing photos, ADUs and follow-up reports appropriate to the product’s scope.
6. Confirm the delivery path. Agree integration access, required verification, submission feedback and release acceptance with the relevant partners.

For implementation references, use Appendix A-1 for delivery mapping, B-1 for report implementation, F-1 for reporting guidance and H-1 for URAR compliance rules. The Fannie Mae UAD documentation hub links the current publications.

From house scanning to appraisal reporting software

We can help connect house scanning and property data collection to review dashboards and appraisal reporting software. Our development services can include conditional data-entry screens, photo workflows, floor-plan tools and Uniform Appraisal Dataset reporting integrations. The required deliverables and acceptance criteria are defined with your team.

This is an independent software planning guide, not an official GSE publication or a complete appraisal standard. References to Fannie Mae and Freddie Mac do not represent affiliation, endorsement or verified-provider status. Appraisers and lenders remain responsible for their applicable professional and delivery requirements.

Related: custom house inspection software development and our interactive floor-plan demonstration.