Review → Proposal Pipeline

A completed Renovation Review (Field) is not the end of the job — it is the beginning of a quote. Before this pipeline existed, that hand-off happened by email: a regional manager read the report, typed findings into a message, and hoped the proposal team read it the same way. Nothing recorded who owed what, so a review could sit for a week with everyone assuming somebody else had it. The pipeline exists to make that hand-off a tracked state on the review itself rather than a thread in somebody’s inbox.

The reviewer reads the report, writes note lines, and adds gallery photos on one screen, then submits those notes to the proposal team. Each note line can become its own linked proposal. The review carries a status the whole way, so the Renovation Reviews queue can always answer “what is waiting on me”.

This workflow is limited to pilot divisions while it is evaluated. Availability is decided by the review’s division, not yours — so an admin in Maryland opening a North Jersey review sees the workflow, and a North Jersey manager opening a Houston review does not. If you expect these controls and cannot see them, your division is not in the pilot yet. See Deployments for the switch itself.

The six rungs

Every renovation review sits on exactly one rung. The status is derived from timestamps recorded as the work moves, and it is evaluated most-final-first — so a review that has been sent to the customer reads as Sent to Customer regardless of which earlier stamps it also carries.

Rung	What it means	Who moves it off
In Progress	The tech is still walking the pool.	The field tech, by completing
Awaiting Review	Completed and nobody has looked yet.	Any Level 2+
Reviewed by Manager	The one-tap flag: someone read it, no notes written.	Any Level 2+
Awaiting Proposals	Notes submitted; the proposal team owes work.	Level 4+
Proposals Complete	Proposals are built and linked.	Level 4+
Sent to Customer	The terminal rung — nobody owes this review anything.	—

Reviewed by Manager and Awaiting Proposals are deliberately distinct. The one-tap flag means “I read it”; submitting notes means “I read it and the proposal team now owes work.” Keeping them apart is what lets a proposal manager filter the queue down to exactly the reviews that owe proposals.

Who does what

Two role floors govern the pipeline, and they are different on purpose.

Action	Floor	Why
Mark Reviewed (one tap)	Level 2	The same floor that reviews the work in the first place
Write and submit review notes	Level 2	Same reviewer, same screen
Create or link a proposal	Level 4	”Create proposal” seeds the Expert Mode builder, so it inherits Expert Mode’s floor
Mark Proposals Complete	Level 4	Closes out the proposal team’s obligation
Mark Sent to Customer	Level 4	The terminal rung

Submitting review notes locks them permanently. There is no edit and no unlock — not for the author, not for a Level 5 admin. Anything you think of afterwards travels by email. Write the notes as though you are sending them, because you are.

Why lock at all? A proposal manager builds quotes against what the notes said at submission time. If notes could change afterwards, a proposal could silently stop matching its own brief, and nobody would know which version was quoted.

Working a review


Renovation Reviews queue
  └── open a completed review
        ├── read the report            (the tech's answers and photos)
        ├── write note lines           (one line per finding worth quoting)
        ├── add gallery photos         (same screen, no separate upload step)
        └── Submit notes ──> Awaiting Proposals
                               └── L4+ links a proposal per note line
                                     └── Proposals Complete ──> Sent to Customer

Reviewer notes, the photo gallery, and the report all live on one screen, so reading and writing do not require moving between pages. Each note line is independently linkable to a proposal — a review with five findings can carry five separate quotes rather than one bundled document.

Turning a division off

The gate is a kill switch, not a delete. Removing a division hides the UI and makes the routes refuse, but every row — notes, proposal links, requests, and timestamps — stays exactly where it was. Re-adding the division restores all of it untouched.

Before switching a division off, cancel every outstanding Manager Request on it first. An inspection with an outstanding request requires a Level 5 admin to delete, and that escalation is deliberately not gated by this switch — but Cancel is. Turn the division off with requests still open and there is no in-app way to clear them, leaving those inspections undeletable by any Level 4 indefinitely.

Pitfalls

Do not expect to edit submitted notes. The lock is permanent by design; send additions by email.
Do not assume the workflow follows the viewer. It follows the review’s division, so the same user sees it on one review and not another.
Do not read a missing control as a bug. An unset or blank division list means nobody gets the workflow — this gate fails closed, unlike the sign-in domain gate, which fails open.
Do not switch a division off while requests are outstanding. Cancel them first, or you strand those inspections behind a Level-5-only delete.
Do not treat Reviewed by Manager as equivalent to Awaiting Proposals. Only the second one tells the proposal team they owe work.

Renovation Review (Field) is the field capture that feeds this pipeline.
Manager Requests is how a reviewer sends work back to the field mid-pipeline.
Accounts & Filing documents the Renovation Reviews queue and its filters.
Roles and Permissions explains the Level 2 and Level 4 floors used here.
Expert Mode is the builder a linked proposal opens into.