Your headline sponsor was promised ten passes. Your public allocation is 500 seats. So do you have 490 to sell, or 500, or did someone quietly count the sponsor ten twice and now the fire officer is asking questions? Handling sponsor ticket allocation badly is how events oversell, how sponsors feel like an afterthought, and how your final revenue report turns into a forensic investigation. The fix is to ring-fence sponsor tickets from public sales from the very start, so their seats never appear on the public page, never eat into your saleable inventory by accident, and always report separately. Here is how to set that up properly.
Why sponsor tickets need to live apart from public sales
Sponsor and partner passes behave nothing like the tickets you sell to the public. They are usually free or pre-paid as part of the sponsorship deal, they go to named people the sponsor nominates, and they must not show up as a buyable option on your event page. If you throw them into the same pool as public tickets, two bad things happen. First, the maths drifts: a comp block that is not clearly counted against capacity leads to accidental overselling. Second, your reporting muddies, because a free sponsor seat and a paid public seat look the same in a single undifferentiated total.
A sponsor pass is a promise you made in a contract. It should be trackable to the last seat, not lost inside your general ticket count like loose change down the back of the sofa.
The building blocks: hidden ticket types and access codes
Every capable ticketing platform gives you two tools for this job. The first is the hidden ticket type: a ticket that is completely valid but does not appear on your public event page. The second is the access code, which works like a password that reveals a hidden ticket to the people who hold it. Access codes are the standard way organisers set aside blocks of complimentary tickets for speakers and sponsors without showing them to the general public. Give each sponsor their own code and they unlock only the allocation you promised them, nothing more.
Used together, they solve the problem cleanly. You create a hidden ticket type per sponsor tier, cap it at the agreed number, and hand each sponsor a unique access code to distribute to their people. The public never sees these tickets. The sponsor never sees anyone else's allocation. And you get a clean count of who has claimed what.
| Method | How it works | Best when |
|---|---|---|
| Hidden ticket type | Valid ticket that never shows on the public page, capped at the agreed number | You control who gets the claim link directly |
| Unique access code per sponsor | A private code unlocks a specific hidden allocation for one sponsor | Different sponsors have different entitlements |
| 100 percent discount code | A promo code drops a ticket price to zero with a strict usage cap | Sponsor passes are technically a paid tier made free |
| Direct comp issue | You add named comp tickets yourself and email them out | Small, fixed guest lists you manage centrally |
Setting it up, step by step
Start by turning each sponsorship tier into its own hidden ticket type: "Platinum Sponsor Pass", "Gold Sponsor Pass", and so on. Set the capacity of each to exactly what the contract promised, so the platform enforces the limit for you rather than trusting a spreadsheet. Crucially, make sure these tickets still count against your total venue capacity. That is the guardrail that stops the sponsor ten from becoming an accidental extra ten on top of a sold-out room.
Next, generate one access code per sponsor and tie it to their allocation. When a sponsor's guest enters the code, they see only that sponsor's hidden pass and can claim up to the remaining number. Because each code is unique, you can see at a glance how many of each sponsor's seats have been claimed and how many are still outstanding, which is the polite nudge you need when a sponsor sits on their allocation until the week before.
Ten seats, one sponsor, zero forensic accounting required. Credit: Jakob Dalbjorn / Unsplash
Reporting: the part everyone forgets until it is too late
The whole point of ring-fencing sponsor tickets is that at the end you can answer three questions instantly: how many passes each sponsor was given, how many they actually claimed, and what those free seats were worth at face value. That last number matters more than people think. If your Platinum tier gives away 20 seats that would have sold at 300 each, that is 6,000 of value you handed over, and it belongs in your sponsorship ROI conversation. When sponsor allocations report separately from public sales, that figure is a click away instead of an afternoon with a calculator.
This is also where keeping sponsor seats out of the public pool pays off in cash terms. Your public sales report shows real revenue, uncontaminated by zero-value comps, so you always know your genuine ticket income. Modern platforms support per-tier reporting precisely so you can slice sponsor, VIP and public numbers apart. If yours cannot, that is a sign you are managing allocations by hope.
Keep it distinct from your VIP and guest list
Sponsor tickets and VIP or guest-list seats are cousins, not twins. Guest lists are usually your own invitees managed centrally; sponsor allocations are handed out by the sponsor to people you may never meet until they scan in. It is worth running them as separate ticket types even though the mechanics rhyme, because the reporting questions differ. For the general playbook on comps and internal guests, our guide to managing VIP and guest lists without a spreadsheet covers that side; this piece stays firmly on sponsor allocation, where the defining feature is that someone outside your team is distributing the seats.
A few honest caveats
If you are running a small, free community event with one friendly sponsor and five passes, you do not need access codes and hidden tiers. Email them five tickets and get on with your life. The setup here earns its keep when you have multiple sponsors, different entitlements per tier, a paid public sale happening alongside, and a real capacity limit you cannot breach. That is exactly the situation where an accidental double-count or an untracked comp block hurts, and where a bit of structure up front saves the awkward "so how many did we actually give away" conversation later.
The short version
Make each sponsor tier a hidden, capped ticket type that counts against capacity. Give each sponsor a unique access code so they claim only what they were promised. Keep the whole block out of your public sales so your saleable inventory and your revenue numbers stay honest. Report on it separately so you know, to the seat and to the pound, what your sponsors received. Do that, and sponsor tickets stop being the wobbliest number in your event and start being one of the tidiest.
If you would like to see hidden ticket types, access codes and per-tier reporting working together in one place, take a look at the eventcloud platform and set your next sponsor allocation up so it never mixes with public sales again.