# organize HANDOVERS

## Why Handover Matters

<details>

<summary>What is this guide?</summary>

This is a short, practical companion for oikos chapters navigating leadership transition. It is not a bureaucratic checklist. It is a **continuity tool.**

It helps outgoing teams pass on **clarity**, **relationships**, and **momentum** — and helps incoming teams step in with **confidence** instead of confusion.

At its core, this guide supports chapters in thinking beyond a single term and beyond a single team.

</details>

<details>

<summary>Why does it exist?</summary>

Because oikos is not a collection of isolated student groups. It is an **ecosystem**.

An ecosystem only works when:

* *Knowledge flows across generations*
* *Chapters stay aligned with shared values*
* *Initiatives outlive individual leaders*
* *Local action connects to global direction*

When transitions are messy, momentum is lost. Partnerships fade. Energy resets to zero.

This guide exists to protect continuity — so that projects, partnerships, and bold ideas can **transcend one academic year** and contribute to long-term systemic impact.

</details>

<details>

<summary>Why <em>you</em> reading this matters.</summary>

Whether you are stepping out or stepping in, you are part of something bigger than your term.

Your decisions shape:

* *How stable your chapter feels next year*
* *Whether initiatives continue or disappear*
* *How aligned your chapter stays with the broader oikos movement*

Leadership in oikos is not just about running events well. It is about **stewarding something that existed before you, and will exist after you.**

</details>

## The Journey Map

Handover isn’t one day. It’s a process. Here’s the simple flow:

{% tabs %}
{% tab title="Start Early" %}

* Begin the handover conversation at least a month before semester end
* Elect or appoint the next core team
* Reflect on what worked and what didn't
* Create a list of all key activities and contacts, even if messy!
  {% endtab %}

{% tab title="Overlap Period" %}

* Schedule 2-3 joint team meetings (new & old teams)
* Let new leads shadow ongoing tasks
* Introduce successors to key partners and allies
* Use informal Q\&A sessions and dedicated co-working time
  {% endtab %}

{% tab title="Support & Step Back" %}

* Set up a simple ongoing chat for questions
* Outgoing leads act as gentle mentors for 2–3 months (and/or join advisory board)
* **Outgoing President introduces new President to oikos International**
* Recommended: Agree on boundaries (support ≠ control)
  {% endtab %}
  {% endtabs %}

## The Essential Kit

{% tabs %}
{% tab title="Must-Share Knowledge" %}

* Constitution and other legal documents
* Role descriptions (even bullet points are fine!)
* Calendar of events & key dates
* What tools you use (emails, drives, platforms)
* Important logins (use a shared **password manager** if possible)
* Partner, sponsor, university, and alumni contacts
* Successes & failures: What worked? What flopped?
  {% endtab %}

{% tab title="Personal Reflections" %}

* What we wish we knew when we started
* What kept us motivated (and what burned us out)
* Our chapter culture: what’s sacred, what’s flexible
  {% endtab %}
  {% endtabs %}

## oikos International Connection

* Make sure to have access to your [chapter's official oikos emails](https://wiki.oikos-international.org/oikosmos/~/revisions/cQanmF4cMPx5ld2MDHj9/starter-kit/community-engagement/community-calendar) (every chapter has at least 2 emails: info & president)
* Submit new President contact info to oikos International
* Share a short action plan for your next 6 months (for feedback and alignment)
* Join oikos International calls & programs
* Request to join relevant [WhatsApp groups](https://wiki.oikos-international.org/oikosmos/~/revisions/cQanmF4cMPx5ld2MDHj9/starter-kit/community-engagement/discord)

## Organising for Continuity

Handover should never be a once-a-year panic. You can make transitions smoother by **designing for continuity all year round.**

{% tabs %}
{% tab title="Set Up Systems That Outlive You" %}

* Use **shared** drives and folders from day one – no personal emails or private docs
* Keep a running log of key decisions, ideas, and updates  (Google Docs, etc.)
* Store all logins in a shared password manager
* Organize your chapter workspace like someone else will use it tomorrow
  {% endtab %}

{% tab title="Build a Culture of Openness" %}

* Regularly involve new members in tasks so they learn by doing
* Document your experiments – successes *and* flops
* Encourage monthly reflections or casual team notes
* Celebrate learning, not just polished results
  {% endtab %}
  {% endtabs %}


---

# 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://wiki.oikos-international.org/oikosmos/best-practices/how-to.../organize-handovers.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.