[{"data":1,"prerenderedAt":188},["ShallowReactive",2],{"blog-mismo-3-6-xml-explained":3},{"post":4,"related":77,"pillar":78},{"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":76},"mismo-3-6-xml-explained","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","2026-10-25","uad-3-6",false,[14,15,16,17,18,19,20,21],"mismo 3.6","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",[23,24,25],"MISMO 3.6","UAD 3.6","XML",[27,28,29],"uad-3-6-complete-guide","uad-3-6-compliance-rules-fatal-warning","uad-3-6-readiness-checklist",[31,34,37,40,43],{"q":32,"a":33},"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":35,"a":36},"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":38,"a":39},"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":41,"a":42},"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":44,"a":45},"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,7,[49,50],"\u003Cp>If you've ever opened an appraisal export and seen a wall of angle brackets, you've met XML. Under UAD 2.6 you could ignore it: your software made a MISMO 2.6 file in the background, glued it to the PDF and you never thought about it again. Under UAD 3.6 you can still avoid editing it, but MISMO 3.6 XML is now the report. The PDF is a picture of it, and the GSEs' compliance rules read the XML, not your PDF. This guide explains what's in the file in plain terms, so the next time a lender forwards a Fatal message you'll know what it's talking about.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key takeaways\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>MISMO 3.6 is the data standard. UAD 3.6 is the GSEs' appraisal dataset built on it.\u003C\u002Fli>\n\u003Cli>The deliverable is a zip: one XML, one matching PDF and an Images folder, 60 MB or less.\u003C\u002Fli>\n\u003Cli>The XML holds every value you entered, labeled with a standard name. The PDF must match it.\u003C\u002Fli>\n\u003Cli>Images are files in the zip. The XML only points to them.\u003C\u002Fli>\n\u003Cli>Compliance rules and UCDP read the XML. A perfect-looking PDF can still fail.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"what-mismo-is-and-why-version-3-6\">What MISMO is, and why version 3.6\u003C\u002Fh2>\n\u003Cp>MISMO, the Mortgage Industry Standards Maintenance Organization, publishes the data standards lenders, investors and vendors use to exchange mortgage data. Its standards define names for things (a property's address, a loan amount, a condition rating) so that every system means the same thing by them.\u003C\u002Fp>\n\u003Cp>UAD 2.6 was built on an older MISMO version, 2.6. For UAD 3.6, Fannie Mae and Freddie Mac moved to the MISMO 3.6 reference model. The sample files in the GSEs' Appendix D-1 declare it right at the top: \u003Ccode>MISMOReferenceModelIdentifier="3.6.0366"\u003C\u002Fcode>. The GSEs also publish a schema, a set of rules for what a valid file looks like, as part of the UAD 3.6 documents 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>.\u003C\u002Fp>\n\u003Cp>You don't need to know any of this to appraise. You need to know one thing: the GSEs now read your appraisal as data, field by field, and the file that carries that data is the XML.\u003C\u002Fp>\n\u003Ch2 id=\"what-s-in-the-zip\">What's in the zip\u003C\u002Fh2>\n\u003Cp>Appendix B-1, the URAR Implementation Guide, describes the package. One zip per appraisal, not more than 60 MB:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Smith_123Main\u002F\n  Smith_123Main.xml     the UAD 3.6 data, UTF-8\n  Smith_123Main.pdf     the report, rendered from the same data\n  Images\u002F\n    DwellingFront.jpg\n    DwellingRear.jpg\n    Street.jpg\n    Comp1.jpg\n    ...\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The rules for each piece, from B-1:\u003C\u002Fp>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Piece\u003C\u002Fth>\u003Cth>Requirements\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>XML\u003C\u002Ftd>\u003Ctd>Well-formed per the MISMO 3.6 reference model, UTF-8. No images and no PDF embedded in it\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>PDF\u003C\u002Ftd>\u003Ctd>Must match the content of the XML. Must be a first-generation PDF produced by the appraiser's software. Not password protected, not encrypted, no DRM\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>Images folder\u003C\u002Ftd>\u003Ctd>Must be named \u003Ccode>Images\u003C\u002Fcode> (case sensitive). Unique file names. Every image referenced at least once in the XML. Allowed types set by the spec (for example JPEG and PNG)\u003C\u002Ftd>\u003C\u002Ftr>\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>"First-generation" is worth a moment. It means the PDF comes straight from your software. A PDF you printed, scanned, edited in Acrobat or reassembled from pieces isn't first-generation. If you need to change something, change it in the report and rebuild the package.\u003C\u002Fp>\n\u003Cblockquote class=\"bl-callout watch-out\">\u003Cp>\u003Cstrong>Watch out:\u003C\u002Fstrong> Don't rename or re-zip the package by hand. If the XML points to \u003Ccode>Images\\Comp1.jpg\u003C\u002Fcode> and you renamed the file to \u003Ccode>comp 1.jpg\u003C\u002Fcode>, the image is missing as far as the XML is concerned. Rebuild from your software instead.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2 id=\"reading-the-xml-without-being-a-developer\">Reading the XML without being a developer\u003C\u002Fh2>\n\u003Cp>Open a UAD 3.6 XML file in any text editor and you'll see nested labels. Each label is called an element. Elements contain other elements, the way a folder contains folders. At the top is \u003Ccode>MESSAGE\u003C\u002Fcode>. Deep inside are the parts that matter to you: the properties (the subject and each comp), the valuation, the parties and the images.\u003C\u002Fp>\n\u003Cp>Here's a real piece from the GSE's own single-family sample (Appendix D-1, SF1), lightly trimmed. It's the subject's area breakdown:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-xml\"><PROPERTY_UNIT_AREA>\n  <UnitAboveGradeUnfinishedAreaMeasure AreaUnitOfMeasureType="SquareFeet">0<\u002FUnitAboveGradeUnfinishedAreaMeasure>\n  <UnitBelowGradeUnfinishedAreaMeasure AreaUnitOfMeasureType="SquareFeet">230<\u002FUnitBelowGradeUnfinishedAreaMeasure>\n  <UnitNonStandardAboveGradeFinishedAreaMeasure AreaUnitOfMeasureType="SquareFeet">0<\u002FUnitNonStandardAboveGradeFinishedAreaMeasure>\n  <UnitNonStandardBelowGradeFinishedAreaMeasure AreaUnitOfMeasureType="SquareFeet">0<\u002FUnitNonStandardBelowGradeFinishedAreaMeasure>\n  <UnitStandardAboveGradeFinishedAreaMeasure AreaUnitOfMeasureType="SquareFeet">3002<\u002FUnitStandardAboveGradeFinishedAreaMeasure>\n  <UnitStandardBelowGradeFinishedAreaMeasure AreaUnitOfMeasureType="SquareFeet">1300<\u002FUnitStandardBelowGradeFinishedAreaMeasure>\n<\u002FPROPERTY_UNIT_AREA>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Read it like a sentence: 3,002 square feet of standard finished area above grade, 1,300 finished below grade, 230 unfinished below grade, and zero nonstandard area, above or below. Notice the zeros. They're written out on purpose. Compliance rules UAD1187 and UAD1484 are Fatal if the nonstandard area fields are missing, "even if the value is 0."\u003C\u002Fp>\n\u003Cp>And here's how the sample refers to a photo:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-xml\"><IMAGE>\n  <ImageCategoryType>DwellingFront<\u002FImageCategoryType>\n  <ImageFileLocationIdentifier>\\\\Images\\SF1_DwellingFront.png<\u002FImageFileLocationIdentifier>\n  <MIMETypeIdentifier>image\u002Fpng<\u002FMIMETypeIdentifier>\n<\u002FIMAGE>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The photo isn't in the XML. The XML says: there's a dwelling front photo, here's where it is in the zip, and here's its file type. That \u003Ccode>ImageCategoryType\u003C\u002Fcode> is what lets the rules check that the right photos exist. Rule UAD1274 is Fatal if the required subject photos aren't included. Rule UAD1275 is Fatal if a sales comparable used in the valuation has no photo.\u003C\u002Fp>\n","\u003Ch2 id=\"why-the-xml-matters-more-than-the-pdf-now\">Why the XML matters more than the PDF now\u003C\u002Fh2>\n\u003Cp>Under UAD 2.6, reviewers mostly read the PDF, and the XML carried a subset of the data. Under UAD 3.6, it flips. The XML carries everything, and three things read it before a person does:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>The schema.\u003C\u002Fstrong> The GSE schema (XSD) defines which elements can appear, in what order and with what kinds of values. An invalid file can fail before any rule runs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The compliance rules.\u003C\u002Fstrong> Appendix H-1 lists 728 rules, 592 Fatal and 136 Warning, written against XML element names. Rule logic reads like "If SketchExistsIndicator = true and MeasurementStandardPublisherType is not provided." That's XML talk for: you included a sketch but didn't say which measurement standard you used.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The GSE models.\u003C\u002Fstrong> Collateral Underwriter and Loan Collateral Advisor score from the data.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>This is why the \u003Ca href=\"\u002Fblog\u002Fuad-3-6-compliance-rules-fatal-warning\">728 UAD 3.6 compliance rules\u003C\u002Fa> matter so much. The rules don't care how your PDF looks. They care whether the right elements exist with the right values.\u003C\u002Fp>\n\u003Ch2 id=\"common-xml-problems-and-what-they-mean-in-plain-english\">Common XML problems and what they mean in plain English\u003C\u002Fh2>\n\u003Cp>Some rule messages say "For assistance with this message, contact the appraisal software vendor." Those are usually about how the file was written, not about your appraisal. Others are about what you entered. Here's how to tell them apart:\u003C\u002Fp>\n\u003Cdiv class=\"bl-table\">\u003Ctable>\u003Cthead>\u003Ctr>\u003Cth>Message you see\u003C\u002Fth>\u003Cth>What it usually means\u003C\u002Fth>\u003Cth>Who fixes it\u003C\u002Fth>\u003C\u002Ftr>\u003C\u002Fthead>\u003Ctbody>\u003Ctr>\u003Ctd>"Provide the interior condition rating."\u003C\u002Ftd>\u003Ctd>You left a required field empty\u003C\u002Ftd>\u003Ctd>You\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>"Provide ... even if the value is 0."\u003C\u002Ftd>\u003Ctd>A field needs an explicit zero or "none"\u003C\u002Ftd>\u003Ctd>You\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>"The 'Net Adjustment Total' does not equal the sum of the individual adjustments."\u003C\u002Ftd>\u003Ctd>Grid math is off\u003C\u002Ftd>\u003Ctd>You or your software\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>"The latitude must be a value between -90 and 90 with at least 5 digits of precision..."\u003C\u002Ftd>\u003Ctd>Coordinates written in the wrong format\u003C\u002Ftd>\u003Ctd>Software, usually\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>"One or more additional row labels are not identical for one or more properties."\u003C\u002Ftd>\u003Ctd>Custom grid rows labeled differently across comps\u003C\u002Ftd>\u003Ctd>Software, sometimes you\u003C\u002Ftd>\u003C\u002Ftr>\u003Ctr>\u003Ctd>"External Depreciation ... must be delivered as a positive number in the UAD XML."\u003C\u002Ftd>\u003Ctd>A sign problem in how the number was written\u003C\u002Ftd>\u003Ctd>Software\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 UCDP message with a rule ID like UAD1461, look the ID up in Appendix H-1. The row gives the message, the logic and the section. It turns a vague complaint into a specific field.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch2 id=\"what-good-software-does-with-the-xml\">What good software does with the XML\u003C\u002Fh2>\n\u003Cp>You shouldn't have to think about elements and namespaces. Your software should:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Write the XML from your entries, using the GSE schema's element order.\u003C\u002Fli>\n\u003Cli>Validate the XML against the GSE schema every time it builds the package.\u003C\u002Fli>\n\u003Cli>Render the PDF from the same data, so the two always match.\u003C\u002Fli>\n\u003Cli>Name and reference images correctly, and refuse to build if a referenced image is missing.\u003C\u002Fli>\n\u003Cli>Check the H-1 rules while you work and take you to the field when one fires.\u003C\u002Fli>\n\u003Cli>Produce the zip to B-1's folder structure.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Carat does each of those. It writes MISMO 3.6 XML validated against the GSE XSD on every build, renders the URAR PDF to the Appendix E style guide, and packages the UCDP-ready zip with the Images folder per Appendix B-1. Its AI-powered readiness checks evaluate hundreds of the H-1 rules locally while you type, each one linked to the field. It doesn't submit to UCDP or sign anything for you. You or your client upload the zip. See \u003Ca href=\"\u002F#pricing\">pricing\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"your-old-mismo-2-6-files-are-still-valuable\">Your old MISMO 2.6 files are still valuable\u003C\u002Fh2>\n\u003Cp>If you've been appraising for a while, you have years of MISMO 2.6 XML files sitting in your old software, or you can export them. Most desktop programs, including ACI and TOTAL, can export MISMO 2.6 GSE XML, and ClickFORMS files can be read directly. Those files are structured data about every subject and comp you've ever worked on.\u003C\u002Fp>\n\u003Cp>That makes them a comps history and an adjustment record, not just a workfile obligation. Carat's legacy import takes a zip of thousands of them and turns them into a searchable history, with median adjustment rates by town and price tier drawn from your own reports. Anything unclear goes to a review queue instead of into a report. More on that in \u003Ca href=\"\u002Fblog\u002Fdata-driven-adjustments-from-past-reports\">your past reports are a data set\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"where-to-go-next\">Where to go next\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>For the full picture of the change, read \u003Ca href=\"\u002Fblog\u002Fuad-3-6-complete-guide\">the complete UAD 3.6 guide\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>To check that your package is right before your first live order, use \u003Ca href=\"\u002Fblog\u002Fuad-3-6-readiness-checklist\">the UAD 3.6 readiness checklist\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>To understand the rules that read your XML, see \u003Ca href=\"\u002Fblog\u002Fuad-3-6-compliance-rules-fatal-warning\">Fatal vs. Warning compliance rules\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you'd like to see your own report as MISMO 3.6 XML, \u003Ca href=\"\u002Fsign-in?mode=create\">create an Carat account\u003C\u002Fa>, build a practice report and open the zip.\u003C\u002Fp>\n",[52,55,58,61,64,67,70,73],{"id":53,"t":54},"what-mismo-is-and-why-version-3-6","What MISMO is, and why version 3.6",{"id":56,"t":57},"what-s-in-the-zip","What's in the zip",{"id":59,"t":60},"reading-the-xml-without-being-a-developer","Reading the XML without being a developer",{"id":62,"t":63},"why-the-xml-matters-more-than-the-pdf-now","Why the XML matters more than the PDF now",{"id":65,"t":66},"common-xml-problems-and-what-they-mean-in-plain-english","Common XML problems and what they mean in plain English",{"id":68,"t":69},"what-good-software-does-with-the-xml","What good software does with the XML",{"id":71,"t":72},"your-old-mismo-2-6-files-are-still-valuable","Your old MISMO 2.6 files are still valuable",{"id":74,"t":75},"where-to-go-next","Where to go next",[],[78,121,155],{"slug":27,"title":79,"seoTitle":80,"description":81,"date":82,"updated":10,"category":11,"pillar":83,"howto":12,"keywords":84,"tags":94,"related":97,"faq":100,"words":119,"minutes":120},"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,[85,86,87,88,89,90,91,92,93,14],"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","uad 3.6 compliance rules",[24,95,23,96],"URAR","Compliance",[98,99,29],"uad-3-6-deadline-timeline","uad-3-6-replaces-1004-1073-1025-2055",[101,104,107,110,113,116],{"q":102,"a":103},"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":105,"a":106},"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":108,"a":109},"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":111,"a":112},"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":114,"a":115},"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":117,"a":118},"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":122,"seoTitle":123,"description":124,"date":125,"updated":10,"category":11,"pillar":12,"howto":12,"keywords":126,"tags":134,"related":136,"faq":138,"words":154,"minutes":47},"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",[93,127,128,129,130,131,132,133],"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",[24,96,135],"UCDP",[27,5,137],"ai-catches-amc-revision-requests",[139,142,145,148,151],{"q":140,"a":141},"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":143,"a":144},"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":146,"a":147},"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":149,"a":150},"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":152,"a":153},"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,{"slug":29,"title":156,"seoTitle":157,"description":158,"date":159,"updated":10,"category":11,"pillar":12,"howto":83,"keywords":160,"tags":169,"related":171,"faq":173,"words":186,"minutes":187},"UAD 3.6 Readiness Checklist: 20 Things to Do Before You Submit","UAD 3.6 Readiness Checklist: 20 Steps | Carat","A UAD 3.6 readiness checklist for appraisers: 20 practical steps covering clients, software, the zip package, compliance rules, sketches and your workfile.","2026-10-13",[161,162,163,164,165,166,167,168],"uad 3.6 readiness checklist","uad 3.6 checklist","prepare for uad 3.6","uad 3.6 preparation appraisers","uad 3.6 transition","uad 3.6 ready","redesigned urar checklist","uad 3.6 training",[24,170,95],"Checklist",[27,28,172],"switch-appraisal-software-without-losing-comps",[174,177,180,183],{"q":175,"a":176},"How do I prepare for UAD 3.6 as an appraiser?","Confirm each client's format and delivery method, make sure your software produces the full UAD 3.6 zip, read the URAR Reference Guide for your common property types, rework your comment library, and build at least one practice report before your first live order.",{"q":178,"a":179},"Do I need special training for UAD 3.6?","There is no required GSE training or credential for appraisers. The GSEs publish free resources, including the URAR Reference Guide and sample reports, and many education providers offer courses.",{"q":181,"a":182},"How long does it take to get ready for UAD 3.6?","If your software is already set up, a focused day is enough to build a practice report and map your comments. Expect your first live reports to take longer than a 1004 did.",{"q":184,"a":185},"What should I ask my AMCs about UAD 3.6?","Ask whether they will order UAD 3.6 on November 2, 2026 or are working under a lender's policy exception, whether their portal accepts the UAD 3.6 zip, and whether they have any added requirements beyond the GSE rules.",1486,6,1793082914901]