AMC-to-AMC Modern Workflows on Appraisal Scope® per UAD 3.6 Updates

Overview

This help article explains how AMC-to-AMC modern workflows function when an appraisal order is routed from a parent AMC to a vendor AMC using UAD 3.6 modernization standards. It covers the end-to-end workflow, including ZIP file transfer, UCDP delivery, expanded MISMO 3.6 payload mapping, split-screen JobType Mapping, child order assignment logic, and multi-URAR AMC routing.

1. ZIP File Transfer and UCDP Delivery

To support modern data-centric reporting, the platform facilitates the direct transfer of validated modern packages between platforms:

Once a vendor AMC uploads and completes the modern appraisal package, the report is securely transmitted to the parent AMC in the mandatory ZIP format.
The parent AMC can immediately access, view, and download the primary ZIP package and the extracted PDF directly from their own Documents tab.
The parent AMC retains full authorization to submit the received package directly to the Uniform Collateral Data Portal (UCDP) from the order record.

2. Modern Payload Expansion

When a modern order is transmitted across the AMC-to-AMC bridge, the system automatically packages and maps all required MISMO 3.6 data elements into the integration payload. This guarantees data consistency without manual entry.

The expanded payload automatically includes:

Property Valuation Method
Accessory Dwelling Unit (ADU) Total Count
Living Unit Excluding ADU Count
PUD Indicator
All Entry Contact Information fields

Note: If the parent AMC attempts to send a modern order to a vendor AMC that does not have the Valuation Modernization workflow enabled, the system will halt the transmission and display a clear error message indicating that the receiving platform is not configured for UAD 3.6 data.

3. Split-Screen AMC JobType Mapping

To accommodate the strict separation between legacy and modern workflows, the JobType Mapping screen interface features a split-screen layout.

Legacy Tab: Manages traditional form-centric mappings (e.g., 1004, 1073).
Modern Tab: Manages data-centric MISMO 3.6 mappings.

This layout allows staff users to easily isolate, audit, and configure local and directory forms when mapping modern services between integrated AMC platforms.

4. Child Order AMC Assignment Logic

When managing subsequent assignments (Restricted Appraisal Updates or Completion Reports) within an AMC-to-AMC workflow, assignment inheritance depends on your platform configurations:

AMC Auto Assign Enabled: Child orders automatically inherit the specific AMC assigned to the parent URAR order, ensuring workflow continuity across platforms.
AMC Auto Assign Disabled: Staff users are presented with a tactical assignment modal window when creating a child order. This modal provides an explicit choice to either route the assignment to the original vendor AMC or select a different candidate AMC.

5. Multi-URAR AMC Routing Logic

Per GSE mandates, up to three separate URAR orders can be established under a single loan number. The assignment engine allows staff to manually or automatically assign the second and third URAR orders to entirely different AMCs. The platform candidate list will no longer exclude or filter out the AMC assigned to the initial URAR, allowing separate vendor panels to fulfill multi-appraisal requirements on the same loan file.

6. Appraisal Scope AMC-to-AMC SSRs

The Scope-to-Scope integration bridge facilitates the direct transfer of Submission Summary Reports (SSRs) from the vendor AMC to the parent AMC for modern orders, ensuring files can be opened and viewed from the parent platform's Documents tab.

Outcome

After reading this article, you will be able to describe how modern appraisal packages are transferred between AMC platforms, identify the required setup and data mapping elements for UAD 3.6 workflows, and explain how assignment and routing logic works for child orders and multi-URAR scenarios.