> 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/guidance-for-campus-leads.md).

# Guidance for Campus Leads

As a µLearn Campus Lead, you are the visionary for your institution. While the µLearn Core Team provides the framework and resources, the transformation of your campus culture depends entirely on your initiative and ownership.

### <mark style="color:$primary;">Begin with Your Campus Reality</mark>

At µLearn, leadership starts with observation rather than assumption.

* **Identify Needs:** Spend time understanding what skills your peers are actually trying to build and what opportunities are currently missing on your campus.
* **Drive Engagement:** Design programs that motivate even the "silent" students to step forward and participate.
* **Feasibility:** Ensure your ideas align with the infrastructure available and the time constraints of your fellow students.

### <mark style="color:$primary;">Identify Challenges Without Fear</mark>

Challenges are a natural part of leadership; identifying them early is a sign of clarity and responsibility.

* **Anticipate Roadblocks:** Be honest about potential delays in faculty approvals, technical equipment issues, or clashes with academic schedules.
* **Solve the µLearn Way:** For every challenge, find a practical, simple solutions such as preparing clean outlines for faculty early or involving interested juniors when the core team is small.

### <mark style="color:$primary;">Strategic Focus: Levelling Up</mark>

Your primary metric for success is advancing the institution through the µLearn Campus Grading Framework.

* **The Progression:** Every chapter starts at Grade D (Emerging) and must work systematically toward Grade C, B, and finally A (Elite).
* **Key Targets:** Focus on increasing the number of Level 4+ µLearners and the frequency of Learning Circles (LCs).
* **Proof-of-Work:** Prioritize the completion of Mument projects and Impact Projects to demonstrate tangible student growth.

Go to[ **Campus Grading Framework**](/campus-chapter-playbook/campus-grading-framework.md) to understand exactly what each grade requires.

### <mark style="color:$primary;">Ownership and Professionalism</mark>

You carry the spirit of µLearn into your campus through every action you take.

* **Lead by Doing:** Set the standard by maintaining your own profile and leading by example within your chosen Interest Group.
* **Execution:** Step into execution with respect for faculty and clear communication with your volunteers.
* **Reflection:** After every program, evaluate what worked and what didn't to strengthen the chapter's future.


---

# 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/guidance-for-campus-leads.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.