Operations guide

A Clear Change Request Process for Wedding Planning Clients

A step-by-step change request process for wedding planners: intake, impact review, decision authority, fee updates, documentation, and approvals.

6 min readReviewed August 24, 2026Juno product & planning team

The short answer

A wedding planner change request process gives every changed decision, priority, or scope item a single intake point, a documented impact review, a named decision authority, and a record that updates contracts, timelines, and vendor communication together. Instead of tracking changes through scattered texts and email threads, the planner logs the request, reviews cost and schedule impact, confirms who approves it, and pushes the update everywhere it matters.

Where should a change request enter your system?

Every change request needs one intake point, not three. Whether it arrives by email, portal message, or a call, the first step is always the same: write it down in the same place every time, with the date, the requester, and the exact ask.

Clients rarely announce a change clearly. It often shows up as a passing comment in a call, a one-line text, or a buried paragraph in an email about something else. The planner's job is to catch it, name it as a change request, and move it into the log before it gets lost in the conversation it arrived in.

Log the request the same day it is raised, regardless of channel
Capture the exact wording of the ask, not a paraphrase
Note who raised it and whether they hold decision authority
Flag whether it touches budget, vendor scope, or a signed decision
Confirm receipt to the client within one business day

What does an impact review actually check?

An impact review answers three questions before anyone says yes: what does this cost, what does this delay, and who else has to agree. Skipping this step is how planners end up absorbing costs or missing vendor deadlines they never saw coming.

This is not a full re-plan. It is a fast, structured check against the current contract, budget, and timeline to see what the request touches. Some requests are contained to one vendor and one line item. Others cascade into deposits, deadlines, and other vendors' deliverables, and the review is what surfaces that before a commitment is made.

Check current vendor contract terms for change fees or deadlines
Confirm remaining budget room against the specific line item
Identify any other vendor or deliverable affected by the change
Note any deadline that moves if this request is approved
Estimate planner hours needed to execute the change

Who actually has authority to approve a change?

Decision authority should be named before a request ever comes in, not decided in the moment. Usually one primary client contact has final approval, and the planner's own approval threshold for fee or scope changes should be written down too.

Ambiguity here causes the most friction. A change approved by one partner and reversed by another costs time and trust. State clearly, ideally in the contract or onboarding materials, who can approve what, and what happens when co-decision-makers do not agree.

Name the primary approving client contact in onboarding documents
Define what counts as a co-decision requiring both partners
Set a planner-side threshold for changes needing owner sign-off
Record verbal approvals in writing within the same day
Treat silence as a pending request, not an approval

How should scope and fee implications be communicated?

Tell the client the cost and timeline impact before you execute the change, not after. A short, plain summary works better than a lengthy explanation, and it should always separate the vendor's charge from the planner's own fee, if any.

Clients respond better to a clear number and a clear reason than to a vague warning that something 'might cost more.' State the actual impact, reference the original agreement, and give the client a real choice rather than a notification of a done deal.

State the added or changed cost in a single clear line
Reference the original budget or contract line being affected
Separate vendor charges from any planner administrative fee
Give a firm deadline for the client to confirm or decline
Offer one alternative if the original request exceeds budget room

What needs to be documented once a change is approved?

A finalized change record needs the original request, the impact review, who approved it, and the date. This record is what protects both the planner and the client if the same topic comes up again months later.

Documentation is not paperwork for its own sake. It is the reference point when a client asks 'didn't we already decide this' or when a vendor questions why a deliverable changed. A thin record with just a yes or no is not enough; it needs the reasoning attached.

Record the final decision in the same log as the original request
Attach the impact review notes to the approval record
Note the approving party's name and the approval date
Link the record to the specific budget line or contract clause
Store the record where the full client history already lives

How does a change ripple through the rest of the plan?

Once approved, a change has to update every downstream document it touches, not just the one it started in. That means the timeline, the vendor communication, and the budget tracker all need the same update on the same day.

This is where changes quietly fall apart. A planner updates the budget but forgets to tell the florist. A timeline shifts but the day-of schedule still shows the old time. Treat every approved change as a checklist of updates, not a single edit.

Update the master timeline with the new date or deliverable
Notify every vendor whose scope or schedule is affected
Adjust the budget tracker to reflect the confirmed new figure
Update any client-facing summary or portal view of the plan
Confirm each downstream update is complete before closing the request

How often should the change log be reviewed?

Review the open change log weekly during active planning and daily in the final month before the wedding. A request left unanswered for more than a few days creates the exact confusion this process is meant to prevent.

A weekly scan catches requests that stalled waiting on a vendor quote or a client decision. In the final weeks, when timelines are tight and vendor lead times shrink, daily review catches anything that could miss a deadline if left pending even one extra day.

Scan all open requests weekly during the general planning period
Move to daily review once inside the final planning month
Close out any request with a final status: approved, declined, or pending
Escalate any request open more than five business days
Note recurring change themes for the post-wedding debrief

Common questions

Does every change need a formal request, even small ones?

Small preference swaps with no cost or timeline impact can be logged informally in meeting notes. Anything touching budget, vendor scope, or a signed decision needs a written request and a recorded response, even if it takes five minutes.

Who should have authority to approve a change?

Name this in your contract or onboarding documents before changes happen. Typically one primary client contact holds approval authority, with a clear note on what happens if co-decision-makers disagree.

What if a client wants to skip the review and decide immediately?

You can still give a same-day answer, but do the impact check first, even informally. A verbal yes without checking vendor terms or budget room creates problems you inherit later.

How long should change request records be kept after the wedding?

Keep them for as long as you retain other client files, following your studio's general record retention practice. They are useful for post-wedding debriefs and for defending fee decisions if questioned later.

Should change requests live in the same system as the main project timeline?

They should at least link to it. If the request changes a deadline or deliverable, the timeline and the change record need to reference each other so no one works from an outdated version.

Continue the system

Related planner resources