[{"data":1,"prerenderedAt":183},["ShallowReactive",2],{"blog-ai-catches-amc-revision-requests":3},{"post":4,"related":72,"pillar":73},{"slug":5,"title":6,"seoTitle":7,"description":8,"date":9,"updated":10,"category":11,"pillar":12,"howto":12,"keywords":13,"tags":22,"related":27,"faq":31,"words":44,"minutes":45,"parts":46,"toc":49,"steps":71},"ai-catches-amc-revision-requests","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","2026-10-25","ai",false,[14,15,16,17,18,19,20,21],"amc revision request","appraisal revision request","ai appraisal review","appraisal automation","uad 3.6 compliance check","appraisal qc checklist","ucdp fatal error","ai for appraisers",[23,24,25,26],"AI","Revisions","UAD 3.6","AMCs",[28,29,30],"ai-appraisal-software-2026","amc-revision-request-survival-guide","uad-3-6-compliance-rules-fatal-warning",[32,35,38,41],{"q":33,"a":34},"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":36,"a":37},"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":39,"a":40},"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":42,"a":43},"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,7,[47,48],"\u003Cp>It's 9:14pm. The email subject line says "REVISION REQUEST - URGENT." The AMC wants the half-bath photo, the net adjustment on comp 4 doesn't match the line items, and the reviewer asks why the zoning section says "legal nonconforming" with no comment on rebuild. None of it changes your value. All of it costs you an evening. This is the AMC revision request most appraisers know best, and it's the one software is best at preventing. Here is how AI-powered checks catch those requests before you deliver, which ones they can't catch, and a pre-delivery routine that works with any software.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key takeaways\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Most revision requests fall into three buckets: rule failures, internal inconsistencies, and judgment or client-specific asks.\u003C\u002Fli>\n\u003Cli>UAD 3.6 publishes the rules: Appendix H-1 has 728 compliance rules, 592 Fatal and 136 Warning. Checking against them before delivery prevents the first bucket.\u003C\u002Fli>\n\u003Cli>Consistency checks (does the commentary agree with the grid?) prevent a lot of the second.\u003C\u002Fli>\n\u003Cli>The third bucket, "add a comp," "support your adjustment," is judgment. Software can help you prepare; it can't answer for you.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"the-three-kinds-of-revision-request\">The three kinds of revision request\u003C\u002Fh2>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Kind\u003C\u002Fth>\u003Cth>Example\u003C\u002Fth>\u003Cth>Can software catch it?\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>Rule failure\u003C\u002Ftd>\u003Ctd>Net adjustment total doesn't equal the line items; missing kitchen photo; inspection date after effective date\u003C\u002Ftd>\u003Ctd>Yes, before delivery\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Inconsistency\u003C\u002Ftd>\u003Ctd>Commentary says $50\u002Fsq ft for GLA, grid uses $35; GLA in the report doesn't match the sketch; zoning "illegal" with no reason\u003C\u002Ftd>\u003Ctd>Often, with consistency checks and careful review\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Judgment or client-specific\u003C\u002Ftd>\u003Ctd>"Add a comp within 0.5 miles sold in the last 90 days"; "support the view adjustment"; the AMC's own exhibit requirements\u003C\u002Ftd>\u003Ctd>Partly: software can surface your data, but you decide\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>The first bucket is pure clerical error. It's also the one that most often comes back from UCDP as a hard stop under UAD 3.6, because the GSEs publish the rules and the lender's portal runs them.\u003C\u002Fp>\n\u003Ch2 id=\"what-the-uad-3-6-compliance-rules-actually-check\">What the UAD 3.6 compliance rules actually check\u003C\u002Fh2>\n\u003Cp>Appendix H-1 is a spreadsheet of rules that the GSEs use to check the MISMO 3.6 XML. Each rule has a message ID, the message text the lender sees on the UCDP Submission Summary Report, and a severity. A \u003Cstrong>Fatal\u003C\u002Fstrong> stops the submission. A \u003Cstrong>Warning\u003C\u002Fstrong> gets through but is visible to the lender and often to the AMC reviewer.\u003C\u002Fp>\n\u003Cp>Here are real rules from H-1 that line up with requests appraisers get every week:\u003C\u002Fp>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Rule\u003C\u002Fth>\u003Cth>Severity\u003C\u002Fth>\u003Cth>Message (from Appendix H-1)\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>UAD1279\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>The mandatory room photos (i.e., kitchen, full-bathroom, half-bathroom) 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>UAD1461\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>The 'Net Adjustment Total' does not equal the sum of the individual adjustments.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1557\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>The 'Inspection Date' must be on or before the 'Effective Date of Appraisal'.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1370\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the 'Reasons Illegal' for site zoning.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1296\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide the type of apparent environmental condition. Select 'None' if there are no apparent environmental conditions.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1624\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>At least one defect, damage, or deficiency must be provided when the appraisal 'Market Value Condition' is 'Subject to Repair'.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1656\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide either an image of the price trend graph or price trend analysis commentary.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1266\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>Provide commentary for the reconciliation of market value.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1767\u003C\u002Ftd>\u003Ctd>Fatal\u003C\u002Ftd>\u003Ctd>The commentary provided for the specified field exceeds the allowable limit of 540 characters.\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>UAD1387\u003C\u002Ftd>\u003Ctd>Warning\u003C\u002Ftd>\u003Ctd>Provide 'Reconciliation of Overall Quality and Condition'.\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Notice how many of these are things you know to do and simply missed at the end of a long day. That's the point. A person reviewing their own report at 11pm skims. A rules engine doesn't.\u003C\u002Fp>\n\u003Cp>The full rule set, and the ones that bite hardest, are in \u003Ca href=\"\u002Fblog\u002Fuad-3-6-compliance-rules-fatal-warning\">the 728 UAD 3.6 compliance rules: Fatal vs. Warning\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cblockquote class=\"bl-callout note\">\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Some H-1 messages say "For assistance with this message, contact the appraisal software vendor." Those are technical XML problems, not appraisal problems. Good software should never let you produce them in the first place.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2 id=\"how-ai-powered-checks-work-in-practice\">How AI-powered checks work in practice\u003C\u002Fh2>\n\u003Cp>"AI" here is mostly disciplined rules evaluation, done continuously instead of once at the end. A useful checker does four things.\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Runs while you work.\u003C\u002Fstrong> You find out the half-bath photo is missing while you're still in the photo section, not after you've packaged the zip.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Understands conditional rules.\u003C\u002Fstrong> UAD 3.6 is dynamic. A pool, an easement or a "subject to" condition switches on more required fields. The checker has to know which fields your report now needs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Links each finding to the field.\u003C\u002Fstrong> "UAD1461" is not useful on its own. "Comp 4: net adjustment doesn't equal the line items," with a click to the grid, is.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Separates Fatal from Warning.\u003C\u002Fstrong> Fix every Fatal. Read every Warning and decide.\u003C\u002Fli>\n\u003C\u002Fol>\n","\u003Cp>Carat's AI-powered readiness checks evaluate hundreds of the H-1 rules locally as you fill the report, with each finding linked straight to the field. Not every rule runs locally yet, and we say so; the share is large and growing. The final word is still UCDP's, at the lender's submission.\u003C\u002Fp>\n\u003Ch2 id=\"consistency-the-second-bucket\">Consistency: the second bucket\u003C\u002Fh2>\n\u003Cp>Rules check that the data is present and valid. Reviewers also read the report as a whole, and they're good at spotting places where it disagrees with itself. Before you deliver, check:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Commentary vs. grid.\u003C\u002Fstrong> If your GLA commentary says $50 per square foot, every GLA adjustment in the grid should use $50 (or you should say why not).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sketch vs. report.\u003C\u002Fstrong> GLA, room counts and below-grade area should match the sketch exactly. A sketch tool that writes GLA into the report removes this one.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Value vs. approaches.\u003C\u002Fstrong> If your final value sits outside the range of every approach you developed, the reconciliation has to say why.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Condition and quality.\u003C\u002Fstrong> The subject's ratings should match the photos and the defects you reported. A C2 with a "Subject to Repair" condition invites a question.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Addresses and parties.\u003C\u002Fstrong> Client name and address, lender, borrower. A wrong ZIP on the client block is a revision.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Exhibits.\u003C\u002Fstrong> License, E&O, maps, sketch, all present and current. If your exhibits come from a firm profile, an expired E&O declaration page is a one-time fix instead of a per-report risk.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote class=\"bl-callout tip\">\u003Cp>\u003Cstrong>Tip:\u003C\u002Fstrong> Keep a short "standing requirements" note for each AMC you work with. If one client always asks for smoke and CO detector photos, or a statement on whether a legal nonconforming property can be rebuilt, put it in the report the first time.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2 id=\"the-third-bucket-judgment-requests\">The third bucket: judgment requests\u003C\u002Fh2>\n\u003Cp>"Please add a comp within 0.5 miles sold in the last 90 days." In a rural market that comp may not exist. "Please support your adjustments." "Please consider these three sales the borrower found." No checker can answer these for you, and none should.\u003C\u002Fp>\n\u003Cp>Software can help you get ready for them:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Show the sales you considered and rejected.\u003C\u002Fstrong> UAD 3.6 includes a section for Additional Properties Analyzed but Not Used. Filling it answers the "did you consider..." question before it's asked.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Show your support.\u003C\u002Fstrong> If you can say "my last 40 reports in this town and price tier used a median of $X for a garage bay," the "support your adjustment" request becomes a sentence, not an afternoon. See \u003Ca href=\"\u002Fblog\u002Fdata-driven-adjustments-from-past-reports\">data-driven adjustments from your own past reports\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Keep your history searchable.\u003C\u002Fstrong> When a reviewer sends three sales, you want to know in a minute whether you've appraised in that subdivision before and what you found.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For the full list of the most common requests and how to answer each one politely and fast, see \u003Ca href=\"\u002Fblog\u002Famc-revision-request-survival-guide\">the AMC revision request survival guide\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"a-10-minute-pre-delivery-routine\">A 10-minute pre-delivery routine\u003C\u002Fh2>\n\u003Cp>Use this with any software.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Run the compliance check. Fix every Fatal.\u003C\u002Fli>\n\u003Cli>Read every Warning. Fix it, or decide it's correct and make sure the report explains why.\u003C\u002Fli>\n\u003Cli>Compare GLA and room counts to the sketch.\u003C\u002Fli>\n\u003Cli>Compare every rate in your commentary to the grid.\u003C\u002Fli>\n\u003Cli>Check the reconciliation against the range of indicated values.\u003C\u002Fli>\n\u003Cli>Check photos: the subject views your client requires, kitchen, every bath, each comp, and anything you called out as a defect.\u003C\u002Fli>\n\u003Cli>Check each commentary field fits its character limit.\u003C\u002Fli>\n\u003Cli>Check the client's standing requirements.\u003C\u002Fli>\n\u003Cli>Check license and E&O dates.\u003C\u002Fli>\n\u003Cli>Read the final value, the effective date and the signature block one last time. Then sign.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2 id=\"what-ai-shouldn-t-do-here\">What AI shouldn't do here\u003C\u002Fh2>\n\u003Cp>It's tempting to want a tool that also "fixes" the report. Be careful. A checker that rewrites your commentary to satisfy a rule, or changes an adjustment to match a pattern, is changing your analysis. The right behavior is to point and explain, then let you decide. The broader case for that line is in our pillar on \u003Ca href=\"\u002Fblog\u002Fai-appraisal-software-2026\">AI appraisal software in 2026\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Revision requests are part of why so many appraisers feel worn down; we wrote about that honestly in \u003Ca href=\"\u002Fblog\u002Fappraiser-burnout-fees-turn-times-revisions\">why appraisers are burned out\u003C\u002Fa>. You won't get to zero. But the ones that come from a missing photo or a sum that doesn't add up are worth eliminating, and you can.\u003C\u002Fp>\n\u003Cp>Carat runs those checks as you work, for \u003Ca href=\"\u002F#pricing\">one flat price with unlimited reports\u003C\u002Fa>. If you'd like to see your next report come back clean, \u003Ca href=\"\u002Fsign-in?mode=create\">create an account\u003C\u002Fa>.\u003C\u002Fp>\n",[50,53,56,59,62,65,68],{"id":51,"t":52},"the-three-kinds-of-revision-request","The three kinds of revision request",{"id":54,"t":55},"what-the-uad-3-6-compliance-rules-actually-check","What the UAD 3.6 compliance rules actually check",{"id":57,"t":58},"how-ai-powered-checks-work-in-practice","How AI-powered checks work in practice",{"id":60,"t":61},"consistency-the-second-bucket","Consistency: the second bucket",{"id":63,"t":64},"the-third-bucket-judgment-requests","The third bucket: judgment requests",{"id":66,"t":67},"a-10-minute-pre-delivery-routine","A 10-minute pre-delivery routine",{"id":69,"t":70},"what-ai-shouldn-t-do-here","What AI shouldn't do here",[],[73,111,146],{"slug":28,"title":74,"seoTitle":75,"description":76,"date":77,"updated":10,"category":11,"pillar":78,"howto":12,"keywords":79,"tags":87,"related":90,"faq":93,"words":109,"minutes":110},"AI Appraisal Software in 2026: What It Does, and What It Shouldn't","AI Appraisal Software in 2026: An Honest Guide | Carat","AI appraisal software in 2026, explained for working appraisers: what automation should handle, where AVMs fit, and why your judgment and signature stay.","2026-10-14",true,[80,21,17,81,82,83,84,85,86],"ai appraisal software","machine learning appraisal","automated valuation model","will ai replace appraisers","ai appraisal tools","appraisal software with ai","uad 3.6 ai",[23,88,25,89],"Automation","AVMs",[91,5,92],"will-ai-replace-appraisers","data-driven-adjustments-from-past-reports",[94,97,100,103,106],{"q":95,"a":96},"What is AI appraisal software?","It is report software that uses automation and statistical models to handle clerical work for the appraiser: filling public-record data, checking the report against rules, and summarizing the appraiser's own past data. The appraiser still inspects, analyzes, concludes value and signs.",{"q":98,"a":99},"Can AI write my appraisal report?","It should not. USPAP holds the appraiser responsible for the analysis and the conclusions in the report. Software can fill facts and flag errors, but the narrative, the adjustments and the value opinion need to be yours.",{"q":101,"a":102},"Is an automated valuation model the same as an appraisal?","No. An AVM is a computer model that estimates value from data without an inspection or an appraiser's analysis. An appraisal is a credentialed appraiser's opinion of value developed under USPAP.",{"q":104,"a":105},"Does the 2024 AVM quality control rule apply to appraisers?","The interagency rule, effective October 1, 2025, applies to mortgage originators and secondary market issuers that use AVMs for credit decisions. The CFPB's compliance guide says it does not cover the development of an appraisal by a certified or licensed appraiser.",{"q":107,"a":108},"What should I look for in AI tools for appraisers?","Look for automation you can check: every auto-filled value shows its source, every warning links to the field, and nothing goes into the report without your review. Avoid tools that produce a value or commentary you cannot trace.",2684,12,{"slug":29,"title":112,"seoTitle":113,"description":114,"date":115,"updated":10,"category":116,"pillar":12,"howto":12,"keywords":117,"tags":124,"related":126,"faq":128,"words":144,"minutes":145},"The AMC Revision Request Survival Guide: The 15 Most Common Asks","AMC Revision Requests: The 15 Most Common | Carat","The 15 most common AMC revision requests on appraisal reports, why each one happens, how to prevent it, and sample response language you can adapt today.","2026-10-06","appraiser-life",[14,15,118,119,120,121,122,123],"appraisal stips","how to respond to appraisal revision","appraisal revision examples","amc appraisal review","appraisal comment templates","reduce appraisal revisions",[26,24,125],"Appraiser Life",[127,5,30],"appraiser-burnout-fees-turn-times-revisions",[129,132,135,138,141],{"q":130,"a":131},"Do I have to make every change an AMC asks for?","No. You must correct real errors and address legitimate questions, but your conclusions are yours. If a request asks you to change an opinion you still believe is supported, you can explain your reasoning instead. Check your engagement terms and get legal advice for specific disputes.",{"q":133,"a":134},"Can an AMC charge me or withhold payment for revisions?","Payment terms are set by your engagement and state AMC laws, which vary. Many appraisers address revision handling and payment timing in their own terms of engagement. Check your state's rules and your agreements.",{"q":136,"a":137},"Is the 15% net and 25% gross adjustment rule still a requirement?","Not for Fannie Mae. Fannie Mae removed the 15% net and 25% gross adjustment guidelines in Selling Guide Announcement SEL-2014-16 and asks for market-supported adjustments instead. Some lenders and AMCs still use the old figures as review triggers.",{"q":139,"a":140},"How do I respond to a reconsideration of value request?","Review the new information honestly, analyze any comparables provided, and explain in writing whether and why your opinion changes. Under the GSE and FHA requirements from 2024, borrower-initiated ROVs follow a lender-managed process with a limit on the number of new comparables.",{"q":142,"a":143},"How can I reduce revision requests?","Answer the predictable questions inside the report before you deliver: comp selection, distance and date, bracketing, large adjustments, ratings, and market trends. Then run a compliance check against the GSE rules so automated findings don't turn into revisions.",1906,8,{"slug":30,"title":147,"seoTitle":148,"description":149,"date":150,"updated":10,"category":151,"pillar":12,"howto":12,"keywords":152,"tags":160,"related":163,"faq":166,"words":182,"minutes":45},"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","uad-3-6",[153,154,155,156,20,157,158,159],"uad 3.6 compliance rules","uad 3.6 fatal errors","appendix h-1 compliance rules","uad compliance api","uad 3.6 warning messages","uad 3.6 hard stops","ucdp submission summary report",[25,161,162],"Compliance","UCDP",[164,165,5],"uad-3-6-complete-guide","mismo-3-6-xml-explained",[167,170,173,176,179],{"q":168,"a":169},"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":171,"a":172},"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":174,"a":175},"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":177,"a":178},"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":180,"a":181},"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,1793082914353]