Angular + Node.js Registration Platform for an Endurance Relay Race Series

Our client runs a national series of overnight endurance relay races, with a New York operations office led by David Rosen, Director of Operations, based out of Brooklyn. Teams of runners cover long distances over a full day and night, which means registration isn't a simple checkout — it's team formation, roster changes, waiver collection for every runner, and race-weekend logistics all rolled into one flow. David brought us in over three years ago to rebuild a registration system that was buckling every time a popular race opened for sign-ups.

What we built

• Team & solo registration — multi-step flow for building a team roster, assigning runners to legs, and handling solo entries.
• Race finder — browse upcoming races by date, location, and distance across the whole season.
• Digital waivers & liability forms — every runner on a roster signs individually before race day, tracked and stored per team.
• Payments & capacity management — team and per-runner payments, with automatic waitlists once a race sells out.
• Race-weekend logistics tools — van assignments, checkpoint tracking, and day-of communication for race staff.
• Mobile-friendly runner dashboard — roster, waiver status, and race details, checked from a phone in a van at 3am.

Why Angular + Node.js

Team registration for a relay race is a genuinely complex, multi-step form — captain sign-up, invite teammates, assign legs, collect waivers, take payment — with a lot of state and validation to keep consistent across steps. Angular's structured framework and strong form-handling made it a good fit for building that flow in a way that stays maintainable as new race formats and rules get added each season.

Node.js handles the backend, which matters most in the exact moments it's tested hardest: when registration opens for a popular race and thousands of teams try to sign up in the same few minutes. Its event-driven model handles that concurrent load without the system falling over.

Three years, season after season

1. Year 1: Rebuilt team registration, waivers, and payments to handle high-demand race openings without crashing.
2. Year 2: Added the race-weekend logistics tools — van assignments and checkpoint tracking for race-day staff.
3. Year 3: Waitlist automation and a mobile-first runner dashboard, built around real feedback from race weekends.
4. Ongoing: New race launches and capacity planning ahead of every registration window each season.

The real test of a registration platform isn't a quiet Tuesday — it's the exact minute a popular race opens and thousands of teams hit "register" at once.

Why this matters for event operators

Race series, tournaments, and large ticketed events all share the same risk: a registration system that works fine most of the year and buckles at the one moment it matters most. Building for that peak-demand moment — not just the average day — is what separates a platform that survives a popular launch from one that goes down in the first five minutes. That's the standard we build to.