Skip to content

samber/dev-event-organizer-skills / skills/event-sponsor-agreement

event-sponsor-agreement

Verified

Turn a sold event sponsorship into a term sheet a lawyer can review - never a signable contract or legal advice. Covers the clause checklist an organizer hands to counsel - a deliverables schedule mirroring the sold tier, payment and late-fee terms, sponsor-withdrawal refunds plus the narrower organizer-cancels remedy, a force-majeure remedy, category exclusivity bounded by published caps, liability and insurance, a code-of-conduct clause with an ejection right, an editorial-independence clause denying sponsors program control, mutual logo licensing, term and renewal. Use whenever the user mentions a sponsorship agreement or contract, sponsor payment or cancellation terms, exclusivity, or a force-majeure clause - even if they never say "agreement". Do NOT use to set prices - use samber/dev-event-organizer-skills@event-sponsor-pricing.

FileKindSize
SKILL.mdskill md29.7 KB
evals/evals.jsonconfig42.8 KB
references/clause-library.mdmarkdown18.8 KB
references/exclusivity-and-renewal.mdmarkdown6.9 KB
references/term-sheet-template.mdmarkdown10.7 KB

references/clause-library.md

View on GitHub
# Sponsorship clause library

Clause shapes for a sponsorship term sheet. **Not legal advice, and none of this language is signable as-is** - every clause here is an example of how real organizers have written the point, offered so counsel starts from evidence rather than from a blank page.

## Contents

1. Payment, late fees and non-payment
2. Sponsor withdrawal
3. Organizer cancellation
4. Force majeure
5. Cure periods and termination
6. Liability, indemnification and insurance
7. Code of conduct
8. Editorial independence
9. Logo and brand licensing
10. Confidentiality, data and governing law

## 1. Payment, late fees and non-payment

**Schedules.**

- AFCEA FedID 2026: "A 100% deposit for the partnership is due at signing of the Agreement."
- PyCon US 2020 (PSF): "Full payment in U.S. funds must accompany this form in order to secure your space as a sponsor or exhibitor."
- SCCE & HCCA: balance "paid in full upon submission of exhibit and/or sponsor application and within 15 days upon receiving the invoice."
- TMS Awards: "Payment shall be made in two instalments: 80% of the Sponsorship Fees on sign up and 20% of the Sponsorship Fees 3 months prior to the Event" - collapsing to a single 100% instalment when signature falls inside three months.
- Air & Waste Management Association (ACE 2021): "Minimum of 50% deposit payment is due with application… due immediately upon receipt of the invoice," balance by a fixed date, with applications after that date payable in full upfront.

A "deposit on signing, balance 30 days before the event" default circulates widely in sponsorship how-to guidance - usable as a fallback shape, never citable as a verified real-world figure.

**Late payment (varies by organizer).**

- TMS Awards charges interest "at the rate of 12% per annum on all late payments post due date."
- AFCEA FedID sets a "late payment penalty calculated at eighteen (18) percent annually on the outstanding balance."

The verified market range is 12-18% per annum. Legal commentary stresses this must be an _express_ clause: without one the organizer has no contractual right to interest, to suspend deliverables, or to terminate for late payment, and statutory pre-judgment interest is typically far lower.

**Non-payment.** Three devices appear repeatedly, and they compose rather than compete:

- Obligation survives non-attendance - ATD/MCI: "Terms are enforced regardless if sponsor does not attend the conference"; SCCE: "Failure to make payment does not relieve the obligation to pay the contracted amount."
- Cost-shifting on collections - ATD/MCI makes a sponsor referred to "a collection agency/attorney for any reason" responsible for "a 25% attorney fee plus interest, lost discounts, and costs associated with any and all collection efforts." Commentary notes attorney fees are generally recoverable only where an express, ideally reciprocal, fee clause exists.
- Immediate self-help short of litigation - AWMA reserves "the right to immediately remove all references to Sponsor and-or Exhibitor on the Conference website and elsewhere."

## 2. Sponsor withdrawal

**Tiered schedules.**

- PyCon US 2020: "We will refund 75% of the total sponsor or exhibitor fee for cancellations received in writing 120 days… before the first day of the conference. We will refund 50%… 80 days… After that date, no refunds will be issued."
- IBTTA: 50% before a fixed cutoff, none after.
- AAPOR 2023: a 50% administrative fee before a fixed date, none after, with an explicit carve-out for a government travel ban.
- NARI Atlanta: refund less a 10% fee beyond 30 business days, 50% within 30, none within 10.
- PyData: full refund beyond 7 days, 50% within 7, none from the start date - the same pattern compressed to a community-event calendar.

**Hard no-refund.**

- ATD/MCI: "No refunds."
- CLOC: "the Sponsorship Fee is non-refundable under any circumstances," with the sponsor additionally liable for the cost of removing its marks from event materials.
- IPE: non-refundable "unless cancellation is the fault of the Company" - a narrow organizer-fault carve-out, not a convenience refund.
- NCSI publishes a liquidated-damages-style schedule grounded in the stated rationale that the organizer "will sustain substantial losses if the Sponsor cancels," which is reusable justification language.

Every clause above requires written notice and measures against a named date. None grants a discretionary refund.

## 3. Organizer cancellation

A **separate and narrower** remedy in every published example - never the mirror image of sponsor withdrawal.

- PyCon US 2020: the PSF "shall determine and refund to Sponsor its proportionate share of the balance of the aggregate display fees received which remain after deducting all expenses incurred by the PSF" - pro-rata, net of sunk costs, and the proportion is the organizer's own determination.
- SCCE & HCCA: refund of the booth fee if cancelled before move-in; on or after move-in the organizer is "not liable for refunding the Exhibit Fee" at all.

Sponsor-side commentary advises sponsors to check separately whether the organizer carries event-cancellation insurance, since even a full fee refund leaves the sponsor's own activation costs - booth build, staff travel, printed collateral - unrecovered. Expect a well-advised sponsor to raise this.

## 4. Force majeure

**The governing principle (case law).** Courts read these clauses narrowly and literally.

- _NetOne, Inc. v. Panache Destination Mgmt., Inc._, 2020 WL 6325704 (D. Haw. Oct. 28, 2020): deposit refund **denied** because the clause did not expressly provide for one; ordering a refund would "effectively re-write the parties['] contracts to include language that could have been (but was not) used."
- _Sanders v. Edison Ballroom LLC_, No. 654992/2020, 2021 WL 1089938 (N.Y. Sup. Ct. Mar. 22, 2021): full refund of a $45,219.28 deposit **ordered** on summary judgment because the clause expressly said "in the event of any such acts of God, [Defendant] shall refund all payments made by [Plaintiffs]."

**Trigger list (industry guidance).** Post-COVID drafting names "pandemic" and "epidemic" expressly rather than relying on generic "act of God" language. Litigation surveys converge on the same reason: whatever the clause does not name, it may not cover.

**Remedy shapes.**

- Sponsor-elected credit or refund with a dated window - Linux Foundation 2021: on converting an in-person event to virtual, sponsors "will have 14 days to choose whether to transfer their sponsorship to the virtual format, or receive [a refund/credit]."
- Flat cash refund - eXp/AGNT: "eXp shall refund the Sponsorship Fee paid within thirty (30) days."
- Pro-rata net of expenses - PyCon US 2020, quoted in §3 above.
- No obligation - TMS Awards: "Should the Event be cancelled, curtailed or adversely affected by any cause not within the reasonable control of the Event Organizer… the Event Organizer shall be under no obligation to refund all or part of the sums paid by the Sponsor."
- Duration-triggered termination right - Personal Finance Society: either party may terminate if force majeure prevents performance for 30 or more days. This composes with any of the remedies above rather than replacing one.

**Two corrections worth carrying.** The PyCon US 2020 clause is **pre-COVID**: it lists "fire, strike, earthquake… government regulation, public catastrophe, an act of God or any similar reason" and names neither pandemic nor epidemic. Borrow its remedy shape, not its trigger list. Separately, PyCon Korea 2022 published its own clause giving partial refunds scaled to when a government-ordered cancellation lands - so "the PSF clause" is not one monolith across editions and regions.

## 5. Cure periods and termination

**Verified lengths.** 30 days is the most common:

- SAGE World: "if the default is not cured within thirty (30) days."
- AFCEA FedID: "uncured after thirty (30) days written notice."
- American Pets Alive!: "remains uncured 30 days."

A 14-day figure appears in a sports-sponsorship agreement sampled on Law Insider. eXp/AGNT uses a deliberately compressed, event-proximate 3-day variant - "fails to cure any remediable breach within three (3) calendar days" - with any breach not curable at least one day before the event deemed non-remediable outright, which is the sensible shape for breaches discovered close to the date.

**A correction to repeat rather than the claim it corrects.** The widely-circulated statement that the PSF uses a 15-day cure period is **unverified and contradicted** by the only public PSF sponsorship contract, which contains no cure period, no "cure" language and no notice-and-remedy provision at all; termination there is at the PSF's "sole discretion… without recourse."

The PSF's current year-round agreement is finalized privately and unpublished, so the figure can be neither confirmed nor refuted against it. Fifteen-day cures do exist in the general template market - they are simply not the PSF's number, and attributing them to the PSF is the error to avoid.

**Termination grounds (PyCon US 2020).**

- Sixty-day termination by either party, for any reason.
- Termination for material breach.
- Termination by mutual consent.
- Immediate termination if the sponsor's materials are found or alleged to infringe a third party's rights.

Two further shapes from the same contract are worth naming as their own clause types:

- A **reputational termination right**, letting the organizer stop accepting funds "if it reasonably determines that it would be detrimental to the reputation and goodwill" of the organization, separate from any breach.
- A **deliverable-non-use penalty**, where failing to use reserved display space risks forfeiting "up to 50% of your Sponsorship Payment," which is distinct from a payment-default penalty.

## 6. Liability, indemnification and insurance

**Insurance minimum (convergent).** $1,000,000 per occurrence / $2,000,000 aggregate commercial general liability, with the organizer named as additional insured. ASTRO's 2026 exhibitor requirements state it verbatim: coverage "at least as broad as… ISO Form CG 00 01 12 04, written on an 'occurrence' basis, with limits of no less than $1,000,000 per occurrence/$2,000,000 aggregate." Independently confirmed across many unrelated exhibitor-requirement documents and convention-center standards - a genuine cross-industry norm rather than one organization's rule.

Layered coverage adds:

- Auto liability ($1M).
- Workers' compensation and employer's liability ($500K).
- Product or liquor liability, where relevant.

**Scale gate.** Small community meetups and hackathons frequently require no sponsor-carried insurance at all, relying on the organizer's or venue's master policy. The $1M/$2M standard is an exhibitor-hall norm, not a universal one.

**Certificates.** Required before move-in, and typically tied to contract execution rather than event-day arrival - the Bank of America Shamrock Shuffle requires certificates "upon execution of contract," naming specified entities as additional insureds. A sponsor objecting that year-round cover is disproportionate can buy a compliant single-event policy from a vendor-insurance marketplace; ESP Specialty publishes $79 for a $1M/$2M single-event booth policy (one vendor's published price - treat the number as illustrative of the order of magnitude, not as a market rate).

**Indemnification: two real shapes, and it is negotiated.**

- One-sided, organizer-favouring (PyCon US 2020): "Sponsor shall indemnify, defend and protect the PSF… from any and all claims… which might result or arise from Sponsor's participation," with the organizer disclaiming its own liability and capping any exposure at "the amount actually paid to it by Sponsor." Note this contract has **no separate liability-cap clause** - protection comes entirely from one-sided indemnification.
- Mutual (Template Republic): "Each party hereto shall indemnify and hold the others harmless."

Sponsor-side commentary notes sponsors generally request broad indemnity covering the organizer's own negligence, breach and IP infringement. Which shape lands reflects bargaining power, not an industry default - present both.

## 7. Code of conduct

The default, not an option: a clause binding the sponsor's own staff to the event code of conduct, with an organizer ejection right and the no-refund consequence stated in the same clause. Confirmed across conferences of very different sizes, domains and formats.

- PyCon US 2020: "Sponsor and all of its representatives shall conduct themselves at all times in accordance with the [PSF Code of Conduct] and/or the PyCon Code of Conduct… The PSF reserves the right to eject from any event any Sponsor or representative violating those standards."
- Write the Docs: sponsors "should not employ aggressive recruiting techniques, invasive marketing behavior… In case of violations, sponsors might be sanctioned and expelled from the event or activity with no return of the sponsorship contribution."
- confcodeofconduct.com (and the strongest evidence the shape is genre-standard because it is a shared open-source template rather than one event's bespoke language): "Booth staff (including volunteers) should not use sexualised clothing/uniforms/costumes… the conference organisers may take any action they deem appropriate, including… expulsion from the conference with no refund."
- GuidePoint Security, TSIA, SCCE and CUES each independently include equivalent removal rights for sponsor personnel, framed at the organizer's sole discretion and without refund.
- Major League Hacking (hackathon-specific): the code of conduct is "the contract between the hacker and the hackathon," and "Anyone that is caught violating the Code of Conduct may be asked to leave." MLH's member-event guidelines bind third-party organizers and league sponsors too, not only individual attendees.

Pair the ejection right with the explicit no-refund consequence in the same sentence - every published example does, rather than leaving the refund question to the general cancellation section.

## 8. Editorial independence

A default, not an option: none of the published contracts quoted in this library grants a sponsor program control, and none denies it in words either. Silence leaves the question to whoever pushes hardest during the edition. Write the denial down.

**Why it needs its own clause.** Organizer guides already state the rule as a value proposition ("No sponsor should be able to buy their way into the program" - DevOpsDays organizing guide). The operating reason: an event whose program bends to one funder ends up depending on that one company, and loses the audience the sponsor paid to reach.

**Clause shape (example elements, not signable language).**

- **No program control.** The sponsor acquires no right to select, approve, veto or review speakers, talk topics, session content, panel composition, judging or the schedule.
- **Organizer refusal right.** The organizer may refuse, edit for length or format, or withdraw any sponsor-supplied content - a talk, a demo, a workshop, printed or on-screen material - and any sponsor-nominated speaker, at its sole discretion.
- **Consequence stated in the same clause.** Exercising the refusal right is not a breach and triggers no refund, mirroring the code-of-conduct pairing in §7. Draft the no-refund sentence here rather than leaving it to the cancellation clauses.
- **Sponsor content is labelled.** Anything the sponsor does present carries a visible sponsor label, so attendees can tell bought placement from selected program.
- **Optional cap on sponsor-affiliated speakers.** A self-set ceiling on talks given by a sponsor's employees per edition, applied at selection rather than negotiated per deal. The selection process that enforces it belongs to `samber/dev-event-organizer-skills@event-talk-selection`; the contract only states that sponsorship does not exempt a sponsor's staff from it.

**Edge cases to flag for counsel.**

- A sponsored workshop or demo slot sold as a perk is placement, not program: list it in the deliverables exhibit with its format and the refusal right attached, and keep it out of the selected program.
- A sponsor whose employee wins a slot through the open call is not a breach. State that the slot was earned through the call and confers nothing on the sponsor.

## 9. Logo and brand licensing

Reciprocal, limited, promotion-only and time-bound - the same four qualifiers in every example below.

- AFCEA FedID: "Each party is granted a nontransferable, non-exclusive license to use the other party's materials, marks and logos… solely for the promotion and execution of the sponsorship at the Event… and only during the agreed upon period," and on termination "each party will cease using the other party's Intellectual Property."
- PyCon US 2020: a "limited, non-exclusive license" solely to identify the sponsorship, prior-approval rights on both sides with "not unreasonably withheld" language, and an explicit ban on implying endorsement.
- Eclipse Foundation, bounding the organizer's side: the sponsor agrees to the foundation using "their company logo in our promotional materials… websites, social media channels, and printed materials," subject to the sponsor's own logo-usage guidelines, with the ceiling stated outright - "No other use of Sponsor's logo is authorized."
- CFA Institute: "a limited license to use Sponsor's trade name, trademarks, and service marks for the purpose of promoting Sponsor's sponsorship."
- SponsorVista, the cleanest expiry sentence to adapt: "All use of the Sponsor's brand ends once the agreement expires, unless otherwise agreed in writing."

Carry both qualifiers into the drafted clause: use is subject to the other party's brand guidelines, and the licence expires automatically rather than continuing silently.

## 10. Confidentiality, data and governing law

**Confidentiality (structure from generic contract practice).** Define confidential information (non-public terms, pricing, business plans), set a survival period, and carve out public-domain, independently-developed and legally-compelled disclosure. This is generic contract practice rather than anything sponsorship-specific; counsel will have a house position.

**Attendee data - the default is no clause at all.** Published sponsorship contracts carry no attendee-data or lead-list delivery clause, including at the foundation-run pole, and community-run organizers publish rules forbidding it outright. A data clause is draftable only where a consented lead-retrieval benefit was genuinely sold; when it is, it needs:

- The lawful basis.
- The consent mechanism.
- The fields collected.
- The delivery timeline.
- Each party's controller role.
- The sponsor's downstream obligations.

All of this is a counsel question, not a template question.

**Governing law and disputes.** Name the governing law, the forum, the escalation path (negotiation, then mediation or arbitration, then courts) and the language of the agreement. This is the most jurisdiction-dependent section in the whole document and should be flagged for counsel rather than drafted from any example here.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall