When a small company has two season tickets and fifty employees who’d each take them if asked, the answer isn’t to hand them to whoever’s closest to the owner’s office or whoever asks first. It’s to decide, once, on a short set of criteria — tenure, recent contribution, rotation, or some combination — and apply it the same way every time, with a record of who’s already gone so the next decision doesn’t start from scratch.

Why does ad hoc ticket allocation break down faster in a small company than a large one?

A large company can run an informal system for years without anyone noticing the pattern, because the sheer number of employees and events dilutes any single bad call. A small company doesn’t have that cover. With only a handful of seats and a workforce where everyone knows everyone, an allocation that looks arbitrary gets noticed immediately — and it tends to look arbitrary by default, because without a documented method, there usually isn’t one. The decision defaults to whoever’s top of mind that week, which is a different person every time and a pattern to no one but the person left out.

What criteria should actually decide who gets the seats?

There’s no single right answer, but there is a wrong one: no criteria at all. Some combination of tenure, recent performance or project contribution, and straightforward rotation tends to hold up because it’s explainable in one sentence. The specific weighting matters less than having one at all — a company that can say “we prioritize X, then Y, and we track who’s already received tickets this year” has something it can defend. A company that can’t explain its own process has nothing to point to when someone asks why they weren’t picked.

Should allocation reward performance, tenure, or just take turns?

Each has a case. Rewarding performance ties the perk to something the business already values. Tenure respects the people who’ve been there longest. A straightforward rotation sidesteps the debate entirely by making the answer “whoever hasn’t gone yet” — which is often the simplest system for a very small team to actually sustain. The mistake is mixing all three without deciding which one governs when they conflict, which produces exactly the inconsistency that makes the process feel political in the first place.

How do you keep the process from feeling arbitrary to the employees who don’t go?

Make the criteria visible before the decision, not after. An employee who knows the rule in advance — even one they don’t love — reads a “no” differently than one who only finds out the rule existed once someone else already has the tickets. The complaint usually isn’t about losing out on a specific event; it’s about not understanding why. A published, consistent method answers that question before it’s asked.

What role does visibility play in making this work long term?

This is where most small companies actually fail, not at the policy stage. A company can write down a fair-sounding rule and still apply it inconsistently because nobody’s tracking who received tickets last quarter or last year. Ticket Booth solves that by keeping the record the policy depends on — who received what, and when — so “we rotate fairly” is something the company can actually demonstrate rather than just assert. See how Ticketnology works for small businesses →

Does fixing allocation ever mean the company just needs more tickets?

Sometimes, and that’s a separate decision from allocation itself. Once a company can see how consistently its current inventory gets requested and how often it has to say no, Ticket Pass makes it straightforward to budget for additional seats deliberately, rather than guessing at demand. That’s a budget question, though — it doesn’t replace the need for a fair method to allocate whatever the company already has. This is a different problem from the one we covered in Holiday Client Appreciation on an SME Budget: that post is about prioritizing which clients get a limited external budget; this one is about allocating a limited internal perk among employees.