We want to help! We recommend scheduling a meeting with your CSA and your successor so that we can discuss the transition and how the CSA will play a role. We can share some best practices for the transition and get a plan in place for ensuring your successor is well trained in the platform and can move forward with the projects you have started!
We recommend that you consider creating a CampusGroups transition document to give to your successor when you leave your position to help them continue where you left off with the platform. Below are some recommended topics to include. You can also download a more detailed and editable guide here.
Share contact information for the CG team and campus collaborators and information about training materials. Discuss the features you use and what projects CG is used for.
Explain any processes related to your role with CG. This may include Registration, Uploading/ Removing Users, Annual Events or Event Hubs, Budgeting Processes, etc.
Share some information about how students in your community are engaged with the platform. Explain what has worked in the past and what hasn't.
Share what you are currently working on as well as any features you would consider adding in the future or projects you think CG could potentially be used for. Share a partnership plan if you have one or direct your successor to the goal website.
Share the Strengths, Weaknesses, Opportunities, and Threats to your Goals with the platform.
Share any additional recommendations, tips, or your favorite things about CG!
Any training guides you have created on campus
Explain what the User Community is and share the link for accessing it
Share that CG University is a training tool we provide that they can access by joining the CG University Group in the User Community
Remind them that they can find all of our help articles here
Remind them to work with your CSA on best practices/ use cases and to email support@campusgroups.com if they need to submit tickets
