Affiliated Team Volunteers (ATVs): Difference between revisions
Line 19: | Line 19: | ||
# '''ATVs are not required to attend team meetings or to log hours,''' and their membership is not tied to fulfilling the annual [[Minimum Service Contribution (MSC)|Minimum Service Contribution]]. However, they can do these things if they wish and are encouraged to. | # '''ATVs are not required to attend team meetings or to log hours,''' and their membership is not tied to fulfilling the annual [[Minimum Service Contribution (MSC)|Minimum Service Contribution]]. However, they can do these things if they wish and are encouraged to. | ||
# '''ATVs are required to confirm their status with their Team Leader''' at least once a year, and any time the Team Leader conducts a review of the team's roster. Team Leaders will have access to the communication information of ATVs on their team. | # '''ATVs are required to confirm their status with their Team Leader''' at least once a year, and any time the Team Leader conducts a review of the team's roster. Team Leaders will have access to the communication information of ATVs on their team. | ||
# '''The assigned role ([[Volunteer Support Functions Introduction and Directory|VSF]]) of an ATV is tied only to a NET's earthquake response plan.''' ATVs are envisioned assisting only in the aftermath of an earthquake. | # '''The assigned role ([[Volunteer Support Functions Introduction and Directory|VSF]]) of an ATV is tied only to a NET's earthquake response plan.''' ATVs are envisioned assisting only in the aftermath of an earthquake. ATVs should be familiar with the latest edition of their NET's earthquake response framework. | ||
# '''All ATVs declare a [[Volunteer Support Functions Introduction and Directory|Volunteer Support Function]] position appropriate for a non-NET volunteer.''' This declaration is made to their Team Leader and it appears on the earthquake response plan. | # '''All ATVs declare a [[Volunteer Support Functions Introduction and Directory|Volunteer Support Function]] position appropriate for a non-NET volunteer.''' This declaration is made to their Team Leader and it appears on the earthquake response plan. | ||
# '''ATVs are tracked in the NET Volunteer database (as ATVs).''' This reporting is important for PBEM in assessing earthquake readiness. | # '''ATVs are tracked in the NET Volunteer database (as ATVs).''' This reporting is important for PBEM in assessing earthquake readiness. | ||
Line 42: | Line 42: | ||
A new volunteer wishing to sign up as an ATV should take the following actions: | A new volunteer wishing to sign up as an ATV should take the following actions: | ||
# Confirm with their Team Leader that they can join the local NET roster. They should work with their Team Leader to decide on a VSF and | |||
== ATV Program History == | == ATV Program History == |
Revision as of 16:12, 1 March 2024
An Affiliated Team Volunteer ("ATV") is a volunteer who associates with and is assigned to a Neighborhood Emergency Team (NET) but does not possess full "Active" NET volunteer status. They are not deployed or indemnified by the City of Portland, though they have a profile in the NET volunteer database. ATVs appear on NET rosters only as prospective resources for an earthquake response. They are not required to log volunteer hours (though encouraged to do so) or meet the Minimum Service Contribution.
Volunteers join their local NET as ATVs from being either:
- An active NET who wishes to step back their involvement but not leave the team entirely; or,
- A neighbor who resides in a NET's Service Area and wants to help the team, but has not completed Basic NET training.
ATVs are envisioned as neighborhood-local volunteer resources to supplement a NET team in the aftermath of an earthquake. They appear on NET team rosters only for earthquake response frameworks, and fall under the response structure of their NET. The Team Leader of the NET in their neighborhood, therefore, is also their Team Leader.
Access and General Expectations of ATVs
The following expectations and policies apply to all ATVs:
- A volunteer in ATV status is not indemnified by the City of Portland. However, Good Samaritan laws still apply.
- A volunteer in ATV status is never deployed by the City of Portland. ATVs may opt to self deploy in the event of an earthquake.
- Unlike NET volunteers, an ATV must be affiliated with a Neighborhood Emergency Team and named on the team roster.
- ATVs are not required to attend team meetings or to log hours, and their membership is not tied to fulfilling the annual Minimum Service Contribution. However, they can do these things if they wish and are encouraged to.
- ATVs are required to confirm their status with their Team Leader at least once a year, and any time the Team Leader conducts a review of the team's roster. Team Leaders will have access to the communication information of ATVs on their team.
- The assigned role (VSF) of an ATV is tied only to a NET's earthquake response plan. ATVs are envisioned assisting only in the aftermath of an earthquake. ATVs should be familiar with the latest edition of their NET's earthquake response framework.
- All ATVs declare a Volunteer Support Function position appropriate for a non-NET volunteer. This declaration is made to their Team Leader and it appears on the earthquake response plan.
- ATVs are tracked in the NET Volunteer database (as ATVs). This reporting is important for PBEM in assessing earthquake readiness.
- ATVs are subscribed to ATV volunteer communications (such as occasional bulletins). Because of the way our volunteer database is designed, an active ATV cannot opt out of email communications, but we try to keep them light. Communications will include training opportunities for ATVs.
- ATVs are permitted access to low risk NET advanced trainings if seats remain after they are offered to NETs. Occasionally, ATVs receive priority access to advanced training seats for training in their chosen VSF.
ATV Intake Process
For former NET volunteers
A NET volunteer may opt to downshift from Active NET status to ATV status. Many NET volunteers consider this move for personal reasons that impact their availability (don't have as much time as they used to, health concerns, etc). Going to ATV status is available as a medial point between full Active status and withdrawing from the program entirely. In this case, the volunteer can re-activate at any point in the future.
A NET wishing to move to ATV status should take the following actions:
- Inform the NET Team Leader: The NET should first inform their TL that they plan to downshift to ATV status, whether they plan for that status change to be permanent or temporary, and what their declared VSF will be. The change should be reflected in the TL's team roster and earthquake response framework.
- Inform PBEM: Next, the volunteer must email net@portlandoregon.gov to report the change in status and the declared VSF. PBEM will update the volunteer database accordingly.
- If the volunteer wishes to return to Active status, they follow the steps above in reverse. Depending on the length of their absence from Active status, they may need a renewed background check and ID.
- They may hang on to their NET vest, hard hat, and ID if they wish. Otherwise, they should turn those items in to their Team Leader.
For non-NET trained neighbors
NET volunteers often meet neighbors who want to be part of their NET's mission, but do not have the time and/or inclination to complete Basic NET Training. Having them sign up as an ATV is ideal in this situation. NETs will find these neighbors have specific skills or interests that correspond well to VSFs. For example, a medical professional who lives in the area is ideally suited to enlist under VSF 08. A neighbor who possesses a HAM license (or wants to get one) should enlist under VSF 02. And so on. Team Leaders should view these ATVs as opportunities to round out the skillsets available on their teams.
A new volunteer wishing to sign up as an ATV should take the following actions:
- Confirm with their Team Leader that they can join the local NET roster. They should work with their Team Leader to decide on a VSF and
ATV Program History
"ATV" was first coined and suggested to Jeremy Van Keuren (PBEM) by NET volunteer David Given. David worked with Boy Scout volunteers and requested a volunteer status that kept a non-NET disaster response volunteer "in the loop" of NET activities and encouraged forming a planning relationship with local teams.
PBEM implemented the ATV status as a solution to two problems:
- It offers exiting NET volunteers an alternative to separating from the NET program completely. If a NET volunteer is unable to meet/uninterested in meeting their Minimum Service Contribution but would like to remain a part of their local team, they can do so as an ATV. ATV status is an alternative to making a NET volunteer "Inactive" and completely discharging them from the program.
- It encourages non-NET neighbors to volunteer with their local NET team by giving them a status in the program. A neighbor may be interested in disaster response activities with their community and want to plan ahead, but do not have the time and/or inclination to complete Basic NET training. Becoming an ATV gives them a team role to fill by declaring a VSF (e.g. radio operator) and makes them more ready to participate with a NET team than a spontaneous volunteer (SUV) would be.