University Program Handbook

• No owner remains on campus after the event.
• No follow-up exists within the two weeks when intent is highest.
• The format rewards attendance rather than a completed build.
• Faculty have no stake, so access is not renewed.
• Graduation erases institutional memory every year.

• Evidence of existing student technical clubs and past events.
• At least one faculty member already engaged in industry programs.
• Administrative willingness to allow recurring sessions and external tooling.
• Reachable location for your operators on a repeating basis.
• Student cohort matched to your segment — not simply a large campus.

Recommendation: qualify campuses with a written scorecard and re-qualify every year.

• Lead with what the faculty member needs: teaching material, student outcomes, research relevance, industry exposure.
• Offer something durable — curriculum modules, lab credits, or workshop material they can reuse.
• Keep one named contact and a predictable communication rhythm.
• Formalise lightly: a short memorandum beats an unwritten arrangement.

Curriculum is the highest-leverage and slowest-moving surface. Treat it as a multi-semester objective, starting with electives, labs, and project work rather than core syllabus change.

1. 01Offer a self-contained lab module with datasets, exercises, and grading guidance.
2. 02Pilot it with one faculty member in one section.
3. 03Collect student outcomes the department can report.
4. 04Extend to additional sections, then additional departments.

Roles

Lead, technical lead, events, content, and outreach — named, not implied.

Term

One academic year, with handover built into the calendar.

Charter

A one-page document stating purpose, cadence, and expectations.

Support

Materials, swag where appropriate, mentor access, and a direct escalation path.

• Select for consistency and follow-through, not popularity.
• Give real responsibility: owning a workshop series, a project track, or onboarding.
• Recognise publicly and specifically — references, certificates, speaking slots.
• Create a path upward: contributor, chapter lead, regional lead, alumni mentor.

• Cap attendance so every participant can be unblocked.
• Require a laptop-ready environment checked before the session.
• End with something built and pushed, not a slide deck.
• Run a follow-up clinic within two weeks.

1. 01Attend a session.
2. 02Complete a guided build.
3. 03Complete an unguided build.
4. 04Make a first external contribution — issue, PR, documentation fix, or demo.
5. 05Help another student do the same.

Leadership should be earned through visible contribution, and handed over before the leader graduates. Plan succession one full semester ahead.

• Standardise materials centrally; let campuses adapt delivery.
• Cluster campuses geographically so one operator can serve several.
• Run a monthly all-chapter call to transfer practice between campuses.
• Keep a single shared calendar and a single reporting format.

Weeks 1–3

Chapter kickoff, recruitment, and orientation session.

Weeks 4–8

Core workshop series and clinics.

Weeks 9–12

Project sprint or campus hackathon, with mentor support.

Weeks 13–15

Showcase, contribution push, review, and succession planning.

Break period

Materials refresh, faculty review, next-semester calendar published.

• Active chapters — those running programming this semester, not those registered.
• Faculty participation — sessions supported or modules taught.
• Student progression — counts moving from attendance to build to contribution.
• Repeat programming — number of consecutive semesters with activity.
• Leadership pipeline — identified successors per chapter.