How Creighton's Ticket Office Actually Handles Game Day Logistics
The Creighton University ticket office runs on a combination of Catanys (yes, still), electronic ticketing through ESPN+ integration, and a lot of manual override work that never makes it into any press release. If you're trying to understand how fans get into games, how season tickets move around, and why the system sometimes feels like it fights you, here's what actually happens behind the scenes. I spent about three months helping a local athletics marketing group audit their ticket distribution workflow after they tried to replicate Creighton's model for their own mid-major program. The short version: it works because they've had fifteen years to patch holes in the system, not because anything about it is inherently simple. The core infrastructure runs on Catanys for season ticket management. That's the same platform used by a lot of NCAA Division I programs. You'd think that means everything is automated and clean. It isn't. The real work happens in the gaps between what Catanys can do and what the stadium operations team needs.
Here's the thing most people don't realize about Creighton's setup. Their Mabee Center has roughly 11,000 seats for basketball, but the ticket office manages far more transactions than that number suggests. Transfer windows, waitlist processing, single-game release logic, academic eligibility holds, donor priority overrides, and emergency seat reassignment all run through the same system simultaneously during peak periods like January and February. A lot of programs underestimate how much manual triage that requires. Creighton got smarter about this by implementing a tiered digital access system. Mobile tickets through the university's official app are now the default for almost every fan. Paper tickets still exist for certain donor levels and legacy season ticket holders, but the shift toward mobile reduced the load on the physical ticket window significantly. This isn't just about convenience. It's about reducing line bottlenecks at entrance points during games that sell out in under an hour, which has happened regularly since the Big East move. The digital system ties into NCAA compliance tracking automatically. If a student-athlete's academic eligibility flag changes, their seating assignment can be adjusted without someone having to manually pull up their account. That integration saves the office probably two to three hours per week during the season. Most smaller programs don't have that level of system connectivity built in.
One edge case I ran into that nobody seems to write about involves group ticket allocations for alumni chapters. Creighton has alumni groups scattered across states like Texas, California, and Florida that order blocks of seats for home games. The ticket office has to reconcile those orders against dynamic inventory because those seats also sit in the general sale pool until a certain deadline. I watched a situation unfold where a Texas alumni chapter had confirmed seats that got pulled eight days before a marquee game because the office couldn't verify the group's payment status in time. The workaround was setting up an automated hold flag in Catanys that locks group inventory earlier in the cycle, but it required a custom API call that the vendor had to build on the fly. That's the kind of problem that doesn't show up in any handbook. For individual fans trying to get tickets, the process has improved but still has friction points. Single-game tickets go on sale about ten days before the event, and popular games — Michigan State, Kansas, Villanova type matchups — sell out within minutes through the official app. The resale market through the university's authorized partner fills the gap, but prices can run two to four times face value for high-demand games. That's standard NCAA economics, not something unique to Creighton, but it's worth knowing if you're planning to walk up day of. Season ticket members get priority windows before the general public. The hierarchy runs: multi-year renewals first, then new members who signed multi-year deals, then single-year renewers, then general sale. Inside each tier, allocation is based on point accumulation from years of membership and spending. It's transparent once you understand the point system, but the point breakdown isn't published anywhere obvious. You have to dig into the member portal or call the office directly. I always tell people to just email the ticket office and ask for the current point table. They'll send it to you within a business day.
Get the Full Details

There's also a separate process for parking passes. Those are managed independently from seating tickets, which trips up a lot of first-time visitors. Buying a ticket doesn't automatically grant you parking. You have to purchase a separate parking pass through the same portal, and the lots fill up on a first-come basis. The office doesn't hold parking inventory, so if you show up game day without a pass, you're looking at the overflow lot about a mile away with a shuttle that runs every twelve minutes. During snow games in February, that shuttle wait can stretch to forty minutes. Not ideal. One counter-intuitive detail about Creighton's operation: the ticket office is technically housed within the department of athletics, but it reports functionally to two different people depending on the task. Student-athlete related seating and compliance issues go through the compliance office. Revenue generation, pricing, and general fan operations go through the athletics fundraising side. This dual reporting structure creates occasional friction. I've seen situations where a fundraising initiative to push premium seating overlapped with a compliance directive to free up seats for academic probation cases, and the ticket office staff had to mediate between the two priorities on the ground. It's handled well most of the time, but it's a structural tension that doesn't exist at programs with flatter reporting lines. Another detail worth noting is how they handle walk-ons and non-scholarship athletes. These individuals are eligible to attend games but often fall through the cracks of the ticketing system because they're not on the primary rosters that feed into the seating software. The office has a manual queue for inserting these athletes into appropriate sections, usually near the team area but separated from official roster passengers. It's a small operational detail, but one that matters if you're working inside the system and notice gaps in the seated population versus the expected roster size.
For people who want to dig into the actual workflow, there isn't a public-facing API or downloadable toolkit from Creighton. The university doesn't publish its ticketing configuration files or internal process documents. What I can say is that the general architecture mirrors what most modern NCAA ticket offices use: a central CRM tied to a ticketing engine, integrated with a university SSO for authentication, and connected to the stadium's scanning hardware via a real-time API. The customizations are where the differences live. Creighton's customizations center around donor management integration, which is tighter than most peer institutions have. If you're running a similar operation at a smaller school and looking to improve your own setup, the realistic first move isn't buying new software. It's cleaning up your data. I've audited systems where half the season ticket holder accounts had duplicate entries or mismatched email addresses, and fixing that alone cut processing time for transfer requests by about sixty percent. Software can't fix bad data. It just amplifies it. The campus spirit angle is harder to quantify but clearly matters to the office. Creighton doesn't run formalized student section ticket programs the way some larger schools do. Students get access through a lottery system tied to enrollment verification, which keeps the student sections full without giving away thousands of free tickets. It's a restraint that some programs would struggle to maintain, especially when student demand outstrips supply. The lottery runs once per semester for home games, and acceptance rates vary depending on how many seats are allocated to students versus the general public. It's not a perfect system, but it prevents the scenario you see at some schools where student sections are half-empty because the allocation process got gamed.
There's also an operational detail about how the office handles guest passes for recruits and their families. These aren't automated. A coach submits a request, the ticket office verifies it against NCAA limits on companion tickets, and then manually generates the passes. During busy recruiting periods in the spring, that manual step becomes a bottleneck. The office typically processes these within forty-eight hours, but I've seen it drag to seventy-two when multiple coaches submitted requests on the same day. No real fix for this other than staffing, which is a budget decision above their level. The biggest downside to the current system is that it's heavily dependent on staying on the current Catanys version and keeping the integrations current. When the university upgraded to a newer module last cycle, there was a two-week period where mobile ticket scanning was unreliable at the Mabee Center doors. Fans showed up, tapped their phones, and got errors. The office had to switch to manual seat lookup by name and zip code, which slowed entry to roughly one hundred and twenty people per minute instead of the normal four hundred. It was resolved after the vendor pushed a patch, but it's a reminder that these systems are fragile in ways that aren't visible until game day. For anyone trying to get a handle on how this all fits together, the practical takeaway is that Creighton's ticket office isn't running anything groundbreaking technologically. What separates it is the depth of customization, the quality of the data hygiene, and the institutional patience to iterate over years rather than expecting a single software purchase to solve the problem. Most programs fail at the data part, not the technology part.
