Skip to content

Onboarding New Leads

Leadership Handover Roadmap & Advice

1. Official Email Access

  • Create and hand over the official email ID to the new lead.

  • Make sure they can:

  • Send and receive emails

  • Reset passwords for linked tools
  • Avoid using personal emails for official work.

2. Google Drive & Documents

  • Explain the folder structure in Google Drive.

  • Highlight:

  • Important documents

  • Policies, disclaimers, and legal files
  • Past plans and reports
  • Ask the new lead to review Google Drive within one month.

3. Google Forms

  • Show all active Google Forms.

  • Explain:

  • Why each form exists

  • Who should access the responses
  • Ensure the new lead checks responses regularly.
  • Transfer ownership of critical forms if needed.

4. GitHub Organization Access

  • Give the new lead Owner permission in the GitHub organization.

  • Walk them through:

  • Repository structure

  • Branch rules
  • PR review and merge process
  • Explain who else has admin or maintainer access.

5. Current Programs & Issues

  • Brief the new lead on:

  • Ongoing programs (e.g., Hacktoberfest, open-source drives)

  • Recent issues or blockers
  • Any legal, technical, or community-related risks
  • Clearly state what is working and what is not.

6. Current Plan & Vision

  • Explain the short-term plan (next 1–3 months).
  • Explain the long-term vision.

  • Share:

  • Pending tasks

  • Deadlines
  • Priorities

7. Advice for the New Lead

  • Keep everything documented.
  • Avoid controversial or sensitive activities.
  • Do not give direct posting permission without tracking users.

  • Regularly monitor:

  • GitHub activity

  • Google Forms
  • Official email inbox
  • Google analytics
  • Ask seniors or previous leads if unsure—no guesswork.