Collateral Management System® | CMS®

Disaster recovery exercise

Disaster Recovery Test Rescheduled to May 2: GAAR, GATR, and UAD 3.6 File Validation Impacts

Cotality will conduct a nine-hour disaster recovery test on May 2, 2026 (rescheduled from March 28), affecting GAAR, GATR, UAD 3.6 File Validation, UCDP submission, File Vault, and the Fee Worksheet Service. No application changes are involved, but users must hold all related activity during the affected windows since queuing is not guaranteed.

March 1, 2026

UAD 3.6

Production release

TPO ID Integration and UAD 3.6 Enhancements Head to UAT (Deploying March 3)

This UAT release, deploying to production on March 3, 2026, adds TPO Organization ID integration with Encompass, customizable EPC error handling, and new UAD 3.6 readiness indicators in AppraisalPort search and profiles. It also resolves nine issues including stuck orders, bulk upload errors, and UAD 3.6 fee calculation problems.

February 27, 2026

UAD 3.6

Disaster recovery exercise

Disaster Recovery Test March 28: GAAR/GATR, UAD 3.6 Workflow, and Fee Worksheet Impacts

Cotality will run a disaster recovery test on Saturday, March 28, 2026 from 5:00 a.m. to 2:00 p.m. CST, causing intermittent unavailability across GAAR/GATR, UAD 3.6 workflow, File Vault, ENV Service, and Fee Worksheet Service. Users are advised to halt activity during the maintenance window.

February 27, 2026

Production maintenance event

Unscheduled UAT Maintenance: Automated Key Rotation and CMSNet Digital Gateway Enhancements

Cotality performed unscheduled UAT maintenance on February 24, 2026 to implement automated key rotation for the ENV Service and CMSNet enhancements supporting the 537 Event and CDG APIs for Product Nicknames. CMSNet and CMSAPI faced up to two hours of downtime, while the ENV Service saw no expected downtime.

February 23, 2026

UAD 3.6

Production release

REO Loan Purpose, Escalated Review API Status, and Modernized AppraisalPort Search (UAD 3.6)

This production release adds API support for transitioning orders to Escalated Review, a free-text fallback for Review Summary fields, and numerous UAD 3.6 enhancements including a new REO Loan Purpose, bulk actions for UAD 3.6 products, and a modernized AppraisalPort search experience. It also resolves multiple issues across GAAR Viewer, Rent Schedule editing, order notifications, and REC integration events.

February 21, 2026

UAT maintenance event

Unscheduled UAT Maintenance for CMS Reports and Gaar Viewer Updates

Cotality performed unscheduled UAT maintenance on CMS Reports and the Gaar Viewer on February 16, 2026 to address defects and technical debt (CLCTUTD-18860, CLCTUTD-16635) ahead of the Bacchus release, with no expected downtime for CMS.

February 13, 2026

UAD 3.6

UAT release

Easy Access to Investigate, Rent Schedule Validation, and Product Maintenance Cleanup (UAT)

This UAT release adds a one-click Investigate launch button to the CMS menu, tightens Rent Schedule field validation to a strict Yes/No selection, and removes the inactive "All Products" service ID from Administrative Product Maintenance.

February 10, 2026

Product news

March 2026 ZIP Code, County, and City Data Refresh for CMS.net

Starting with the March 14, 2026 production release, Cotality is reinstating monthly ZIP code, county, and city data updates for CMS.net, including the addition of ZIP 96508 and the removal of three retired ZIP codes. Changes are already available in UAT for validation.

February 9, 2026

Disaster recovery exercise

Disaster Recovery Exercise Complete: CMS Ecosystem Returns to Production

The Collateral Management System ecosystem has successfully returned to production and resumed normal operations, completing the disaster recovery exercise. Cotality also acknowledged a third-party notification system malfunction that delayed status updates throughout the day.

February 7, 2026

Disaster recovery exercise

Disaster Recovery Exercise Extended Due to Storage Hardware Vendor Escalation

The scheduled CMS Ecosystem disaster recovery test was extended after a technical issue during data synchronization back to production required escalation to the storage hardware vendor, pushing the expected completion time to approximately 7:15 PM. A separate notification-tool failure delayed status updates during the extension.

February 7, 2026