How to Review an Event Contract: A Clause-by-Clause Checklist

How to review an event contract before you sign Almost every event dispute traces back to four questions the contract should answer without argument: what exactly is being delivered, what happens to the money if the event is cancelled or postponed, who carries the risk if something goes wrong on the day, and who holds each permit. Read the contract with those four in mind and the weak clauses stand out fast. Work through the checklist below clause by clause. Whether you are the host or the provider, the test for each clause is the same: is the rule clear enough that a dispute could be settled by reading it? This is general information, not legal advice; for a large or high-value event, have a lawyer check the final draft. ## The clause-by-clause checklist ### 1. The event and the scope

• Are the date, timings, access time and venue exact? Is there a detailed scope (a schedule or run sheet), and does it say that anything not listed is excluded?
• Red flag: a one-line description of the services with no schedule, so each side has a different picture of what was bought. ### 2. Fees, deposit and payment
• Is the fee clear, is GST stated, and is the pricing basis (fixed, per plate, per hour) defined? Are the deposit and balance dates set?
• Red flag (host): a large non-refundable deposit with no matching commitment from the provider. Red flag (provider): the balance due only after the event, leaving you exposed if the host does not pay. ### 3. Final numbers and minimum spend
• Is there a date by which guest numbers are locked, and is there a minimum billed count or minimum spend?
• Red flag (host): a high minimum you may not reach. Red flag (provider): no cut-off date, so a last-minute drop in numbers leaves you with committed cost and no cover. ### 4. Cancellation
• Is there a sliding scale of cancellation charges tied to how close to the event the cancellation falls?
• Red flag: a flat 100% charge regardless of notice, or, from the provider side, a term letting it cancel and keep the deposit with no consequence. ### 5. Postponement
• Can the event be moved to a new date, on what terms, and within what window?
• Red flag: no postponement option at all, so a minor date change forces a full cancellation and full charge. ### 6. Force majeure
• Does it cover natural disaster, government order, epidemic and similar events, and does it say what happens to money already paid?
• Red flag: no force majeure clause, or one that protects only the provider and lets it keep all sums paid even when the event is stopped by law. ### 7. Permits and licences
• Is responsibility for each permit assigned: venue and trade licence, fire and police permissions, music or performance licence, FSSAI for food, liquor licence?
• Red flag: silence on licences, so a missing permit on the day becomes a fight about whose job it was. ### 8. Liability and indemnity
• Is the provider's liability capped at a sensible figure, are indirect losses excluded, and are death and personal injury carved out of the cap?
• Red flag (host): the provider excludes almost all liability, including for its own negligence. Red flag (provider): uncapped liability for a modest fee. ### 9. Insurance
• Does the provider hold public liability insurance at a sensible level, and will it show a certificate? Is event insurance for the host considered?
• Red flag: no insurance requirement for a large gathering, where injury or property damage is a real risk. ### 10. Damage and security deposit
• Is any refundable security deposit clearly defined, with a fair basis for deductions and a date for return?
• Red flag: an open-ended right for the venue to keep the deposit for vaguely described damage. ### 11. Vendors and exclusivity
• Can the host bring its own vendors (caterer, decorator, DJ), or does the venue require its panel, and at what cost?
• Red flag (host): forced use of in-house vendors at undisclosed prices, or a corkage or outside-vendor fee you were not told about. ### 12. Conduct, timings and overruns
• Are rules on noise, end times and overrun charges clear?
• Red flag: heavy per-hour overrun charges that are easy to trigger and were not flagged up front. ### 13. Governing law and disputes
• Is the governing law stated and the forum fair and convenient?
• Red flag: an inconvenient exclusive forum that makes a modest claim uneconomic to pursue. ## Read it in this order Do not review an event contract top to bottom. Start with the scope and the final-numbers clauses (1 and 3), because they decide what you are actually getting and paying for. Then read cancellation, postponement and force majeure together (4, 5 and 6), because they decide what happens to the money if the day changes or does not happen. Only then check liability, insurance and the housekeeping. Reviewing in that order keeps your attention on the clauses that move the most money. ## A quick note on the law An event contract is a services contract governed in India by the Indian Contract Act, 1872, with GST on the services and sector licences such as FSSAI for food and state excise rules for liquor. Consumer-protection rules may also apply where the host is a consumer. The commercial structure is similar across jurisdictions, but licensing and consumer rules differ, so for the UK, Ireland, Singapore, Australia or the US, check local requirements. This is not legal advice. ## Where a contract workspace helps Reviewing one event contract by hand is manageable. The strain shows when you run many events: catching a weak force majeure before the next washout, applying a consistent cancellation ladder, and tracking deposits and final-count cut-offs. Drafting, reviewing, tracking and governing event contracts can sit in one AI workspace tuned to how your company runs its events. Adira is built around that single workspace.