RESO StandardStatus lookups + HistoryTransactional resource — the schema that models the historical layer

reference · Scope: business · Status: current

Created 2026-06-21

Summary

Claim. RESO models the listing-status layer with StandardStatus lookups (Active, Backup, Canceled, Closed, Expired, Pending, Withdrawn) and the HistoryTransactional resource (23 fields). These together model expired/terminated/suspended/cancelled/conditional ("Pending Sold" = firm, unconditional) statuses and relisting chains.

Source. RESO Data Dictionary (dd.reso.org), accessed 2026-06-21.

Confidence. Verified for the schema (StandardStatus + HistoryTransactional); industry-consensus for the analytic interpretations (relisting chains etc.).

Caveats. Local MLS implementations can extend or restrict the StandardStatus enumeration; do not assume the lookup is universal across boards.

Implication / use. The schema-side anchor for the cancel-and-relist tactic (Cancel-and-relist resets DOM to zero — Pasalis-adjacent practitioner (Globe & Mail); condo relistings hit 163pct of sales in mid-October in the 416; GTA condo months-of-inventory 3.1 in September) and any "relisting chain" analytics claim.

Related entries

Depends on

research-notes Research notes (capture-layer): inside the MLS box — what an Ontario member agent's account exposes, what goes unused, and what they're licensed to do with it (June 2026)

reference RESO DD 2.0 — full resource list with field counts (Property 652, Contacts 91, Member 87, Office 73, …, TransactionManagement 4)

Referenced by (1)

research-notes Research notes (capture-layer): inside the MLS box — what an Ontario member agent's account exposes, what goes unused, and what they're licensed to do with it (June 2026) · relates-to