event-sponsor-agreement

Start with a term sheet, not a contract: list the sold tier and fee, build a deliverables exhibit from the rate card, then draft payment, cancellation, force-majeure, insurance, and code-of-conduct clauses. This Skill produces that term sheet with counsel flags, and a qualified lawyer turns it into the final contract.

Use a dated two-tier cutoff as the default, such as a partial refund before a fixed date and none after, and never leave refunds discretionary. Draft sponsor withdrawal and organizer cancellation as two separate clauses, since the organizer-cancels remedy is narrower in every published example.

No. It explicitly never produces a signable contract or legal advice; the output is a term sheet with example clause language and open questions flagged for a qualified lawyer in the event's jurisdiction. Every workflow ends at counsel review before any sponsor signs.

Name trigger events expressly, including pandemic and epidemic, then state the remedy in words for each branch: cancelled, postponed, or converted to virtual. Case law such as NetOne v. Panache shows silent clauses are read as no refund, so the remedy must never be implied.

Small meetups and hackathons typically require none, relying on the venue's master policy. The 1M per occurrence / 2M aggregate CGL standard applies once sponsors staff booths or bring physical demos, and layered coverage applies when alcohol, vehicles, or heavy equipment are involved.

Only if exclusivity was actually sold, and never looser than the caps published in the prospectus. An enforceable clause needs a specific category definition, a stated duration and channel scope, and an explicit breach remedy; missing any one of the three, it should not be drafted.