Define exactly what you own, what the couple owns and what vendors own.
Think like a planner before you plan anything.
A professional planner does not start with flowers, colors or vendor lists. The first job is to turn a couple’s hopes, constraints and decision dynamics into a planning system that can survive real-world tradeoffs.
Finish with work product—not notes.
By the end of this module you will have built a client scope map, discovery notes, a wedding brief, a budget architecture and a dependency-aware planning roadmap for a realistic simulated couple.
Ask questions that reveal priorities, constraints, decision dynamics and risk.
Convert scattered ideas into ranked priorities and operating requirements.
Spot financial conflicts before a venue or vendor contract locks them in.
Sequence decisions by dependency instead of using a generic checklist.
The planner’s real job is decision architecture.
Couples rarely need another person who can make a checklist. They need someone who can reduce uncertainty, identify dependencies, keep commitments visible and protect the few priorities that matter most when budget, time and vendor constraints collide.
That starts with scope. A planning relationship becomes fragile when the couple believes “the planner handles everything” while the planner believes a task belongs to the couple or venue. Professionalism begins by making ownership explicit.
Three service scopes that must not blur together
Planner leads the planning system from early strategy through vendor coordination and wedding-day execution.
Planner owns a clearly defined subset of planning work; existing decisions and contracts must be audited before taking over.
Planner operationalizes an already-planned wedding near the event date. It is not a disguised full-planning package.
Personal decisions, approvals and any tasks excluded from scope stay visible with deadlines and dependencies.
Discovery is not “What colors do you like?”
The highest-value discovery questions expose decision criteria. Before recommending venues or vendors, learn what the couple is optimizing for, what would disappoint them, which constraints cannot move and how decisions are actually made.
A discovery conversation in five passes
What do they want guests and themselves to remember about the day?
Which three elements deserve protection if tradeoffs become necessary?
Budget ceiling, guest realities, date flexibility, location, accessibility and family obligations.
Who decides, who influences and what topics are already creating friction?
What existing commitments, assumptions or deadlines could narrow options quickly?
The venue-first couple
Maya and Chris want 140 guests and have a $30,000 total budget. They love a venue whose catering minimum and mandatory fees could consume roughly half the budget before photography, attire, entertainment, florals, transport, stationery or contingency.
The wedding brief becomes the source of truth.
A good brief converts adjectives into planning requirements. “Elegant and relaxed” is not actionable until it is translated into guest experience, service level, venue characteristics, schedule, design boundaries and budget priorities.
Brief essentials
What the event should feel like and what memories matter most.
Three protected priorities plus explicit lower-priority areas.
Budget ceiling, guest range, location/date limitations, access needs.
Who approves, response expectations and how changes are documented.
Preference vs requirement
“We love outdoor ceremonies.”
Outdoor ceremony only if a credible rain plan keeps the same guest capacity and accessibility.
“Food is really important.”
Catering experience is a top-three protected budget priority; venue shortlists must allow the required service model.
Budget is a constraint system, not a spreadsheet total.
Early budget work is about preventing irreversible mistakes. A planner should not pretend there is one universal allocation formula. Instead, test whether large commitments leave enough capacity for the couple’s protected priorities and known mandatory costs.
Budget Constraint Simulator
Move the venue + catering share and watch how much remains for every other category. The point is not to prescribe a universal percentage—it is to expose a constraint before a contract is signed.
Sequence decisions by dependency.
A generic 12-month checklist hides the logic of the project. A professional roadmap makes dependencies visible. You should know which decisions unlock other work, which deadlines are contractual and which tasks can safely wait.
Dependency-first planning sequence
Brief, priorities, constraints and decision owners come first.
Date, venue, guest-capacity assumptions and major budget implications.
Prioritize categories whose availability or decisions affect later planning.
Make aesthetic and guest-flow decisions inside confirmed operational constraints.
Finalize timeline, logistics, confirmations, responsibilities and contingency plans.
Build Maya & Chris’s first planning package.
Use the client brief template to document priorities, constraints, unresolved questions, decision ownership, the initial budget architecture and the next five planning decisions. Your work product—not quiz completion—is the point of the module.
Open printable client briefNow inspect the complete curriculum before deciding.
The founding reservation remains refundable and does not obligate you to enroll.