ENV files and UAD 3.6: what's actually required.

What an .env file actually is

.ENV is short for "envelope." It's the file extension a la mode's software (WinTOTAL, TOTAL, and the AppraisalPort delivery network) has used for close to two decades to package a finished appraisal report into one container file. The accreditation for that packaging standard is called AI Ready — "Appraisal Institute Ready" — a certification the Appraisal Institute grants to forms software that reads and writes that shared XML-in-an-envelope format, so that reports produced by different vendors' software could still move through the same delivery pipes.

In other words: ENV / AI Ready is a transport format — a way of shrink-wrapping a report so a delivery network (classically AppraisalPort) can move it from an appraiser's desktop to a lender or AMC's intake system. It was never a GSE dataset specification. It's the wrapper, not the contents.

What UAD 3.6 actually requires

Appendix A-1 (the UAD Delivery Specification) and Appendix H-1 (the compliance ruleset) both describe the UAD 3.6 deliverable the same way: a MISMO 3.6 XML dataset, a human-readable PDF representation of the report, and the property's images — packaged together and submitted to UCDP. There's no ENV envelope anywhere in that spec. A couple of the compliance rules make the actual package structure explicit, because the XML has to reference the other files by name:

• UAD1270  Does Not Display — "Provide the location and file name of the appraisal (e.g., \SF1Appraisal_v1.pdf)." The XML carries a pointer to the PDF sitting alongside it.
• UAD1705  Does Not Display — "Provide the file name and location of the image within the .zip file (e.g., \Images\MH1_DwellingFront.png)." Every photo lives in the ZIP too, and the XML has to name exactly where.

That's the whole shape of a UAD 3.6 delivery: one ZIP, three kinds of contents (XML, PDF, images), cross-referenced by filename. It's also a real change from how the legacy format handled photos — images used to be flattened directly into the PDF; on 3.6 they ship as their own files inside the ZIP, which is exactly what the filename-reference rules above exist to check.

Why "do I need ENV for 3.6" is still a live question

Because for the better part of twenty years, "deliver the appraisal" and "save an ENV" meant the same thing to most desktop appraisal software. AppraisalPort's intake, a lot of AMC portals, and more than a few lender LOS integrations were all built around that one file type. None of that plumbing updates itself the day a new GSE spec ships — and through the current transition window (lenders may accept UAD 2.6 or 3.6 right up to the November 2, 2026 mandatory date), some of those pipelines are legitimately still asking for the legacy format because they're legitimately still processing legacy 2.6 reports. Others are just running on old instructions nobody has updated yet. From the outside, both look identical: a portal field or a client email that says "upload your ENV."

The forms software itself adds to the confusion. Vendors that built AI Ready support into their product over the years often keep the option to export an ENV around for backward compatibility, even after they've added a 3.6-compliant ZIP export next to it. Seeing "Save as ENV" in a menu doesn't mean your client wants one.

What to actually do about it

Don't assume your delivery format based on habit, and don't assume it's uniform across your client list — it almost certainly isn't yet. Before you renew an ENV-centric plugin, a delivery add-on, or a software seat sold specifically around AppraisalPort compatibility:

• Ask each AMC, lender, and portal directly: "For orders after [date], do you want the UAD 3.6 ZIP package, or are you still on 2.6 / ENV for now?" One email per client, before the order — not after a bounce.
• Confirm what your own forms software actually exports today. "3.6-ready" marketing copy and a validated 3.6 ZIP export are not always the same claim — ask specifically whether the export passes UCDP's schema validation, not just whether the form fields exist.
• If a client portal's instructions still say "ENV," get it in writing that they want the legacy format before you deliver it — several lenders are already moving to 3.6-format delivery ahead of the November mandate, and portal copy lags real intake behavior.
• Treat the November 2, 2026 date as the deadline, not the start date. The safer planning assumption is that your busiest clients switch weeks earlier.