Parties
Full legal names and entity types for organizer and vendor, including DBA names, mailing addresses, and a designated contract contact for notices.
A clear Event Festival Agreement reduces misunderstandings, assigns liability, and documents permit and insurance responsibilities. It preserves the organizer’s ability to manage safety and compliance while protecting vendors with defined payment, access, and cancellation terms.
Multiple stakeholders use or complete Event Festival Agreements depending on the role: organizers, vendors, venues, and municipal permitting offices.
Each signer should ensure they have authority to commit insurance, indemnity, and payment obligations before executing the agreement.
Full legal names and entity types for organizer and vendor, including DBA names, mailing addresses, and a designated contract contact for notices.
Clear description of services, booth size or performance slot, technical riders, setup/load-in times, and deliverables — avoid vague language that creates disputes.
Total fee, deposit amount and timing, refund and cancellation rules, accepted payment methods, and any security deposit or holdback conditions.
Minimum liability limits, additional insured wording, required certificates of insurance, and responsibility for local permits and vendor licenses.
Mutual or unilateral indemnity clauses, limitations on consequential damages, and allocation of responsibility for property damage or personal injury.
Events of default, cure periods, organizer’s right to remove noncompliant vendors, and the effect of force majeure or public health orders.
| Field | Configuration |
|---|---|
| Signature Authentication | Email link or SMS two-factor authentication |
| Conditional Fields | Show insurance upload only if vendor selects a particular option |
| Template Variables | Pre-fill party names, event dates, and fees |
| Reminder Schedule | Automated reminders 14 and 3 days before deadlines |
Agreements can be shared via secure email links, embedded signing pages, or integrated directly from event software to reduce friction.
Choose methods that preserve an audit trail (timestamp, IP, signer attribution) and align with your document retention policy; integrations reduce manual upload errors and centralize record storage.
Submit permits 30–60 days before event in many jurisdictions
Provide COI at least 14 days before load-in
Final balance due 7–14 days prior to event
Execute contract before booth allocation or rehearsal
Material changes requested 10–14 days before event
Agreement signed and executed; assigns booth or performance slot
Required permits applied for with executed agreement attached
Certificate of insurance delivered and reviewed by organizer
Final site plan, load-in schedule, and onsite contacts confirmed