Build and send a proposal
Prepare the customer package, review generated details, and send only the version you approve.
A priced package the customer can read and accept, with the version you approved recorded as the one that went out, so an argument about what was quoted has an answer.
Before you start
- A customer
Choose the customer who will receive the proposal.
- Reviewed scope and quantities
Confirm the work, quantities, options, and exclusions before sending.
- Payment and warranty terms
Have the terms your company intends to offer ready for review.
Follow the task on screen.
- Step 1. New proposalOpens the proposal intake on this page.
- Step 2. All recordsEvery proposal regardless of state. The filters beside it narrow to one lifecycle stage.
- Step 3. SentWhat has actually gone out. Draft sits to its left, Accepted to its right.
- Step 4. Needs reviewProposals FL Permit Pay is holding back until a person resolves the notice on them.
- 1Marker 1 on the screenshot
Start the proposal
Select New proposal. The intake opens on this page, below the header.
You know it worked when The proposal intake fields appear and are ready for the customer and job.
- 2Not on this screen
Review the scope before anyone else sees it
Open the proposal and work through the scope, quantities, exclusions and terms, using Options for the good/better/best tiers you want the customer to choose between. Generated quantities and prices are working inputs, not an approved quote.
You know it worked when The internal package reflects what your company intends to offer.
- 3Marker 4 on the screenshot
Clear anything sitting in Needs review
Use the Needs review filter to find proposals FL Permit Pay is holding back, and resolve each notice before sending.
You know it worked when The proposal leaves the Needs review filter once every notice is resolved.
- 4Marker 3 on the screenshot
Send the version you approved
Confirm the recipient, then select Send to customer. The lifecycle filters across the top (Draft, Sent, Accepted) are where you watch what happened next.
You know it worked when FL Permit Pay records the send attempt. A recorded send is not proof of delivery; uncertain delivery still needs a phone call.
You are finished when
The reviewed proposal is shared with the customer
FL Permit Pay records the send attempt and keeps the current proposal lifecycle visible for follow-up.
What still needs your review
- Generated estimates require reviewGenerated quantities and prices are working inputs. A person must review them before sending.
- A send is not guaranteed deliveryA recorded send can still have uncertain delivery and may require direct customer follow-up.
- Accepted proposals are lockedThe accepted snapshot protects what the customer agreed to; changes require a new version or workflow.
If the screen looks different
The workspace can be in any of these states when you arrive. Find the one in front of you.
Confirm the proposal appears in the workspace before moving on.
Use the page's first-record action when no proposal exists yet.
Wait for the workspace to finish loading before selecting a record or action.
Use the retry shown on the page. Do not treat an error as an empty record set.
Reconnect before saving. Keep the page open so entered details are not mistaken for a saved record.
Read the availability note and verify any missing source details before acting on them.
Ask an organization owner for the capability named in this guide.
Review the access notice shown in FL Permit Pay before continuing.
Troubleshooting
The proposal will not send.
Open it from the Needs review filter, resolve the notice shown on it, and confirm your role has proposal and email-send access.
Supplier pricing is marked stale.
Refresh and review the affected generated lines before sending.