The business
A university-level events operation coordinating student events, participants, and internal approvals.
The problem
- Participant sign-ups and internal approvals handled over email
- No shared record of which events were approved, staffed or ready
- Reporting rebuilt manually after every event
The system
An event platform where each event moves through submission, approval, participant registration and execution, with attendance and reporting built in.
Unifest · Event approvalrecreated · illustrative
SubmittedStudent society
ReviewedActivities office
ApprovedAdministration
4
Registration open312 registered
Event-day attendanceopens on the day
- Event submissions
- Approval flow
- Participant registration
- Attendance
- Reporting
- Role-based access
Interface recreated with illustrative data — production screenshots aren't published to protect client data. We walk through the live system on a call where the client permits.
The workflow
- 01Event submitted
- 02Approval
- 03Registration
- 04Participants
- 05Event Day
- 06Attendance
- 07Reporting
“ORCHESTR understood that managing UniFest involves many moving parts that need to stay connected. They built the system around those workflows instead of trying to fit us into an existing template. It gives us a much clearer structure for managing the operation and keeping the important information in one place.”
Running something with this many moving parts?
Next caseJackets