Background
Student clubs and campus organizations frequently conduct events such as workshops, hackathons, seminars, and competitions.
Managing these events often involves manual registrations, scattered communication, and poor participant tracking, leading to
inefficiency and confusion for both organizers and participants.
Objective
Design and build a working prototype that helps student clubs or organizing bodies manage events
effectively, focusing on registrations, communication, and participant tracking.
Core Requirements
-
Participant Flow: Implement a complete flow covering registration, confirmation, and participant updates.
-
Role-Based Views: Clearly differentiate between a participant (user) view and an admin (organizer) view.
Participant View (User)
- Register for an event
- View registration or participation status
- Receive updates or announcements
Admin View (Organizer)
- Create and manage events
- View and manage registered participants
- Update participant status (confirmed, pending, rejected)
- Send announcements or updates
Scope & Constraints
- Focus on core functionality over design perfection
- Mock data and simulated workflows are acceptable
- Any tech stack or libraries may be used
- Deployment is optional, but the prototype must be demo-ready
What Is Not Required
- Production-ready systems
- Payment gateways
- Complex authentication mechanisms
- Mobile applications (web prototype is sufficient)
Expected Outcome
By the end of the hackathon, teams should demonstrate a functional prototype showing both participant and admin workflows,
explain their design decisions, and briefly discuss possible future improvements.