Decoding the New URAR: A Guide to the UAD 3.6 Style Guide Codes

As an appraiser who’s spent years in the field, I’ve seen my share of industry shifts. But the move toward the new Uniform Appraisal Dataset (UAD) 3.6 and the redesigned Uniform Residential Appraisal Report (URAR) is more than just another update—it’s a fundamental change in how we document and deliver our findings. We’ve all heard about the high-level changes, like the move to a dynamic, data-driven format. Today, I want to go a level deeper and look at the very architecture of the new report. By dissecting the official “Report Style Guide Supplement,” we can start to understand the new visual language we’ll all be using, from section headers to the specific codes that define every piece of data.

Beyond the Form: A Modular, Coded Structure

The first thing to internalize is that we are moving away from the concept of a static, monolithic form. The days of simply filling in the blanks on a familiar PDF like the 1004 are ending. Instead, the new URAR is a dynamic report assembled from modular components, driven by the data collected for a specific property. If you need a refresher on how this data-first approach replaces traditional form numbers, I recommend reading my colleague's post on how six key data points are redefining appraisals.

This modularity is governed by a strict set of rules outlined in the Style Guide. Every label, every text box, and every table has a specific code. This isn’t just for looks; it’s to ensure the final report is perfectly machine-readable for the GSEs and lenders.

Decoding the Building Blocks: From H1 to TXR-B

To navigate the new URAR, you need to learn its structural language. The Style Guide Supplement provides a complete map, and here are some of the most important codes you’ll encounter:

• H1 and H2 (Headers): These are the primary organizational elements. An H1 code signifies a major section header, like Assignment Information or Quality and Condition. An H2 code is a sub-header within that section, such as Appraiser or Exterior Features. This creates a clear and consistent hierarchy.

• TXR-B (Text, Regular, Bold): This is one of the most common codes, representing a standard data field label. When you see Property Valuation Method or Construction Method in the new report, that’s a TXR-B element. It’s a bolded label for a discrete data point.

• TXC-I (Text, Commentary, Italic): This code denotes an instructional or commentary text block. For example, the sentence “The items listed below represent the As Is condition as of the effective date of this report” is a TXC-I element. It provides context or guidance in italics.

• TCH and TB (Table Elements): These codes define the structure of tables. TCH is the Table Column Header (e.g., Feature, Location, Description) and TB is the Table Body, where the rows of data go.

Interactive and Conditional Elements

The new URAR is dynamic, meaning it changes based on the property. The Style Guide shows how this is controlled through specific codes for interactive elements.

• CK1 (Checkbox): This code denotes a checkbox, such as those for Planned Unit Development (PUD) or Condominium. This is a critical input. Checking one of these boxes will trigger other required data fields and sections to appear in the report.

• TAB (Navigation Tab): This code represents a major navigational tab within the report’s digital structure, such as Subject Property or Sales Contract. It shows how the different modules of the report are organized for user navigation.

A Practical Example: The Defects Section

Let’s see how these codes work together by looking at the Apparent Defects, Damages, Deficiencies Requiring Action section, as shown on page 28 of the Style Guide Supplement.

1. The section starts with an H1 header.

2. It’s followed by a TXC-I line of italicized text explaining what the section contains.

3. A table is then built using TCH for the headers (Feature, Location, etc.) and TB for the data rows.

4. Below the table, you find two TXR-B fields: As Is Overall Condition Rating and Total Estimated Cost of Items Recommended for Repair.

This highly structured format ensures that every piece of information about a defect is captured in a predictable, discrete, and machine-readable way, eliminating the need for long, narrative addenda.

What This Means for Your Daily Workflow

This coded structure is the backbone of the entire UAD 3.6 initiative. It’s what allows the GSEs' and lenders' automated systems to "read" and analyze your report instantly. For us in the field, it means data accuracy and consistency are more critical than ever before. A comment placed in the wrong field or an incorrectly formatted data point won't be buried in a PDF; it will be an immediate data error.

This is where technology built for this new ecosystem can be a significant advantage. For instance, an application like Valuemate is designed to capture data in a structured format from the moment of inspection. By using a LiDAR scan to generate a floor plan and prompting for specific data points room-by-room, it ensures that the information flows correctly into the corresponding coded components of the new URAR. This approach can drastically reduce the risk of manual data entry errors and helps align your work with the new standards from the ground up.

The Way Forward

While it may seem daunting, this new coded structure is designed for clarity, consistency, and efficiency. Learning to read the language of the new URAR—understanding what H1, TXR-B, and CK1 signify—is a crucial step in preparing for the transition. We are moving from being authors of a document to being assemblers of a precise data package. Embracing this change and becoming fluent in the new format will position you for success in the modernized appraisal landscape.