Quick answer
A wedding scope change should move through request, impact review, authorised approval and confirmed handover before it becomes an operational instruction. Record what changes in work, timing and cost, and separate a proposed request from an agreed commitment. Planno helps organise wedding and vendor responsibilities; the agency owns commercial approvals.
Key takeaways
- A request in a family chat is not automatically permission to order additional work.
- Review schedule and guest effects alongside quoted cost.
- Update the approved operating record and notify affected owners after the decision.
Small additions can change several workstreams
A family asks for another performance, additional decor or a new guest group. The request sounds simple in conversation, but it may affect production time, supplier scope, invitation eligibility, meals or transport. If a coordinator agrees immediately without reviewing those effects, the team can create obligations nobody has approved. Scope control is a way to make helpfulness deliverable, not a reason to resist every client change.
Begin with the agreed service and supplier commitments. Planno provides the planner's wedding, vendor and payment-tracking workspace, while the included Wedence guest experience handles the invitation and guest journey. Both need to reflect approved decisions. Neither should turn a tentative family idea into a final vendor instruction before the appropriate people have agreed it.
Define the approved baseline
The baseline describes the agency's service, functions, suppliers, relevant guest arrangements and approval rules. Keep it understandable enough that a colleague can identify what has changed. If the original proposal says guest coordination but never states the service boundary, later requests will be harder to classify. Clarify the boundary early rather than arguing about wording when the wedding is close.
Name the people authorised to approve different decisions. The couple may approve design, a parent may approve supplier spending and a hotel contact may confirm inventory. A family member can make a valid request without having authority to commit every affected workstream. Your process should allow the request to be considered while preserving the approval boundary.
Capture the request without promising the result
Record what the client wants, which function or service it affects and when a decision is needed. Ask enough questions to understand the requested outcome. Add more decor is not a usable supplier brief; another guest group may mean different functions or hospitality expectations. The coordinator should acknowledge the request and explain the next review, rather than confirming work that has not been assessed.
An adaptable response is: We have recorded the request for [change]. We will review the supplier scope, schedule and any guest-service effect, then share the proposed arrangement for approval by [date]. Until that review is complete, the existing approved plan remains the operating instruction. Replace the placeholders and use wording appropriate to your client relationship.
Review four kinds of impact
First review the work: what changes in deliverables or staffing? Then review timing: what needs to happen earlier, later or in a different sequence? Review guest effects: do invitations, replies, rooming or transport need attention? Finally review the commercial effect according to the supplier and agency arrangements. A cost-neutral request can still create a serious schedule dependency.
| Review area | Question to resolve |
|---|---|
| Work | Which deliverable or responsibility changes? |
| Timing | Which access, setup or function activity is affected? |
| Guests | Which invitation, count or hospitality decision changes? |
| Supplier | Has the relevant vendor confirmed feasibility? |
| Commercial terms | What amount or agreement needs approval? |
| Communication | Who receives the revised instruction? |
Use the table to prepare a short proposal rather than a long internal discussion for the family. The approver needs to understand the outcome, trade-offs and decision. Keep supporting supplier detail in the appropriate business record. Do not present a vendor's preliminary estimate as an agreed amount before the quotation and scope are confirmed through your usual process.
Treat guest-driven changes carefully
A late attendance correction may affect several plans, but it is not automatically a new commercial guarantee. Review the relevant supplier cutoff and counting rules before revising meals or rooms. Wedence's wedding RSVP gives function-specific reply information; the planner and authorised family contact decide what that information means for the agreed vendor commitment.
Similarly, adding a household to the guest list may require an invitation-group decision and a hospitality review. Do not assume every added guest is invited to every function or covered for every hotel night. Keep the guest record accurate while separately obtaining the approvals needed for the service arrangement.
Present the change for an explicit decision
Summarise the requested change, confirmed scope, timing effect, commercial effect and the approval needed. State any conditions or unresolved dependency. The family should know whether it is approving a complete arrangement or allowing the planner to investigate further. Those are different permissions and should not be merged into a vague sounds good response.
Where the decision is time-sensitive, explain the actual deadline and why it matters. Avoid creating artificial urgency when the supplier has not established a cutoff. If the requested outcome cannot be delivered within the confirmed constraints, offer the feasible alternative with its own approval requirement. A clear no or revised option is more professional than an enthusiastic promise the production team cannot fulfil.
Update the operational plan after approval
Once the authorised decision is recorded through your agency's process, update the relevant workstream information. This may include vendor milestones, the run sheet, invitation groups or guest instructions. Name the owner for each update and confirm completion. A change is not fully handed over because the family approved it; the people performing the work must understand the revised requirement.
Planno's documented workspace can support the wedding responsibilities and vendor payment review, but this article does not promise a dedicated automated change-request module. Use the supported workflow demonstrated by the team and retain commercial evidence in your normal document process. The important principle is that the planner's current operating information should describe approved commitments.
Control guest-facing communication
If the approved change affects a venue, time or arrival instruction, publish one clear revision through the agreed owner. Explain which function changed and what guests should now do. Wedence's guest messaging is a relevant destination for the communication capability included in the ecosystem. Review the supported sending process and keep the website and messages consistent.
Do not broadcast an internal option before the decision is made. Guests should receive an instruction they can act on, not an unresolved production discussion. The family and supplier may need more detailed internal information than the guest. Prepare the right level of detail for each audience so one update does not create new confusion across the wedding.
Review open changes before final readiness
At the final review, distinguish requested, under review, approved and handed over. A task marked approved may still need a supplier acknowledgement or guest communication. Check that the latest run sheet and vendor commitments reflect the decision. If a request was declined or withdrawn, make that visible to coordinators who may otherwise keep pursuing it.
Also check whether two changes conflict. An added performance can affect meal timing; an earlier transport departure can affect family readiness. The planner's value lies in seeing those interactions, not merely listing requests. Use the run-sheet template to review dependencies before wedding-day activity makes detailed discussion harder.
Improve the next client agreement
After delivery, identify which requests caused confusion and why. The issue may be an unclear original package, a missing approver or a rushed supplier handover. Update the onboarding questions and service description accordingly. Scope control should become a normal part of a transparent planning relationship rather than an emergency procedure brought out only during disagreements.
Planno and Wedence are a strong foundation for connecting professional coordination with guest information. Request a demo with a late function addition and a changed guest requirement. Ask how your team can keep the approved plan understandable while preserving the commercial decisions your business must manage separately.
Planno brings your enquiries, client weddings, vendors, payments and team together, with per-function RSVP and WhatsApp invites for every couple. Free for 2 months.
Try Planno freeFrequently asked questions
Not necessarily. Follow the agreed authority and approval process, with the scope and impact made explicit before treating the request as a commitment.