Accounts & Filing
Inspections are filed by account. Every inspection, pool, and job belongs to a customer, and the Accounts view makes that customer the primary way to find work. It exists because a flat, chronological list of inspections answers “what happened recently” but not “what do we have on file for this customer” — and the second question is the one supervisors, estimators, and account managers actually ask.
How it fits
The Accounts browser
The Accounts browser shows one card per customer, each carrying a chip for every pool (body of water) on that account, with the pool’s name on the card. Instead of scrolling a long inspection feed, a user finds the customer first, then drills into the specific pool or record they need.
Cards can be filtered by Division, Branch, and Inspector, and sorted A–Z or Z–A.
Renovation Reviews queue
The Renovation Reviews tab is the manager’s work queue for completed field reviews. It exists because a completed review is a piece of work owed to somebody, and a chronological inspection feed cannot express that.
Each row carries the review’s current rung in the review → proposal pipeline:
| Chip | Meaning |
|---|---|
| In Progress | The tech is still walking the pool |
| Awaiting Review | Completed; nobody has looked yet |
| Reviewed by Manager | Read and flagged, no notes written |
| Awaiting Proposals | Notes submitted; the proposal team owes work |
| Proposals Complete | Proposals built and linked |
| Sent to Customer | Closed out |
The queue filters by inspector, division, and branch, and every row offers its PDF report directly. A Request outstanding chip marks reviews where the field is still working on a Manager Request, with a matching filter — it counts both unanswered requests and answered ones nobody has accepted yet, because both are live work. The same chip appears on account rows.
The one-tap Mark Reviewed action, the queue itself, and per-row PDFs are available in every division. Only the fuller notes-and-proposals workflow is limited to pilot divisions.
The account page
Opening an account collects everything on file for that customer in one place — the inspections that have been run, the bodies of water on the account, and the Job Documentation captured against its pools. Inspection rows show who ran each inspection, so the account page doubles as a quick history of activity for that customer.
Grouping Recent Inspections by account
Recent Inspections can be grouped by account with a toggle. The default remains the chronological view for “what happened recently,” while the grouped view rolls the same records up under their customer for “what do we have for this customer.” Both read from the same data; the toggle only changes how it is arranged.
Why account-first matters
Account-first filing is the shared entry point for the newer flows. A Renovation Review (Field) starts by picking the account and then the body of water; Job Documentation hangs off the pool on that account. Filing by account keeps those pieces connected instead of scattered across separate lists.
Pitfalls
- Do not rely only on the chronological Recent Inspections list to find a customer’s history; the account page is the complete view.
- Do not create a duplicate customer or pool when one already exists on the account; start from the Accounts browser to confirm what is already on file.
- Do not assume grouping by account changes permissions. Grouping only rearranges records the user could already see.
- Do not read a Request outstanding chip as merely informational. While it is showing, that inspection cannot be deleted by a Level 4 — it escalates to Level 5 only.
- Do not expect the notes-and-proposals controls on every review. The queue and Mark Reviewed are universal; the fuller pipeline is division-gated.
Related pages
- Standard Workflow covers the inspection path and the Recent Inspections list that can group by account.
- Renovation Review (Field) uses the account-first start.
- Job Documentation is the per-pool media that appears on an account.