Event Planner Contract Template

Why the contract is a planning document first

A client contract in event planning gets read twice. It is read once when it is signed, and again when something has gone wrong, usually a few weeks before the date. The first reading is where it earns its keep. Writing down the scope, the payment dates and the cancellation terms forces both of you to decide things that would otherwise be assumed, and assumptions are what surface at the worst possible moment. A couple who believe "full planning" includes the rehearsal and a planner who priced it without the rehearsal are both acting in good faith right up until the week of the wedding.

The contract also protects the date. When you accept a booking you turn away every other inquiry for that day, and in a business where a handful of peak-season Saturdays carry much of the year, a date is inventory. The cancellation clause is what makes that date worth something if the client walks away.

Writing the scope so it cannot be read two ways

Describe the service as a list of things you will do, with numbers wherever numbers exist: how many planning meetings, how many venue visits, how many hours on the day, whether you attend the rehearsal, and whether you set out place cards and favors. Then write the exclusions just as plainly. A line such as "does not include styling, floral design or the purchase of decor items" prevents one very specific argument before it starts.

State who contracts each supplier. If the client signs the caterer's agreement directly, a catering failure is a matter between the client and the caterer, and your job is to manage it on the day. If you contract the caterer and pass the cost on, you carry that supplier's performance, and your wording and your insurance both need to reflect it. Unit 2 of the course works through both arrangements and explains why most new planners are better off starting with the first.

Money, cancellation and postponement

Tie the payment schedule to dates rather than to milestones. "Balance due 21 days before the event" cannot be misread, while "balance due on final confirmation of numbers" invites a debate about when numbers were final. Write cancellation as a sliding scale of dates and the share of the fee retained at each point, so nobody has to calculate "reasonable costs" after the fact.

Postponement needs its own clause because it is a different situation from cancellation. Say how long the client has to choose a new date, whether the fee carries over in full, what happens if the new date falls in a busier season, and when a postponement that is never rescheduled becomes a cancellation. Liability and force majeure wording depends heavily on local law, which is why this guide keeps recommending a single review by somebody qualified where you trade.

A filled-in example

Mistakes to avoid

• Copying another planner's contract. Their clauses were written for their packages, their market and their jurisdiction. The scope clause in particular has to describe the service you actually sell, or it describes somebody else's business. Use another contract as a checklist of topics, never as your wording.
• Leaving the scope as a package name. A phrase like "Gold package" means nothing in a dispute. List what is included in the contract itself, even when your price list describes the same package.
• Treating postponement as cancellation. Without a postponement clause, a moved date becomes an argument about which clause applies. Write both, and make them refer to each other.
• Starting work before it is signed. Holding venues and calling suppliers on a verbal yes gives away all of your leverage. Send the contract and the deposit invoice together, and begin when both come back.