Standard Workflow
The standard workflow is the guided path for a normal Spring field inspection. It is intentionally staged because users should not jump straight to customer proposals before the inspection has been completed, synced, reviewed, and submitted correctly. The sequence reduces duplicate documents, stale Salesforce line items, and customer-facing quotes that were generated before internal review was finished.
While the company-wide renovation push is on, a new inspection defaults to Renovation Review (Field). To run the Spring workflow described here, switch the Inspection Type to Spring on the New Inspection screen.
Starting an inspection
Inspections are filed by account. A new inspection starts by picking the customer account and then the body of water being inspected, so the record is attached to the right pool from the first tap. Houston uses its own inspection structure, selected automatically for Houston work.
The New Inspection screen uses plain language rather than CRM terms, and if the pool you are standing at is not in the list, you can still start a review for it.
The 90-day duplicate warning. If the same pool was inspected in the last 90 days, the screen says so before you begin — including reviews someone else started or is still working on. Two techs dispatched to the same site is the exact waste this catches, so read the warning before continuing. It warns; it does not block.
A double-tap or a dropped connection while starting can no longer create duplicate inspections.
Role-specific path
| Role | Main capability | Salesforce submission |
|---|---|---|
| Level 1 | Create inspections and capture notes/photos | No |
| Level 2 | Create inspections, see pricing, use Other Repairs | Own inspections |
| Level 3 | Level 2 plus same-division review/submission | Same-division inspections |
Workflow stages
Operational rule
Customer proposal generation belongs inside Review Mode. That keeps the workflow clean: field completion first, Salesforce Opportunity second, review third, customer-facing proposal last.
Offline behavior
The app is offline-first once an inspection has been opened online. That is what lets a tech keep working after service drops in a mechanical room or a remote site:
- Section drafts are kept in browser storage as they are filled in.
- Photos are queued on the device and upload in the background when the connection returns.
- Report generation and completion are gated until queued offline work has finished syncing, so a proposal is never built from a half-uploaded inspection.
Open the app while connected at least once so it can load; after that, the field form and photo capture keep working through connectivity gaps.
Pitfalls
- Do not use a generated customer proposal before review is complete.
- Do not assume Salesforce edits are invisible to the app. The app compares the latest Salesforce Opportunity line items against the latest app-generated proposal state and flags a mismatch as outdated.
- If a proposal is marked outdated, regenerate it from Review Mode so the attached customer document matches Salesforce.
- Do not force-complete an inspection while photos are still queued offline; let the sync finish so the report and proposal are complete.
Related pages
- Renovation Review (Field) is the photo-first alternative to this priced flow, and the current default type.
- Review Mode explains the review and proposal-generation step.
- Accounts & Filing explains the account-first start and Recent Inspections.
- Roles and Permissions explains why different users see different actions.
- Expert Mode explains the Level 4+ proposal workflow.