How a Global Nonprofit Ran a 10,000+ Person Conference With a System Its Team Could Operate

01The constraint

The registration team needed to manage a complex set of rules across roughly six pass types and 150 locations, with locations grouped into regions.

A simple operational change could require engineering work.

Moving available pass slots from one location to another meant changing the backend and database. User mistakes could also create support issues that required developer intervention. The team had limited visibility into who had changed what, and different administrators needed different levels of access.

As the conference approached, reliability became a bigger concern. The registration team could not afford to spend the event worrying about whether the system would handle the load or whether a routine issue would require an engineer.

They needed the system to handle the complexity while giving the people running the conference direct control over the operation.

02The context

The organization regularly organizes large conferences that require registration, pass allocation, payments, communications, and coordination across multiple teams.

For the conference, the Philippine delegation alone involved roughly 10,000 attendees. The registration operation needed to manage different pass types, location-based allocations, payment processing, and a large volume of changes and user requests.

The previous system had been developed in-house. The registration team depended on developers for operational changes, including moving pass slots between locations. When bugs appeared, engineers had to step in and resolve them. The team also faced the usual pressure of preparing a large event while knowing that the registration system had to remain reliable under a significant load.

03How we approached it

Scale XY rebuilt the registration operation around the way the conference team actually worked.

We gave administrators direct control over pass allocations and locations, rather than making routine changes dependent on developers. The system also gave the team configurable control over copy, images, and other registration content.

We introduced role-based access controls so different team members could work within appropriate permissions. Audit logs gave the organization a clear record of changes and actions.

We also designed the system around the operational problems that appear during a large event. Administrators could correct user information, such as a mistyped email address, and resend confirmation emails themselves.

Scale XY also handled deployment and infrastructure, including scalability, security against bots and spam, and observability.

The entire system was built, tested, and refined over three months.

04What we changed

The registration team moved from relying on developers for routine operational changes to managing the registration operation themselves.

They could move pass allocations between locations, update registration content, manage user information, resend confirmation emails, and review activity through audit logs.

Administrators gained clear reporting and visibility into registration activity. Role-based permissions gave different members of the team defined access to the system.

The platform supported approximately 10,000 Philippine delegates within a broader global conference of 10,000–12,000 attendees, with six pass types distributed across 150 locations.

The biggest change became clear after the conference.

During the post-conference review, the registration team highlighted the system as one of the strongest parts of the event. Instead of spending their time worrying about system reliability and troubleshooting, they could focus on work that required people: creating and distributing physical passes, talking to attendees, and handling the event itself.

The team reported encountering only one system-related error, which they identified as human error. They were also able to resolve most issues themselves without waiting for developers.

05Technology

Scale XY built the registration platform with configurable administration, role-based access, payment integration with Maya, automated email workflows, audit logs, and infrastructure designed for scale, security, and observability.

The technology gave the registration team control over the operation without requiring them to understand the underlying system.

06What we'd tell you again

Large event systems create a different kind of software problem. The challenge does not end when the platform launches.

The people running the event need enough control to respond to changes, mistakes, and edge cases while maintaining accountability for every action.

For the organization, giving the registration team that control reduced their dependence on engineering during the period when engineering support mattered most.