Services Cluster: Difference between revisions
Jump to navigation
Jump to search
Template |
Filled out from previously submitted form |
||
| Line 1: | Line 1: | ||
== Service Cluster Lead Responsibilities == | == Service Cluster Lead Responsibilities == | ||
The Service Cluster coordinates the cores that support our participants! | |||
* Gnome Core | |||
* Coffee Core | |||
* Sanctuary Core | |||
* Accessibility Core | |||
Lead responsibilities: | |||
* Identify and fill any key vacancies in the above-listed cores prior to event, working with Volunteer Coordinator as needed | |||
* Communicate with core leads throughout planning; ensure they are empowered to successfully lead their cores. | |||
* Work with core leads to create budget for each core in the cluster. | |||
* Check in with cores & provide updates at daily meeting during the event. | |||
* Participate in after-burn activities/planning for next year. | |||
== Who makes a good Service Cluster Lead? == | == Who makes a good Service Cluster Lead? == | ||
Revision as of 15:04, 10 January 2026
Service Cluster Lead Responsibilities
The Service Cluster coordinates the cores that support our participants!
- Gnome Core
- Coffee Core
- Sanctuary Core
- Accessibility Core
Lead responsibilities:
- Identify and fill any key vacancies in the above-listed cores prior to event, working with Volunteer Coordinator as needed
- Communicate with core leads throughout planning; ensure they are empowered to successfully lead their cores.
- Work with core leads to create budget for each core in the cluster.
- Check in with cores & provide updates at daily meeting during the event.
- Participate in after-burn activities/planning for next year.