When 7,000 Students Need Your Platform to Work
Every three years, InterVarsity Christian Fellowship runs Urbana—the largest missions conference in North America. For 75 years, college students have gathered for five days of workshops, worship, and conversations with ministry leaders about vocation and calling.
At Urbana 25, every student would complete TruCenter, a vocational assessment that reveals God-given motivations and helps students understand how to steward their gifts. The results would shape their conversations with mentors, recruiters, and coaches throughout the week.
But TruCenter had never operated at this scale. And in the high-pressure environment of a conference—packed schedules, unpredictable venue wifi, thousands of students accessing the platform simultaneously—there was no backup plan.
The platform had to work. The first time. Under load. Without failure.
6,000+
Assessments Completed
10,000
Users Stress Tested
0
Minutes of Downtime
75
Years of Urbana History
The Problem
TruCenter isn't a personality quiz. It's a tool for vocational discernment that helps students identify intrinsic motivations—the patterns that shape how they engage with work, relationships, and calling. Students complete the assessment, receive personalized results, and use those insights in real conversations about career direction and ministry involvement.
For Urbana 25, TruCenter was central to the conference experience. But the platform had only served hundreds of concurrent users at a time. Urbana would bring thousands—all accessing the system simultaneously during breaks between sessions, on devices ranging from phones to tablets to laptops, competing for bandwidth with hundreds of other conference systems.
InterVarsity needed three custom features built before the conference:
- Emergency contact collection integrated into registration, ensuring staff could track student safety throughout the event.
- Post-event survey capability that would automatically appear in the app after the conference concluded, capturing feedback while the experience was still fresh.
- Custom data exports tailored to Urbana's operational workflows, giving staff immediate access to the information they needed in formats they could actually use.
The technical challenge was clear: scale the platform to handle conference load without compromising the experience. But the real pressure was organizational. Urbana had invested heavily in making TruCenter central to their vocational discernment framework. If the platform failed during the conference, thousands of students would miss crucial conversations with mentors and ministry leaders. The programming schedule didn't have room for technical recovery.
This wasn't a product launch where you can iterate based on user feedback. This was a single moment, with 7,000 students, and no second chance.
What We Built
We began conversations in February 2025 and started development in August, giving ourselves four months to build, test, and prepare before the December conference.
The first priority was understanding constraints. Conference wifi is notoriously unreliable. Students would access TruCenter during breaks—meaning sudden traffic spikes when sessions ended and thousands tried to complete assessments simultaneously. The platform needed to handle that reality, not ideal conditions.
We focused on three areas: infrastructure, performance, and reliability.
Infrastructure for Scale
The existing hosting infrastructure wasn't built for conference-scale load. We reconfigured the environment to support auto-scaling, allowing the platform to spin up additional capacity automatically as traffic increased. We built in significant margin—if Urbana expected 5,000 concurrent users, we designed for 10,000.
Performance Under Pressure
We analyzed the application's database queries and found opportunities to reduce load. Strategic caching meant the platform could serve common requests without hitting the database repeatedly. We restructured data access patterns to handle concurrent users efficiently.
The goal wasn't just keeping the platform online—it was keeping response times fast enough that students wouldn't wait. In a conference environment where students have ten minutes between sessions, a slow platform is a broken platform.
Reliability When It Matters
We integrated the three custom features—emergency contacts, post-event surveys, and data exports—directly into the core platform rather than building them as separate systems. This reduced complexity and potential failure points.
By November, we moved into intensive stress testing. We simulated loads that exceeded expected conference traffic, watching how the system responded under pressure. Each test revealed adjustments to make: queries to optimize, cache policies to tune, infrastructure settings to refine.
We couldn't control conference wifi. We couldn't control what devices students would use or when they'd all decide to access the platform at once. But we could control how efficiently TruCenter used whatever connection it got.
By early December, we were ready.
What Happened
Urbana 25 ran December 28 through January 1 in Phoenix. Over five days, approximately 6,000 students completed the TruCenter assessment. The platform handled peak concurrent load without incident.
No downtime. No bottlenecks. No emergency calls to troubleshoot issues during the conference.
Students accessed their results immediately after completing the assessment and used those insights in conversations with mentors, vocational coaches, and ministry recruiters throughout the week.
Conference staff had real-time access to student data through the custom export tools. Emergency contact information flowed into their systems automatically. When the conference ended, the post-event survey deployed without manual intervention.
The feedback from Urbana's team was straightforward: "Thanks. Everything worked perfectly."
For software serving high-stakes events, that's what success looks like. Not dramatic saves or heroic troubleshooting during the conference—just infrastructure doing exactly what it was built to do, invisibly and reliably, when thousands of students needed it to work.
What This Changed
Students got clarity when it mattered most
The entire vocational discernment framework at Urbana depended on students understanding their motivations before sitting down with mentors and recruiters. TruCenter delivered those insights immediately, during the week when decisions about calling and direction were actually being made. No waiting for results after the conference. No technical delays interrupting the experience.
Conference staff operated with confidence
Previous large-scale events carried anxiety about whether systems would hold up under load. For Urbana 25, that anxiety never materialized. Staff focused on serving students rather than troubleshooting technical failures. The custom data exports gave them operational visibility throughout the week without manual workarounds.
Ministry partners had substantive conversations
Recruiters and vocational coaches relied on TruCenter results to guide conversations with students about fit and next steps. When the platform worked reliably, those conversations happened at depth rather than getting derailed by missing data or incomplete assessments.
InterVarsity gained proof of concept
TruCenter is now validated at conference scale. The platform can serve Urbana's largest gatherings and support ongoing use between conferences. What was uncertain in February became proven infrastructure by January.
What We Learned
Understanding constraints matters more than adding capacity
The technical work—infrastructure changes, caching strategy, database optimization—was methodical but not exotic. What made it succeed was understanding the real constraints: conference wifi, student devices, simultaneous traffic spikes during breaks. We built for those conditions rather than ideal circumstances.
Stress testing finds what planning misses
Simulating traffic that exceeded expected conference load revealed bottlenecks that looked fine in design documents. When you can't afford failure, you can't skip testing. The margin we built into infrastructure proved necessary when real-world usage patterns didn't match predictions.
Integration reduces failure points
Building emergency contacts, surveys, and data exports directly into the platform rather than bolting them on afterward meant fewer systems to coordinate and fewer places where things could break under pressure.
Mission organizations can deliver at enterprise scale
Faith-based organizations sometimes assume that 'enterprise-grade' infrastructure is out of reach—reserved for venture-backed companies with massive budgets. Urbana proved otherwise. With disciplined engineering, methodical testing, and partnership with a team that understands both technical requirements and mission context, organizations serving thousands of users can deliver experiences that work without compromise.
Invisible software is successful software
The best outcome for high-stakes infrastructure is that nobody notices it. No drama during the event. No heroics required to keep systems running. Just reliable performance that lets the actual work—in this case, helping students discern calling—happen without technical interference.
Need Your Platform Ready for Scale?
Whether you're preparing for a major event or building infrastructure that needs to grow with your organization, we can help you get there.