# Being On Volunteer Teams

## Time Commitment for Volunteers

As a volunteer we cannot force you to work certain hours or schedule. Weekly time expectations range anywhere from 1 to 10 hours a week depending on the volunteer role you want to join. Typically, we provide a way for volunteers to commit to a 3 month timeframe, but this is flexible. We accommodate your schedule and time restrictions outside of our community. 

When you sign up for volunteering, you can see the information about the general expectations of time commitment, and you can make your own schedule around the expected time commitment. You choose what level of time commitment you can take on. It’s important as a volunteer to be responsive, consistent, and detail-oriented. 

## Onboarding for Volunteer Work

When volunteers onboard, they should read all three of our handbooks for community members: the [Agile Handbook](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization), the [Project Success Handbook](https://guide.techfleet.org/project-portal/new-project-success-handbook), and the [Teammate Handbook](https://guide.techfleet.org/project-portal/new-teammate-handbook/project-training-teams/being-on-project-training/hand-off-and-case-study-creation). After signing up for a volunteer role, you will join a volunteer onboarding call together with other volunteers. Each volunteer role may have its own training for you to receive after this onboarding as a volunteer. We highly recommend all volunteers also attend the Service Leadership Masterclass, a free class that offers the basic training about being a Service Leader. All Volunteers are expected to practice service leadership in their volunteer work, so this class is beneficial for your expectation setting. 

## Attending Meetings as a Volunteer Teammate

Meetings on volunteer teams are determined by the teams who operate the volunteer work. As self-organized teams, they make the call about how often they meet and when. Read more about this in the [Agile Handbook](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization).

## Using Tools as a Volunteer Teammate

Volunteers use the same kinds of tools that trainees do. Check out the [Common Tools Used in Tech Fleet](https://guide.techfleet.org/resources/quick-links/tools-used-in-tech-fleet-programs) to learn more about the tools we use on teams.

## Communication with Other Volunteers and Leadership

All communication is via Discord or email. You can have voice calls on Discord or video calls on Google Meet. We ask that you don’t communicate outside of these channels (e.g. text).

## Generating Case Studies and Reports After Volunteer Teamwork

Volunteers contribute to great teamwork and change that’s made just like trainees. You, too, can generate story-driven case studies that showcase the impact you’ve made in your teamwork. Read more about this here about [Case Study Creation](https://guide.techfleet.org/project-portal/new-teammate-handbook/project-training-teams/being-on-project-training/hand-off-and-case-study-creation).

## Ending your Volunteer Term with the Community

To end your volunteer experience, please email your project coordinator. A response must come from them to be captured in our tracking system. 

<br>


---

# 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://guide.techfleet.org/team-portal/new-teammate-handbook/volunteering-teams/being-on-volunteer-teams.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.