How to Transition to UAD 3.6 on Mercury Network®

Key Message/s: The industry is moving away from static form numbers (like the 1004) toward a dynamic, data-centric process. This is an industry-driven change, its not optional and not Mercury-only. UAD 3.6 is a structural shift, not a UI refresh.

• UAD 3.6 introduces a new data structure (MISMO 3.6) and modernized submission approach.

• Property characteristics now drive the appraisal report and scope of work rather than a specific form number.

• Appraisals will no longer be .ENV or MISMO XML files. They must be delivered as a UAD 3.6 Zip file containing the MISMO 3.6 XML, the appraisal PDF, and photos.

• Mercury Network® will continue to support legacy forms (current state) alongside the new UAD 3.6 flow.

What’s Changing in Mercury Network®

• The new dynamic Appraisal URAR moves us from a form-centric fulfillment process to a data-centric process, where data that describes the subject property drives the appraisal report, not a form.

• Many of the features and functions in our valuation platforms today differentiate behavior by appraisal form number.

• The MISMO XML structure, which contains all appraisal data points, is changing from version 2.6 to version 3.6, resulting in a new set of data points and corresponding validations. The UAD 3.6 accepted appraisal file format will not be an .ENV or MISMO XML file, but instead a UAD 3.6 Zip file that contains MISMO 3.6 XML, photos, and the appraisal PDF.

• Each platform will be integrated with the new UCDP portal for UAD 3.6.

• Our automated rules and review solution will be redesigned for UAD 3.6 appraisals.

Note: UAD 3.6 updates do not impact legacy forms (current state) process flow. Mercury will continue to support the legacy forms process flow as it is today.

Related articles/Resources

Mercury Network® Valuation Modernization migration guide:
Your go-to location for ongoing resources and a live FAQ document that we update as new questions arise.

Mercury Network® Valuation Modernization client resource hub:
General information for all things Valuation Modernization on Mercury Network®.

Important Callouts:

• This is an industry shift: UAD 3.6 is a required move from form-centric appraisals (e.g., “1004”) to a data-centric, MISMO 3.6-based process.

• New delivery package: UAD 3.6 appraisals are delivered as a ZIP containing MISMO 3.6 XML + appraisal PDF + photos (legacy forms continue in parallel).

Facilitator Notes:

• “UAD 3.6 changes what the appraisal is (data set) and how it’s delivered—not just screens in Mercury.”

• Ask learners to name one thing that stays the same (legacy forms still supported) and one thing that changes (ZIP + MISMO 3.6).

Knowledge Check:

• Q1: Multiple choice: UAD 3.6 primarily shifts the industry from: (A) data-centric to form-centric (B) form-centric to data-centric (C) manual to automated ordering

  • Answer: (B) form-centric to data-centric.

• Q2: Short answer: What three items are included in the UAD 3.6 ZIP delivery package?

  • Answer: MISMO 3.6 XML + appraisal PDF + photos (in a ZIP package).

• Q3: True/False: UAD 3.6 updates eliminate legacy forms in Mercury immediately.

  • Answer: False.

FAQs:

• Is UAD 3.6 optional? No—this is an industry-driven requirement (not Mercury-only).

• Does UAD 3.6 replace legacy forms immediately? No—Mercury will support legacy forms alongside the new UAD 3.6 flow.

• What does “data-centric” mean? Property characteristics and structured data drive the report and scope of work, rather than selecting a form number.

• What is MISMO 3.6? The updated appraisal data structure/version used for UAD 3.6 submissions and validations.

• What is delivered in the new UAD 3.6 appraisal file? A ZIP package containing MISMO 3.6 XML, the appraisal PDF, and photos.

Key Message: UAD 3.6 introduces “Products” derived primarily from Property Valuation Method and Property Type (plus additional characteristics). Products replace forms to improve consistency and automation. As we transition away from appraisal form numbers, we will rely instead on several property characteristics to define the scope of work. To achieve this, we have updated the data points captured at order creation and added new APIs to support additional features such as Property Details Collaboration.

• UAD 3.6 introduces a new data structure (MISMO 3.6) and modernized submission approach.

• Property characteristics now drive the appraisal report and scope of work rather than a specific form number.

• Appraisals will no longer be .ENV or MISMO XML files. They must be delivered as a UAD 3.6 Zip file containing the MISMO 3.6 XML, the appraisal PDF, and photos.

• Mercury Network® will continue to support legacy forms (current state) alongside the new UAD 3.6 flow.

Key Message: To support UAD 3.6 orders, we have designed a set of "Products" to provide clients with a baseline to start from, like the list of form types/products you use today for legacy forms.

Two of the primary UAD 3.6 data points —“Products” derived primarily from Property Valuation Method and Property Type (plus additional characteristics). —serve as the basis for our UAD 3.6 appraisal product list. This list also includes the Completion Report and Restricted Appraisal Update reports.

Examples include:

• Desktop / Exterior / Hybrid / Traditional Appraisal by property type (Single Family, Condo, Manufactured Home, etc.).

• Completion Report and Restricted Appraisal Update (as child orders).

Callout: Parent/Child linkage

We have also introduced a new concept that allows us to link orders for the same loan together. When a second order is placed for the same loan (a second appraisal for a jumbo loan or a Completion report, for example), customers will provide the Mercury platform with the Tracking ID or Tracking Number for the first “parent order”. This enables Mercury to connect these orders so they are all visible in one place during UCDP submission

LOS API - Ready in UAT

There are several components involved in this process (order placement, order updates, communication between the LOS and the platform throughout the lifecycle, and the new product collaboration feature, among others). An updated API guide is now available, highlighting the primary areas of change:

Important Callouts:

• Products replace forms: UAD 3.6 uses standardized Products (derived primarily from Property Valuation Method + Property Type + additional characteristics) instead of selecting legacy form numbers.

• Baseline product list + linkage: Mercury provides a baseline product list (e.g., Desktop/Exterior/Hybrid/Traditional by property type) and supports parent/child linkage (e.g., Completion/Restricted Update reports) using the parent order Tracking ID/Number.

Facilitator Notes:

• Talk track: “In legacy you pick a form; in UAD 3.6 you enter property data and Mercury derives the right product.”

• Use one scenario (e.g., Single Family + Desktop) and ask learners to identify the likely product; then ask when a child order (Completion/Update) would be linked to the parent.

Knowledge Check:

• Q1: Multiple choice: In UAD 3.6, products are derived primarily from: (A) Form/type (B) Valuation method + property type (C) Loan purpose + occupancy

  • Answer: (B) Valuation method + property type.

• Q2: Short answer: What identifier is used to link a child order (e.g., Completion/Update) to the parent order?

  • Answer: The parent order’s Tracking ID/Tracking Number.

• Q3: Scenario: A user says “I can’t find 1004.” What is the correct explanation?

  • Answer: In UAD 3.6 you don’t select form numbers; Mercury derives the correct product from the entered property data (valuation method + property type + characteristics).

FAQs:

• What is a “Product” in UAD 3.6? A standardized appraisal scope/category derived from property data (primarily valuation method + property type) rather than a legacy form number.

• Where do the available products come from? Mercury provides a baseline list to start from (similar to the form/type list in legacy) and organizations can align to it as they transition.

• Are Completion/Restricted Update reports part of the product list? Yes—these are supported products, often placed as child orders tied to a parent loan/order.

• How are multiple orders for the same loan connected? By providing the parent order’s Tracking ID/Tracking Number when placing the related (child) order.

• Do integrations change? Yes—new/updated APIs support additional UAD 3.6 fields and workflows; the updated API guide highlights key changes.

Key Message: When placing a manual order, Mercury users will now select whether the order pertains to a legacy form or a UAD 3.6 URAR/Completion Report/Update Report.

On Secure: To place a UAD 3.6 order, users should choose Residential Appraisal. Alternatively, select– Legacy Forms for legacy.

On VMP Client: To place a UAD 3.6 order, users should choose Appraisal URAR. Alternatively, select Legacy Form displays the existing manual form for placing a legacy appraisal order.

What’s different on the UAD 3.6 order form?

Key Message: When Residential Appraisal/ Appraisal URAR is selected, a new order form will appear with additional fields needed to place your order. These new UAD 3.6 fields are designed to outline the scope of work as we transition away from legacy appraisal forms.

Few important changes:

• There is no Form/type selection in the Assignment Information section. For UAD 3.6 orders, the product is derived from the Valuation Assignment Method and Property Type fields located in the Property Information section. Standard UAD 3.6 products are listed at the beginning of this document.

• There are several New fields added to the order form to describe property characteristics, including (non exhaustive):

  • Prop Attachment

  • Property Type

  • Living Unit Excluding ADU

  • Property Valuation Method

  • Project Legal Structure

  • ADU Count

  • Construction Method

  • Rent Schedule Indicator

  • PUD Indicator

  • Land Owned in Common Indicator

  • Property Usage

  • Order Type

  • Mortgage Type

  • Valuation Assignment Type

  • Parent Tracking Number

Form view for Secure:

Form view for VMP Client:

Fields removed/renamed vs legacy

Key Message: There are also several fields present on the legacy forms order form but absent from the UAD 3.6 Residential Appraisal/Appraisal URAR order form. Several of these fields are replaced with fields that house similar information.

Legacy-only fields not present on UAD 3.6 order form include:

• Form/type

• Loan Type

• Loan Purpose

• Prop Type

• Occupancy

VMP Client note:
Order Type has been renamed to Order Mode on the Appraisal URAR order form. There is a new field called Order Type, which captures different information.

Related article/s

How to Place UAD 3.6 Order in Mercury Network® (Secure)
How to Configure Client Group Profiles in Mercury Network® (Secure)
How to Place a UAD 3.6 Residential Order Form in Mercury Network® (Client)

Important Callouts:

• First choice is legacy vs UAD 3.6: Manual ordering now starts by selecting whether you’re placing a Legacy Forms order or a UAD 3.6 order (Residential Appraisal/Appraisal URAR).

• No Form/Type on UAD 3.6 orders: The product is derived from Valuation Assignment Method and Property Type (plus additional characteristics), so users shouldn’t look for a “1004/70” style selection.

Facilitator Notes:

• Demo both paths quickly: (1) Legacy Forms (existing manual form) vs (2) UAD 3.6 (new form with added property characteristics).

• Call out UI naming differences: Secure uses Residential Appraisal; VMP Client uses Appraisal URAR. Also note VMP Client rename: Order Mode (formerly Order Type), and the new Order Type field captures different info.

Knowledge Check:

• Q1: Multiple choice: On Secure, which selection starts a UAD 3.6 order? (A) Legacy Forms (B) Residential Appraisal (C) Form/Type

  • Answer: (B) Residential Appraisal.

• Q2: True/False: The UAD 3.6 manual order form includes a Form/Type selection to choose 1004 vs 70.

  • Answer: False.

• Q3: Short answer: Name two UAD 3.6 fields used to derive the product on the manual order form.

  • Answer: Valuation Assignment Method and Property Type (plus additional characteristics).

FAQs:

• How do I place a UAD 3.6 order vs a legacy order? Choose the UAD 3.6 option (Residential Appraisal/Appraisal URAR) for UAD 3.6; choose Legacy Forms for legacy.

• Why don’t I see Form/Type on the UAD 3.6 manual order form? UAD 3.6 derives the product from valuation method + property type + characteristics, rather than selecting a form number.

• Which fields were removed compared to legacy? Legacy-only fields like Form/Type, Loan Type, Loan Purpose, Prop Type, and Occupancy are not present on the UAD 3.6 order form.

• Why do I see more fields on the UAD 3.6 order form? Additional property characteristic fields are required to define scope of work and support automation/workflows.

• Why does Order Type look different in VMP Client? In VMP Client, “Order Type” was renamed to Order Mode, and a new “Order Type” field was added that captures different information.

Key Message: Fee management in Mercury Network® has been upgraded, allowing users with appropriate permissions to create and manage complex fee plans directly in the user interface. At this time, the new module is used only to manage UAD 3.6 fee plans; however, it is on the roadmap to extend the module to manage legacy form fees as well. These plans will be handled separately to accommodate distinct configuration data points for each. Clients will establish UAD 3.6 fee plans using a forms matrix that maps legacy forms to a specific set of UAD 3.6 data points.

• Clients establish UAD 3.6 fee plans using a forms matrix mapping from legacy forms to UAD 3.6 data points.  

• Fee plans support base fees + add-ons; add-ons can include Rush, Construction Method Type, PUD, Land Owned in Common, ADU count, Rent Schedule, Mortgage Type, Property Usage, Valuation Assignment Type, Property Characteristics.

Related article/s
Mercury Network® UAD 3.6 Configuration - Appendix A

Related article/s

• Understanding the Fees Module in Mercury Network®

• How to Create & Manage Vendor Fee Plans in Mercury Network®

• Mercury Network® UAD 3.6 Fee Templates

• How to Create & Manage Fee Plan Value Tiers in Mercury Network®

• How to Create & Manage Vendor Fee Plans in Mercury Network®

• How to Create & Manage Vendor Exception Fee Plans in Mercury Network®

• How to Create & Manage Client Price Plans in Mercury Network®

• How to Create & Manage Client Exception Price Plans in Mercury Network®

• Mercury Network® UAD 3.6 Configuration - Appendix B

• Mercury Network® UAD 3.6 Configuration - Appendix C

Important Callouts:

• UAD 3.6 only (for now): The upgraded Fees module currently manages UAD 3.6 fee plans; legacy fee management remains separate until the roadmap expands.

• Forms-to-data mapping: UAD 3.6 fee plans are built using a forms matrix that maps legacy forms to UAD 3.6 data points (then adds base fees + add-ons).

Facilitator Notes:

• Show where fee configuration lives and emphasize the separation: UAD 3.6 fees in Preferences → Fees; legacy fees stay in the current location.

• When learners ask “Why so many add-ons?”, tie add-ons back to measurable UAD 3.6 characteristics (e.g., ADU Count, Construction Method, Property Usage).

Knowledge Check:

• Q1: Multiple choice: The upgraded Fees module is used today to manage: (A) Legacy form fee plans (B) UAD 3.6 fee plans (C) Both legacy and UAD 3.6 fee plans

  • Answer: (B) UAD 3.6 fee plans

• Q2: Short answer: What two components typically make up a UAD 3.6 fee plan in Mercury?

  • Answer: A base fee plus add-ons (e.g., rush, ADU count, construction method, etc.).

• Q3: Short answer: Why do customers use a “forms matrix mapping” when establishing UAD 3.6 fee plans?

  • Answer: To map familiar legacy forms to the UAD 3.6 data points used to price and define scope during the transition.

FAQs:

• Can I manage legacy form fees in the new Fees module? Not yet—the upgraded module is currently for UAD 3.6 fee plans; legacy fees will be supported later per roadmap.

• Why is the UAD 3.6 fee plan based on a forms matrix? It helps customers transition by mapping familiar legacy forms to the UAD 3.6 data points that now define scope.

• What makes up a fee plan? A base fee plus optional add-ons (e.g., rush, ADU count, construction method, property usage, valuation assignment type).

• Where do fees get applied during ordering? Fees are calculated using the fee plan logic rather than being stored directly in Product Requirements.

• Who can configure UAD 3.6 fees? Users with the appropriate permissions (e.g., “Manage UAD 3.6 Fees”).

Key Message: Product Requirements under the Preferences menu has been updated to split residential appraisals into two tabs,

• Residential Appraisal (UAD 3.6 products)

• Residential Appraisal – Legacy Forms (existing)

The Residential Appraisal tab list differs from the current screen in two ways:

• It does not display the fee because it is no longer stored in the Product Requirements module, and the fee calculation extends beyond the product.

• It represented by one field on the order form.

While the configurations for Legacy forms will remain unchanged, preferences for UAD 3.6 products must be configured during a client's UAD 3.6 migration.

Key Message: The Product Requirements screen at the individual UAD 3.6 product level looks a little different from the legacy forms:

• The Required Forms section is not available for UAD 3.6 products because the requirements will be primarily dictated by the scope of work defined for the service provider and the applicable sections on the new URAR dynamic appraisal form.

• The Designations section is unchanged.

• The Order Options section no longer has a place to enter fees; UAD 3.6 fees are managed in the Preferences → Fees module.

From the Product Requirements > Residential Appraisal tab, the Order Options section no longer has a place to enter fees; UAD 3.6 fees are managed in the Preferences → Fees module.

Related article/s
How to Edit Preferences & Product Requirements on Mercury Network®

Important Callouts:

• Two tabs now: Product Requirements splits into Residential Appraisal (UAD 3.6 products) and Residential Appraisal – Legacy Forms (existing).

• Fees moved out: UAD 3.6 fees are no longer entered here—fees are managed in Preferences → Fees.

Facilitator Notes:

• Navigate to Preferences → Product Requirements and show learners the two tabs; ask them which tab they’d use for a UAD 3.6 order.

• If learners look for “Required Forms,” explain that UAD 3.6 scope/sections on the dynamic URAR replace that legacy concept.

Knowledge Check:

• Q1: Multiple choice: To configure requirements for UAD 3.6 products, you use: (A) Residential Appraisal – Legacy Forms tab (B) Residential Appraisal tab (C) Fees module

  • Answer: (B) Residential Appraisal tab

• Q2: Short answer: Where are UAD 3.6 fees managed now?

  • Answer: Preferences → Fees module.

• Q3: True/False: The “Required Forms” section is available for UAD 3.6 products in Product Requirements.

  • Answer: False.

FAQs:

• Where do I configure requirements for UAD 3.6 products? Preferences → Product Requirements → Residential Appraisal tab.

• Where do I configure requirements for legacy forms? Preferences → Product Requirements → Residential Appraisal – Legacy Forms tab.

• Why don’t I see fees on the UAD 3.6 Product Requirements screen? Fees are no longer stored here; UAD 3.6 fee logic is managed in Preferences → Fees.

• Why is “Required Forms” not available for UAD 3.6 products? UAD 3.6 requirements are driven by scope of work and the dynamic URAR sections rather than selecting required legacy forms.

• What parts of the product screen stayed the same? Sections like Designations remain unchanged.

Key Message: Legacy forms and UAD 3.6 products have different data points available within the order, and the scope of work is described differently. For this reason, customers must maintain separate engagement letter templates for each type of order. Mercury Network® now has a separate default Engagement Letter template for UAD 3.6 orders in addition to the existing default template for legacy forms.

For customers creating custom Engagement Letter Templates, those templates must now be classified as either Legacy Forms or Products (UAD 3.6).

All existing Engagement Letter Templates have been classified as Legacy Forms. When a user creates a new Engagement Letter Template, they must select the template type.

The selected template determines which fields are available to populate in the Engagement Letter Template. Additional fields available to use in UAD 3.6 Products templates include:

• Prop Attachment

• Property Type

• Living Unit Excluding ADU

• Property Valuation Method

• Project Legal Structure

• ADU Count

• Construction Method

• Rent Schedule Indicator

• PUD Indicator

• Land Owned in Common Indicator

• Property Usage

• Order Type

• Mortgage Type

• Valuation Assignment Type

To create a new Engagement Letter Template
Click Preferences > Product Requirements > click Engagement Letter Templates in the top left corner.

Applying an Engagement Letter Template:
Applying an Engagement Letter Template to a specific product is configured in the Product Requirements module.

Related article/s
How to Manage Engagement Letter Templates in Mercury Network®

VMP Client Notifications: Additional notifications will be added for new statuses introduced to Mercury Network®. More details will be coming soon.

Client Users: Permissions that have been added or changed:

Manage UAD 3.6 Fees: This permission allows users to configure fees in the Preferences → Fees module.

Submit to Review: Today, this permission allows users to submit orders to RealView manually. For UAD 3.6 orders, this permission allows users to manually send the valuation product to the Investigate Review solution. The option to submit to Investigate will be available only for orders in a Completed status that have not already been sent to Investigate.

Submit to UCDP: Today, this permission allows users to manually submit an order to UCDP. This also now applies to manually submitting UAD 3.6 orders to UCDP. However, note that all users, regardless of this permission setting, can view our new Investor Submission section in the order workspace.

Related article/s
How to Manage UCDP Submission in Mercury Network®

Client Groups:

• VMP Client Notifications

  • Additional notifications will be added for new statuses introduced to Mercury Network®. More details will be coming soon.

• Details Tab

  • UAD 3.6 orders are not managed within the Client Group profile; they are handled in the new fees module.

• Automated Tab

  • Customers can now configure Sure Receipts for UAD 3.6 products and legacy forms.

  • A new permission has been added to control whether the “Use Pending Release” feature is enabled. Customers can use the Pending Release feature to control whether a UAD 3.6 order transitions to the Pending Release status. The “Use Quality Control (QC) folders” setting does not apply to UAD 3.6 orders; however, customers can configure at the Client Group level whether an order transitions to the Pending Release status rather than automatically moving forward to the Completed status. This enables customers to perform any manual checks they need before moving the order to the Completed status.

  • The existing UCDP settings do not apply to UAD 3.6 orders. To simplify and streamline UCDP submission settings, we now host a single set of customized UCDP submission plans in Preferences → Connection Settings. In each Client Group profile, customers will select which UAD 3.6 UCDP Submission Plan applies to that Client Group.

Related article/s
How to Configure Client Group Profiles in Mercury Network®

Important Callouts:

• Separate templates required: Legacy forms and UAD 3.6 products have different fields/scope language, so engagement letters must be maintained separately.

• Template type drives merge fields: New templates must be classified as Legacy Forms or Products (UAD 3.6), which determines what order fields can be inserted.

Facilitator Notes:

• Show where the Engagement Letter Templates live, then point out the template type selection when creating a new template.

• Remind learners all existing templates defaulted to Legacy Forms—teams need to create/validate new UAD 3.6 versions rather than reusing legacy text/fields.

Knowledge Check:

• Q1: Multiple choice: When creating a new Engagement Letter Template, you must classify it as: (A) UCDP or Non-UCDP (B) Legacy Forms or Products (UAD 3.6) (C) Vendor or Client

  • Answer: (B) Legacy Forms or Products (UAD 3.6)

• Q2: True/False: Existing Engagement Letter Templates were automatically classified as Legacy Forms.

  • Answer: True.

• Q3: Short answer: Where do you configure which Engagement Letter Template applies to a specific UAD 3.6 product?

  • Answer: In Preferences → Product Requirements (for the relevant product).

FAQs:

• Why do we need separate engagement letters for UAD 3.6? UAD 3.6 uses different order data points and describes scope of work differently than legacy forms.

• What happens to our existing templates? All existing Engagement Letter Templates are classified as Legacy Forms.

• What must users select when creating a new template? The template type: Legacy Forms or Products (UAD 3.6).

• Why do the available fields change? The selected template type controls which order fields can be used to populate the letter.

• Where do we assign an engagement letter to a product? In the Product Requirements module for the relevant product.

Key Message: Today, vendor assignment relies heavily on appraisal form numbers. Vendor profiles (which house eligibility criteria for order assignment) and the auto-assignment logic are updated to use UAD 3.6 data points to determine who is eligible for specific orders/scopes of work.

Vendor Profile Updates/Assignment Eligibility

Vendor profiles have been revised to include new eligibility criteria. These criteria must be activated for a vendor to qualify for any order that features these specific values or characteristics.

• UAD 3.6 products (referred to as Residential Appraisals) added to Coverage Area.

  • Legacy appraisal forms are now under a tab called Residential Appraisal - Legacy Forms

• New/updated Assignment Criteria fields include:

  • Valuation Assignment Type

  • Mortgage Type

  • Construction Method Type (multi-select enumerations)

  • PUD (single checkbox)

  • Land Owned in Common (single checkbox)

  • Living Unit Excluding ADU Count

  • ADU (single checkbox indicating an ADU is present)

  • Rent Schedule (single checkbox indicating a rent schedule is required)

  • Rush

  • Property Usage

The MISMO 3.6 “Conventional” Mortgage Type has been added to all vendor profiles as read-only. All new vendors will automatically be eligible for UAD 3.6 orders with a “Conventional” Mortgage Type.

Service Providers must update their profiles to include coverage for these order characteristics as applicable. Customers must assess these criteria and determine vendor eligibility as needed.

Related article/s
Vendor Profiles Overview in Mercury Network®

Key Message: Automated Vendor Assignment Logic
Automated vendor assignment logic has been updated to account for all new eligibility criteria and correctly evaluate eligibility for legacy forms versus UAD 3.6 orders. For customers using advanced automated assignment, we will work with you to update your existing logic.

Important Callouts:

• Vendor eligibility expands for UAD 3.6: Providers must have coverage for new order characteristics (e.g., Mortgage Type/Property Usage and other UAD 3.6 property characteristics) to be eligible for assignment.

• Default “Conventional” coverage: MISMO 3.6 Conventional Mortgage Type is added to all vendor profiles as read-only; new vendors will automatically be eligible for UAD 3.6 orders with Conventional Mortgage Type.

Facilitator Notes:

• Show where vendor profile eligibility criteria are maintained, then call out which criteria are new/most likely to break automated assignment if not updated.

• Reinforce the difference between “eligible” (meets profile/logic) and “assigned” (selected by assignment rules/rotation); troubleshoot by checking profile coverage first, then assignment logic.

Knowledge Check:

• Q1: Multiple choice: The MISMO 3.6 Mortgage Type added to all vendor profiles as read-only is: (A) FHA (B) Conventional (C) VA

  • Answer: (B) Conventional

• Q2: True/False: New vendors are automatically eligible for UAD 3.6 orders with a Conventional Mortgage Type.

  • Answer: True

• Q3: Short answer: If automated vendor assignment fails for a UAD 3.6 order, what is the first thing you should verify?

  • Answer: Confirm the vendor profile has coverage for the required UAD 3.6 order characteristics (eligibility) before troubleshooting assignment logic.

FAQs:

• Why are vendors suddenly ineligible for some orders? UAD 3.6 introduces additional order characteristics used to evaluate eligibility; if a vendor profile doesn’t include coverage for those characteristics, they won’t qualify.

• Do vendors need to update their profiles? Yes—service providers must update profiles to include coverage for new order characteristics as applicable; customers decide how strictly to enforce eligibility.

• What does the MISMO 3.6 “Conventional” Mortgage Type change do? It is added to all vendor profiles as read-only, and new vendors are automatically eligible for UAD 3.6 orders with Conventional Mortgage Type.

• Will automated vendor assignment work the same? The logic is updated to evaluate legacy vs UAD 3.6 eligibility correctly, but advanced automated assignment rules may need customer-specific updates.

Key Message: We are excited to introduce a new feature that allows service providers to submit modifications to property characteristics identified during their evaluation process. The appraiser or AMC can now send updates to the lender prior to the appraisal's completion. This enables the Secure user to either approve or decline the change and assess any potential impacts on the transaction and re-disclosure requirements.

This process facilitates quick communication between the service provider and their client. The Secure order is placed into a Product Order Details Requested status so that Mercury Secure users immediately know it needs their attention. Users with the appropriate permissions can approve or decline a request to revise order details via the Mercury user interface or the LOS integration, provided the LOS supports this functionality.

Related article/s
Lender View - Property Order Details Request in Mercury Network® (Lender)
Vendor View - Property Order Details Request in Mercury Network® (Vendor)

Important Callouts:

• New collaboration step: Appraisers/AMCs can request changes to property characteristics before appraisal completion; lenders decide to approve/decline.

• Status cue: The Secure order moves to Product Order Details Requested so teams can quickly triage and clear the blocker.

Facilitator Notes:

• Walk through one example request and model the decision: confirm impact (fees/timeline), then approve or decline.

• Approve/decline can happen in the Mercury UI or via LOS integration (only if the LOS supports it).

Knowledge Check:

• Q1: Multiple choice: When a provider requests a property detail change, the order moves to: (A) Delivered (B) Product Order Details Requested (C) Review Complete

  • Answer: (B) Product Order Details Requested.

• Q2: True/False: Lenders can approve/decline requests only in Mercury (never through LOS integration).

  • Answer: False. Approve/decline can be done in Mercury UI or via LOS integration if supported.

• Q3: Scenario: A change request could affect fees or timing—what should you do before approving?

  • Answer: Assess potential impacts (transaction details, timing, fees, and any re-disclosure requirements) and follow internal policy before approving.

FAQs:

• What is Property Details Collaboration? A workflow where the service provider can propose changes to property characteristics before the appraisal is completed.

• What status tells me I need to take action? Product Order Details Requested.

• Who can approve or decline the change? Secure users with the appropriate permissions (and some LOS users if the integration supports it).

• Does approving automatically re-disclose? No—approval allows the update; your organization still evaluates impacts on the transaction and re-disclosure requirements.

• What if we decline? The order continues with the original details; the service provider proceeds accordingly.

Key Message: The only acceptable file format for a UAD 3.6 appraisal is a .zip file. PDFs and MISMO XML are not acceptable. Service providers cannot upload a .zip file to legacy form orders, and they cannot upload anything other than a .zip file for the appraisal on a UAD 3.6 order.

Important Callouts:

• ZIP-only for UAD 3.6: The appraisal report must be uploaded as a .zip; PDF and MISMO XML alone are not accepted for UAD 3.6 delivery.

• Temporary lockout during upload: While the ZIP is uploading, the order is locked and Attach Documents

Facilitator Notes:

• Show what a valid delivery looks like (ZIP) and call out what happens if a vendor attempts the wrong format.

• If buttons are disabled, it’s usually “upload still in progress,” not a permissions issue—wait/refresh

Knowledge Check:

• Q1: Multiple choice: The only acceptable UAD 3.6 appraisal delivery format is: (A) PDF (B) MISMO XML (C) ZIP

  • Answer: (C) ZIP

• Q2: True/False: It is normal for Attach Documents and Complete to be disabled while the appraisal file is uploading.

  • Answer: True.

• Q3: Scenario: A vendor says “Complete is greyed out.” What’s your first troubleshooting step?

  • Answer: Verify whether the ZIP upload is still in progress or failed—confirm upload completion/status

FAQs:

• What file type is required for UAD 3.6 appraisal delivery? A single .zip file.

• Can vendors upload a ZIP to legacy form orders? No—ZIP upload is specific to UAD 3.6 orders.

• Why are Attach Documents and Complete disabled? The order is temporarily locked while the appraisal ZIP uploads to prevent a second upload; buttons re-enable when the upload finishes.

• Is a PDF acceptable by itself? No—PDF (and MISMO XML) alone are not acceptable as the appraisal delivery file for UAD 3.6.

• What should I do if a vendor says they can’t complete the order? Confirm the ZIP upload completed successfully; if not, the vendor may need to re-upload per the error/status message.

Key Message: Mercury Network® has implemented new automated rules that run the moment an appraisal is uploaded. This allows customers to catch completeness and compliance issues immediately—before the file even hits a reviewer’s desk. We run several different types of rules:

• Basic virus scan and file validation to ensure the file is well-formatted.

  • If a rule fails, a Document Failed status is returned. The secure user will receive a system alert indicating that a product upload was attempted, failed, and that the vendor has been asked to reupload the file.

• UAD Rules to confirm that the zip file meets basic UAD guidelines for successful upload to UCDP

  • If a rule fails, the order will move to a Revision - Correction Needed status, and the vendor will receive a revision request to correct the issue.

• Review rules that check for compliance and risk factors (Investigate Customers Only)

  • Investigate customers can configure which review rules they want to categorize as Severe. If a Severe review rule fires upon appraisal upload, the order will move to a Revision - Correction Needed status, and the vendor will receive a revision request to correct the issue.

Related article/s
Critical Rules and Automated Revision Requests in Mercury Network® per UAD 3.6 Updates

Important Callouts:

• Rules run immediately at upload: Failures can trigger an automated status change and/or revision request before the file reaches a reviewer.

• Know the outcomes: File/virus/validation failures return Document Failed; UAD/Severe review rule failures move the order to Revision – Correction Needed and send a revision request to the vendor.

Facilitator Notes:

• Teach the three buckets: (1) file validation, (2) UAD rules, (3) review rules (Investigate customers). Connect each bucket to its resulting status.

• Call out override carefully: Severe review rule overrides are permission-based and should be used only when a special circumstance requires proceeding without an appraisal update.

Knowledge Check:

• Q1: Multiple choice: A UAD rule failure at upload results in: (A) Review Complete (B) Revision – Correction Needed (C) Pending Release

  • Answer: (B) Revision – Correction Needed.

• Q2: Match: Validation/virus scan failure → _____. Severe review rule firing (Investigate) → _____.

  • Answer:  Validation/virus scan failure → Document Failed. Severe review rule firing (Investigate) → Revision – Correction Needed.

• Q3: True/False: Any user can override a Severe review rule if they think it’s unnecessary.

  • Answer: Overrides are permission-based and should follow policy/special-circumstance guidance.

FAQs:

• When do the automated rules run? Immediately when the appraisal is uploaded.

• What causes a Document Failed status? Basic virus scan/file validation failures (file is not well-formatted or fails validation checks).

• What triggers Revision – Correction Needed? UAD rule failures (ZIP doesn’t meet UAD guidelines) and, for Investigate customers, Severe review rule firings.

• Who gets notified when a critical rule fails? The vendor receives a revision request; the Secure user typically receives a system alert/status update indicating the upload failed or needs correction.

• Can we override a Severe review rule? Yes—if permitted, authorized users can override to bypass the required correction step and move the order forward.

Review Rule Firings Override:
Key Message: If an appraisal triggers a Severe review rule but a special circumstance requires the order to move forward without an appraisal update, users with the appropriate permissions can override the Severe rule. This override bypasses the required correction step, allowing the order to move forward immediately instead of remaining in Revision – Correction Needed.

Important Callouts:

• Exception workflow: Override is for special circumstances only—use it to proceed without an appraisal update when a Severe review rule fired.

• Controlled by permissions: Only authorized users can override; it bypasses the Revision – Correction Needed step and moves the order forward.

Facilitator Notes:

• “Override changes the workflow, not the risk—document your rationale and follow internal policy.”

• Ask learners who in their org is authorized to override and what documentation/approval is required.

Knowledge Check:

• Q1: True/False: An override resolves the Severe rule issue in the appraisal file.

  • Answer: False.

• Q2: Multiple choice: Who can use the override? (A) Any Secure user (B) Only users with configured permission (C) Only the vendor

  • Answer: (B) Only users with configured permission.

• Q3: Scenario: A Severe rule fired, but closing is today—what must you confirm before overriding?

  • Answer: Confirm this is an approved special circumstance, you have permission, and required internal documentation/approvals are complete.

FAQs:

• What does “override” do? It bypasses the required correction step after a Severe review rule fires so the order can move forward.

• Does override fix the appraisal issue? No—it only allows the workflow to proceed; the underlying risk/issue still exists and should be handled per policy.

• Who can override? Only users with the appropriate permissions (as configured by your organization).

• When should override be used? Only when a special circumstance requires proceeding without an appraisal update (with appropriate approvals/documentation).

Automated Revision Requests:
Key Message: Several processes within the UAD 3.6 workflow automatically initiate revision requests to the service provider. These requests detail the specific issues that need to be addressed in the appraisal.

When an automated revision request is generated as a result of a UAD rule or Review Rule firing, both the vendor and secure user can view the revision request details in the Revision Details PDF inside the order’s document repository.

The system also generates automated revision requests when it detects a Uniform Collateral Data Portal (UCDP) fatal submission finding. UCDP fatal findings requiring appraisal modifications automatically trigger a revision request to the vendor that details the issues to be resolved.

In addition to the Revision Details PDF, Secure users can also view these requested revisions and their contents in the Investor Submission workspace. For more information, see the Investor Submission section.

Note: In the future, you can configure Mercury to consolidate vendor feedback across various rule checks to reduce the number of automated revision requests.

Related article/s
How to Submit and Manage the UCDP Submission in Mercury Network®

Important Callouts:

• Multiple triggers: Automated revision requests can come from UAD rule failures, Severe review rule firings, or UCDP fatal submission findings.

• Where to read details: Use the Revision Details PDF in the document repository; Secure users may also see related revisions in the Investor Submission workspace (when tied to upload/submission findings).

Facilitator Notes:

• Show one example of the Revision Details PDF and point out where the rule description and required action are listed.

• Consolidation of vendor feedback is a future configuration—set expectation that today learners may see multiple requests.

Knowledge Check:

• Q1: Multiple choice: Which is not a possible trigger for an automated revision request? (A) UAD rule failure (B) UCDP fatal finding (C) Review Complete status

  • Answer: (C) Review Complete status.

• Q2: Short answer: What document in the repository summarizes the revision request details?

  • Answer: The Revision Details PDF.

• Q3: Scenario: A vendor asks where to find the exact items to correct—what do you tell them to open?

  • Answer: Open the Revision Details PDF in the order’s document repository (it lists rule descriptions and required actions).

FAQs:

• Why did a revision request generate automatically? A rule check or a UCDP fatal finding detected an issue that requires appraisal modification.

• Where do I see exactly what needs to be corrected? In the Revision Details PDF within the order’s document repository (and sometimes in Investor Submission for submission-related findings).

• Who sees the request? Both the vendor and the Secure user can view the revision details; the vendor receives the request to update/re-upload.

• Can multiple automated revision requests be created for one order? Yes—different rule checks can generate separate requests (future consolidation may reduce this).

Where to access Revision Requests:
Key Message: Revision requests are now more clearly formatted and easier to review. You can access revision requests in the following locations:

• Order History Log (Legacy Forms Only).

• Investor Submission section of the workspace (Secure only, and only when the revision results from a fatal finding during appraisal upload or investor submission).

• Order Document Repository, where a PDF detailing the revision request will be added.

See screenshot below for example of Revisions Requests Details and Rule Descriptions.

Important Callouts:

• Three access points: Order History Log (legacy only), Investor Submission workspace (Secure; certain finding types), and the Document Repository (Revision Details PDF).

• Fastest path for most users: The Revision Details PDF in the document repository is the most consistent place to start.

Facilitator Notes:

• Have learners locate the same revision request in two places (Repository PDF + Investor Submission, if available) to reinforce where to look by workflow.

Knowledge Check:

• Q1: Multiple choice: Which location is legacy-forms only? (A) Investor Submission workspace (B) Order History Log (C) Document Repository

  • Answer: (B) Order History Log.

• Q2: Short answer: What is the name of the PDF that contains the revision request details?

  • Answer: The Revision Details PDF.

• Q3: Scenario: A Secure user can’t find revision details in Investor Submission—where should you direct them first?

  • Answer: The Document Repository (Revision Details PDF), since it’s the most consistent access point.

FAQs:

• Where is the best place to start when looking for revision details? The Revision Details PDF in the order’s document repository.

• Why don’t I see revision requests in the Order History Log? That location applies to legacy forms only.

• When would I see revisions in Investor Submission? When the revision results from a fatal finding during appraisal upload or investor submission (Secure only).

• Can vendors see the revision details too? Yes—vendors receive the revision request and can view the details needed to correct the file.

Key Message: Mercury Network® will use a modernized module to manage UCDP submissions for UAD 3.6 orders. Legacy form orders will continue to use the current process flow.

The Investor Submission Workspace is a new section within the order workspace for managing UAD 3.6 UCDP submissions. In this workspace, clients can:

• Manage all products associated with the same GSEDocFileID in one convenient location.

• Easily check the status of each submission or automated revision requests sent to the vendor due

• to fatal findings.

• Create manual revision requests.

• Access the SSR.

• Review a history log specifically for investor submissions.

• Download the zip file, and much more.

Related article/s
How to Submit and Manage the UCDP Submission in Mercury Network®

Important Callouts:

• New workspace for UAD 3.6 only: UAD 3.6 orders use the Investor Submission Workspace for UCDP submissions; legacy form orders continue using the current process flow.

• One ID, multiple products: Products associated to the same Investor Doc File ID (formerly GSE Doc File ID) are managed together, including statuses, revision requests, history, and downloads.

Facilitator Notes:

• Show learners where to see submission status, revision requests, and the history log—then show where to download PDF/XML/ZIP from the same screen.

• Viewing the Investor Submission section may be broader than having permission to submit/manage actions in UCDP—roles can differ by customer setup.

Knowledge Check:

• Q1: Multiple choice: The Investor Submission Workspace is used for: (A) UAD 3.6 UCDP submissions (B) all legacy form submissions (C) ordering new appraisals

  • Answer: (A) UAD 3.6 UCDP submissions.

• Q2: True/False: UCDP fatal findings that require appraisal changes can trigger an automated revision request to the service provider.

  • Answer: True.

• Q3: Short answer: Name two things a UCDP Submission Plan can specify.

  • Answer: Any two of: business unit and seller servicer numbers, which GSE entity(ies) to submit to, which products are eligible/not eligible for UCDP submission, and (by configuration) which plan applies to a client group.

FAQs:

• What is the Investor Submission Workspace? A section in the order workspace used to manage UAD 3.6 UCDP submissions (statuses, revision loop, history, and downloads).

• Does this change the submission process for legacy forms? No—legacy form orders continue to use the current submission workflow.

• What triggers an automated revision request? UCDP fatal findings that require appraisal modification automatically trigger a revision request to the service provider.

• Can we submit to UCDP automatically? Yes—each customer chooses manual or automatic submission as a global setting for UAD 3.6 orders.

• Why would we need multiple UCDP Submission Plans? To apply different business unit/seller-servicer numbers, GSE targets, and eligible products by Client Group.

Key Message: UCDP Fatal findings that require an appraisal modification will automatically trigger a revision request to the service provider, detailing the issue(s) to be resolved. Clients can view the requested revisions and their contents in each GSE section and in the history log.

Knowledge Check:

• Q1: Multiple choice: Automated revision requests are triggered by: (A) review complete (B) UCDP fatal findings requiring changes (C) pending release configuration

  • Answer: (B) UCDP fatal findings requiring changes.

• Q2: Short answer: Name one place a user can view the contents of a revision request.

  • Answer: Either: the relevant GSE section or the Investor Submission history log.

• Q3: True/False: Automated revision requests eliminate the need for any manual revision requests.

  • Answer: False (manual revision requests may still be needed).

FAQs:

• What triggers an automated revision request? UCDP fatal findings that require an appraisal modification.

• Who receives the revision request? The service provider/vendor, with the issue(s) to be resolved.

• Where can users view revision details? In each GSE section and in the Investor Submission history log.

• Can we still create revision requests manually? Yes—users can create manual revision requests when needed.

Key Message: Each customer will decide whether the UCDP submission for UAD 3.6 orders will be triggered manually or automatically. This is a global setting that applies to all UAD 3.6 orders.

Administrative configurations must be set up to define UCDP Submission Plans. Clients can use a single default plan or create multiple plans and specify which UCDP Submission Plan to apply to each Client Group. Each plan specifies:

• Business unit and Seller Servicer #s

• The GSE entity(ies) to submit to

• Which products are eligible and not eligible for UCDP submission.

Related article/s

How to Configure Investor Submission Automatic Settings on Mercury Network®

How to Add & Configure Client Group Profiles on Mercury Network®

If a customer chooses manual submission, the configuration defining which products are eligible and not eligible for submission do not apply. Any user with the proper permissions can manually submit a UAD 3.6 product to UCDP.

Customers can configure within the Client Group Profile which Investor Submission plan should be used for orders associated with that client group. This is necessary only if the client group requires a different submission plan from the global plan(s).

Advanced Investor Submission Features
Key Message: In 2026, the new workspace will also allow clients to perform advanced actions on files within the UCDP portal, such as deleting and repositioning.

Important Callouts:

• Global decision: Manual vs automatic UCDP submission is a customer-level setting that applies to all UAD 3.6 orders (not set per order).

• Plans + client groups: Submission plans define seller/servicer numbers, GSE target(s), and product eligibility; assign different plans only when a Client Group needs different submission details than the global plan.

Facilitator Notes:

• Ask learners to explain the difference between a global submission setting and a client-group submission plan using a simple example (two business units, different Seller/Servicer numbers).

• Call out common confusion: Manual submission means product eligibility rules in the plan don’t restrict submission—permissions control who can submit.

Knowledge Check:

• True/False: Manual vs automatic UCDP submission is configured per order.

  • Answer: False. It’s a global setting for all UAD 3.6 orders.

• Multiple choice: A UCDP Submission Plan can specify: (A) Seller/Servicer numbers (B) which GSE(s) to submit to (C) eligible products (D) All of the above

  • Answer: (D) All of the above.

• Short answer: When would you assign a different submission plan to a Client Group?

  • Answer: When a client group needs different submission details than the global plan (e.g., different business unit/Seller-Servicer numbers, different GSE targets, or different eligible products).

FAQs:

• Is UCDP submission manual or automatic? Each customer chooses manual or automatic submission; it’s a global setting for all UAD 3.6 orders.

• What is a UCDP Submission Plan? A configuration that defines the submission details (e.g., Seller/Servicer numbers, GSE target, product eligibility).

• Why would we create multiple submission plans? To apply different plans to different Client Groups (e.g., different business units or Seller/Servicer numbers).

• What happens if we choose manual submission? Product eligibility rules don’t apply—any properly permissioned user can manually submit a UAD 3.6 product to UCDP.

• Where is the submission plan assigned? In the Client Group Profile, if that client group needs a plan different from the global plan.

Key Message: We are excited to introduce a brand new review tool called Investigate. This new tool replaces RealView for UAD 3.6 orders and will revolutionize your review process. Information and user guides for the Investigate solution will be covered in a separate document.

For customers under contract for our review solution, all orders will flow to review by default after they have passed the automated rules and investor submission is successful (if applicable).

Customers can configure review submission plans to bypass review for specific products, and assign different review plans to each client group if necessary.

Click on Preferences> Review Settings >Investigate Tab

Related article/s
How to Configure Review Settings on Mercury Network®

How to Review the UAD 3.6 Order Process on Mercury Network®

Important Callouts:

• Investigate replaces RealView for UAD 3.6 orders (review experience changes, not just a label change).

• Default review routing: For customers under contract, orders flow to review after automated rules pass and investor submission is successful (if applicable); review plans can bypass review by product and vary by client group.

Facilitator Notes:

• Show where the setting lives: Preferences > Review Settings > Investigate tab (use screenshots if you don’t have admin access in training).

Knowledge Check:

• Q1: Multiple choice: Investigate replaces which tool for UAD 3.6 orders? (A) UCDP (B) RealView (C) Order List View

  • Answer: (B) RealView.

• Q2: Short answer: Name the navigation path to configure Investigate settings.

  • Answer: Preferences > Review Settings > Investigate tab.

• Q3: Scenario: A client group wants Product A to bypass review, but Product B must always be reviewed—what configuration concept supports this?

  • Answer: Review submission plans (configure by product and, if needed, by client group).

FAQs:

• What is Investigate? It’s the new review tool for UAD 3.6 orders, replacing RealView for that workflow.

• Does Investigate replace RealView for all orders? No—this change is specific to UAD 3.6 orders (legacy workflows may differ based on your setup).

• When does an order go to review? After automated rules pass and investor submission is successful (if applicable), for customers under contract for the review solution.

• Can we bypass review? Yes—review submission plans can bypass review for specific products and can be different by client group.

• Where do I configure Investigate settings? Preferences > Review Settings > Investigate tab.

Key Message: UAD 3.6 orders will not flow through the QC folders; however, customers can still “pause” orders for manual review before releasing them to a Completed status. A new administrative configuration allows customers to choose whether orders are set to Completed status or stop in a Pending Release status first. Customers who choose to stop the order in the Pending Release status must manually move it to Completed once their manual processes are complete.

Note: All UAD 3.6 secure orders will now move to a Delivered status once the service provider uploads the appraisal. If your system is configured to sync the Pending Quality Review status to your client order, the client order will move to Pending Quality Review when the secure order is in a Delivered status.

Related article/s

Investigate Review Business Workflow in Mercury Network®

Important Callouts:

• What changed: UAD 3.6 orders don’t use the QC folders; Pending Release is the new optional “pause point” for manual review before an order becomes Completed.

• Admin-controlled behavior: Customers can configure whether orders go straight to Completed or stop at Pending Release and require a manual move to Completed.

Facilitator Notes:

• “Pending Release is a deliberate hold—use it when you need a manual check before final completion.”

• Confirm if your org uses Pending Release; if not, coach them to expect Delivered → Review → Completed instead.

Knowledge Check:

• Q1: Multiple choice: Pending Release is best described as: (A) an automated rules failure (B) an optional manual hold before completion (C) a document upload error

  • Answer: (B) an optional manual hold before completion.

• Q2: True/False: If Pending Release is enabled, orders will move to Completed automatically once they reach Pending Release.

  • Answer: False. When enabled, orders require a manual move from Pending Release to Completed.

• Q3: Short answer: Why might an organization choose to enable Pending Release?

  • Answer: Example answers: to pause orders for a manual quality/compliance check, internal sign-off, or other non-system steps before final completion.

FAQs:

• What is Pending Release? A configurable status that pauses an order for manual steps before it is moved to Completed.

• Why don’t UAD 3.6 orders go through QC folders? The UAD 3.6 workflow supports a different end-to-end path; Pending Release is the alternative control point if you need a manual hold.

• Who decides whether we use Pending Release? It’s an administrative configuration choice made by the customer (your org’s admin team).

• What happens if we enable Pending Release? Orders stop at Pending Release and must be manually moved to Completed after manual processes are done.

Key Message: Order Details now shows UAD 3.6 property characteristic fields (Prop Attachment, Property Type, ADU Count, etc.).
The following fields are now visible on UAD 3.6 orders.

• Prop Attachment

• Property Type

• Living Unit Excluding ADU

• Property Valuation Method

• Project Legal Structure

• ADU Count

• Construction Method

• Rent Schedule Indicator

• PUD Indicator

• Land Owned in Common Indicator

• Property Usage

• Order Type

• Mortgage Type

• Valuation Assignment Type

• Parent Tracking Number (this will only be populated on Completion Reports and Restricted

• Update Reports) VMP Client view only. On Secure orders, this information is available in the new Investor Submission section.

GSE Doc File ID has been renamed to Investor Doc File ID.

There are also several fields present on legacy forms orders but not on UAD 3.6 orders. Several of these fields are replaced with fields that house similar information.

• Form/type

• Loan Type

• Loan Purpose

• Prop Type

• Occupancy

The document repository has been updated for better usability.

Download Files without Opening:

Key Message: Customers can now download files directly without first opening them. For appraisal files, users can view or download the PDF, download the XML, or download the entire Zip file.

VMP Client View

Secure View

Additional Changes to Secure View Only:

Key Messages:

• We have added a new Investor Submission section for UCDP submissions. This is discussed in detail in the Investor Submission section of this document.

• The Start to Review button is now labeled Send to Review, since it triggers the order to be sent to our new Investigate review solution.

• Once an order is sent to Investigate, users can use the Message button to create a message that will be sent to the reviewer.

Business Management View:

Important Callouts:

• Visibility nuance: Parent Tracking Number populates only on Completion/Restricted Update Reports (client view). For Secure orders, find it in Investor Submission.    

• UAD 3.6 vs legacy: UAD 3.6 orders show additional standardized property characteristic fields; legacy orders won’t match one-for-one.    

• Renamed field: “Investor Doc File ID” replaces “GSE Doc File ID.”

• Download options: Files can be downloaded directly; appraisal files offer PDF, XML, or ZIP.    

• Permission differences: Actions vary between      Client View and Secure View; in Secure, “Send to Review” routes to      Investigate and “Message” contacts the reviewer.

Facilitator Notes:

• Open a sample UAD 3.6 order and do a 30–60 second “where to look” scan of the new fields.  

• Explain why some legacy fields (Loan Purpose/Occupancy, etc.) don’t appear—similar info is captured differently in UAD 3.6.

Knowledge Check:

• Q1: Multiple choice: Which file would you download to capture the full package for storage/sharing? (A) PDF (B) XML (C) ZIP

  • Answer: (C) ZIP.

• Q2: Short answer: In Secure View, what does “Send to Review” do?

  • Answer: It routes/sends the order to the Investigate review solution for review.

• Q3: Scenario: A user can’t see the same actions you demoed—what is the first thing you check?

  • Answer: Permissions/role and whether they are in Client View vs Secure View (and any feature enablement).

FAQs:

• Why do I see different fields on a UAD 3.6 order vs a legacy order? UAD 3.6 uses standardized property characteristic fields, so the Order Details layout won’t match legacy forms one-for-one.

• Where is Parent Tracking Number? It populates only on Completion/Restricted Update Reports in the client view; for Secure orders, it’s available in the Investor Submission section.

• What happened to GSE Doc File ID? It was renamed to Investor Doc File ID.

• Why don’t I see Loan Purpose/Occupancy (or other legacy fields)? Some legacy fields are not displayed on UAD 3.6 orders because similar information is captured using different UAD 3.6 fields.

• Which fields should I verify first? Start with key property characteristics (e.g., Property Type, ADU Count, Construction Method) because they impact downstream review and submission.

• Do I have to open a file before downloading it? No—files can now be downloaded directly from the repository.

• What’s the difference between PDF, XML, and ZIP? PDF is the readable report, XML is the data file used for submissions/validation, and ZIP contains the full package for storage/sharing.

• Why does my menu look different from someone else’s? Available actions vary by role/permission and by whether you are in Client View or Secure View.

• What does “Send to Review” do? It routes the order to the Investigate review solution (Secure View workflow).

  How do I contact the reviewer after I send it? Use the Message button once the order is in Investigate.

Key Message: We have added new folders to the active order folder list:

• Product Details Requested - The service provider has requested a change to the property details, and the order requires the user to make a decision before proceeding in the lifecycle.

• Under the Review Folder:

  • In Progress - The order is currently being reviewed by a reviewer in Investigate

  • Needs Reconciliation - The reviewer has indicated a second appraisal order is needed.

• Appraisal Delivered

• Pending Release

Key Message: Action Required Folder Updates:

Key Message: Users can filter between legacy forms and UAD 3.6 appraisals.

Key Message: We have added an Investigate launch button to the menu at the top of the screen.

Related article/s
How to Use Search & Order List in Order Management

Important Callouts:

• Folders: Product Details Requested = decision needed to proceed; Under Review shows Investigate activity (In Progress / Needs Reconciliation).

• Filtering: Filter between legacy and UAD 3.6 so users don’t assume orders are missing.

Facilitator Notes:

• Point out where to launch Investigate, then run one quick scenario using an order in Product Details Requested.

Knowledge Check:

• Q1: Short answer: What does “Product Details Requested” mean, and what must happen next?

  • Answer: The service provider requested a change to property details; the user must

• Q2: Multiple choice: Under Review > Needs Reconciliation indicates: (A) Review is complete (B) A second appraisal order is needed (C) The report is pending release.

  • Answer: (B) A second appraisal order is needed.

• Q3: True/False: If you can’t find an order, checking the legacy vs UAD 3.6 filter is a good first step.

  • Answer: True.

FAQs:

• What does “Product Details Requested” mean? The service provider requested a change to property details; the order needs a user decision before it can proceed.

• What’s the difference between Under Review > In Progress and Needs Reconciliation? In Progress means a reviewer is actively working the order in Investigate; Needs Reconciliation indicates a second appraisal order is needed.

• Why can’t I find my order in the list? Check filters—orders may be filtered out if you’re viewing legacy forms vs UAD 3.6 (or vice versa).

• What is the Investigate launch button for? It opens the Investigate experience for review (where enabled and permissioned).

• Which folders should I work first? Start with Action Required and Product Details Requested to remove blockers, then work review and in-progress queues.

Key Message: To better support the UAD 3.6 end-to-end workflow, we have introduced several new statuses.

Major statuses include:

• Product Order Detail Requested / Accepted / Declined  

• Delivered  

• Review in Progress / Review Complete  

• Pending Release (if enabled)

Minor statuses include:
Document Upload Failed, GSE submission success/fail statuses, UCDP Submission Error, Review Platform message.

Note: Note: All UAD 3.6 secure orders will now move to a Delivered status once the service provider uploads the appraisal. If your system is configured to sync the Pending Quality Review status to your client order, the client order will move to Pending Quality Review when the secure order is in a Delivered status.

Related article/s
Status Definitions on Mercury Network®

Important Callouts:

• Lifecycle flow: Product Details Requested → Delivered → Review in Progress/Complete → Pending Release (if enabled).

• Secure nuance: UAD 3.6 Secure orders move to Delivered when the appraisal is uploaded; may map to client Pending Quality Review (if configured).

Facilitator Notes:

• Major statuses = lifecycle milestones; minor statuses = system errors/messages (troubleshoot/escalate per process).

Knowledge Check:

• Q1: Multiple choice: Which is a major status? (A) UCDP Submission Error (B) Delivered (C) Document Upload Failed

  • Answer: (B) Delivered.

• Q2: Short answer: For UAD 3.6 Secure orders, what event triggers the status to move to Delivered?

  • Answer: The service provider uploads the appraisal (upload event triggers Delivered for Secure UAD 3.6 orders).

• Q3: Scenario: You see UCDP Submission Error—list one immediate check you would perform before escalating.

  • Answer: Example answers: confirm required documents are present, verify required Order Details fields are completed, check submission/validation error details, and confirm the correct file (XML/PDF) was uploaded.

FAQs:

• What are “major” vs “minor” statuses? Major statuses indicate lifecycle milestones; minor statuses are system events/errors (e.g., upload/submission messages).

• When does an order move to Delivered? For UAD 3.6 Secure orders, it moves to Delivered when the service provider uploads the appraisal.

• Why did my client order change to Pending Quality Review? If configured, the client order may sync to Pending Quality Review when the Secure order is Delivered.

• What status tells me it’s being reviewed right now? Look for Review in Progress (and the Under Review > In Progress folder).

• What should I do if I see UCDP Submission Error or Document Upload Failed? Review the error details, confirm required documents/fields, and follow your escalation/support process if it’s not quickly resolvable.

Key Message: We're excited to announce a new suite of standardized reports specifically designed for customers who have migrated to UAD 3.6!

These powerful reports were developed after extensive analysis of the reporting utilized across our entire customer base, ensuring you get the essential insights you need.

Key Features:

• Run On-Demand: Access and run any report at any time, whenever you need immediate data.

• Automate Your Insights: Set up subscriptions to schedule specific reports. Choose the interval that works best for you and have the data automatically distributed to the email addresses you provide.

The new reporting suite gives you simplified, targeted access to the key metrics that drive your business.

Important Callouts:

• What’s new: Standardized UAD 3.6 report suite (more consistent names/fields).

• How to use: Run on-demand for ad hoc questions; use subscriptions for recurring delivery.

Facilitator Notes:

• Confirm report/subscription permissions in the training environment; clarify subscriptions deliver reports (not lifecycle notifications).

Knowledge Check:

• Q1: Multiple choice: Which is the best use of a subscription? (A) One-time audit request (B) Weekly pipeline metrics for leadership (C) Checking a single order status.

  • Answer:(B) Weekly pipeline metrics for leadership.

• Q2: True/False: A report subscription is the same thing as an order lifecycle notification.

  • Answer: False.

• Q3: Short answer: If you can’t create a subscription, what is the most likely first thing to verify?

  • Answer: Verify permissions/access (reporting role and subscription rights) in the environment.

FAQs:

• What’s included in the new reporting suite? A standardized set of reports designed for customers migrated to UAD 3.6, with consistent fields and metrics.

• When should I run a report on-demand? When you need a one-time answer or a quick snapshot right now.

• When should I use a subscription? When the same report is needed on a recurring cadence (daily/weekly/monthly) and should be emailed automatically.

• Are subscriptions the same as system notifications? No—subscriptions deliver report results; lifecycle notifications come from order status/alerts.

• Why can’t I create a subscription? It’s usually permission-related—confirm reporting access and subscription rights in your environment.

Key Message: This update highlights UAT-ready administrative configuration changes and supporting documentation improvements. You should review newly added client statuses and, if desired, configure status syncing to VMP and update mappings so new statuses route to the Action Required folder.

With UAD 3.6, certain needs previously handled through product selection (e.g., 203k, HomeStyle renovation, Reverse mortgage) are now captured through additional order data—particularly Property Characteristics (e.g., UAD 3.6 203k uses Traditional Appraisal + Single Family + Property Characteristic: 203k). You may need to add new Property Characteristics options via Configure Order Form; however, newly added fields on the UAD 3.6 Residential Appraisal order form are not configurable at this time.

FAQs:

• How do I indicate 203k (or HomeStyle renovation / Reverse mortgage) in UAD 3.6 if there is no product specific to it? Use additional order data points rather than product selection. For example, for UAD 3.6 203k, place an order with Valuation Method = Traditional Appraisal, Property Type = Single Family, and Property Characteristic = 203k.

• What should we use Property Characteristics for in UAD 3.6? Use Property Characteristics to capture distinctions that drive fees or vendor requirements and are not accounted for in standard order fields. Review your current list and add any needed options via Configure Order Form.

• Can we configure the new fields added to the UAD 3.6 Residential Appraisal order form? Not at this time. You can add additional Property Characteristics options through Configure Order Form, but the additional fields added to the UAD 3.6 Residential Appraisal order form are not configurable currently.

Key Message: UAD 3.6 introduces major ordering and workflow changes and sunsets several legacy configuration paths. Emphasize that new UAD 3.6 fields and product names are not configurable at launch, and ordering/fee management shifts away from Client/Client Group profiles and Business Management into the administrative module (Business Management fee tables and UAD 3.6 order placement do not apply). Highlight operational constraints: no bulk ordering initially, UCDP manual vs. automated submission is a single global setting (not client-group specific), and submissions must use the UAD zip file with MISMO 3.6 XML (PDF/XML alone won’t be accepted). Finally, call out process differences—Completion/Update Reports for UAD 3.6 must be placed as child orders tied to a parent tracking number, and valuation review workflows move to Investigate Review (some legacy Workbench rules won’t be available for UAD 3.6).

FAQs:

• Can customers configure the new UAD 3.6 fields or rename UAD 3.6 products at launch? No. Newly added UAD 3.6 fields are not configurable at launch, and customers cannot customize the names of available UAD 3.6 products.

• Where do we manage UAD 3.6 vendor fees and client prices—do Client/Client Group profiles or Business Management still apply?
  UAD 3.6 fees and pricing are managed through the administrative module. You will no longer specify fees within Client/Client Group profiles, and fee tables set up by client group in Business Management do not apply to UAD 3.6 orders (and UAD 3.6 orders cannot be placed through Business Management).

• What are the key ordering/submission constraints trainers should call out for UAD 3.6?  UAD 3.6 appraisals must be submitted as the UAD zip file (with MISMO 3.6 XML); PDF-only or XML-only isn’t accepted. Bulk ordering is not available at initial launch. Completion/Update Reports tied to a UAD 3.6 appraisal must be placed as child orders and require the parent order tracking number, and UCDP manual vs. automated submission is controlled by one global setting (not client-group specific).