[ ← back to projects ]
> cat case-studies/event-management.md

Event Management Platform

Client
JRC Investments
Role
Senior Software Engineer — maintenance, production support, security hardening
Team
2 developers
Stack
Angular + Ionic (frontend/mobile), Laravel (backend)
Scale
100+ events supported, 10-20 events/month, 100+ attendees per event
Status
Live, in active use — ongoing maintenance engagement
< Angular />< Ionic />< Laravel />< Maintenance />
// awaiting assetsScreenshots for Event Management Platform are coming soon
> the situation

Running events at volume — 10 to 20 a month, each with 100+ attendees — breaks down fast if check-in, event operations, and the money side of the business aren't unified. JRC Investments needed a platform that could run event creation and management, attendee check-in, and event-day mobile operations, together with a separate accounting/finance portal, reliably as event volume scaled.

> what was built

Core platform (Angular + Ionic frontend, Laravel backend) — event creation and management, attendee check-in, and a Quick Scan mode for high-volume check-in, all accessible via mobile event operations rather than requiring a desktop PC on-site. A separate accounting/finance portal handles the money side independently.

Ongoing engineering ownership — responsible for maintenance of both the platform and mobile app, production issue patching, and backend contribution alongside the other developer.

Modernization — the applications ran on a significantly outdated Angular codebase (roughly 6-7 versions behind); upgraded to the current latest Angular version, including the downstream Android/iOS build-target modernization that comes with a jump that size.

Security hardening — identified sensitive secrets and access credentials exposed directly in the frontend, trivially extractable from the client application; remediated by moving those operations behind the proper backend boundary.

> results
100+
Events supported
10-20/month
Event volume
100+
Attendees per event
Up to ~6×
Check-in speed (Quick Scan vs. standard)
observed workflow timing
2 developers
Engineering team

No verified revenue-lift percentage is claimed — the scale figures above are directly observed and verifiable instead.

> the lesson

The most valuable part of this engagement isn't a single feature — it's ownership of the platform's reliability at production scale. Rapid patching under real event-day pressure, closing a real credential-exposure gap before it became an incident, and modernizing a stack running on deprecated dependencies are the unglamorous work that keeps a live system trustworthy as usage grows.