Create and send a proposal
Proposals is where a job gets priced and sent to a customer before it's booked — a repair quote, an equipment replacement bid, or a rental proposal. A proposal starts as a draft, moves to sent once you send it to the customer, and lands on approved, declined, or expired.
Create a proposal
Start from New proposal, pick the customer and site, and build the scope from the Price Book. A proposal can carry more than one tier — a good/better/option set the customer chooses between — instead of one fixed price. You can also start a proposal directly from a job's inspection deficiencies; see Manage inspections.
If your org requires internal approval before a proposal goes out, mark it internally approved first — see Money topics.
Send it and track the response
Send moves the proposal from draft to sent and makes it visible to the
customer at its own link (/proposal/[id]). From there:
- Send a reminder if it's gone quiet.
- Request a deposit if the job needs one before work starts.
- The customer accepts a tier, which moves the proposal to approved, or the proposal can be marked declined.
- A sent proposal that runs past its expires on date without a decision shows as expired.
When a proposal is approved
An approved proposal is ready to become real work — the tier the customer picked is what carries forward. Duplicate a proposal to reuse its scope on a similar job, or archive one that's no longer relevant.
Money topics
- A proposal only becomes billable work once it's approved with a tier chosen. Advancing straight to "approved" without a tier selected would leave nothing priced — the UI won't let you skip that step.
- Internal approval, if your org requires it, is separate from the customer's approval — it's a draft-stage gate before the proposal can be sent at all, not something the customer sees.
Reference
- Proposal status values — draft, sent, approved, declined, expired.
- Who can reach Proposals — Owners and Office users. See Roles & permissions.