[{"data":1,"prerenderedAt":187},["ShallowReactive",2],{"blog-uad-3-6-compliance-rules-fatal-warning":3},{"post":4,"related":74,"pillar":75},{"slug":5,"title":6,"seoTitle":7,"description":8,"date":9,"updated":10,"category":11,"pillar":12,"howto":12,"keywords":13,"tags":22,"related":26,"faq":30,"words":46,"minutes":47,"parts":48,"toc":51,"steps":73},"uad-3-6-compliance-rules-fatal-warning","The 728 UAD 3.6 Compliance Rules: Fatal vs. Warning, and the Ones That Bite","UAD 3.6 Compliance Rules: Fatal vs. Warning | Carat","UAD 3.6 compliance rules explained: 728 rules in Appendix H-1, 592 Fatal and 136 Warning, how they work and which ones are most likely to stop your report.","2026-10-08","2026-10-25","uad-3-6",false,[14,15,16,17,18,19,20,21],"uad 3.6 compliance rules","uad 3.6 fatal errors","appendix h-1 compliance rules","uad compliance api","ucdp fatal error","uad 3.6 warning messages","uad 3.6 hard stops","ucdp submission summary report",[23,24,25],"UAD 3.6","Compliance","UCDP",[27,28,29],"uad-3-6-complete-guide","mismo-3-6-xml-explained","ai-catches-amc-revision-requests",[31,34,37,40,43],{"q":32,"a":33},"How many UAD 3.6 compliance rules are there?","Appendix H-1 version 1.5, the compliance rules for the redesigned URAR, lists 728 rules: 592 Fatal and 136 Warning.",{"q":35,"a":36},"What is the difference between a Fatal and a Warning in UAD 3.6?","A Fatal finding makes the UCDP submission unsuccessful until the report is corrected and resubmitted. A Warning does not stop the submission, but it is reported to the lender on the Submission Summary Report for review.",{"q":38,"a":39},"Where can I find the UAD 3.6 compliance rules?","Fannie Mae and Freddie Mac publish them on their Uniform Appraisal Dataset pages. Appendix H-1 is the rule set for the redesigned URAR, and the GSE FAQ also points to Appendices H-2 and H-3.",{"q":41,"a":42},"Who runs the UAD 3.6 compliance rules?","The GSEs run them through the UAD Compliance API when a lender submits to UCDP. Good appraisal software runs the same rules locally so you can fix findings before you deliver.",{"q":44,"a":45},"Why does a rule say to contact the appraisal software vendor?","Those messages usually point to how the XML was written, such as a number format or an internal reference, rather than to something the appraiser entered. Report them to your software vendor.",1711,7,[49,50],"\u003Cp>Under UAD 2.6, a missing field usually meant a revision request from a reviewer, sometimes days later. Under UAD 3.6, it often means a Fatal finding the moment the lender submits to UCDP. The UAD 3.6 compliance rules are the reason. Fannie Mae and Freddie Mac publish them as Appendix H-1, and version 1.5 for the redesigned URAR has 728 of them: 592 Fatal and 136 Warning. This post explains how the rules work, what Fatal and Warning mean for you, and the rules most likely to catch an experienced appraiser on a Tuesday afternoon.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key takeaways\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>728 rules, 592 Fatal (stop the submission) and 136 Warning (flag for the lender).\u003C\u002Fli>\n\u003Cli>Most rules are conditional: they only fire when some other answer makes them apply.\u003C\u002Fli>\n\u003Cli>"Even if the value is 0" appears in 29 rules. Blank isn't zero.\u003C\u002Fli>\n\u003Cli>89 rules tell the reader to contact the software vendor. Those are mostly about how the XML was written.\u003C\u002Fli>\n\u003Cli>Running the rules while you work, not after delivery, is what saves the revision.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"where-the-rules-come-from\">Where the rules come from\u003C\u002Fh2>\n\u003Cp>The rules are part of the UAD 3.6 specification set on the \u003Ca href=\"https:\u002F\u002Fsinglefamily.fanniemae.com\u002Fdelivering\u002Funiform-mortgage-data-program\u002Funiform-appraisal-dataset\" target=\"_blank\" rel=\"noopener\">Fannie Mae UAD page\u003C\u002Fa> and the \u003Ca href=\"https:\u002F\u002Fsf.freddiemac.com\u002Ftools-learning\u002Funiform-mortgage-data-program\u002Fuad\" target=\"_blank\" rel=\"noopener\">Freddie Mac UAD page\u003C\u002Fa>. The \u003Ca href=\"https:\u002F\u002Fsf.freddiemac.com\u002Ffaqs\u002Fuad-and-forms-redesign\" target=\"_blank\" rel=\"noopener\">Freddie Mac UAD 3.6 FAQ\u003C\u002Fa> points to Appendices H-1, H-2 and H-3 for the full list of UAD Compliance API rules. H-1 is the set for the redesigned URAR, and it's the one this post covers.\u003C\u002Fp>\n\u003Cp>Each row in H-1 has:\u003C\u002Fp>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Column\u003C\u002Fth>\u003Cth>What it tells you\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Rule ID\u003C\u002Ftd>\u003Ctd>A number like UAD1187. This is what a lender will quote back to you\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Message\u003C\u002Ftd>\u003Ctd>Plain-English text, for example "Provide the interior condition rating."\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Logic\u003C\u002Ftd>\u003Ctd>The condition in data terms, for example "If InteriorConditionRatingCode is not provided"\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Severity\u003C\u002Ftd>\u003Ctd>Fatal or Warning\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Property affected\u003C\u002Ftd>\u003Ctd>Subject, a sales comparable, a rental comparable, a GRM comparable, or N\u002FA\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Section and label\u003C\u002Ftd>\u003Ctd>Where it lives on the URAR\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The rules are written against the MISMO 3.6 XML, not the PDF. If you're not sure what that means, \u003Ca href=\"\u002Fblog\u002Fmismo-3-6-xml-explained\">MISMO 3.6 XML explained\u003C\u002Fa> covers it in plain English.\u003C\u002Fp>\n\u003Ch2 id=\"fatal-vs-warning\">Fatal vs. Warning\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Fatal\u003C\u002Fstrong> means the submission is unsuccessful. The lender can't complete the UCDP submission until the report is fixed and resubmitted. In practice, that's a revision request with a short clock, and often an annoyed AMC coordinator.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Warning\u003C\u002Fstrong> means the submission goes through, but the finding shows up on the lender's Submission Summary Report. The lender decides whether it's acceptable. Some lenders let warnings pass. Others send every warning back to you as a question. Plan as if Warnings will come back.\u003C\u002Fp>\n\u003Cp>Here's how the 728 break down across the sections with the most rules:\u003C\u002Fp>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>URAR section\u003C\u002Fth>\u003Cth>Fatal\u003C\u002Fth>\u003Cth>Warning\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Data that doesn't display on the report\u003C\u002Ftd>\u003Ctd>78\u003C\u002Ftd>\u003Ctd>23\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Site\u003C\u002Ftd>\u003Ctd>66\u003C\u002Ftd>\u003Ctd>18\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Sales Comparison Approach\u003C\u002Ftd>\u003Ctd>70\u003C\u002Ftd>\u003Ctd>12\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Assignment Information\u003C\u002Ftd>\u003Ctd>41\u003C\u002Ftd>\u003Ctd>13\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Unit Interior\u003C\u002Ftd>\u003Ctd>43\u003C\u002Ftd>\u003Ctd>7\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Project Information\u003C\u002Ftd>\u003Ctd>41\u003C\u002Ftd>\u003Ctd>3\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Subject Property\u003C\u002Ftd>\u003Ctd>37\u003C\u002Ftd>\u003Ctd>2\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Dwelling Exterior\u003C\u002Ftd>\u003Ctd>28\u003C\u002Ftd>\u003Ctd>9\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Manufactured Home\u003C\u002Ftd>\u003Ctd>19\u003C\u002Ftd>\u003Ctd>9\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Market\u003C\u002Ftd>\u003Ctd>19\u003C\u002Ftd>\u003Ctd>3\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Cost Approach\u003C\u002Ftd>\u003Ctd>7\u003C\u002Ftd>\u003Ctd>10\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Reconciliation\u003C\u002Ftd>\u003Ctd>14\u003C\u002Ftd>\u003Ctd>1\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Two things stand out. Site is one of the heaviest sections, because site influences, features, utilities, hazard zones and encumbrances are all structured now. And over a hundred rules check data that doesn't display on the printed report at all: coordinates, internal links between parts of the file, flags that turn sections on and off. That's software territory.\u003C\u002Fp>\n\u003Cp>By property, 445 rules apply to the subject, about 100 apply to sales comparables, and the rest cover rental and GRM comparables, land comps or the report as a whole.\u003C\u002Fp>\n","\u003Ch2 id=\"how-the-rules-think\">How the rules think\u003C\u002Fh2>\n\u003Cp>Only a small share of the rules are as simple as "this field must be filled." About 61 have logic as short as "If [field] is not provided." Most are conditional. Their logic starts with "If" and joins several conditions with "and":\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Trigger rules.\u003C\u002Fstrong> If you said X, you must also say Y. If the property has a sales concession, indicate whether the amount is known (UAD1127). If a reconsideration of value was requested, comment on the outcome (UAD1751).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Explicit-none rules.\u003C\u002Fstrong> You must answer even when the answer is nothing. Provide the total number of ADUs, even if the value is 0 (UAD1010). Hazard zone type must be included, select "None" if there isn't one (UAD1313).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Consistency rules.\u003C\u002Fstrong> Two answers must agree. The net adjustment total must equal the sum of the line adjustments (UAD1461). The ADU count plus the non-ADU unit count must equal the total living units (UAD1693).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sanity rules.\u003C\u002Fstrong> Values must make sense. The effective date can't be in the future (UAD1258). The opinion of market value must be at least one dollar (UAD1263). Year built can't be after the effective date (UAD1053).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"the-ones-that-bite\">The ones that bite\u003C\u002Fh2>\n\u003Cp>These are the rules that catch appraisers who've been doing this for twenty years, because they ask for things the 1004 never did.\u003C\u002Fp>\n\u003Ch3 id=\"zero-is-an-answer\">Zero is an answer\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1187\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the Finished Above Grade (Nonstandard) area, even if the value is 0\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1484\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the Finished Below Grade (Nonstandard) area, even if the value is 0\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1010\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the total number of ADUs, even if the value is 0\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1779\u003C\u002Ftd>\u003Ctd>Warning\u003C\u002Ftd>\u003Ctd>Provide the comp's Finished Area Above Grade (Nonstandard), even if the value is 0\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>On a 1004, you left a box blank when it didn't apply. UAD 3.6 needs to know that you looked and found nothing. A blank field and a zero are different answers.\u003C\u002Fp>\n\u003Ch3 id=\"sketch-and-measurement\">Sketch and measurement\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1676\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Indicate whether a sketch or floor plan has been included\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1677\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the measurement standard (ANSI, AMS) used, when a sketch is included\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1678\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Describe the standard when the measurement standard is "Other"\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Your sketch software has to report the standard, not just the area. See \u003Ca href=\"\u002Fblog\u002Fansi-z765-gla-uad-3-6\">ANSI Z765 and GLA under UAD 3.6\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"photos\">Photos\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1274\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>The required subject property photos must be included\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1275\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide a photo of each sales comparable used in the valuation\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1043\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the legal description or an image of the legal description\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Photos are checked by their category in the XML. A photo with the wrong category is, to the rules, a missing photo.\u003C\u002Fp>\n\u003Ch3 id=\"defects-and-condition\">Defects and condition\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1046\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Indicate whether the subject property amenities have any defects, damages or deficiencies\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1094\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Indicate whether the outbuilding has any defects, damages or deficiencies\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1160\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the interior condition rating\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1267\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the as-is overall condition rating (when value is subject to completion or repairs)\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The as-is rating on a subject-to report is easy to miss. If your value is subject to repairs, the report still needs the property's condition today.\u003C\u002Fp>\n\u003Ch3 id=\"comps-and-the-market\">Comps and the market\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1396\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the proximity to subject distance for the sales comparable\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1428\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the total days on market for the sales comparable\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1634\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the median days on market for the active listings\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1461\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Net adjustment total doesn't equal the sum of the individual adjustments\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1657\u003C\u002Ftd>\u003Ctd>Warning\u003C\u002Ftd>\u003Ctd>Provide the price trend source for each data source used\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"history-and-the-paper-trail\">History and the paper trail\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1191\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Indicate whether the subject property has a prior sale or transfer\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1750\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Indicate whether a reconsideration of value has been requested\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1659 \u002F UAD1660\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Indicate whether the highest and best use is financially feasible \u002F legally permissible\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Ch3 id=\"warnings-that-come-back-as-questions\">Warnings that come back as questions\u003C\u002Fh3>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Message\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1353\u003C\u002Ftd>\u003Ctd>No public electricity connection has been identified. Please check for accuracy\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1051\u003C\u002Ftd>\u003Ctd>The property can only be considered new construction when year built is within 1 year of the effective date\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1512\u003C\u002Ftd>\u003Ctd>Appraiser certification #10 doesn't align with the property valuation method\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1212\u003C\u002Ftd>\u003Ctd>Provide the federal agency (VA, USDA, FHA) for which the appraisal was prepared\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1367\u003C\u002Ftd>\u003Ctd>Provide the site zoning classification code\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cblockquote class=\"bl-callout tip\">\u003Cp>\u003Cstrong>Tip:\u003C\u002Fstrong> When a lender forwards a finding, ask for the rule ID, not just the message. "UAD1677" points to one field. "Missing measurement info" could mean three.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2 id=\"the-vendor-rules\">The vendor rules\u003C\u002Fh2>\n\u003Cp>89 of the 728 messages end with "For assistance with this message, contact the appraisal software vendor." Examples: latitude must have at least five digits after the decimal (UAD1742); external depreciation must be delivered as a positive number in the XML (UAD1234); custom grid row labels must be identical across comps (UAD1455).\u003C\u002Fp>\n\u003Cp>You mostly can't fix these by typing a different value. They're about how the file was built. If you see one, send it to your software vendor with the report. If you see them often, that tells you something about your software.\u003C\u002Fp>\n\u003Ch2 id=\"catch-it-before-the-amc-does\">Catch it before the AMC does\u003C\u002Fh2>\n\u003Cp>The best time to see a Fatal finding is while the field is still on your screen, not three days after delivery when the AMC sends it back. That means running the rules locally, as you work, with each finding pointing at the field that caused it.\u003C\u002Fp>\n\u003Cp>A short workflow that works:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Fill the report in order.\u003C\u002Fstrong> Many rules are conditional, so earlier answers change what's required later.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Watch the findings list, not just the PDF.\u003C\u002Fstrong> A clean-looking PDF can still have a dozen Fatal findings in the data.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Clear Fatal first, then Warnings.\u003C\u002Fstrong> Treat Warnings as questions the reviewer will ask.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rebuild the package and re-check.\u003C\u002Fstrong> Every build should validate the XML against the GSE schema.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Keep your rule IDs.\u003C\u002Fstrong> If a lender quotes one, you can trace it back fast.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Carat's AI-powered readiness checks work this way. They run hundreds of the H-1 rules locally while you work, and each finding links straight to the field. The share of rules it evaluates locally is large and growing, and the XML is validated against the GSE schema on every build. You or your client still submit to UCDP. For more on catching problems before delivery, see \u003Ca href=\"\u002Fblog\u002Fai-catches-amc-revision-requests\">how AI catches AMC revision requests before you deliver\u003C\u002Fa>, and for the full list of AMC asks, \u003Ca href=\"\u002Fblog\u002Famc-revision-request-survival-guide\">the AMC revision request survival guide\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"where-this-fits\">Where this fits\u003C\u002Fh2>\n\u003Cp>The compliance rules are the part of UAD 3.6 that changes your day most directly. For the whole picture, read \u003Ca href=\"\u002Fblog\u002Fuad-3-6-complete-guide\">the complete UAD 3.6 guide\u003C\u002Fa>. To work through your setup before November 2, use \u003Ca href=\"\u002Fblog\u002Fuad-3-6-readiness-checklist\">the UAD 3.6 readiness checklist\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you'd like to see which rules your own report trips, \u003Ca href=\"\u002Fsign-in?mode=create\">create an Carat account\u003C\u002Fa> and build one. It's \u003Ca href=\"\u002F#pricing\">$99 a month per appraiser, unlimited reports\u003C\u002Fa>.\u003C\u002Fp>\n",[52,55,58,61,64,67,70],{"id":53,"t":54},"where-the-rules-come-from","Where the rules come from",{"id":56,"t":57},"fatal-vs-warning","Fatal vs. Warning",{"id":59,"t":60},"how-the-rules-think","How the rules think",{"id":62,"t":63},"the-ones-that-bite","The ones that bite",{"id":65,"t":66},"the-vendor-rules","The vendor rules",{"id":68,"t":69},"catch-it-before-the-amc-does","Catch it before the AMC does",{"id":71,"t":72},"where-this-fits","Where this fits",[],[75,119,152],{"slug":27,"title":76,"seoTitle":77,"description":78,"date":79,"updated":10,"category":11,"pillar":80,"howto":12,"keywords":81,"tags":91,"related":94,"faq":98,"words":117,"minutes":118},"UAD 3.6: The Complete Guide for Residential Appraisers (2026)","UAD 3.6 Guide for Appraisers (2026) | Carat","UAD 3.6 explained for working appraisers: the redesigned URAR, MISMO 3.6 XML, the 728 compliance rules, the November 2, 2026 mandate and how to get ready.","2026-10-20",true,[82,83,84,85,86,87,88,89,14,90],"uad 3.6","uad 3.6 appraisal","uniform appraisal dataset 3.6","redesigned urar","uad 3.6 mandate","uad 3.6 for appraisers","uad 3.6 changes","new urar form","mismo 3.6",[23,92,93,24],"URAR","MISMO 3.6",[95,96,97],"uad-3-6-deadline-timeline","uad-3-6-replaces-1004-1073-1025-2055","uad-3-6-readiness-checklist",[99,102,105,108,111,114],{"q":100,"a":101},"When is UAD 3.6 mandatory?","UAD 3.6 is mandatory for new appraisal reports submitted to UCDP on or after November 2, 2026. The date is based on the initial UCDP submission date, not the loan application date or the effective date of the appraisal.",{"q":103,"a":104},"What is UAD 3.6?","UAD 3.6 is the redesigned Uniform Appraisal Dataset from Fannie Mae and Freddie Mac. It replaces the separate appraisal forms with one dynamic report, the redesigned URAR, delivered as MISMO 3.6 XML with a matching PDF and image files in a single zip.",{"q":106,"a":107},"Does UAD 3.6 change how I value a house?","No. The appraisal process, USPAP and your analysis stay the same. UAD 3.6 changes how the data is collected, structured and reported, and it asks for more of your reasoning in structured fields and commentary.",{"q":109,"a":110},"Can I still use the Form 1004 after November 2, 2026?","Only in limited cases. Sellers that obtained a one-time GSE policy exception may submit new UAD 2.6 reports through May 19, 2027, and resubmissions of UAD 2.6 reports are accepted through June 27, 2027. UAD 2.6 is retired on June 28, 2027.",{"q":112,"a":113},"Do appraisers submit UAD 3.6 reports to UCDP?","Usually not. The appraiser delivers the zip package to the client, and the lender or its AMC submits it to UCDP. FHA loans go to the FHA EAD portal.",{"q":115,"a":116},"Is there an approval appraisers need for UAD 3.6?","No. There is no appraiser certification for UAD 3.6. Software vendors can go through GSE verification, which is a vendor listing that lenders check, not an approval for the appraiser.",3159,14,{"slug":28,"title":120,"seoTitle":121,"description":122,"date":123,"updated":10,"category":11,"pillar":12,"howto":12,"keywords":124,"tags":132,"related":134,"faq":135,"words":151,"minutes":47},"MISMO 3.6 XML Explained for Appraisers (No Developer Required)","MISMO 3.6 XML Explained for Appraisers | Carat","MISMO 3.6 XML explained in plain English for appraisers: what's in the UAD 3.6 file, how it relates to the PDF and images, and why the zip package matters.","2026-09-29",[90,125,126,127,128,129,130,131],"mismo 3.6 xml","uad 3.6 xml","mismo xml appraisal","uad 3.6 zip file","appraisal xml file","mismo 2.6 vs 3.6","ucdp xml",[93,23,133],"XML",[27,5,97],[136,139,142,145,148],{"q":137,"a":138},"What is MISMO 3.6?","MISMO is the Mortgage Industry Standards Maintenance Organization, which publishes data standards for the mortgage industry. Version 3.6 of its reference model is the base the GSEs used for the UAD 3.6 appraisal dataset.",{"q":140,"a":141},"Do appraisers need to read or edit MISMO XML?","No. Your appraisal software writes the XML from what you enter. It helps to know what's in it, because the GSE compliance rules check the XML, not the PDF.",{"q":143,"a":144},"What files are in a UAD 3.6 zip?","One UAD 3.6 XML file, one first-generation PDF of the report that matches the XML, and a folder named Images with every photo, map and exhibit the XML references. The zip can't exceed 60 MB.",{"q":146,"a":147},"Can I edit the PDF after my software creates it?","You shouldn't. Appendix B-1 says the PDF must match the XML and must be a first-generation PDF produced by the appraiser's software. Make changes in the report and rebuild the package.",{"q":149,"a":150},"Are photos embedded in the UAD 3.6 XML?","No. Images go in the Images folder of the zip. The XML holds only metadata for each image, such as its category and its relative path in the zip.",1563,{"slug":29,"title":153,"seoTitle":154,"description":155,"date":156,"updated":10,"category":157,"pillar":12,"howto":12,"keywords":158,"tags":166,"related":170,"faq":173,"words":186,"minutes":47},"How AI Catches AMC Revision Requests Before You Deliver","How AI Catches AMC Revision Requests | Carat","How AI checks catch AMC revision requests before you deliver: the UAD 3.6 rules behind them, a pre-delivery review, and what software can't catch.","2026-10-07","ai",[159,160,161,162,163,164,18,165],"amc revision request","appraisal revision request","ai appraisal review","appraisal automation","uad 3.6 compliance check","appraisal qc checklist","ai for appraisers",[167,168,23,169],"AI","Revisions","AMCs",[171,172,5],"ai-appraisal-software-2026","amc-revision-request-survival-guide",[174,177,180,183],{"q":175,"a":176},"Why do AMCs send so many revision requests?","Most come from three places: data errors that fail the GSE compliance rules at UCDP, inconsistencies a reviewer spots between parts of the report, and client-specific requirements or judgment questions about comps and adjustments. Software can prevent most of the first kind and some of the second.",{"q":178,"a":179},"Can AI review an appraisal before I send it?","Software can check the report against the GSE Appendix H-1 compliance rules and flag missing data, math that doesn't add up and fields that contradict each other. It cannot judge whether your comps or your value are right; that review is still yours.",{"q":181,"a":182},"What is a Fatal finding under UAD 3.6?","A Fatal finding is a compliance rule failure that stops the submission at UCDP until it is fixed. Appendix H-1 lists 728 rules for the redesigned URAR: 592 Fatal and 136 Warning.",{"q":184,"a":185},"How do I reduce revision requests from AMCs?","Run a rules check before every delivery and fix every Fatal, keep a list of each client's standing requirements, make sure commentary agrees with the grid, and answer the obvious questions in the report before a reviewer asks them.",1513,1793082914939]