Study for the AACWP Certified Wedding Planner exam by organizing content around scope of duty: at every service tier, in every budget line, on every version of the timeline, and in every contract clause, ask who is obligated to act, when, and with what authority. Work through paired concepts rather than isolated definitions, and test yourself with written scenarios where you must name the responsible party and the decision point. Note that administrative details of the credential are set by AACWP directly; confirm logistics on aacwp.org rather than relying on third-party summaries.
Service tiers: why full planning, partial planning, and month-of coordination are different duties, not different sizes
The three common service tiers differ in when the planner's duty begins, not merely in hours worked. Full planning spans engagement to event; partial planning covers defined segments; month-of coordination begins shortly before the event with the couple's own arrangements.
A common confusion is treating month-of coordination as a miniature version of full planning. It is a distinct scope: the couple has already selected vendors and made decisions, and the coordinator's duty is to collect documents, build or verify the event timeline, confirm vendor arrival details, and execute the day. A coordinator who starts renegotiating contracts or re-selecting vendors has usually exceeded the agreed scope, which creates both client friction and professional risk.
Full planning, by contrast, carries duty from the first budget conversation: vendor research, contract review support, design development, and ongoing decision management. Partial planning sits between them, typically covering a defined list of tasks or a defined window. When studying, write each tier as a sentence beginning 'the planner is responsible for...' and check whether the sentence would still be true if you swapped the tier label. If it is, you have merged scopes and should separate them again.
| Dimension | Full planning | Partial planning | Month-of coordination |
|---|---|---|---|
| When duty begins | Early in engagement | At an agreed task list or date | Final weeks before event |
| Vendor selection | Research, shortlists, review support | Only listed vendors or tasks | None; vendors already booked |
| Budget role | Built and tracked with couple | Reviewed for defined items | Not created; status documented |
| Timeline authorship | Developed and iterated | Shared with planner | Compiled from couple's bookings |
| Day-of role | Directs full team | Directs agreed elements | Executes existing plan |
Fixed versus variable wedding costs: budget arithmetic you can actually apply
Wedding budgets divide into costs that hold regardless of guest count and costs that scale per person. Naming each line correctly changes how a planner reacts when the guest count moves, so this distinction deserves deliberate practice.
Variable costs scale with attendance: per-person catering, beverage packages, rentals for place settings, favors, and often invitations. Fixed costs do not move with the count: venue fee, photographer or videographer base coverage, entertainment, planning fee, and much of decor. The practical consequence appears in every budget revision: a ten-guest reduction saves ten multiplied per-person amounts plus related rentals, but it does not shrink the band's fee or the venue's minimum in most contracts.
Work the arithmetic rather than describing it. Suppose catering is 95 per person, rentals add 12 per guest, and the venue charge is 4,000 with a photographer at 3,200. Dropping from 120 to 110 guests reduces headcount by 10, so the saving is 10 x (95 + 12) = 10 x 107 = 1,070, while the 7,200 in fixed amounts stays put. A self-check: take any budget and label every line F or V, then predict the new total if the count drops by fifteen. If your labels and math disagree, you have found a concept to re-study before the exam.
One wedding, three timelines: production schedule, vendor confirmations, and guest itinerary
Professional planning separates the internal production schedule, vendor-facing arrival and setup windows, and the guest-facing itinerary. These documents share times but differ in detail, audience, and who is expected to act on them.
The production schedule is the planner's private operating document: every touchpoint from load-in to load-out, including behind-the-scenes moves like cake table placement during dinner or staging the grand entrance. Vendor confirmations condense this into what each vendor needs — arrival time, access instructions, power needs, strike time — and are sent to that vendor, not broadcast. The guest itinerary carries only what guests act on: ceremony time, transportation, meal choices if required, and significant moments.
An instructive mistake is sending one document to everyone. Guests who receive vendor strike times are confused; a florist who receives only guest-facing times may arrive after access opens, or a DJ reading the full production sheet may announce internal cues. Practice by taking a single evening — cocktail hour through last dance — and writing all three versions. Expected observations: the production sheet has the most rows, the vendor sheet has contact and logistics columns, and the guest sheet fits on one card with no internal staging notes.
Retainer, deposit, cancellation, postponement: reading the contract before the crisis
Contract vocabulary carries decision weight. A retainer compensates for holding a date; a deposit is prepayment applied to the balance. Cancellation and postponement clauses often have different consequences, and the planner's duty is to know which applies before advising.
Scenario one: a couple books a caterer eight months out, paying a signing amount, then a family illness leads them to consider moving the wedding a year. Their instinct is to 'cancel the caterer and rebook later.' The better decision is to read the agreement first: if the payment is styled a retainer for a specific date, cancellation may forfeit it, while a postponement clause may allow the date to move once within a defined window, preserving the payment. Advising the couple to request a postponement in writing — before terminating — can protect several thousand dollars and the vendor relationship.
Why this matters as a study point: certification-level questions about vendor agreements tend to turn on which instrument applies and what the documented terms permit, not on general fairness. When practicing, take any contract sentence and ask three questions — is this money earned for holding the date or a credit toward service, what event triggers this clause, and what does the clause actually require the parties to do. If you cannot answer all three, mark the clause for further study; do not rely on industry rumor about what is standard.
Contingency decisions: making a defensible weather call before weather forces it
Sound contingency planning fixes the decision process in advance: a stated decision time, a named decision-maker, pre-selected alternate configurations, and a vendor communication list. The scenario below shows why improvisation on the day is the failure mode.
Scenario two: a ceremony is planned outdoors with an indoor ballroom as the flip space. The forecast deteriorates two days out. A plausible mistake is deferring the choice to the morning, hoping to keep the preferred setting — which leaves the florist, rental company, and catering team with no time to execute the alternate layout and may conflict with the venue's stated flip deadline. The better decision follows the plan made weeks earlier: at the agreed 1 p.m. call time, the planner reviews the forecast, consults the couple as the named decision-maker, executes the flip, and sends one confirmation message to all affected vendors with the revised access times.
In your written practice, grade weather scenarios on four observations: was a decision time stated, was the decision-maker named, were alternate requirements known per vendor, and was communication sent once and consistently? Scenarios that improvise any of these — changing the layout twice, or letting each vendor decide independently — demonstrate the concept that contingency duty belongs to the plan, not to the planner's judgment on the day. This is scope-of-duty reasoning again: the planner's authority is whatever the documented plan delegated.
Referrals, commissions, and disclosure: ethics as a testable boundary
Ethical study points in wedding planning center on disclosure and client interest: any compensation received for recommending a vendor should be disclosed, recommendations should fit the client's needs, and the planner should be able to explain every referral on its merits.
The concept to internalize is that a referral is a duty to the client, not a revenue line to be concealed. Professional standards in the events industry generally call for transparency about commissions, rebates, or preferred-vendor arrangements, and for offering alternatives when a preferred list does not match the client's budget or style. A planner who recommends a higher-priced vendor because of an undisclosed incentive has placed a personal interest ahead of the client's, which is the classic failure certification study is designed to surface.
Practice with a three-way comparison. First, a planner recommends a florist she has worked with successfully and says so plainly — disclosed experience, no hidden payment, defensible. Second, a planner recommends a vendor who pays her a referral fee she does not mention — the disclosure is missing even if the vendor is good. Third, a planner refuses to recommend anyone outside her paid list even when a client's needs differ — the list has replaced the client's interest. Writing these three cases in your own words is faster and more durable than memorizing an ethics paragraph.
A scenario-based practice sequence and readiness rubric
Prepare with a repeating cycle: study a paired concept, write a scenario applying it, grade the scenario against a rubric, then close gaps before moving on. Readiness is demonstrated by written decisions, not by rereading notes.
A realistic sequence: weeks one and two, build the service-tier table and the fixed-versus-variable budget from scratch without notes, then redo each after two days. Weeks three and four, write the three timeline versions for one detailed wedding and one contract-analysis scenario with the retainer-versus-postponement decision. Weeks five and six, write a full weather-contingency scenario and a referral-ethics case, then assemble a personal glossary of every paired concept. Throughout, keep each scenario to one page and force yourself to name the responsible party, the decision time, and the communication for every decision point.
Use this rubric for every written scenario, scoring each item 0 to 2 for a maximum of 10 points: correct tier or duty named for the planner; contract or plan terms cited before advice given; decision-maker and decision time stated; affected vendors and clients identified with a single consistent communication; budget arithmetic shown where guest count or costs move. Scoring 8 out of 10 on two consecutive scenarios is a learning milestone showing the concepts are holding; re-study any individual item where you scored zero. These milestones measure study progress only, not exam outcomes.
One note on logistics: administrative details of the AACWP credential — requirements, scheduling, and current program structure — belong to the issuing organization, so confirm them at aacwp.org rather than from secondary summaries, then return to scenario practice as the core of preparation.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.