> 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/the-6-week-onboarding-roadmap.md).

# The 6-Week Onboarding Roadmap

Every new campus chapter follows a 6-week launch sequence from appointing core leadership to running the first Learning Circle to launching the first Impact Project.

{% stepper %}
{% step %}

### <mark style="color:$primary;">Week 1: Establishing the Pillars</mark>

* **Leadership Appointments:** Within 7 days, the Campus Lead must finalize the dual-pillar support system by appointing a proactive Campus Co-Lead and a Lead Faculty Enabler.
* **Campus Co-Lead:** Select a student who is reliable, proactive, and a strong communicator to share upcoming responsibilities and decision-making.
* **Lead Faculty Enabler:** Identify an approachable faculty member to serve as the primary liaison between the student chapter and the college administration.
* **Strategic Management Meeting:** The Lead, Co-Lead, and Enabler must conduct a formal briefing with the Principal or Director.
* **Institutional Value:** Highlight how µLearn complements academics through skill-building and provides rigorous evidence for NAAC/NIRF metrics through documented "Impact Projects" and "Learning Circles".
* **Resource Commitment:** Secure official "green lights" for infrastructure access (labs/classrooms), venue bookings, and policy alignment for student initiatives.
  {% endstep %}

{% step %}

### <mark style="color:$primary;">Week 2: Core Team & Identity</mark>

* **Domain Identification:** Observe your campus to identify which interest areas (Software, Maker, Creative, or Management) have the highest demand.
* **Recruitment & Synergy:** Select IG Leads to form the Core Team. If specialized communities already exist on campus (e.g., an AI club), collaborate with them to expand their impact rather than duplicating effort.
* **Campus Orientation:** Host a session to define the µLearn movement, share success stories, and outline student benefits.
  * **What is µLearn?:** Define the movement, its core values, and its focus on skill development through peer-to-peer interaction.
  * **Success Stories:** Share examples of past µLearn achievements to inspire potential members.
  * **Student Benefits:** Clearly outline the opportunities for networking, real-world project experience (Muments), and the benefits of joining specific Interest Groups (IGs).
  * **Call to Action:** Encourage students to register on the platform and join their respective department or domain-based learning circles.

{% hint style="info" %}
***Orientation Deck: <https://mulearn.org/r/orientationdeck>***
{% endhint %}
{% endstep %}

{% step %}

### <mark style="color:$primary;">Week 3: The "Icebreaker" Phase</mark>

* **First Activity:** Conduct a fun, high-energy event to generate curiosity. It need not be technical; games or performances can be used to create a vibrant atmosphere.
* **Digital Setup:** Establish official Instagram and LinkedIn accounts using the mandatory **mulearn.\<campuscode>** naming convention.
* **Community Groups:** Launch a WhatsApp group for internal coordination and begin sharing highlights of activities to build social presence.
  {% endstep %}

{% step %}

### <mark style="color:$primary;">Week 4: Anchoring the Learning Culture</mark>

* **First Learning Circle (LC):** Select a high-interest topic and host a session during or after college hours.
* **Collaborative Learning:** Divide students into small groups, providing them with the mentors and resources needed to learn together.
* **Proof-of-Work:** Every LC must culminate in a simple project to apply learned skills.
* **Public Visibility:** Participants must make their work public via GitHub, LinkedIn, Behance, or Medium to build their professional portfolios.
  {% endstep %}

{% step %}

### <mark style="color:$primary;">Week 5 & Beyond: The Impact Launch</mark>

* **Scale Operations:** Increase the frequency of Learning Circles and peer-learning gatherings.
* **Impact Project Launch:** Initiate the first official Impact Project following the "Learn-Build-Deploy" cycle.
* **Public Announcement:** Publicly announce the project; this external accountability ensures the team remains motivated to achieve the end result.
  {% endstep %}

{% step %}

### <mark style="color:$primary;">Week 6 & Beyond: Trajectory to Excellence</mark>

* **Grading Alignment:** Consult the µLearn Campus Grading Framework to move from Grade D toward Grade A.
* **Leaderboard Strategy:** Monitor the global leaderboard and emulate successful strategies from top-performing campuses.

→ To understand the grading framework in full, go to [**Campus Grading Framework**](/campus-chapter-playbook/campus-grading-framework.md)
{% endstep %}
{% endstepper %}


---

# 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/the-6-week-onboarding-roadmap.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.