All guides

Property type·8 min read·Sample: Condo1, Condo2

Condominium appraisals in UAD 3.6

Project data, ownership interest, and unit-level modeling for attached condominium units — using the two condo sample scenarios.

In this guide
Rules coveredUAD1021
Worked examplesCondominium (Condo1)

Ask the copilot about this guide — it has read the whole hub and cites what it uses.

A condo appraisal is really two appraisals stapled together: the unit you're valuing and the project it lives in. On the old 1073 those were rows on a form; in UAD 3.6 the project is its own data with its own required fields, and the unit's requirements shift depending on what the project is. The two condo samples cover both a clean mid-rise unit and a messier project scenario.

$778,000
Condo1 opinion of value
1973
Year built
C3 / Q4
Overall condition / quality
Hybrid
Valuation method (used a PDR)
Hybrid Appraisal$778,000
Condominium (Condo1)
Attached · 4 comps
Worked example$778,000
Condominium (Condo1)

Condo1 is a hybrid appraisal of an attached mid-rise unit — a good one to open because it also shows how a Property Data Report threads through the assignment data.

Project membership rewrites the requirements

PropertyInProjectIndicator and ProjectLegalStructureType are the switches. When the property is in a project, project-level data — name, legal structure, ownership, control — is expected. When it isn't, the estate-type requirements move instead. The trap is that these interact: the estate type is required both when there's no project AND when the project is a condominium, so "it's a condo, surely the project covers it" is exactly the wrong instinct.

UAD1021FatalField 1.023Rule details →
Rule logic
If (PropertyInProjectIndicator = "false" or ProjectLegalStructureType = "Condominium"), and PropertyEstateType is not provided
Fix
Provide the estate type whenever the property is not in a project, or the project is a condominium. This is a compound condition — both branches require it, and a condo hits the second branch.
Seen in a sample
FeeSimple in Single-family (SF1)

Keep the unit and the project in separate boxes

The single most common data-quality issue in condo reports is putting project-level facts on the unit and vice versa. Common areas, parking assignment, and shared amenities belong to the project; the unit carries its own interior improvements and condition. Cross them and you get consistency edits that are hard to trace because everything "looks" filled in.

Condo1 price trend chart
A real analysis exhibit from Condo1 — the price-trend chart supporting the market conditions.

Keep reading