UAD 3.6 mandate: which pipeline files are at risk Nov 2?

The UAD 3.6 mandate puts a file at risk on November 2 if its appraisal report has not been initially submitted to the Uniform Collateral Data Portal before that date, because the cutover follows the submission date, not when the loan was applied for. To find which of your in-flight files are exposed:

UAD stands for Uniform Appraisal Dataset, the standard format for appraisal data that lenders submit to the GSEs. This post is an operations guide for a sales-led loan team, not appraisal-form instruction or compliance advice. Your compliance and appraisal desk owns the form itself. Your job as the person running the pipeline is coordination, and that is where files get lost.

What changes on November 2 and why the submission date is what matters

Beginning November 2, 2026, every new appraisal report initially submitted to UCDP must use UAD 3.6, and legacy UAD 2.6 submissions are rejected with a Not Successful status, per Freddie Mac's UAD and Forms Redesign FAQ. The same FAQ makes clear the mandate is based on the initial UCDP submission date of each report, not the loan application date or the appraisal's effective date.

That one detail is why your pipeline is exposed. A file you took in September, with an appraisal ordered in October, is still at risk if that report does not hit the portal until November. Loans already in process can cross the boundary, and HousingWire reports that a UAD 2.6 appraisal not submitted before the mandate cannot simply be entered into the portal afterward as a new submission. So ordering a 2.6 in October protects nothing on its own. What protects the file is the submission landing before November 2.

A September 30 policy exception exists, but read it carefully before you lean on it. MBA NewsLink notes the exception is request-only per GSE and the November 2 date has not moved. Approved sellers granted an exception may keep submitting UAD 2.6 through May 19, 2027. The part that matters for a broker: only lenders that sell loans directly to the GSEs request the exception. National Mortgage Professional reports that brokers generally follow the UAD requirements of the wholesale partner or investor receiving the loan. You do not get to pick your own format. Each partner picks theirs, and you inherit it per deal.

The two coordination jobs that leak without a system

The mandate itself is simple to understand. What leaks is the coordination around it, because the work spreads across many files and many partners and depends on a person remembering to check each one. There are two jobs, and both fail quietly.

Confirming each wholesale lender's accepted format in writing

The first job is asking every wholesale lender and investor you use whether they requested the exception and which format they will accept after November 2, and getting that answer in writing. NAMB recommends exactly this step in its broker guide. The reason to put it in writing is that your partners will not all answer the same way.

National Mortgage Professional reports that wholesale lenders adopted different rules for appraisal transfers, loan product changes, and reporting formats. So one partner may accept 2.6 under an exception while another requires 3.6 on anything submitted November 2 or later, at the same time, on deals sitting side by side in your pipeline. If you confirm once and file the answer in your head, you have no record when a deal moves to a different partner halfway through, and no way to hand that context to whoever picks up the file next.

Tracking which in-flight files owe a submission before the boundary

The second job is knowing, at any moment, which active files have not yet hit UCDP and could cross November 2. This is the one that surfaces at closing if nobody owns it. The same National Mortgage Professional piece notes that a loan product change during processing can trigger the need for a new appraisal, and a transferred report may face additional requirements. Any of those can push a submission past the cutover on a file you thought was fine a week ago.

A one-time list is not enough. The view has to update as files move, as products change, and as partners answer. A weekly meeting where someone reads down a spreadsheet is how a file slips: the spreadsheet is a snapshot, and the deadline does not wait for Monday's meeting. If you have ever watched a handoff between intake and processing drop context, this is the same leak, with a hard date attached.

What it costs you if the timing problem surfaces at closing

The cost of missing one of these is not abstract, so it is worth naming item by item what goes wrong when an appraisal-timing problem is not caught until the end.

None of this is appraisal advice, and your appraisal desk owns the form and the exception request. The point is that the coordination failure costs money, time, and a partner relationship, and it costs them at the worst possible moment.

Manual tracking versus a system that nudges before the deadline

Most teams run this on a spreadsheet and a group text, and for a handful of files that works. The problem is that the method depends on a human remembering to re-check every file against a moving set of partner rules. The difference in practice:

This is the kind of per-deal commitment-tracking SalesOS is built for: it keeps your CRM and loan origination system data in sync, tracks what each deal owes at each stage, and nudges the owner or partner before a deadline passes, so an appraisal-timing problem shows up weeks early instead of at the closing table. It works inside the tools you already run and follows the rules your team sets. See how AI Cofounder works if you want the mechanics.

A tracked process also solves the question nobody on page one answers: how do you avoid this becoming a weekly scramble. You avoid it by making the pipeline visible on its own, so the at-risk files surface without anyone having to remember to go look. That is the same problem as seeing your pipeline across four systems without a status meeting, just with a November 2 line drawn through it.

FAQ

Which files in my pipeline are at risk on November 2?

Any active file whose appraisal report has not been initially submitted to UCDP before November 2 is at risk, because the mandate follows the submission date, not the application date. A file applied for in September with an appraisal ordered in October is still exposed if that report does not reach the portal until November.

Does ordering a 2.6 appraisal in October protect the file?

Ordering a UAD 2.6 appraisal in October does not protect the file on its own. What protects it is the appraisal report being initially submitted to UCDP before November 2; a 2.6 report submitted on or after the cutover is rejected, and HousingWire reports it cannot be entered into the portal afterward as a new submission.

Why are my wholesale partners on different formats at the same time?

Your wholesale partners can be on different formats because only lenders that sell directly to the GSEs can request the exception, and each one decides independently. National Mortgage Professional reports that wholesale lenders adopted different rules for transfers, product changes, and formats, so as a broker you follow each partner's requirement per deal, not one rule across your whole pipeline.

Can automation help without making a mess in my partners' systems?

Automation can track which files owe a submission and nudge the right person before a deadline, working inside the CRM and systems you already use and following the rules your team sets. It does not make appraisal decisions, request exceptions, or give borrowers cost advice; your appraisal and compliance desks own that, and the automation handles the remembering and the follow-up around it.

You run a pipeline where a few in-flight files could cross November 2 and the partner-format answers live in scattered emails and someone's memory. If you want those at-risk files surfaced on their own and the right person nudged before a deadline passes, Book a Demo: SalesOS follows up with every lead in your own voice, keeps your CRM in sync, and shows you where every deal stands. See it working on a pipeline like yours.