Clubs die between events. The ones that last publish a calendar and put names on it, so a missed week is a known gap and not the beginning of the end. This is the yearly shape TechVerse Enclave settled into, adapted for an academic year that starts in July or August.
Quarter 1: recruit and orient (Aug–Oct)
- Induction session for first-years with a practitioner speaker — see planning an induction seminar.
- Two beginner build sessions: a page, a form, a deploy.
- First project demo day at the end of the quarter: everyone shows something, however small.
- One external hackathon entered as club teams.
Quarter 2: build depth (Nov–Jan)
- A one-day GenAI workshop with a visiting practitioner.
- Weekly office hours; see office hours for students.
- An internal mini-hackathon over one weekend, judged with a published rubric.
- A quiet fortnight around exams, announced in advance.
Quarter 3: compete and show (Feb–Apr)
- The college's own hackathon or fest, organised with the organiser's guide.
- Two external hackathons — the season when many institutes run theirs.
- Portfolio and mock-interview clinic for pre-final years.
Quarter 4: hand over (May–Jul)
- Leadership transition with written ownership of each track.
- A summer build challenge with remote check-ins.
- Planning the next year's calendar and speaker outreach, eight weeks before inductions.
Who owns what
Each track — AI, web, security, data, startups, operations — has one named owner responsible for its sessions. Owners change yearly; the calendar does not. That continuity is what let a college group become a 500+ member community.
Clubs that want a practitioner slotted into this calendar — an induction talk, a workshop, a judge for the internal hackathon — can plan the year with me through the invite page.
— Pranjul Rathour, GenAI Engineer from Kanpur, India. Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at any campus: pranjulrathour41@gmail.com.