Handle trust transfers
Identify non-arm's-length transfers before they pollute price, appreciation, or market-read conclusions.
Fast read
Use the left sidebar or direct page link named in the guide, then check the visible page title before touching filters, sends, downloads, or billing buttons.
Open the final page, shared link, tracker link, embedded widget, or exported report in the same browser before treating the task as complete.
Copy the URL from the address bar, note the account email in Account Settings, take a screenshot, and include the last button you clicked.
Step-by-step
- Open Data and search the building or unit before interpreting appreciation, median price, or $/SF.
- Scan sale rows for $1, nominal, family, trust, estate, or obviously non-market consideration values.
- Do not include those rows as normal resale evidence. Treat them as ownership transfers unless the record proves an arm's-length sale.
- Open the related unit page when available and check the transaction chain around the suspicious transfer.
- If a trust transfer appears to be polluting a metric, capture the building, unit, date, consideration, and URL so the data row can be reviewed.
Mistakes to avoid
Treating trust transfers, package deeds, or missing registry context like clean market sales.
Changing filters or modes without checking the final rendered surface.
Assuming a highlighted, shared, or pinned item changed source truth instead of presentation or access.
Frequently asked questions
Start with account, URL, selected mode, filters, building or unit, date range, and recipient context. Most confusion comes from looking at the right data through the wrong workflow state.
Most controls change the view, filter, workflow state, access, or presentation layer. Source sale and unit records remain unchanged unless an admin data-sync or data-correction process explicitly updates them.
Open the final surface the client will see and verify that the key evidence, action, label, or next step is visible without needing you to narrate it separately.
Send the account email, URL, building or unit, saved search or report name, timestamp, screenshot, and the exact action you took immediately before the issue appeared.