> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/campus-chapter-playbook/lead-selection-and-tenure.md).

# Lead Selection and Tenure

All µLearn Campus Chapters operate on a fixed annual cycle in January to December. Campus Leads are selected through a structured nomination and interview process. Tenure is one full year.

### <mark style="color:$primary;">Tenure Duration</mark>

To ensure consistency and alignment with the academic calendar, all µLearn Campus Chapters operate on a fixed annual cycle:

* **Period:** The leadership tenure lasts for one full year.
* **Timeline:** The cycle runs from January to December.
* **Annual Review:** At the end of December, the chapter's progress is audited, and the transition to the new leadership team begins.

### <mark style="color:$primary;">Nomination & Application (For Existing Chapters)</mark>

For chapters already in operation, the candidate pool is built through three specific channels to ensure both continuity and fresh talent:

* **Lead Nomination:** The outgoing Campus Lead may nominate a successor based on their performance within the current Execom.
* **Faculty Nomination:** The Lead Faculty Enabler may nominate a candidate who has shown exceptional academic and leadership potential.
* **Open Application:** An open call for applications is sent out to the entire student body. Any student meeting the Level 4 and IG Task criteria may apply.

### <mark style="color:$primary;">The Selection & Interview Framework</mark>

Once the candidate pool is finalized, the selection follows a rigorous evaluation:

* **New Campus Chapters:** Interviews are scheduled and conducted by the Campus Activation Team from the µLearn Foundation (including District Leads, Zonal Leads, and Associates).
* **Existing Campus Chapters:** The outgoing Executive Committee (Execom) conducts the internal interviews.
* **Evaluation:** All candidates are assessed using a standardized evaluation sheet to ensure transparency and merit-based selection.
* **Appointment:** Exactly one Campus Lead is chosen from the interviewed candidates to head the chapter for the new tenure.

{% hint style="warning" %}
Manual Intervention: Campus Lead appointments for new chapters are managed by the Campus Activation Team. For existing chapters, the outgoing Execom conducts interviews. Contact \[<campus@mulearn.org>] for support.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mulearn.org/campus-chapter-playbook/lead-selection-and-tenure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.