Coordinating guard availability across web and mobile platforms was fraught with scheduling conflicts, especially during peak events like concerts or festivals. The platform lacked granular filters for guard skills (e.g., first aid, crowd control), leading to mismatches between client needs and guard expertise. Payment disputes arose frequently due to ambiguous timesheet tracking, and sudden traffic surges during major events crashed the servers.
Geolocation-based guard allocation was unreliable, often assigning guards too far from event locations. Clients demanded flexible payment options (split billing, subscriptions), but the existing gateway couldn’t handle complex workflows. The Flutter app suffered from slow load times, and admins lacked tools to resolve booking conflicts efficiently, resulting in last-minute cancellations.
02 . The Solution
A geolocation algorithm prioritized guards within a 10-mile radius of events, with skill tags for precise matching. The Flutter app added GPS-based check-in/out timers to log guard hours, reducing payment disputes by 80%. Auto-scaling cloud servers handled traffic spikes, and a modular payment gateway supported split billing and subscriptions. Next.js dashboards gave admins real-time conflict resolution tools, improving booking efficiency by 60%.
Optimized by Seraphinite Accelerator