Revise a sent proposal
When to use this
Use this guide when the client wants changes after seeing the proposal and you need to preserve the original commercial history while preparing a revised version.
What you need first
- the proposal that was sent to the client
- a clear list of the requested changes
- the event data updated if scope or pricing inputs have changed
Step-by-step walkthrough
Start from the sent proposal
Open the event’s Proposal view. A sent proposal is locked, so the workspace will tell you a new version is needed before edits can happen.
Create a new version
Create the revision rather than trying to force the original back into draft. BloomBoard starts a new draft version and keeps the previous one as history, marked Superseded once the new version goes out.
Update the draft version
Adjust the items, fees, notes, or pricing in the new version. If the change comes from the event itself, such as different quantities or a new arrangement, make that change in the event first so the proposal reflects it.
Compare against what the client saw
Review what changed between the old and new versions before sending. The version history shows the differences, which is also useful when explaining the revision to the client.
Send the revised proposal
Send the new version through your preferred channel. The client always sees the latest version, and your history keeps every earlier one intact.
What to remember
- Sent proposals do not go back to draft.
- A new version preserves history and marks the older version as superseded.
- Clients can request changes from their review page, which flags the proposal for revision on your side.
- Accepted proposals are locked commercial history. If something must change after acceptance, treat it as a deliberate re-issue, not a quiet edit.
Do not patch customer-facing changes into the wrong version. If the original and revised documents blur together, approval and invoicing become harder to trust.