Review Mode
Review Mode is the internal checkpoint between a submitted inspection and a customer-facing proposal. It exists because the customer document should never be the raw output of a field entry: prices, priorities, notes, and the photo appendix all deserve a deliberate look by a qualified user before anything goes to a customer. Review Mode is where that look happens, and it is where the customer proposal is generated — not earlier in the flow.
How it fits
Review Mode opens on an inspection that has already been submitted, so it works against the live Salesforce Opportunity and its line items rather than local draft data.
What you can do in review
| Action | Notes |
|---|---|
| Edit line item pricing | Available to reviewers with pricing rights; a price override changes what the customer sees and what is written back to Salesforce. |
| Adjust priorities | Line item priority drives grouping in the generated proposal. |
| Edit repair notes | Technician notes are stored on the line item, kept separate from the customer-facing description. |
| Add or remove line items | Items can be added from the catalog, and app-linked review items can be deleted; the change is reflected on the Salesforce Opportunity. |
| Curate the photo appendix | Choose which photos appear in the proposal’s photo appendix, and upload additional photos during review. |
| Generate the customer proposal | Produce the PDF/DOCX proposal once the review is right. |
Line item sources
Review Mode distinguishes where each line item came from. An item created by the app during the inspection is marked differently from an item that already existed natively on the Salesforce Opportunity. This matters because deletion and price rules differ: the app can freely manage its own line items, while native Salesforce items are treated as authoritative and handled conservatively.
Stale proposal detection
Once a customer proposal has been generated, the app keeps watching the underlying Salesforce Opportunity. If the line items change afterward — a price edit in Salesforce, an added or removed item, a review edit inside the app — the previously generated proposal is flagged as outdated.
A proposal marked outdated is a signal, not a failure. Regenerate the proposal from Review Mode so the attached customer document matches the current Salesforce line items. Sending a stale proposal is the specific mistake this detection exists to prevent.
Manager review state
An inspection carries a review workflow state that records whether it has been reviewed. This gives supervisors a way to see, across Recent Inspections and the Operations panel, which submitted inspections still need a review pass and which are cleared for a customer proposal.
Who can review
Review rights follow the role ladder:
- Level 2 — review and submit their own inspections.
- Level 3 — review and submit inspections created by other users in the same division.
- Level 4 and Level 5 — the above plus the admin and setup surfaces that support review.
Pitfalls
- Do not generate a customer proposal before the review is actually complete; the staged sequence exists to prevent premature quotes.
- Do not assume Salesforce edits are invisible to the app. The app compares the latest Opportunity line items against the last generated proposal and will flag a mismatch.
- Do not send a proposal flagged as outdated. Regenerate it first so the document matches Salesforce.
- Do not delete a native Salesforce line item expecting the app to treat it like an app-created one; sources are handled differently on purpose.
Related pages
- Standard Workflow shows where review sits in the end-to-end inspection path.
- Salesforce Integration explains the Opportunity and line item records review reads and writes.
- Roles and Permissions explains who can review and submit.