> For the complete documentation index, see [llms.txt](https://wiki.tinkerhub.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.tinkerhub.org/campus-community/campus-communities/campus-advisory-committee.md). # Campus Advisory Committee The Campus Advisory Committee brings together experienced TinkerHub campus leadership graduates to support the next generation of Campus Leads by sharing experiences, offering guidance, and helping campus communities grow. Having led campus communities themselves, the committee mentors Campus Leads throughout their leadership journey, helping them understand the current state of their campus, reflect on their progress, navigate challenges, and make meaningful decisions that strengthen their community. The 2026–27 structure introduces a dedicated mentorship system that ensures every campus has access to experienced alumni who can provide context, encouragement, and guidance throughout the campus program. ### Committee Structure The Campus Advisory Committee consists of experienced TinkerHub campus leadership graduates. Each member will be assigned **1–3 campus communities**, depending on the number of campuses and committee members. Members will serve for the entire **2026–27 Campus Program**. ### Selection The Campus Advisory Committee functions under the Campus Team. Experienced campus leadership graduates who wish to continue contributing to TinkerHub can express their interest by filling out the Advisory Committee application form. Based on the support required across campus communities and the overall composition of the committee, the Campus Team will onboard members and assign campus communities accordingly. ### Purpose & Responsibilities * Support assigned campus communities throughout the campus program by mentoring Campus Leads and their leadership teams. * Spend around **one hour every two weeks** with each assigned campus through regular conversations and check-ins. * Help Campus Leads understand where their campus currently stands, identify opportunities for growth, and think through the next steps for their community. * Share experiences, learnings, and best practices from previous campus leadership journeys to help leadership teams make informed decisions. * Provide guidance when campuses face challenges and encourage leadership teams to explore possible approaches rather than offering direct solutions. * Act as a sounding board for Campus Leads by listening, providing perspective, and encouraging reflection throughout their leadership journey. * Support leadership teams in building sustainable practices, healthy communities, and meaningful learning experiences. * Connect campuses with relevant people, resources, and opportunities across the wider TinkerHub ecosystem whenever appropriate. * Escalate concerns to the Campus Team whenever additional support or intervention is required. ### Meeting Cadence #### Bi-weekly Campus Check-ins Advisory Committee members are expected to stay in regular touch with their assigned campuses by spending around **one hour every two weeks** with each community. These conversations are intended to be informal check-ins where Campus Leads can discuss progress, seek guidance, reflect on challenges, or think through ideas with someone who has previously led a campus community. There is no fixed agenda for these conversations. The discussions should naturally evolve based on the needs of each campus while ensuring continuous support throughout the program. #### Monthly Advisory Committee Catch-up The Campus Advisory Committee and the Campus Team will come together once every month to reflect on how campus communities are progressing across the network. These sessions provide an opportunity to discuss common patterns, share learnings from campus conversations, identify recurring challenges, and align on how the Campus Team and Advisory Committee can better support Campus Leads. The meeting also serves as a space for Advisory Committee members to exchange experiences with one another, raise concerns that require collective attention, and collaboratively improve the mentorship experience across the campus program. ### Documentation Members are encouraged to maintain brief notes from campus interactions to help track progress, remember important discussions, and provide continuity throughout the campus program. ### Community Presence Members of the Campus Advisory Committee will receive an **Advisory Committee** tag recognising their continued contribution to the TinkerHub campus ecosystem. ### Collaboration with the Campus Team The Campus Advisory Committee works closely with the Campus Team to strengthen support for campus communities throughout the program. Members may be invited to contribute to leadership camps, selection camps, review sessions, onboarding programs, and other campus initiatives where their experience can benefit Campus Leads and leadership teams. The nature and extent of this involvement may evolve based on the needs of the campus program. ### Continuous Support & Communication The Campus Advisory Committee serves as a continuous support system for Campus Leads throughout the campus program. Campus Leads are encouraged to stay in touch with their assigned advisor whenever they need guidance, feedback, or an external perspective. While the responsibility of running a campus always remains with the Campus Lead and leadership team, the Advisory Committee exists to ensure that every campus has someone who understands the journey, believes in their growth, and is invested in helping them succeed. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.tinkerhub.org/campus-community/campus-communities/campus-advisory-committee.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.