# Campus ExCom Structure

**TLDR:** The Executive Committee (Execom) is the core operating team of the chapter, Campus Lead, Co-Lead, Tech Lead, Creative Lead, Media Lead, and Alumni & Industry Lead. It operates on a "Lead by Doing" principle where every role is tied to domain expertise.

The Executive Committee (Execom) is the core operating team of the chapter. It should be a reflection of skill, leadership, and diverse interests, functioning as the engine that drives all campus initiatives.

### <mark style="color:$primary;">Core Team Structure & Selection</mark>

The Execom operates on a "Lead by Doing" principle, where administrative roles are directly tied to domain expertise.

* **Standard Roles:** The core team includes the Campus Lead, Co-Lead, Tech Lead, Media Lead, Creative Lead, and Alumni & Industry Lead.
* **Flexibility:** The structure is not rigid; campus chapters have the freedom to decide their specific structure and size.
* **Selection Logic:** Members must be chosen based on their skill sets and leadership capacities to ensure the chapter remains impact-oriented.

### <mark style="color:$primary;">Role Descriptions</mark>

<mark style="color:$primary;">**Campus Lead - Visionary**</mark>\
Strategy, community synergy, and operational execution. The Campus Lead is the visionary for the institution. The transformation of campus culture depends entirely on their initiative and ownership.

<mark style="color:$primary;">**Co-Lead - Executioner**</mark>\
Shares upcoming responsibilities and decision-making with the Campus Lead. Must be reliable, proactive, and a strong communicator.

<mark style="color:$primary;">**Tech Lead**</mark>\
Must actively lead the Software or Maker Interest Groups. Responsible for all technology-oriented initiatives on campus.

<mark style="color:$primary;">**Creative Lead**</mark>\
Must actively lead the Creative Interest Groups. Responsible for design, media production, and creative community activities.

<mark style="color:$primary;">**Media Lead**</mark>\
Manages all official social media handles, documentation, and campus communications. Maintains the mulearn.\<campuscode> handle.

<mark style="color:$primary;">**Alumni & Industry Lead**</mark>\
Facilitates the "Industry-Bridge" initiatives. Identifies and engages alumni and industry professionals to support campus IGs through mentorship, domain sessions, and opportunities.

### <mark style="color:$primary;">Interest Group (IG) Integration</mark>

Interest Groups are the heartbeat of the Execom. To ensure the leadership stays grounded in the learning philosophy:

* **IG Leadership:** IG Leads are preferred for core functional roles. A Lead from the Software Cluster should ideally serve as the Tech Lead, while those from the Creative Cluster should lead Media and Creative responsibilities.
* **Mandatory Membership:** Every single Execom member must belong to at least one Interest Group.
* **Support System:** The Execom exists to serve and support all IGs, ensuring every Interest Group has a planned pipeline of activities and defined goals.

### <mark style="color:$primary;">The Enabler Family</mark>

The leadership ecosystem extends beyond students to include faculty:

* **Unlearn Network:** It is mandatory to ensure that the Lead Faculty Enabler joins Unlearn, the global µLearn campus enabler family.
* **Role:** The Enabler acts as the primary liaison, providing the "scaffolding" (permissions and institutional guidance) that allows the student-led ecosystem to function.

### <mark style="color:$primary;">Branding & Resources</mark>

* **Access:** Upon request by the Campus Lead, the µLearn Foundation provides official social media links and comprehensive branding kits.
* **Support:** The µLearn Core Team further supports the Execom by providing templates, documents, and best practices to ensure the chapter never feels isolated in its journey.

{% hint style="warning" %}
Manual Intervention: Campus Lead appointments and changes require core team approval. Contact \[<campus@mulearn.org>].
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mulearn.org/campus-chapter-playbook/campus-excom-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.