Standard Workflow
The standard workflow is the guided path for normal field inspections. 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.
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.
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.
- If a proposal is marked outdated, regenerate it from Review Mode so the attached customer document matches Salesforce.
Related pages
- Roles and Permissions explains why different users see different actions.
- Expert Mode explains the Level 4+ bypass workflow.
Last updated on