Team Development Arcs: Difference between revisions

(93 intermediate revisions by one other user not shown)

Line 1:

Another term for a "Team Development Arc" in the context of NETs is "developmental pathway". PBEM asks NET teams to meet regularly, but to do what? Without a defined purpose, team meetings can drift, prompting some members to stop attending meetings, and teams do not build their capacity as neighborhood-based disaster responders. The purpose of Team Developmental Arcs are to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap through team development rather than convening meetings around "what should we talk about this month?"'''

Another term for a "Team Development Arc" in the context of NETs is "developmental pathway". PBEM asks NET teams to meet regularly, but to do what? Without a defined purpose, team meetings can drift, prompting some members to stop attending meetings, and teams do not build their capacity as neighborhood-based disaster responders. The purpose of Team Developmental Arcs are to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap through team development''' rather than convening meetings around "what should we talk about this month?"

'''There is a two part objective to this program:'''

# '''Provide Team Leaders with team meeting activity modules that can be easily planned, like a recipe, for team meetings.'''

# '''Help teams move along a path or paths of development towards greater efficacy as a team of disaster responders.'''

The use of Team Development Arcs are completely optional, and can be changed or edited to suit the needs of NETs who use them. They are intended as a supplementary resource for NET Team Leaders.

{| class="wikitable"

|+

! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents

! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated

|-

|Form: [https://app.smartsheet.com/b/form/45b4b43047e74ce0842e3dc924f43f4e Development Arc Feedback]

|2025.10.04

|-

|Form: [https://app.smartsheet.com/b/form/104dab042ef84ca5a9fce7b2076d5ad3 I Would Like to Create a Module]

|2025.10.04

|-

|Form: [https://app.smartsheet.com/b/form/0199b17984a073d69aad94f410695792 I Would Like to Instruct a Module]

|2025.10.04

|}

{|style="border:1px solid grey; border-collapse:collapse;"

|+

!style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|Contents

|-

|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Team Development Arc Leadership Approach|Team Development Arc Leadership Approach]]

[[Team Development Arcs#Team Development Arcs Table|Team Development Arcs Table]]

[[Team Development Arcs#Braiding the Arcs Together|Braiding the Arcs Together]]

[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|'''Development Arc I:''' Team Organization and Cohesion]]

[[Team Development Arcs#Development Arc II: Response Operations Planning|'''Development Arc II:''' Response Operations Planning]]

[[Team Development Arcs#Development Arc III: Exercises and Tabletops|'''Development Arc III:''' Exercises and Tabletops]]

[[Team Development Arcs#Development Arc IV: Communications|'''Development Arc IV:''' Communications]]

[[Team Development Arcs#Development Arc V: Basic Response Skills|'''Development Arc V:''' Basic Response Skills]]

[[Team Development Arcs#Development Arc VI: Disaster DIY|'''Development Arc VI:''' Disaster DIY]]

|}

__NOTOC__

Line 14:

Line 61:

* '''IV.) Communications:''' Modules for developing best practices around post-disaster communications.

* '''V.) Basic Response Skills:''' Review modules for any basic skillsets introduced in the Basic NET curriculum.

* '''VI.) Disaster DIY:''' Like crafting night! Assemble an item or items that will be helpful in an emergency. Unlike the others, these activities ''do'' cost money because they require participants to purchase supplies.

===== Developing a team of NETs vs. developing individual volunteers =====

As a NET Team Leader, your most important responsibility is '''helping your team grow together''' into a capable disaster response group. The purpose of this Development Arc curriculum is to give you a clear roadmap for building your team’s overall capacity.

At the same time, each volunteer is also on their own personal growth journey. NET volunteers are largely responsible for their '''individual development''', which is where the Volunteer Support Function (VSF) system comes in. VSFs provide pathways for volunteers to specialize in skills that interest them and strengthen the team.

At the same time, each volunteer is also on their own personal growth journey. NET volunteers are largely responsible for their '''individual development''', which is where the [[Volunteer Support Functions Directory|Volunteer Support Function (VSF)]] system comes in. VSFs provide pathways for volunteers to specialize in skills that interest them and strengthen the team.

Your role as Team Leader is to see both sides: to think about your team as a whole unit, and also to recognize the unique skills and strengths each volunteer brings. You don’t need to control an individual’s development, but you can guide them—helping them choose VSFs that align with team needs, and working with PBEM to make sure those paths stay open. In short: '''you shape the team, while supporting each volunteer in shaping themselves as volunteer responders'''.

Line 49:

Line 97:

|+

!

! colspan="2" |<big>Development Arc I:Team Organization and Cohesion</big>

! colspan="2" |<big>[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|Development Arc I:Team Organization and Cohesion]]</big>

|-

!style="background-color:#AC96B7;"|

Line 88:

Line 136:

|-

|I.09

|Family Preparedness Discussion

|[[Team Development Arcs#I.09 Family Preparedness Discussion|Family Preparedness Discussion]]

|Either

|-

|I.10

|Fundraising Review

|[[Team Development Arcs#I.10 Fundraising Review|Fundraising Review]]

|Either

|-

|I.11

|~~Leadership Succession Planning~~

|[[Team Development Arcs#I.11 Non-Disaster Related Social Event|Non-Disaster Related Social Event]]

~~|Either~~

|-

|I.12

|Non-Disaster Related Social Event

|Either

|}

Line 165:

Line 209:

|II.13

|Post-Earthquake Decedent Care

|Either

|-

|II.14

|Response Debrief

|Either

|}

Line 175:

Line 223:

{| class="wikitable sortable" style="width: 70%;"

|+

! colspan="3" |<big>Development Arc III: Exercises and Tabletops</big>

! colspan="3" |<big>[[Team Development Arcs#Development Arc III: Exercises and Tabletops|Development Arc III: Exercises and Tabletops]]</big>

|-

!style="background-color:#94AC96;"|

Line 190:

Line 238:

|-

|III.03

|~~Tabletop: Windstorm~~

|[[Team Development Arcs#III.03 FEMA's CERT Tabletops|FEMA's CERT Tabletops]]

* Earthquake Response

|Indoors

|-

Line 217:

Line 266:

|-

|IV.01

|Personal Accountability Reporting (PAR)

|[[Team Development Arcs#IV.01 Personal Accountability Reporting (PAR)|Personal Accountability Reporting (PAR)]]

|Either

|-

Line 239:

Line 288:

</div>

{| class="wikitable sortable" style="width: 35%;"

{| class="wikitable sortable" style="width: 70%;"

|+

! colspan="3" |<big>Development Arc V: Basic Response Skills</big>

Line 292:

Line 343:

|Either

|}

</div>

{| class="wikitable sortable" style="width: 70%;"

|+

! colspan="3" |<big>[[Team Development Arcs#Development Arc VI: Disaster DIY|Development Arc VI: Disaster DIY]]</big>

|-

!style="background-color:#f7ffb2;"|

!style="background-color:#f7ffb2;"|Activity

!style="background-color:#f7ffb2;"|Indoors/Outdoors

|-

|VI.01

|[[Team Development Arcs#VI.01 DIY Air Cleaner|DIY Air Cleaner]]

|Either

|-

|VI.02

|[[Team Development Arcs#VI.02 Hands-Free Portable Sink|Hands-Free Portable Sink]]

|Either

|-

|VI.03

|[[Team Development Arcs#VI.03 Easy-Build Handwashing Station|Easy-Build Handwashing Station]]

|Either

|}

</div>

Line 313:

Line 388:

===== EXAMPLE: Team development over the course of one year =====

[[File:Wemmick Heights.jpg|thumb|''Actual photo of Wemmick Heights NET team meeting planning session.'']]

So let's say the completely made-up NET team of Wemmick Heights has a newly elected Team Leader, Joe Gargery, after TL Thérèse Defarge had an [[wikipedia:Madame_Defarge|unfortunate guillotine accident]]. Joe wishes to take a more collaborative and delegative approach than Madame Defarge did. He asks his team to come together to plan out their next twelve meetings (they meet once a month, so this will cover the year for them). After discussing their goals, they agreed on the following calendar:

So let's say the completely made-up NET team of [[Media:2016.08.20.Wemmick Heights Ops Plan.pdf|Wemmick Heights]] has a newly elected Team Leader, Joe Gargery, after TL Thérèse Defarge had an [[wikipedia:Madame_Defarge|unfortunate guillotine accident]]. Joe wishes to take a more collaborative and delegative approach than Madame Defarge did. He asks his team to come together to plan out their next twelve meetings (they meet once a month, so this will cover the year for them). After discussing their goals, they agreed on the following calendar:

{| class="wikitable" style="width: 60%;"

|+

Line 414:

Line 489:

== Development Arc I: Team Organization and Cohesion ==

=== I.01Team Meeting Logistics Discussion ===

[[File:2024.07.27.CentennialExercise (2).jpg|thumb|350x350px|''Karen Wolfgang and Centennial NET. Popsicles always makes things more palatable.'']]

Line 519:

Line 594:

* If there is time (i.e. at least two weeks before the session), the facilitator should encourage all team members to check they have all the equipment PBEM issues: ID card, hard hat (which should be replaced every five years), hard hat chin strap, and vest. Any missing items or items in need of replacement can be requested at the '''[https://app.smartsheet.com/b/form/5b3303eec5114f6ba0d6ffa52e496933 NET/BEECN ID Card, Helmet, and/or Vest Request Form]'''. PBEM also issues FRS/GMRS radios (if a volunteer cannot afford one), Field Operating Guides (FOGs), and waterproof backpack covers as supplies are available.

'''Facilitation'''[[File:Netpack.jpg|right|265x265px]]Ask each team member to bring their NET bag or response kit to the meeting. Begin by reviewing the [[Basic NET Training Standard Syllabus#Equipment: Basic NET Response Packs|official NET kit list]]. Explain that the purpose of this exercise is not to judge completeness but to help everyone become more familiar with their gear, share practical tips, and make sure nothing critical is missing.

'''Facilitation'''

[[File:Netpack.jpg|right|265x265px]]Ask each team member to bring their NET bag or response kit to the meeting. Begin by reviewing the [[Basic NET Training Standard Syllabus#Equipment: Basic NET Response Packs|official NET kit list]]. Explain that the purpose of this exercise is not to judge completeness but to help everyone become more familiar with their gear, share practical tips, and make sure nothing critical is missing.

Facilitate a guided walkthrough of major kit categories—personal safety/PPE (helmet, vest, gloves), communication (radio, whistle, contact sheet), medical (first aid supplies), tools, and comfort items (snacks, water). Invite volunteers to share how they’ve adapted their kits to fit their neighborhood context or personal needs (e.g., dog leash, maps, laminated cards). Keep the conversation focused on functionality and portability. End with a brief “gap check”: have members note items they need to add or replace, and suggest a timeline for completing those updates. If possible, document any common shortages so the team can discuss bulk purchases or supply-sharing at a future meeting.

Line 804:

Line 881:

=== I.09 Family Preparedness Discussion ===

'''Learning Objective'''

[[File:Stock Image Family.jpg|thumb|350x350px|''I looked for a free stock image of a family preparing for a disaster. This one aint bad, but I hope they rotate that water.'']]

''Team members will reflect on their own household readiness and identify steps to ensure their families are safe and self-sufficient when they deploy as NET volunteers after a disaster.''

'''Supplemental Resources'''

Ready.gov [https://www.ready.gov/plan Make a Plan]

:Ready.gov [https://www.ready.gov/plan Make a Plan]

'''Preparation'''

Line 840:

Line 917:

'''Module Outputs'''

None.

None.

<hr>

=== Fundraising Review ===

=== I.10 Fundraising Review ===

'''''Learning ~~objective:'''~~'' ''Team members will assess whether fundraising is necessary for their operations (such as building an equipment cache) and, if so, identify appropriate and realistic fundraising strategies and how to use Friends of Portland NET as a fiscal agent to support those efforts.''

'''Learning Objective'''

'''''~~Preparation~~:''''' Review the [https://friendsofportlandnet.org/ Friends of Portland NET] website.

''Team members will assess whether fundraising is necessary for their operations (such as building an equipment cache) and, if so, identify appropriate and realistic fundraising strategies and how to use Friends of Portland NET as a fiscal agent to support those efforts.''

'''Supplemental Resources'''

:''[https://friendsofportlandnet.org/ Friends of Portland NET] website''

'''Preparation'''

Review the [https://friendsofportlandnet.org/ Friends of Portland NET] website. If it is already confirmed that the team would like to pursue fundraising, the facilitator should contact FPN and ask to open an account.

'''Facilitation'''

~~'''''Facilitation:'''''~~ Open the discussion by asking: ''“What are the things our team would like to do or have that require money?”'' Write down ideas such as equipment cache supplies, radios, signage, printing outreach materials, or team-specific projects. Clarify what PBEM and the NET program already provide, and identify any gaps that may require outside support.

Open the discussion by asking: ''“What are the things our team would like to do or have that require money?”'' Note that PBEM will provide assistance for some things (such as printing or radios) as resources allow. Write down ideas such as [[Team Equipment Caches|equipment cache supplies]], radios, signage, printing outreach materials, or team-specific projects. Clarify what PBEM and the NET program already provide, and identify any gaps that may require outside support.

Explain that the nonprofit '''[https://friendsofportlandnet.org/ Friends of Portland NET (FPN)]''' can serve as the fiscal sponsor for NET teams. This means teams can raise funds (through donations, grants, or partnerships) without managing their own bank accounts or nonprofit paperwork. Funds raised are held and managed by ~~FoPNET~~ on behalf of the team. This arrangement ensures compliance, transparency, and accountability, while still giving teams access to the resources they need.

Explain that the nonprofit '''[https://friendsofportlandnet.org/ Friends of Portland NET (FPN)]''' can serve as the fiscal sponsor for NET teams. This means teams can raise funds (through donations, grants, or partnerships) without managing their own bank accounts or nonprofit paperwork. Funds raised are held and managed by FPN on behalf of the team. This arrangement ensures compliance, transparency, and accountability, while still giving teams access to the resources they need.

If the team agrees that fundraising is needed, brainstorm '''realistic approaches''' such as:

Line 859:

Line 948:

* Running a one-time community fundraiser for a specific project.

Once ideas are generated, guide the group to select one or two strategies to pursue. Assign roles (who will contact ~~FoPNET~~, who will draft outreach language, who will liaise with a grant source), and set a timeline. If fundraising isn’t needed now, capture that decision and plan to revisit later.

Once ideas are generated, guide the group to select one or two strategies to pursue. Assign roles (who will contact FPN, who will draft outreach language, who will liaise with a grant source), and set a timeline. If fundraising isn’t needed now, capture that decision and plan to revisit later.

'''Debrief Questions:'''

'''Debrief Questions'''

* What needs do we have that could reasonably be supported through fundraising?

* How does working with ~~FoPNET~~ simplify the process for us?

* How does working with FPN simplify the process for us?

* Which fundraising methods feel both achievable and consistent with our team’s values?

* Who will connect with ~~FoPNET~~ and take the first step toward pursuing this?

* Who will connect with FPN and take the first step toward pursuing this?

'''Module Outputs'''

None.

<hr>

=== Non-Disaster Related Social Event ===

=== I.11 Non-Disaster Related Social Event ===

'''''Learning ~~objective:'''~~'~~' ''Loosen up, nerds! Also, to help get to know each other better.~~''

'''Learning Objective'''

''~~'''Facilitation:''''' Remind the group that NET is not just about emergency response—it’s also about being good neighbors and building strong community bonds. A relaxed~~, ~~non-disaster social event gives team members a chance~~ to ~~connect as people first, which often makes them more cohesive and resilient when an emergency does come~~.

''Loosen up, nerds! Also, to help get to know each other better.''

Facilitate a short brainstorming session: what kinds of low-key social activities would appeal to your team and fit the neighborhood context? Examples might include a potluck, park picnic, movie night, coffee meet-up, or a group volunteer project at a local charity. Keep it simple—this is about fun and connection, not logistics. Make sure events are inclusive and accessible: consider dietary needs, childcare, and mobility.

'''Supplemental Resources'''

~~Once the team has identified an idea, assign one or two volunteers to organize details (date, location, invites)~~. ~~Emphasize that these gatherings don’t need to be big or frequent—even one or two casual social events a year can go a long way toward improving morale and retention~~. ~~Encourage members to invite family or neighbors, as broadening participation can both strengthen social ties and spark interest in~~ the ~~NET program~~.

Oh I don't know. Probably any number of Martha Stewart books. Don't ask the introvert.

Some possible ideas:

'''Preparation'''

None.

[[File:2023.08.25.NET Camp.Bob Crispin (6).jpg|thumb|350x350px|''NETs know how to party.'']]

'''Facilitation'''

Remind the group that NET is not just about emergency response—it’s also about being good neighbors and building strong community bonds. A relaxed, non-disaster social event gives team members a chance to connect as people first, which often makes them more cohesive and resilient when an emergency does come.

Facilitate a short brainstorming session: what kinds of low-key social activities would appeal to your team and fit the neighborhood context? Examples might include a potluck, park picnic, movie night, coffee meet-up, or a group volunteer project at a local charity. Keep it simple—this is about fun and connection, not logistics. Make sure events are inclusive and accessible: consider dietary needs, childcare, and mobility. PBEM also recommends considering that some team members may be in recovery, and it may be best to avoid having alcohol at the event.

Once the team has identified an idea, assign one or two volunteers to organize details (date, location, invites). Emphasize that these gatherings don’t need to be big or frequent—even one or two casual social events a year can go a long way toward improving morale and retention. Encourage members to invite family or neighbors, as broadening participation can both strengthen social ties and spark interest in the NET program.

The big challenge is: try not to talk about anything disaster related.

Some possible ideas:

'''Food & Drink Gatherings'''

Line 895:

Line 1,003:

'''Community-Oriented Fun'''

* '''Group Volunteering:''' Help at a local food bank, park cleanup, or neighborhood project.

* '''Group Volunteering:''' Help at a [https://www.oregonfoodbank.org/get-involved/volunteer local food bank], park cleanup, or neighborhood project.

* '''Movie Night:''' Project a film in someone’s yard or at a community hall.

* '''Holiday Gathering:''' Seasonal potluck or cookie swap around winter or summer holidays.

Line 905:

Line 1,013:

* NET birthday/anniversary celebration (marking when the team formed).

'''Debrief Questions:'''

'''Debrief Questions'''

*What kinds of social events would feel fun and inclusive for our team?

Line 914:

Line 1,022:

*What’s one way we can make sure these events become part of our team culture?

'''Module Outputs'''

None.

<hr>

</div>

== Development Arc II: Response Operations Planning ==

=== VSF Gap Analysis ===

'''''Learning ~~objective:''~~' Team members will understand the purpose of Volunteer Support Functions (VSFs), identify their own areas of specialization, and consider how their team’s mix of VSFs can strengthen neighborhood response.''

'''Learning Objective'''

'''''~~Facilitation:~~''''' Begin by explaining that PBEM organizes all volunteers (NETs, BEECN, ATVs) into Volunteer Support Functions (VSFs). These are specialized areas of disaster skills or knowledge—such as Search & Rescue, Medical, Communications, Logistics, or Public Information. VSFs serve two main purposes: they allow volunteers to deepen skills in areas they’re interested in, and they give teams and PBEM a clear picture of what capabilities exist across the city.

''Team members will understand the purpose of Volunteer Support Functions (VSFs), identify their own areas of specialization, and consider how their team’s mix of VSFs can strengthen neighborhood response.''

'''Supplemental Resources'''

'''Preparation'''

'''Facilitation'''

Begin by explaining that PBEM organizes all volunteers (NETs, BEECN, ATVs) into Volunteer Support Functions (VSFs). These are specialized areas of disaster skills or knowledge—such as Search & Rescue, Medical, Communications, Logistics, or Public Information. VSFs serve two main purposes: they allow volunteers to deepen skills in areas they’re interested in, and they give teams and PBEM a clear picture of what capabilities exist across the city.

Provide a simple overview of how VSFs work:

Line 942:

Line 1,063:

Wrap up by encouraging interested members to contact PBEM if they want to update their VSF, and consider recording your team’s VSF mix on your NETwiki page for future reference.

'''Debrief Questions:'''

'''Debrief Questions'''

*Which VSFs are represented on our team right now? Where are the gaps?

Line 951:

Line 1,072:

*How can we support each other in building depth in these areas (peer training, shared resources, guest speakers)?

'''Module Outputs'''

<hr>

Line 1,205:

Line 1,329:

=== Scenario Village Preparation ===

=== ~~Tabletop: Windstorm~~ ===

=== III.03 FEMA's CERT Tabletops ===

'''Learning Objective'''

====== Earthquake Response Scenario ======

'''''Note: This tabletop used to be part of Basic NET training, so some members may already be familiar with it.'''''

"A major earthquake has struck at 1:00 p.m. on a mid-week afternoon. The day is cool and cloudy. It has been raining lightly all day, and the temperature is expected to fall quickly by 5:30 p.m. The local CERT has been activated to assess damage in its neighborhood. CERT members have just arrived at the pre-designated meeting point."

:''[[Media:FEMA CERT Tabletop Exercise 1.Facilitator.pdf|Facilitator Packet FEMA CERT Tabletop Exercise #1]]'' (one copy for the facilitator); 31 pages.

:''[[Media:FEMA CERT Tabletop Exercise 1.Participants.pdf|Participant Packet FEMA CERT Tabletop Exercise #1]]'' (each participant should receive one packet); 14 pages.

=== Disasterville Board Game ===

Line 1,216:

Line 1,350:

== Development Arc IV: Communications ==

=== Personal Accountability Reporting (PAR) ===

=== IV.01 Personal Accountability Reporting (PAR) ===

'''Learning Objective:'''

Line 1,375:

Line 1,509:

'''Learning Objective:'''

''Team members will practice ~~using proper~~ radio ~~etiquette~~, ~~including prowords~~, ~~clear phrasing~~, and ~~the phonetic alphabet, to~~ ensure ~~efficient~~ and ~~accurate communication~~ during disaster response.''

''Team members will practice clear, efficient radio communication by developing practical message-handling skills—using phonetics, “I spell,” pacing, and fills—to ensure information is accurately sent and received during disaster response.''

'''Facilitation Guide:'''

Begin by ~~highlighting~~ that ~~clear, concise~~ radio communication is '''~~critical under stress~~'''~~. Unlike phone calls,~~ radio ~~transmissions~~ are ~~one-to-many, brief,~~ and ~~subject~~ to ~~interference~~. ~~A little discipline goes a long way in reducing confusion and speeding operations~~.

Begin by setting expectations clearly:

This module is not radio certification training. It is a practical, team-based exercise designed to help all NET volunteers—especially those who use radios infrequently—communicate clearly and confidently under stress. The focus is not perfection, but making sure the person on the other end actually understands the message.

Emphasize that good radio communication is less about sounding “professional” and more about being helpful, patient, and precise.

'''Step 1 – What Radios Are Good (and Bad) At:'''

Briefly discuss radio realities:

* Radios are shared channels

* Messages may be missed or cut off

* Background noise is common

* Stress affects how we speak and listen

Frame the goal:

“Your job on the radio is not to talk fast or fancy. Your job is to make it easy for the listener to copy your message.”

'''Step 1 – ~~Review the~~ Basics ~~of Radio Etiquette~~:'''

'''Step 2 – Call-Up Basics (Keep It Simple):'''

* Think before you speak: Plan your message in your head before keying the ~~mic.~~

Review the basic call-up pattern: Who you are calling → who you are

* Press, pause, then talk: ~~Wait 1 second after pressing transmit so your first words aren’t cut off.~~

* Keep it short: Use plain language, avoid unnecessary chatter.

* Identify who ~~you’re calling, then yourself: Example: “Staging, this is Team Alpha.”~~

* Acknowledge messages: ~~Use “Copy~~,~~” “Affirmative/Negative,” or repeat back essential details.~~

Example: ''“Staging, this is Team Alpha.”''

* One at a time: Pause before speaking in case someone else is ~~transmitting~~.

~~'''Step 2 – Introduce Prowords~~:~~'''~~

Reinforce:

~~Explain that '''prowords''' are standard words that carry agreed-upon meanings in radio traffic. Review and practice common ones:~~

* Use tactical identifiers, not names

* Pause briefly before speaking

* Speak clearly, not loudly

* '''“Over”''' – I’m done speaking and expect a reply.

'''Step 3 – Message Handling Skills (Core Focus):'''

* '''“Out”''' – I’m done, no reply expected.

* '''“Say Again”''' – Repeat your last transmission.

* '''“Copy”''' – ~~I received and understood.~~

* '''~~“Standby”~~'~~'' – I acknowledge but need more time.~~

* '''“Affirmative” / “Negative”''' – Yes / No.

* '''“Break”''' – Used to separate different portions of a message.

~~'''Step 3 – Phonetic Alphabet Practice:'''~~

Explain that most radio problems are message problems, not equipment problems. Introduce the four core skills adapted from GRO practice.

~~Provide the NATO phonetic alphabet~~ (~~Alpha, Bravo, Charlie, etc.~~) ~~and stress its importance when spelling out names, addresses, or codes over a noisy channel.~~

'''A.) Pacing (speed)'''

~~'''~~Practice ~~exercise~~:''' ~~Have each member spell their last name phonetically. Then practice with addresses, street names, or team designators.~~

Demonstrate the difference between:

* Talking at conversation speed

* Talking at radio speed (slower, deliberate)

Practice:

* Read a short message too fast

* Then read it slowly enough that someone could write it down

Key coaching point: ''"If someone is writing, you are probably talking too fast"''

'''~~Step 4 – Transmission Exercise:~~'''

'''B.) Phonetics (Flexible, not formal)'''

~~Pair up participants with radios~~.

Explain: Phonetics simply means using words to make letters clear. There is no requirement to memorize a specific alphabet.

~~Provide each pair with a short scripted message to relay (e.g., “Requesting medical supplies at 123 Pine Street”).~~

Examples:

~~Have them practice proper call-up, use of prowords, and phonetic spelling when needed~~.

* “J as in Jelly”

* “B as in Boy”

* “M as in Mountain”

Encourage improvisation — clarity matters more than correctness.

~~Rotate scripts so participants adapt to new scenarios.~~

Practice:

~~'''Step 5 – Group Drill:'''~~

* Spell names, street names, or intersections using any clear phonetics

* Listener repeats back what they heard

~~Set up a mock NET radio net with one person as~~ '''~~Net Control~~'''~~. Assign others roles (Team Alpha, Team Bravo, Logistics, etc.). Practice a short scenario (e.g., small fire, blocked road, injured resident) where teams must report in using proper etiquette.~~

'''C.) "I spell"'''

'''~~Debrief Questions~~:'''

Introduce “I spell” as a listener-friendly cue. Example:

''“The street name is I spell: J as in Jelly, E as in Eagle, R as in Raspberry.”''

Practice:

* Have volunteers announce “I spell”

* Spell slowly

* Pause between letters

'''D.) Fills, Repeats, and Corrections'''

Explain that mistakes are normal. What matters is fixing them clearly. Useful techniques:

* “Correction…”

* “Say again from…”

* Repeating critical info twice (addresses, numbers)

Practice:

* Intentionally introduce a garbled message

* Ask the listener to request a fill

* Practice clean corrections without frustration

'''Step 4 – Numbers and Addresses:'''

* ~~Which habits helped~~ messages ~~come through most clearly~~?

Review best practices:

* What ~~mistakes~~ did ~~we make that caused confusion~~?

* ~~How can we reinforce consistent use of prowords and phonetic spelling in future drills~~?

* Speak numbers slowly

* What ~~challenges might~~ we ~~face under stress~~, and how do ~~we prepare for them?~~

* Group long numbers

</~~div~~>

* Repeat addresses if important

Example: ''"Address is one-two-three Pine Street. I repeat: one-two-three Pine Street."''

Practice with:

* Addresses

* Block numbers

* Unit counts

'''Step 5 – Paired Message Practice:'''

Pair participants with radios. Give each pair short, realistic messages:

* Requesting supplies

* Reporting damage

* Checking in on status

Focus coaching on:

* Pacing

* Phonetics

* Listener confirmation

Rotate roles so everyone speaks and listens.

'''Step 6 – Group Net Practice'''

Set up a simple radio net:

* One Net Control

* Several teams checking in

Inject common challenges:

* “Say again”

* Missed numbers

* Competing traffic

Pause occasionally to coach: ''What could make that message easier to copy?"''

'''Debrief Questions:'''

* What made messages easiest to understand?

* When did pacing matter most?

* What helped you as a listener?

* What habits do we want to practice regularly as a team?

'''Module Outputs:'''

By the end of this module, teams should have:

* Practiced pacing messages for clarity

* Used phonetics flexibly and confidently

* Used “I spell” appropriately

* Corrected and repeated messages effectively

* Increased confidence speaking on the radio without overthinking it</div>

== Development Arc V: Basic Response Skills ==

== Development Arc VI: Disaster DIY ==

=== VI.01 DIY Air Cleaner ===

{{#ev:youtube|aw7fUMhNov8|430|right|'''''Video: How to Make a DIY Air Filter'''''|frame}}

'''Learning Objective'''

''Team members will learn how to construct a low-cost, do-it-yourself air cleaner using readily available materials, understand when and why it should be used during smoke or poor air quality events, and practice assembling one together to build skills they can share with neighbors.''

'''Materials List'''

{| class="wikitable"

|+

!Item

!Qty.

!Example

!Cost

|-

|20" x 20" box fan

|1

|

|-

|20" x 20" x 1" or 4" [https://www.epa.gov/indoor-air-quality-iaq/what-merv-rating MERV] 13 air filter

|1 to 5

|

|-

|Sheet of scrap cardboard (at least 20" x 20"

|1

|

|-

|Clamps, bungee cords, or duct tape

|

|}

'''Instructions'''

{| class="wikitable"

|+

! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources

! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated

|-

|[[Media:2023.06.09.Do-It-Yourself Air Cleaners Making Cleaner Air More Accessible US EPA.pdf|EPA Instructions]]

|2024.08.26

|}

=== VI.02 Hands-Free Portable Sink ===

'''Learning Objective'''

''Team members will learn how to build a portable, hands-free handwashing station using two plastic buckets and a one-way squeeze pump, with an option to organize a community “work party” to produce multiple stations. Volunteers will also recognize how pre-positioning several units across the neighborhood—along with stored water—ensures immediate access to safe, sanitary handwashing after a disaster. This module was created by NET volunteer Merilee Karr.''

'''Materials List'''

See instructions.

'''Instructions'''

{| class="wikitable"

|+

! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources

! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated

|-

|[https://www.instructables.com/Portable-Foot-pump-Handwashing-Station/ Hands-Free Portable Sink at Instructables]

|≈ 2020

|}

=== VI.03 Easy-Build Handwashing Station ===

'''Learning Objective'''

''Team members will recognize the importance of maintaining safe handwashing practices when plumbing is unavailable—whether due to a major or minor disaster, or in everyday off-grid settings such as community events or camping. Volunteers will explore low-cost, portable solutions that ensure hygiene and reduce the spread of illness when conventional water systems are disrupted. This module was created by NET volunteer Merilee Karr.''

'''Materials List'''

See instructions.

'''Instructions'''

{| class="wikitable"

|+

! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources

! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated

|-

|[https://www.instructables.com/Easy-Build-Handwashing-Station-With-Videos/ Easy-Build Handwashing Station at Instructables]

|2021.02.26

|}

== Team Development Arcs Frequently Asked Questions (FAQs) ==

Anonymous

Search

Team Development Arcs: Difference between revisions

Namespaces

More

Page actions

Navigation

Navigation

Wiki tools

Wiki tools

@@ Line 1: / Line 1: @@
-<mark>Another term for a "Team Development Arc" in the context of NETs is "developmental pathway".</mark> PBEM asks NET teams to meet regularly, but to do what? Without a defined purpose, team meetings can drift, prompting some members to stop attending meetings, and teams do not build their capacity as neighborhood-based disaster responders. The purpose of Team Developmental Arcs are to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap through team development rather than convening meetings around "what should we talk about this month?"'''
+<mark>Another term for a "Team Development Arc" in the context of NETs is "developmental pathway".</mark> PBEM asks NET teams to meet regularly, but to do what? Without a defined purpose, team meetings can drift, prompting some members to stop attending meetings, and teams do not build their capacity as neighborhood-based disaster responders. The purpose of Team Developmental Arcs are to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap through team development''' rather than convening meetings around "what should we talk about this month?"
+'''There is a two part objective to this program:'''
+# '''Provide Team Leaders with team meeting activity modules that can be easily planned, like a recipe, for team meetings.'''
+# '''Help teams move along a path or paths of development towards greater efficacy as a team of disaster responders.'''
 The use of Team Development Arcs are completely optional, and can be changed or edited to suit the needs of NETs who use them. They are intended as a supplementary resource for NET Team Leaders.
+{| class="wikitable"
+|+
+! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents
+! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
+|-
+|Form: [https://app.smartsheet.com/b/form/45b4b43047e74ce0842e3dc924f43f4e Development Arc Feedback]
+|2025.10.04
+|-
+|Form: [https://app.smartsheet.com/b/form/104dab042ef84ca5a9fce7b2076d5ad3 I Would Like to Create a Module]
+|2025.10.04
+|-
+|Form: [https://app.smartsheet.com/b/form/0199b17984a073d69aad94f410695792 I Would Like to Instruct a Module]
+|2025.10.04
+|}
+<br/>
+<br>
+{|style="border:1px solid grey; border-collapse:collapse;"
+|+
+!style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|<small>Contents</small>
+|-
+|style="background:#eaecf0;border:0px #eaecf0;border-collapse:collapse;"|[[Team Development Arcs#Team Development Arc Leadership Approach|<small>Team Development Arc Leadership Approach</small>]]
+[[Team Development Arcs#Team Development Arcs Table|<small>Team Development Arcs Table</small>]]
+[[Team Development Arcs#Braiding the Arcs Together|<small>Braiding the Arcs Together</small>]]
+[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|<small>'''Development Arc I:''' Team Organization and Cohesion</small>]]
+[[Team Development Arcs#Development Arc II: Response Operations Planning|<small>'''Development Arc II:''' Response Operations Planning</small>]]
+[[Team Development Arcs#Development Arc III: Exercises and Tabletops|<small>'''Development Arc III:''' Exercises and Tabletops</small>]]
+[[Team Development Arcs#Development Arc IV: Communications|<small>'''Development Arc IV:''' Communications</small>]]
+<small>[[Team Development Arcs#Development Arc V: Basic Response Skills|'''Development Arc V:''' Basic Response Skills]]</small>
+[[Team Development Arcs#Development Arc VI: Disaster DIY|<small>'''Development Arc VI:''' Disaster DIY</small>]]
+|}
 __NOTOC__
@@ Line 14: / Line 61: @@
 * '''IV.) Communications:''' Modules for developing best practices around post-disaster communications.
 * '''V.) Basic Response Skills:''' Review modules for any basic skillsets introduced in the Basic NET curriculum.
+* '''VI.) Disaster DIY:''' Like crafting night! Assemble an item or items that will be helpful in an emergency. Unlike the others, these activities ''do'' cost money because they require participants to purchase supplies.
 ===== Developing a team of NETs vs. developing individual volunteers =====
 As a NET Team Leader, your most important responsibility is '''helping your team grow together''' into a capable disaster response group. The purpose of this Development Arc curriculum is to give you a clear roadmap for building your team’s overall capacity.
-At the same time, each volunteer is also on their own personal growth journey. NET volunteers are largely responsible for their '''individual development''', which is where the Volunteer Support Function (VSF) system comes in. VSFs provide pathways for volunteers to specialize in skills that interest them and strengthen the team.
+At the same time, each volunteer is also on their own personal growth journey. NET volunteers are largely responsible for their '''individual development''', which is where the [[Volunteer Support Functions Directory|Volunteer Support Function (VSF)]] system comes in. VSFs provide pathways for volunteers to specialize in skills that interest them and strengthen the team.
 Your role as Team Leader is to see both sides: to think about your team as a whole unit, and also to recognize the unique skills and strengths each volunteer brings. You don’t need to control an individual’s development, but you can guide them—helping them choose VSFs that align with team needs, and working with PBEM to make sure those paths stay open. In short: '''you shape the team, while supporting each volunteer in shaping themselves as volunteer responders'''.
@@ Line 49: / Line 97: @@
 |+
 !
-! colspan="2" |<big>Development Arc I:Team Organization and Cohesion</big>
+! colspan="2" |<big>[[Team Development Arcs#Development Arc I: Team Organization and Cohesion|Development Arc I:Team Organization and Cohesion]]</big>
 |-
 !style="background-color:#AC96B7;"|
@@ Line 88: / Line 136: @@
 |-
 |I.09
-|Family Preparedness Discussion
+|[[Team Development Arcs#I.09 Family Preparedness Discussion|Family Preparedness Discussion]]
 |Either
 |-
 |I.10
-|Fundraising Review
+|[[Team Development Arcs#I.10 Fundraising Review|Fundraising Review]]
 |Either
 |-
 |I.11
-|Leadership Succession Planning
+|[[Team Development Arcs#I.11 Non-Disaster Related Social Event|Non-Disaster Related Social Event]]
-|Either
-|-
-|I.12
-|Non-Disaster Related Social Event
 |Either
 |}
@@ Line 165: / Line 209: @@
 |II.13
 |Post-Earthquake Decedent Care
+|Either
+|-
+|II.14
+|Response Debrief
 |Either
 |}
@@ Line 175: / Line 223: @@
 {| class="wikitable sortable" style="width: 70%;"
 |+
-! colspan="3" |<big>Development Arc III: Exercises and Tabletops</big>
+! colspan="3" |<big>[[Team Development Arcs#Development Arc III: Exercises and Tabletops|Development Arc III: Exercises and Tabletops]]</big>
 |-
 !style="background-color:#94AC96;"|
@@ Line 190: / Line 238: @@
 |-
 |III.03
-|Tabletop: Windstorm
+|[[Team Development Arcs#III.03 FEMA's CERT Tabletops|FEMA's CERT Tabletops]]
+* Earthquake Response
 |Indoors
 |-
@@ Line 217: / Line 266: @@
 |-
 |IV.01
-|Personal Accountability Reporting (PAR)
+|[[Team Development Arcs#IV.01 Personal Accountability Reporting (PAR)|Personal Accountability Reporting (PAR)]]
 |Either
 |-
@@ Line 239: / Line 288: @@
 </div>
+<div style="display: flex; justify-content: center; gap:5px">
 <div style="flex: 1;">
-{| class="wikitable sortable" style="width: 35%;"
+{| class="wikitable sortable" style="width: 70%;"
 |+
 ! colspan="3" |<big>Development Arc V: Basic Response Skills</big>
@@ Line 292: / Line 343: @@
 |Either
 |}
+</div>
+<div style="flex: 1;">
+{| class="wikitable sortable" style="width: 70%;"
+|+
+! colspan="3" |<big>[[Team Development Arcs#Development Arc VI: Disaster DIY|Development Arc VI: Disaster DIY]]</big>
+|-
+!style="background-color:#f7ffb2;"|
+!style="background-color:#f7ffb2;"|Activity
+!style="background-color:#f7ffb2;"|Indoors/Outdoors
+|-
+|VI.01
+|[[Team Development Arcs#VI.01 DIY Air Cleaner|DIY Air Cleaner]]
+|Either
+|-
+|VI.02
+|[[Team Development Arcs#VI.02 Hands-Free Portable Sink|Hands-Free Portable Sink]]
+|Either
+|-
+|VI.03
+|[[Team Development Arcs#VI.03 Easy-Build Handwashing Station|Easy-Build Handwashing Station]]
+|Either
+|}
+</div>
 </div>
 <br>
@@ Line 313: / Line 388: @@
 ===== EXAMPLE: Team development over the course of one year =====
 [[File:Wemmick Heights.jpg|thumb|''Actual photo of Wemmick Heights NET team meeting planning session.'']]
-So let's say the completely made-up NET team of Wemmick Heights has a newly elected Team Leader, Joe Gargery, after TL Thérèse Defarge had an [[wikipedia:Madame_Defarge|unfortunate guillotine accident]]. Joe wishes to take a more collaborative and delegative approach than Madame Defarge did. He asks his team to come together to plan out their next twelve meetings (they meet once a month, so this will cover the year for them). After discussing their goals, they agreed on the following calendar:
+So let's say the completely made-up NET team of [[Media:2016.08.20.Wemmick Heights Ops Plan.pdf|Wemmick Heights]] has a newly elected Team Leader, Joe Gargery, after TL Thérèse Defarge had an [[wikipedia:Madame_Defarge|unfortunate guillotine accident]]. Joe wishes to take a more collaborative and delegative approach than Madame Defarge did. He asks his team to come together to plan out their next twelve meetings (they meet once a month, so this will cover the year for them). After discussing their goals, they agreed on the following calendar:
 {| class="wikitable" style="width: 60%;"
 |+
@@ Line 414: / Line 489: @@
 == Development Arc I: Team Organization and Cohesion ==
+<div class="mw-collapsible mw-collapsed">
 === I.01Team Meeting Logistics Discussion ===
 [[File:2024.07.27.CentennialExercise (2).jpg|thumb|350x350px|''Karen Wolfgang and Centennial NET. Popsicles always makes things more palatable.'']]
@@ Line 519: / Line 594: @@
 * If there is time (i.e. at least two weeks before the session), the facilitator should encourage all team members to check they have all the equipment PBEM issues: ID card, hard hat (which should be replaced every five years), hard hat chin strap, and vest. Any missing items or items in need of replacement can be requested at the '''[https://app.smartsheet.com/b/form/5b3303eec5114f6ba0d6ffa52e496933 NET/BEECN ID Card, Helmet, and/or Vest Request Form]'''. PBEM also issues FRS/GMRS radios (if a volunteer cannot afford one), Field Operating Guides (FOGs), and waterproof backpack covers as supplies are available.
-'''<mark>Facilitation</mark>'''[[File:Netpack.jpg|right|265x265px]]Ask each team member to bring their NET bag or response kit to the meeting. Begin by reviewing the [[Basic NET Training Standard Syllabus#Equipment: Basic NET Response Packs|official NET kit list]]. Explain that the purpose of this exercise is not to judge completeness but to help everyone become more familiar with their gear, share practical tips, and make sure nothing critical is missing.
+'''<mark>Facilitation</mark>'''
+[[File:Netpack.jpg|right|265x265px]]Ask each team member to bring their NET bag or response kit to the meeting. Begin by reviewing the [[Basic NET Training Standard Syllabus#Equipment: Basic NET Response Packs|official NET kit list]]. Explain that the purpose of this exercise is not to judge completeness but to help everyone become more familiar with their gear, share practical tips, and make sure nothing critical is missing.
 Facilitate a guided walkthrough of major kit categories—personal safety/PPE (helmet, vest, gloves), communication (radio, whistle, contact sheet), medical (first aid supplies), tools, and comfort items (snacks, water). Invite volunteers to share how they’ve adapted their kits to fit their neighborhood context or personal needs (e.g., dog leash, maps, laminated cards). Keep the conversation focused on functionality and portability. End with a brief “gap check”: have members note items they need to add or replace, and suggest a timeline for completing those updates. If possible, document any common shortages so the team can discuss bulk purchases or supply-sharing at a future meeting.
@@ Line 804: / Line 881: @@
 === I.09 Family Preparedness Discussion ===
 '''<mark>Learning Objective</mark>'''
+[[File:Stock Image Family.jpg|thumb|350x350px|''I looked for a free stock image of a family preparing for a disaster. This one aint bad, but I hope they rotate that water.'']]
 ''Team members will reflect on their own household readiness and identify steps to ensure their families are safe and self-sufficient when they deploy as NET volunteers after a disaster.''
 '''<mark>Supplemental Resources</mark>'''
-Ready.gov [https://www.ready.gov/plan Make a Plan]
+:Ready.gov [https://www.ready.gov/plan Make a Plan]
 '''<mark>Preparation</mark>'''
@@ Line 840: / Line 917: @@
 '''<mark>Module Outputs</mark>'''
-None.<br/>
+None.
+<br/>
 <hr>
-=== Fundraising Review ===
+=== I.10 Fundraising Review ===
-'''''Learning objective:''''' ''Team members will assess whether fundraising is necessary for their operations (such as building an equipment cache) and, if so, identify appropriate and realistic fundraising strategies and how to use Friends of Portland NET as a fiscal agent to support those efforts.''
+'''<mark>Learning Objective</mark>'''
-'''''Preparation:''''' Review the [https://friendsofportlandnet.org/ Friends of Portland NET] website.
+''Team members will assess whether fundraising is necessary for their operations (such as building an equipment cache) and, if so, identify appropriate and realistic fundraising strategies and how to use Friends of Portland NET as a fiscal agent to support those efforts.''
+'''<mark>Supplemental Resources</mark>'''
+:''[https://friendsofportlandnet.org/ Friends of Portland NET] website''
+'''<mark>Preparation</mark>'''
+Review the [https://friendsofportlandnet.org/ Friends of Portland NET] website. If it is already confirmed that the team would like to pursue fundraising, the facilitator should contact FPN and ask to open an account.
+'''<mark>Facilitation</mark>'''
-'''''Facilitation:''''' Open the discussion by asking: ''“What are the things our team would like to do or have that require money?”'' Write down ideas such as equipment cache supplies, radios, signage, printing outreach materials, or team-specific projects. Clarify what PBEM and the NET program already provide, and identify any gaps that may require outside support.
+Open the discussion by asking: ''“What are the things our team would like to do or have that require money?”'' Note that PBEM will provide assistance for some things (such as printing or radios) as resources allow. Write down ideas such as [[Team Equipment Caches|equipment cache supplies]], radios, signage, printing outreach materials, or team-specific projects. Clarify what PBEM and the NET program already provide, and identify any gaps that may require outside support.
-Explain that the nonprofit '''[https://friendsofportlandnet.org/ Friends of Portland NET (FPN)]''' can serve as the fiscal sponsor for NET teams. This means teams can raise funds (through donations, grants, or partnerships) without managing their own bank accounts or nonprofit paperwork. Funds raised are held and managed by FoPNET on behalf of the team. This arrangement ensures compliance, transparency, and accountability, while still giving teams access to the resources they need.
+Explain that the nonprofit '''[https://friendsofportlandnet.org/ Friends of Portland NET (FPN)]''' can serve as the fiscal sponsor for NET teams. This means teams can raise funds (through donations, grants, or partnerships) without managing their own bank accounts or nonprofit paperwork. Funds raised are held and managed by FPN on behalf of the team. This arrangement ensures compliance, transparency, and accountability, while still giving teams access to the resources they need.
 If the team agrees that fundraising is needed, brainstorm '''realistic approaches''' such as:
@@ Line 859: / Line 948: @@
 * Running a one-time community fundraiser for a specific project.
-Once ideas are generated, guide the group to select one or two strategies to pursue. Assign roles (who will contact FoPNET, who will draft outreach language, who will liaise with a grant source), and set a timeline. If fundraising isn’t needed now, capture that decision and plan to revisit later.
+Once ideas are generated, guide the group to select one or two strategies to pursue. Assign roles (who will contact FPN, who will draft outreach language, who will liaise with a grant source), and set a timeline. If fundraising isn’t needed now, capture that decision and plan to revisit later.
-'''Debrief Questions:'''
+'''<mark>Debrief Questions</mark>'''
 * What needs do we have that could reasonably be supported through fundraising?
-* How does working with FoPNET simplify the process for us?
+* How does working with FPN simplify the process for us?
 * Which fundraising methods feel both achievable and consistent with our team’s values?
-* Who will connect with FoPNET and take the first step toward pursuing this?
+* Who will connect with FPN and take the first step toward pursuing this?
+'''<mark>Module Outputs</mark>'''
+None.
 <br/>
 <hr>
-=== Non-Disaster Related Social Event ===
+=== I.11 Non-Disaster Related Social Event ===
-'''''Learning objective:''''' ''Loosen up, nerds! Also, to help get to know each other better.''
+'''<mark>Learning Objective</mark>'''
-'''''Facilitation:''''' Remind the group that NET is not just about emergency response—it’s also about being good neighbors and building strong community bonds. A relaxed, non-disaster social event gives team members a chance to connect as people first, which often makes them more cohesive and resilient when an emergency does come.
+''Loosen up, nerds! Also, to help get to know each other better.''
-Facilitate a short brainstorming session: what kinds of low-key social activities would appeal to your team and fit the neighborhood context? Examples might include a potluck, park picnic, movie night, coffee meet-up, or a group volunteer project at a local charity. Keep it simple—this is about fun and connection, not logistics. Make sure events are inclusive and accessible: consider dietary needs, childcare, and mobility.
+'''<mark>Supplemental Resources</mark>'''
-Once the team has identified an idea, assign one or two volunteers to organize details (date, location, invites). Emphasize that these gatherings don’t need to be big or frequent—even one or two casual social events a year can go a long way toward improving morale and retention. Encourage members to invite family or neighbors, as broadening participation can both strengthen social ties and spark interest in the NET program.
+Oh I don't know. Probably any number of Martha Stewart books. Don't ask the introvert.
-Some possible ideas:
+'''<mark>Preparation</mark>'''
+None.
+[[File:2023.08.25.NET Camp.Bob Crispin (6).jpg|thumb|350x350px|''NETs know how to party.'']]
+'''<mark>Facilitation</mark>'''
+Remind the group that NET is not just about emergency response—it’s also about being good neighbors and building strong community bonds. A relaxed, non-disaster social event gives team members a chance to connect as people first, which often makes them more cohesive and resilient when an emergency does come.
+Facilitate a short brainstorming session: what kinds of low-key social activities would appeal to your team and fit the neighborhood context? Examples might include a potluck, park picnic, movie night, coffee meet-up, or a group volunteer project at a local charity. Keep it simple—this is about fun and connection, not logistics. Make sure events are inclusive and accessible: consider dietary needs, childcare, and mobility. PBEM also recommends considering that some team members may be in recovery, and it may be best to avoid having alcohol at the event.
+Once the team has identified an idea, assign one or two volunteers to organize details (date, location, invites). Emphasize that these gatherings don’t need to be big or frequent—even one or two casual social events a year can go a long way toward improving morale and retention. Encourage members to invite family or neighbors, as broadening participation can both strengthen social ties and spark interest in the NET program.
+The big challenge is: try not to talk about anything disaster related.
+Some possible ideas:
 '''Food & Drink Gatherings'''
@@ Line 895: / Line 1,003: @@
 '''Community-Oriented Fun'''
-* '''Group Volunteering:''' Help at a local food bank, park cleanup, or neighborhood project.
+* '''Group Volunteering:''' Help at a [https://www.oregonfoodbank.org/get-involved/volunteer local food bank], park cleanup, or neighborhood project.
 * '''Movie Night:''' Project a film in someone’s yard or at a community hall.
 * '''Holiday Gathering:''' Seasonal potluck or cookie swap around winter or summer holidays.
@@ Line 905: / Line 1,013: @@
 * NET birthday/anniversary celebration (marking when the team formed).
-'''Debrief Questions:'''
+'''<mark>Debrief Questions</mark>'''
 *What kinds of social events would feel fun and inclusive for our team?
@@ Line 914: / Line 1,022: @@
 *What’s one way we can make sure these events become part of our team culture?
+'''<mark>Module Outputs</mark>'''
+None.
 <br>
 <hr>
-<br>
+</div>
 == Development Arc II: Response Operations Planning ==
 <div class="mw-collapsible mw-collapsed">
 === VSF Gap Analysis ===
-'''''Learning objective:''' Team members will understand the purpose of Volunteer Support Functions (VSFs), identify their own areas of specialization, and consider how their team’s mix of VSFs can strengthen neighborhood response.''
+'''<mark>Learning Objective</mark>'''
-'''''Facilitation:''''' Begin by explaining that PBEM organizes all volunteers (NETs, BEECN, ATVs) into Volunteer Support Functions (VSFs). These are specialized areas of disaster skills or knowledge—such as Search & Rescue, Medical, Communications, Logistics, or Public Information. VSFs serve two main purposes: they allow volunteers to deepen skills in areas they’re interested in, and they give teams and PBEM a clear picture of what capabilities exist across the city.
+''Team members will understand the purpose of Volunteer Support Functions (VSFs), identify their own areas of specialization, and consider how their team’s mix of VSFs can strengthen neighborhood response.''
+'''<mark>Supplemental Resources</mark>'''
+'''<mark>Preparation</mark>'''
+'''<mark>Facilitation</mark>'''
+Begin by explaining that PBEM organizes all volunteers (NETs, BEECN, ATVs) into Volunteer Support Functions (VSFs). These are specialized areas of disaster skills or knowledge—such as Search & Rescue, Medical, Communications, Logistics, or Public Information. VSFs serve two main purposes: they allow volunteers to deepen skills in areas they’re interested in, and they give teams and PBEM a clear picture of what capabilities exist across the city.
 Provide a simple overview of how VSFs work:
@@ Line 942: / Line 1,063: @@
 Wrap up by encouraging interested members to contact PBEM if they want to update their VSF, and consider recording your team’s VSF mix on your NETwiki page for future reference.
-'''Debrief Questions:'''
+'''<mark>Debrief Questions</mark>'''
 *Which VSFs are represented on our team right now? Where are the gaps?
@@ Line 951: / Line 1,072: @@
 *How can we support each other in building depth in these areas (peer training, shared resources, guest speakers)?
+'''<mark>Module Outputs</mark>'''
 </br>
 <hr>
@@ Line 1,205: / Line 1,329: @@
 === Scenario Village Preparation ===
-=== Tabletop: Windstorm ===
+=== III.03 FEMA's CERT Tabletops ===
+'''<mark>Learning Objective</mark>'''
+====== Earthquake Response Scenario ======
+'''''Note: This tabletop used to be part of Basic NET training, so some members may already be familiar with it.'''''
+"A major earthquake has struck at 1:00 p.m. on a mid-week afternoon. The day is cool and cloudy. It has been raining lightly all day, and the temperature is expected to fall quickly by 5:30 p.m. The local CERT has been activated to assess damage in its neighborhood. CERT members have just arrived at the pre-designated meeting point."
+:''[[Media:FEMA CERT Tabletop Exercise 1.Facilitator.pdf|Facilitator Packet FEMA CERT Tabletop Exercise #1]]'' (one copy for the facilitator); 31 pages.
+:''[[Media:FEMA CERT Tabletop Exercise 1.Participants.pdf|Participant Packet FEMA CERT Tabletop Exercise #1]]'' (each participant should receive one packet); 14 pages.
 === Disasterville Board Game ===
@@ Line 1,216: / Line 1,350: @@
 == Development Arc IV: Communications ==
 <div class="mw-collapsible mw-collapsed">
-=== Personal Accountability Reporting (PAR) ===
+=== IV.01 Personal Accountability Reporting (PAR) ===
 '''Learning Objective:'''
@@ Line 1,375: / Line 1,509: @@
 '''Learning Objective:'''
-''Team members will practice using proper radio etiquette, including prowords, clear phrasing, and the phonetic alphabet, to ensure efficient and accurate communication during disaster response.''
+''Team members will practice clear, efficient radio communication by developing practical message-handling skills—using phonetics, “I spell,” pacing, and fills—to ensure information is accurately sent and received during disaster response.''
 '''Facilitation Guide:'''
-Begin by highlighting that clear, concise radio communication is '''critical under stress'''. Unlike phone calls, radio transmissions are one-to-many, brief, and subject to interference. A little discipline goes a long way in reducing confusion and speeding operations.
+Begin by setting expectations clearly:
+This module is not radio certification training. It is a practical, team-based exercise designed to help all NET volunteers—especially those who use radios infrequently—communicate clearly and confidently under stress. The focus is not perfection, but making sure the person on the other end actually understands the message.
+Emphasize that good radio communication is less about sounding “professional” and more about being helpful, patient, and precise.
+'''Step 1 – What Radios Are Good (and Bad) At:'''
+Briefly discuss radio realities:
+* Radios are shared channels
+* Messages may be missed or cut off
+* Background noise is common
+* Stress affects how we speak and listen
+Frame the goal:
+“Your job on the radio is not to talk fast or fancy. Your job is to make it easy for the listener to copy your message.”
-'''Step 1 – Review the Basics of Radio Etiquette:'''
+'''Step 2 – Call-Up Basics (Keep It Simple):'''
-* Think before you speak: Plan your message in your head before keying the mic.
+Review the basic call-up pattern: Who you are calling → who you are
-* Press, pause, then talk: Wait 1 second after pressing transmit so your first words aren’t cut off.
-* Keep it short: Use plain language, avoid unnecessary chatter.
-* Identify who you’re calling, then yourself: Example: “Staging, this is Team Alpha.”
-* Acknowledge messages: Use “Copy,” “Affirmative/Negative,” or repeat back essential details.
+Example: ''“Staging, this is Team Alpha.”''
-* One at a time: Pause before speaking in case someone else is transmitting.
-'''Step 2 – Introduce Prowords:'''
+Reinforce:
-Explain that '''prowords''' are standard words that carry agreed-upon meanings in radio traffic. Review and practice common ones:
+* Use tactical identifiers, not names
+* Pause briefly before speaking
+* Speak clearly, not loudly
-* '''“Over”''' – I’m done speaking and expect a reply.
+'''Step 3 – Message Handling Skills (Core Focus):'''
-* '''“Out”''' – I’m done, no reply expected.
-* '''“Say Again”''' – Repeat your last transmission.
-* '''“Copy”''' – I received and understood.
-* '''“Standby”''' – I acknowledge but need more time.
-* '''“Affirmative” / “Negative”''' – Yes / No.
-* '''“Break”''' – Used to separate different portions of a message.
-'''Step 3 – Phonetic Alphabet Practice:'''
+Explain that most radio problems are message problems, not equipment problems. Introduce the four core skills adapted from GRO practice.
-Provide the NATO phonetic alphabet (Alpha, Bravo, Charlie, etc.) and stress its importance when spelling out names, addresses, or codes over a noisy channel.
+'''A.) Pacing (speed)'''
-'''Practice exercise:''' Have each member spell their last name phonetically. Then practice with addresses, street names, or team designators.
+Demonstrate the difference between:
+* Talking at conversation speed
+* Talking at radio speed (slower, deliberate)
+Practice:
+* Read a short message too fast
+* Then read it slowly enough that someone could write it down
+Key coaching point: ''"If someone is writing, you are probably talking too fast"''
-'''Step 4 – Transmission Exercise:'''
+'''B.) Phonetics (Flexible, not formal)'''
-Pair up participants with radios.
+Explain: Phonetics simply means using words to make letters clear. There is no requirement to memorize a specific alphabet.
-Provide each pair with a short scripted message to relay (e.g., “Requesting medical supplies at 123 Pine Street”).
+Examples:
-Have them practice proper call-up, use of prowords, and phonetic spelling when needed.
+* “J as in Jelly”
+* “B as in Boy”
+* “M as in Mountain”
+Encourage improvisation — clarity matters more than correctness.
-Rotate scripts so participants adapt to new scenarios.
+Practice:
-'''Step 5 – Group Drill:'''
+* Spell names, street names, or intersections using any clear phonetics
+* Listener repeats back what they heard
-Set up a mock NET radio net with one person as '''Net Control'''. Assign others roles (Team Alpha, Team Bravo, Logistics, etc.). Practice a short scenario (e.g., small fire, blocked road, injured resident) where teams must report in using proper etiquette.
+'''C.) "I spell"'''
-'''Debrief Questions:'''
+Introduce “I spell” as a listener-friendly cue. Example:
+''“The street name is I spell: J as in Jelly, E as in Eagle, R as in Raspberry.”''
+Practice:
+* Have volunteers announce “I spell”
+* Spell slowly
+* Pause between letters
+'''D.) Fills, Repeats, and Corrections'''
+Explain that mistakes are normal. What matters is fixing them clearly. Useful techniques:
+* “Correction…”
+* “Say again from…”
+* Repeating critical info twice (addresses, numbers)
+Practice:
+* Intentionally introduce a garbled message
+* Ask the listener to request a fill
+* Practice clean corrections without frustration
+'''Step 4 – Numbers and Addresses:'''
-* Which habits helped messages come through most clearly?
+Review best practices:
-* What mistakes did we make that caused confusion?
-* How can we reinforce consistent use of prowords and phonetic spelling in future drills?
+* Speak numbers slowly
-* What challenges might we face under stress, and how do we prepare for them?
+* Group long numbers
-</div>
+* Repeat addresses if important
+Example: ''"Address is one-two-three Pine Street. I repeat: one-two-three Pine Street."''
+Practice with:
+* Addresses
+* Block numbers
+* Unit counts
+'''Step 5 – Paired Message Practice:'''
+Pair participants with radios. Give each pair short, realistic messages:
+* Requesting supplies
+* Reporting damage
+* Checking in on status
+Focus coaching on:
+* Pacing
+* Phonetics
+* Listener confirmation
+Rotate roles so everyone speaks and listens.
+'''Step 6 – Group Net Practice'''
+Set up a simple radio net:
+* One Net Control
+* Several teams checking in
+Inject common challenges:
+* “Say again”
+* Missed numbers
+* Competing traffic
+Pause occasionally to coach: ''What could make that message easier to copy?"''
+'''Debrief Questions:'''
+* What made messages easiest to understand?
+* When did pacing matter most?
+* What helped you as a listener?
+* What habits do we want to practice regularly as a team?
+'''Module Outputs:'''
+By the end of this module, teams should have:
+* Practiced pacing messages for clarity
+* Used phonetics flexibly and confidently
+* Used “I spell” appropriately
+* Corrected and repeated messages effectively
+* Increased confidence speaking on the radio without overthinking it</div>
+== Development Arc V: Basic Response Skills ==
+== Development Arc VI: Disaster DIY ==
+<div class="mw-collapsible mw-collapsed">
+=== VI.01 DIY Air Cleaner ===
+{{#ev:youtube|aw7fUMhNov8|430|right|'''''Video: How to Make a DIY Air Filter'''''|frame}}
+'''<mark>Learning Objective</mark>'''
+''Team members will learn how to construct a low-cost, do-it-yourself air cleaner using readily available materials, understand when and why it should be used during smoke or poor air quality events, and practice assembling one together to build skills they can share with neighbors.''
+'''<mark>Materials List</mark>'''
+{| class="wikitable"
+|+
+!Item
+!Qty.
+!Example
+!Cost
+|-
+|20" x 20" box fan
+|1
+|
+|
+|-
+|20" x 20" x 1" or 4" [https://www.epa.gov/indoor-air-quality-iaq/what-merv-rating MERV] 13 air filter
+|1 to 5
+|
+|
+|-
+|Sheet of scrap cardboard (at least 20" x 20"
+|1
+|
+|
+|-
+|Clamps, bungee cords, or duct tape
+|
+|
+|
+|}
+'''<mark>Instructions</mark>'''
+{| class="wikitable"
+|+
+! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources
+! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
+|-
+|[[Media:2023.06.09.Do-It-Yourself Air Cleaners Making Cleaner Air More Accessible US EPA.pdf|EPA Instructions]]
+|2024.08.26
+|}
+<br>
+=== VI.02 Hands-Free Portable Sink ===
+'''<mark>Learning Objective</mark>'''
+''Team members will learn how to build a portable, hands-free handwashing station using two plastic buckets and a one-way squeeze pump, with an option to organize a community “work party” to produce multiple stations. Volunteers will also recognize how pre-positioning several units across the neighborhood—along with stored water—ensures immediate access to safe, sanitary handwashing after a disaster. This module was created by NET volunteer Merilee Karr.''
+'''<mark>Materials List</mark>'''
+See instructions.
+'''<mark>Instructions</mark>'''
+{| class="wikitable"
+|+
+! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources
+! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
+|-
+|[https://www.instructables.com/Portable-Foot-pump-Handwashing-Station/ Hands-Free Portable Sink at Instructables]
+|≈ 2020
+|}
+<br>
+=== VI.03 Easy-Build Handwashing Station ===
+'''<mark>Learning Objective</mark>'''
+''Team members will recognize the importance of maintaining safe handwashing practices when plumbing is unavailable—whether due to a major or minor disaster, or in everyday off-grid settings such as community events or camping. Volunteers will explore low-cost, portable solutions that ensure hygiene and reduce the spread of illness when conventional water systems are disrupted. This module was created by NET volunteer Merilee Karr.''
+'''<mark>Materials List</mark>'''
+See instructions.
+'''<mark>Instructions</mark>'''
+{| class="wikitable"
+|+
+! scope="col" width="300px" style="background-color: darkkhaki;color:white;"|Relevant Documents/Resources
+! scope="col" width="100px" style="background-color: darkkhaki;color:white;"|Updated
+|-
+|[https://www.instructables.com/Easy-Build-Handwashing-Station-With-Videos/ Easy-Build Handwashing Station at Instructables]
+|2021.02.26
+|}
+<br>
 == Team Development Arcs Frequently Asked Questions (FAQs) ==

Anonymous

Search

Team Development Arcs: Difference between revisions

Navigation

Wiki tools

Page tools