Building a Scalable Student Volunteer Structure: Coordinators vs Desk Staff

The Volunteer Management Trap

Every student convener begins with high enthusiasm: 120 juniors sign up to volunteer for the annual festival.

By Day 1 at 11:00 AM: 30 volunteers are standing near the stage watching rehearsals. 40 volunteers are sitting in the canteen eating lunch. * Only 4 volunteers are at the main gate, completely overwhelmed by 800 incoming attendees.

When volunteer roles are ambiguous, work concentrates on a few exhausted leaders while the rest wander aimlessly.

---

1. The Three-Tier Festival Hierarchy

Level 1: Core Conveners (3–5 Students)
         └── Overall festival accountability, faculty liaison, emergency decisions.

Level 2: Domain Leads (8–10 Students) ├── Head of Gate Operations & Security ├── Head of Finance & Ticketing ├── Head of Stage & Artist Logistics └── Head of Hospitality & Catering

Level 3: Operational Volunteers (80–100 Students) └── Divided into dedicated 4-person functional cells. ```

---

2. Enforcing Role Separation on Spark

In Spark (20261107000200_club_owner_and_member_only.sql): To prevent security leaks, Spark enforces strict, minimal event staff roles:

A. Co-Organizer / Manager (manager) Given to Domain Leads (Finance, Gate Heads). Permissions: Edit event details, approve pending direct UPI registrations, execute gate overrides, export CSV ledgers.

B. Volunteer (volunteer) Given to junior desk staff and ushers. Permissions: Open the mobile scanner, check attendees into assigned stations, view the live door list. Safeguard: Volunteers cannot edit event settings, view private financial credentials, or delete attendees.*

---

3. Shift Rotations & Care

Maximum 3-Hour Shifts: Never keep a student on gate duty for 8 continuous hours. Rotate gate volunteers every 3 hours. Feed Your Crew First: Ensure volunteers receive festival meals 45 minutes before general lunch lines open. A well-fed volunteer team is patient, alert, and courteous to attendees.