Slow Page
Use slow page with the right account, visible state, final-surface check, and escalation packet.
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 the exact page that produced the issue and reproduce slow page from the exact URL or workflow where the problem appeared.
- Write down the visible page title, selected filters, building/unit/report/search name, and account email before refreshing or changing anything.
- Click the same control once and wait for the page to update. Do not double-click sends, checkouts, exports, or save buttons because that can create duplicate state.
- Open the final destination surface if one exists: shared link, tracker link, exported PDF, embedded page, report, unit, or billing card.
- Compare what you expected with what is visible on that final surface, then capture the mismatch in one screenshot.
- 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
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.