Building an honest audience profile for sponsors
A prospective sponsor has asked who actually attends, and the last event's records are patchy.
The short answer
An honest audience profile states who attended or registered, how you know, and what you do not know. Use counts and ranges from your own records, name the source and date of each, and leave out anything you cannot support.
A short, accurate profile is easier for a sponsor to assess than a long one with rounded-up claims.
Start from data you already hold
- Registration records: job-title categories, organisation types and locations, counted in groups rather than listed by person.
- Attendance records: how many registered, how many attended, how many came for each session if you scanned entry.
- Membership records, where the event is for members: membership grades and sectors.
- Post-event survey responses, with the number who answered and the question asked.
Say how each figure was produced
Next to every number, write the source, the date and the base. For example, 212 registered, 171 attended by badge scan, 64 survey responses, which is about 37 percent of attendees.
State when a figure is self-reported. Job titles typed by delegates are their description, not verified seniority.
What to leave out
- Claims about purchasing authority, budgets or decision-making power that you did not collect. The next page, valuing audience relevance without inventing buying power, covers what you can say instead.
- Rounded-up attendance, or registration counts presented as attendance.
- Data that identifies individuals. Share grouped figures only, and ask a privacy adviser what delegates were told when their details were collected.
- Comparisons with other events that you cannot evidence.
Show the limits
Add a short note on gaps: for example, that sector was optional on the form and 28 percent left it blank, or that last year's attendance was recorded only for the plenary.
Sponsors treat visible limits as a sign of reliable reporting, and it prevents later disputes about what was promised.
Using the profile
- Prepare one page, reviewed by the committee and anyone responsible for data protection.
- Use it consistently in the prospectus and in conversations, so numbers do not drift.
- Update it after each event with the new figures and keep older versions.
- Use it to score fit in the sponsor fit scorecard, which works from evidence you define.
Worked example · Fictional example
A one-page profile built from partial records
Fictional organisation and figures, illustrative only.
A fictional healthcare administrators' association had 212 registrations and 171 recorded attendees at its last forum. Sector was an optional field, so 28 percent of registrations have no sector.
The secretariat reports grouped figures with sources, notes that survey responses came from 64 attendees, and lists what it did not collect, including purchasing responsibility.
| Item | Figure | Source and limit |
|---|---|---|
| Registered | 212 | Registration system, closed on event day |
| Attended | 171 | Badge scan at main entrance only |
| Organisation type: hospital or clinic | 96 | Self-reported on form; 28% blank |
| Job-title group: managers | 74 | Typed by delegates; not verified |
| Survey responses | 64 | Voluntary; may not represent all attendees |
Use this yourself
Audience profile template
Complete this on one page. Where you hold no data, write Not collected rather than estimating.
- Event, date and edition the figures refer to:
- Registered, attended and how attendance was recorded:
- Organisation types, counted in groups, with percentage left blank:
- Job-title groups, labelled as self-reported or verified:
- Geographic spread by region, grouped:
- Survey response count and how respondents were reached:
- Items not collected, such as purchasing responsibility:
- Known gaps and how they might skew the figures:
- Data-protection check: what delegates were told, and reviewer name and date:
- Version number and date of last update:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Registration and attendance data is clean and one person owns it.
- The event is small enough to describe its audience in a page.
- A privacy contact can confirm what may be shared.
Outside planning help earns its fee when
- Records sit across several systems or agencies and do not match.
- The sponsor is asking for data the organiser holds under uncertain permissions.
- A new event has no history to profile and the committee needs an honest way to describe it.
Want the audience profile built from your records?
An Event Blueprint can plan this part of the commercial workstream: which data to gather at registration, how to group it, what the profile says and does not say, and who reviews it before it goes to sponsors. Data-protection questions go to your privacy adviser, and no sponsor outcome is promised.
Questions organisers ask
Can I share the delegate list with a sponsor?
Treat that as a question for your privacy adviser, based on what delegates were told when they registered. Grouped figures can usually be shared without a list, but confirm.
What if my records are incomplete?
Report what you have, mark the gaps, and add the missing questions to the next registration form. Estimates should be labelled as estimates and kept out of headline claims.
Should I include delegate seniority?
Only as self-reported job-title groups, and say so. Seniority you did not verify should not be presented as fact.
Related resources
- Valuing professional audience relevance without inventing buying power
- Testing sponsor interest before committing to event scale
- Separating sponsor benefits from delegate personal data
- Designing a sponsor prospectus with substantiated claims
- Event sponsor fit scorecard
- Event Blueprint: your conference planning pack
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.