A sponsorship prospectus is the document you send a company before it buys: what the event
is, who attended the last edition, what each package includes, what you will count on the
sponsor's behalf, and the date the report arrives.

It is a sales document and a measurement
agreement at the same time, and the second half is the one organizers skip. The template
below is free, needs no email, and comes as a CSV that opens in Excel and Google Sheets.

[Download sponsorship-prospectus.csv](https://eventiq.io/templates/sponsorship-prospectus.csv)
(plain CSV, no sign-up). In Excel, open the file directly. In Google Sheets, use File, then
Import, then Upload. The rows match the table below, and the last column is blank for your
own draft.

Write it so that every promise inside can be measured the same way you will report it later.
A prospectus that promises leads, sent by an organizer whose records hold booth visits and
email matches, produces an argument in the third month after the event that neither side can
win. The sponsor's finance team reads the report next to the prospectus, line by line, so the
two documents have to use the same nouns.

This page is for associations, AMCs, and independent B2B organizers selling to companies
that answer to their own finance teams. In a Global DMC Partners survey from May 2026 of 162
event professionals, 71% of them in the US, 68% reported pressure from stakeholders to prove
the business impact of their programmes, and one in five called it significant or extreme.

## What goes into a sponsorship prospectus?

Twelve sections, and each one has a source behind it. A section with no source is a claim,
and it is the first thing a sponsor's finance team asks about.
| Section | What it contains | Where the data comes from | Common mistake |
| --- | --- | --- | --- |
| Event and edition | Name, format, dates, location, edition number, and the audience the event serves | Your event plan and programme | Opening with your organization's mission when the sponsor came for the audience |
| Audience composition | Counts of last edition's attendees by role level, organization type and size, and region, each with the date it was taken | Registration form fields | Putting this year's target audience in the same table as last year's measured counts |
| Attendance history | Registrations and attendance as two separate counts, per edition | Registration platform and check-in records | One audience number that merges registrations, attendance, and newsletter reach |
| Package contents by level | Visibility, audience access, and post-event data, under the same 3 headings on every level | Your inventory list and last year's signed agreements | Levels that differ only in logo size, which invites a discount request |
| Price and what it is built from | The price per level, the units behind it, and the items sold separately | Your pricing worksheet | A price with no build-up, which the sponsor's finance team cannot check |
| What you will count | One row per promise: the unit, the counting rule, the window, and the system that holds the record | The platforms you already run | Promising a unit that exists in no record you keep |
| What you will not count | The measures you decline to report, and why, such as figures produced by multiplying attendance | Your own reporting policy | Leaving it blank, so the sponsor assumes everything is on the table |
| Shortfall terms | What happens when delivery lands under a guarantee: credit, added inventory, or a resized renewal | Your contract template, reviewed with legal | A guarantee with no remedy written next to it |
| Data and consent terms | What the sponsor receives afterwards, what stays aggregate, and the consent rule behind each | Your registration terms and privacy policy | Promising a contact list your registration terms do not permit |
| Reporting date and format | The date the report arrives, the template it uses, and the fields it carries | Your post-event reporting calendar | No date, so the report lands after the renewal decision |
| Last edition's delivery | What sponsors at each level received last time, counted the way this prospectus counts | Last year's sponsor reports | Leaving it out because the numbers look modest; a checkable number outsells a bold one |
| Deadlines and contact | Sign-by dates, the person who answers questions, and what happens in the week after signature | Your sales calendar | Deadlines with none of the steps that follow them |
The source column names one system or one document per row. A section assembled from three
places drifts between editions, because nobody remembers which of the three produced the
number. Name the source in the prospectus itself, where the sponsor can see it.

Order matters more than length. Audience composition and attendance history come before
packages and prices, because they are the evidence a price rests on. Setting those prices from
audience units, and choosing how many levels to sell, is a separate job, worked through in
[event sponsorship packages](https://eventiq.io/md/blog/event-sponsorship-packages).

Sponsorship also competes with other things associations sell. In Naylor's 2026 Association
Benchmarking Report, a survey of 665 senior association professionals in North America,
sponsorship's share of non-dues revenue slipped from 29.7% to 25.3%, while job postings rose
from 3.6% to 10%
([Naylor press release](https://www.prweb.com/releases/2026-association-benchmarking-report-reveals-associations-are-getting-more-intentional-about-data-ai-and-revenue-302842546.html)).
That is how the mix moved. The report does not say sponsorship income fell in absolute
terms, and it says nothing about any single event. What it does tell you is that your
prospectus is read beside line items that report their results cleanly.

## How do you describe the audience without overstating it?

Describe the audience by the composition of the people who came last time, and put a date on
it. A sponsor can check a count of people who attended. Nobody can check a promise about
people who have not registered yet, and a sponsor who finds the gap after the event treats
every other number in your prospectus as the same kind of claim.

1. **Registrations and attendance stay 2 counts.** They answer different questions, and one
   merged audience figure hides the one the sponsor cares about. Write both, per edition.
2. **Every figure carries an as-of date.** "1,480 attendees, counted from check-in records on
   14 November 2025" is a fact. The same number with no date gets quoted back to you.
3. **Segment counts come from fields you collect.** "Directors and above at organizations
   over 500 people" has to match two registration fields. If you do not collect organization
   size, add the field before registration opens or drop the segment from the offer.
4. **Say what you do not know.** Optional fields come back partly empty. A segment count with
   the number of records missing that field beside it reads as a working system; the same
   count alone reads as a rounded guess.

Forecasts belong in the prospectus too, under their own heading. An organizer selling a March
event in September has a target, and sponsors expect to see it. Label it as a target, show
the registration count it stands on today and the
[conference registration forecast](https://eventiq.io/md/blog/conference-registration-forecasting) range behind it, and keep it out of the table that holds measured
history. One table of facts and one marked target beats a single table where the reader has
to work out which is which.

Do not sum audiences across channels. Attendees plus newsletter subscribers plus social
followers is a reach number no finance team accepts and you cannot report against afterwards.
And when a person appears in two of your systems, say which count includes them: a total
assembled from several sources counts some people more than once, and the sponsor finds that
out at report time rather than at signature.

## What should the prospectus promise about measurement?

Promise units that already exist as records in a system you can name. Run that test on every
line of the package before the document goes out.

**A promise is safe to print when 3 things are already true:**

**the unit exists as a record in a named system, the counting rule is written down, and the window has a start time and an end time.**

Run it on a promise of qualified leads. The unit exists only if a system you operate captures
those interactions and your registration terms let you pass them on, and the rule has to say
which interaction qualifies and whether a person who returns on day 2 counts once or twice.
If either half is missing, the promise is not measurable by you, whatever the contract says.
Rewrite it as the interactions you do hold.

The window is the part that breaks without anyone noticing. Booth visit records exist from the hour the hall
opens to the hour it closes. If the prospectus does not fix those hours, next year's count
includes the welcome reception and this year's does not, and the difference between editions
is your own counting rather than the sponsor's performance.

Write the section on what you will not count with the same care. Impressions produced by
multiplying attendance, a return figure calculated on a cost you do not hold, any pipeline
number the sponsor did not send you: naming these in advance costs nothing at signature and
saves the renewal conversation. The return calculation belongs to the sponsor, who holds both
the cost and the revenue, and the method is in
[event sponsorship ROI](https://eventiq.io/md/event-roi/event-sponsorship-roi).

Sponsors already suspect their own systems miss part of the story. In a Vendelux survey of
more than 120 B2B marketing and events leaders in 2026, run by a vendor selling to that same
market, 90% said events influence deals that get no credit in their CRM. Hand them countable
records and the event and campaign names to join on, and leave the conclusion to them.

Finish with the remedy. A guarantee of 150 qualified interactions against a delivery of 130
is an ordinary outcome, and the prospectus should already say what follows: a credit at the
stated unit price against the next edition, extra inventory, or a resized package. Written in
advance, a shortfall is arithmetic, and nobody has to negotiate it.

## How does the prospectus line up with the report you send afterwards?

The report is this prospectus with the counts filled in. Same rows, same order, same names,
same counting rules, so the sponsor can lay the two documents side by side and check every
promise without asking you a question. The [sponsor report template](https://eventiq.io/md/templates/sponsor-report)
is the other half of that pair, laid out row for row.

Three things have to survive the gap between the two documents. The names come first: if the
prospectus sells "sponsored session attendance," the report says sponsored session
attendance, because a row that arrives renamed reads as a row that was substituted.

Then the counting rules. Write each one in the prospectus and carry it into the report
unchanged. When a rule has to change, because the registration form gained a field or the
session moved days, put the change on the report the year it happens, with the date it took
effect, and keep the note the following year.

Then the sources. A sponsor checking a figure should get one system in reply, so a count
assembled from 2 systems belongs on 2 rows, in both documents.

Set the reporting date in the prospectus itself, and pick one that falls before your renewal
conversation. The [post-event report template](https://eventiq.io/md/blog/post-event-report-template) covers the
whole event in the same style, with attendance, cost, and pipeline in one reviewable record.

Plan the second year from the first. Two editions of the same rows, counted the same
way, is the series a finance team needs before approving an increase, and the reason last
edition's delivery belongs inside the prospectus rather than in a separate deck. A sponsor
who can see what their level delivered last time, under the rule it was counted by, defends
the renewal without you in the room.

## Where EventIQ fits

EventIQ replaces nothing. It connects on top of the platforms you already run:
registration and ticketing (Cvent, Zoom, Swapcard, StubHub), CRM (Salesforce,
HubSpot, GoHighLevel), and marketing (Google Ads, Meta Ads, LinkedIn Ads,
Mailchimp, Google Analytics). Platforms with an API outside that list are
connected on request.

Registrations and attendance stay separate records. Contacts are matched by exact
email, and every record keeps its result: matched, unmatched, or no email.
Salesforce deals, stages, and close dates link to an event through a campaign
relationship you confirm. Marketing spend sits by event and channel, with the
author of every change. Records sync on a schedule: Swapcard every 15 minutes,
Cvent every 30, Zoom every 2 hours, Salesforce every 4. The Event Dashboard and
the Portfolio Dashboard show them in one view, and a forecast is visible before
the event.

Swapcard booth visits, session views, survey answers, and questions arrive as
records per participant. Sponsor tiers, contract value, and fulfilment terms
stay in your sponsorship agreements.

[Book a demo](https://eventiq.io/#early-access) to see which kinds of prospectus promises exist as records
on a sample event: booth visits and session records per participant, the match result
on each contact, and spend by event and channel. The demo takes 20 minutes.

---

HTML version: https://eventiq.io/templates/sponsorship-prospectus