Price Band Analysis
Use price band analysis without losing sale-quality context, source nuance, or the final number a client will rely on.
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 Analytics from the left sidebar and wait for the KPI cards and Building Performance table to populate.
- Set the building scope first for price band analysis: keep All Buildings, remove building chips, or click Add Building and choose the exact buildings.
- Set the relevant filter chips one by one and watch the KPI row/table update after each change so you know which control moved the number.
- Click table headers or chart controls only after the filters are correct. Sorting changes ranking; it does not change the underlying filtered sale set.
- Before quoting or sharing the analysis, read the visible building scope, date window, row count/closed sales count, and filter chips out loud to yourself.
- If the expected result does not happen, copy the full URL from the browser address bar, open Account Settings and note the signed-in email, take a screenshot of the current page, and write down the last button or link you clicked.
Mistakes to avoid
Quoting a chart without naming the filter set, date window, and sale-quality assumptions.
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.