Operations guide
A Wedding Planner Proposal and Pricing Review Process
A practical process for reviewing, versioning, and updating wedding planner client proposals so pricing and scope stay accurate and disputes stay rare.
The short answer
Wedding planners need a clear process for reviewing and updating client-facing proposals and pricing documents before they go stale, get miscommunicated, or create scope disputes. This means assigning an owner for every active proposal, setting a review cadence tied to key milestones, tracking which version a client last saw, and defining exceptions for rush requests or vendor price changes so nothing gets sent out of date.
Why does a proposal need a review process after it is sent?
A proposal is not a static document once it leaves your outbox. Vendor pricing shifts, guest counts change, and clients often negotiate verbally before anything is written down, so the original file can become inaccurate within weeks.
Treat every sent proposal as a living record until it converts to a signed agreement or is formally closed. If you skip review, planners end up working from memory instead of the actual document, which creates mismatched expectations at signing and awkward conversations mid-planning when a client references a number that no longer applies.
- Assign a review owner the moment a proposal is sent to a client
- Flag any proposal untouched for more than 30 days for a manual check
- Treat verbal pricing discussions as pending updates, not final terms
- Close out proposals that go cold instead of leaving them open indefinitely
What should trigger an immediate proposal update?
Certain events should trigger an update the same week, not at the next scheduled review. These include vendor price changes, guest count shifts past a set threshold, added services, and any client request that changes scope.
Build a short trigger list your team checks against every incoming vendor quote or client email. If an event on the list occurs, the proposal owner updates the document and confirms with the client in writing before any new invoice or contract references it. This keeps the paper trail consistent and avoids disputes over what was agreed to and when.
Common questions
How often should a proposal actually be reviewed?
Review any open proposal at least every 30 days, and immediately after a vendor price change, scope change, or client request. Proposals tied to a near-term deadline should be checked weekly until signed or closed.
Who should own proposal accuracy on a small team?
One named person, usually the lead planner or studio owner, should own final review even if an associate drafts updates. Shared ownership without a single accountable reviewer is how outdated versions get sent.
What if a client already signed an outdated version?
Document the discrepancy, note the date the change occurred, and address it directly with the client before proceeding with any new work. Do not silently apply new pricing to a signed agreement.
Should verbal pricing conversations count as a proposal update?
No. Any verbal discussion of price or scope change should be followed by a written update to the proposal record within a set number of business days so the file matches what was actually discussed.
Continue the system
Related planner resources
Turn this guidance into a repeatable process for your planning team.