Team Development Arcs: Difference between revisions

(277 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 ~~many Team Leaders have requested guidance on the "why" of meeting.~~ 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 is to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap rather than ~~running~~ meetings by "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__

== Team Development Arc Leadership Approach ==

~~A NET Team Leader is responsible for developing their team. PBEM recommends NET Team Leaders approach the task with the following in mind:~~

* Use team meetings to develop the team (~~not necessarily individual NETs~~)

===== What is a Team Development Arc and how does a Team Leader use them? =====

* Think of your operations plan

A single "Arc" is a set of individual meeting modules collected around a theme. There are five themes (each theme being an Arc):

* '''~~Begin with the end in mind~~:''' ~~TLs should visualize what~~ a ~~capable~~ NET ~~team for~~ their neighborhood ~~looks like. For example, by~~ the ~~end~~ of ~~the arc,~~ the team...

** Can set up a ~~command post quickly and assign roles~~.

* '''I.) Team Organization and Cohesion:''' The modules in this arc are designed to develop the team ''as a team'' and to plug the team more into the immediate community they serve''.'' These modules help the NET expand their presence into the neighborhood while also reinforcing the social fabric of the team itself.

** Knows local hazards and ~~prospective resources~~.

* '''II.) Response Operations Planning:''' These modules are related to development and maintenance of a Team's Operations Plan.

** Can deploy BEECN, DAMM, or other comms with little prompting.

* '''III.) Exercises and Tabletops:''' Exercises and tabletops serve to build confidence and teamwork, reveal gaps in planning, and improve response capacity.

** Has regularly practiced light search and rescue and other basic skillsets.

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

** Has team ~~cohesion and a predictable meeting rhythm~~.

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

* '''~~Delegate:~~''' ~~A TL~~ is responsible for ~~being~~ the ~~"conductor" at~~ the ~~front of~~ the ~~orchestra~~, but the ~~conductor does not play~~ an ~~instrument. After~~ a ~~TL develops~~ their ~~team~~'s ~~Development~~ Arcs, ~~they~~ should ~~assign responsibility for most meeting topics~~ to ~~different members of the~~ team

* '''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.

* Braid arcs together and ~~pursue simultaneously~~

===== 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 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'''.

===== The relationship between Arcs and team operations planning =====

Every NET Team should have an Ops Plan that clarifies for the team, after a disaster, such things as where their staging area is, who will take what role, where the neighborhood's most significant hazards are, and so on.

Many of the individual modules in the Arcs curriculum have a direct bearing on completion of an Ops Plan. For example, researching and exploring your neighborhood's risk profile or reaching out to local businesses. Therefore, completion of some modules will lead towards completion of an Ops Plan (or refreshing an existing Ops Plan). Teams that need more work on their Ops Plan should prioritize modules that will bring them closer to that goal. [[Team Development Arcs#Development Arc II: Response Operations Planning|Development Arc II: Response Operations Planning]] particularly includes modules related to Operations Plan development.

===== The relationship between Arc modules, team meeting agendas, and delegation =====

Most modules in this guide take about an hour for a team to complete. Some are shorter, and a few may run longer. That flexibility gives you options when planning agendas. A single module might fill an entire meeting, or you might use part of a module alongside other agenda items. And since modules are optional, you don’t need to use one at every meeting.

~~(TBA)~~

Modules are also a great tool for delegation. Team Leaders should practice handing off responsibilities, and team members should practice taking them on. This skill is vital in a real response, but it also prevents burnout by making sure the Team Leader isn’t doing all the work during “blue sky” times. PBEM encourages Team Leaders to assign modules to different team members and let them facilitate. This builds confidence, spreads knowledge, and makes meetings more engaging for everyone.

~~Maintenance and recycling..~~.

===== Begin with the end in mind =====

Whether a Team Leader plans the team's arc alone or in consultation with team members, PBEM encourages planners to envision how a team will change by the time they are done planning their progress. For example, by the end of a year, perhaps a team:

~~Individual vs~~. ~~Team development~~

* ...can set up a command post quickly and assign roles

* ...knows local hazards and prospective neighborhood resources

* ...can deploy BEECN, DAMM, and other comms with little prompting

* ...has regularly practiced a few basic skillsets, such as managing SUVs

== Team Development Arcs Table ==

Line 28:

Line 96:

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

|+

! colspan="2" |<big>~~Developmental~~ 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;"|

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

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

|-

|NET Response Kit Inventory

|I.01

|[[Team Development Arcs#I.01Team Meeting Logistics Discussion|Team Meeting Logistics Discussion]]

|Either

|-

|I.02

|[[Team Development Arcs#I.02 NET Response Kit Inventory|NET Response Kit Inventory]]

|Either

|-

|Local Fire Station Meeting

|I.03

|[[Team Development Arcs#I.03 Local Fire Station Meeting|Local Fire Station Meeting]]

|Indoors

|-

|NETwiki Team Page Discussion

|I.04

|[[Team Development Arcs#I.04 Team Equipment Cache Evaluation/Checkup|Team Equipment Cache Evaluation/Checkup]]

|Depends on cache

|-

|I.05

|[[Team Development Arcs#I.05 NETwiki Team Page Discussion|NETwiki Team Page Discussion]]

|Indoors

|-

|Team ~~Recruitment Strategy~~

|I.06

|[[Team Development Arcs#I.06 Local Business Outreach|Local Business Outreach]]

|Outdoors

|-

|I.07

|[[Team Development Arcs#I.07 Neighborhood Association Meeting|Neighborhood Association Meeting]]

|Either

|-

|Team ~~Equipment Cache Evaluation/Checkup~~

|I.08

|~~Depends on cache~~

|[[Team Development Arcs#I.08 Team Recruitment Strategy|Team Recruitment Strategy]]

|Either

|-

|Family Preparedness Discussion

|I.09

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

|Either

|-

|Fundraising Review

|I.10

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

|Either

|-

|Non-Disaster Related Social Event

|I.11

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

|Either

|}

Line 62:

Line 152:

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

|+

! colspan="2" |<big>~~Developmental~~ Arc II: Response Operations Planning</big>

!

! colspan="2" |<big>Development Arc II: Response Operations Planning</big>

|-

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

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

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

|-

|II.01

|Operations Plan Check-In

|Either

|-

|II.02

|Neighborhood Profile Discussion

|Either

|-

|II.03

|Neighborhood Risk Assessment Discussion

|Either

|-

|II.04

|VSF Gap Analysis

|Either

|-

|~~Neighborhood URM Inventory~~

|II.05

|~~Outdoors~~

|Incident Objectives Discussion

|-

~~|Operations Plan Check-In~~

|Either

|-

|~~Local Business Outreach~~

|II.06

|Establishing a NET Incident Command Post

|Outdoors

|-

|II.07

|Severe Cold Weather Planning

|Either

|-

|II.08

|Severe Hot Weather Planning

|Either

|-

|~~Post-Earthquake Sanitation Planning~~

|II.09

|Deploying to Down Power Lines

|Either

|-

|~~Post~~-~~Earthquake Decedent Care~~

|II.10

|~~Either~~

|Clearing Storm Drains

|Outdoors

|-

|II.11

|Neighborhood URM Inventory

|Outdoors

|-

|~~Neighborhood Profile Discussion~~

|II.12

|Post-Earthquake Sanitation Planning

|Either

|-

|~~Neighborhood Risk Assessment Discussion~~

|II.13

|Post-Earthquake Decedent Care

|Either

|-

|~~Incident Objectives Discussion~~

|II.14

|Response Debrief

|Either

|-

~~|Clearing Storm Drains~~

~~|Outdoors~~

|}

</div>

Line 111:

Line 223:

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

|+

! colspan="2" |<big>~~Developmental~~ 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;"|

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

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

|-

|III.01

|Citywide Deployment Exercise (CDE)

|Outdoors

|-

|III.02

|Scenario Village Preparation

|Either

|-

|~~Tabletop: Windstorm~~

|III.03

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

* Earthquake Response

|Indoors

|-

|III.04

|Disasterville Board Game

|Indoors

|-

|III.05

|Railway Accident Tabletop

|Indoors

|-

|III.06

|Triage Boardgame

|Indoors

|-

~~|Citywide Deployment Exercise (CDE)~~

~~|Outdoors~~

|}

</div>

Line 139:

Line 259:

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

|+

! colspan="2" |<big>~~Developmental~~ Arc IV: Communications</big>

! colspan="3" |<big>Development Arc IV: Communications</big>

|-

!style="background-color:#7ABACA;"|

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

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

|-

|Personal Accountability Reporting (PAR)

|IV.01

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

|Either

|-

|IV.02

|Damage Assessment Mapping Module (DAMM) Exercise

|Outdoors

|-

|IV.03

|FRS/GMRS Radio Mapping

|Outdoors

|-

|IV.04

|BEECN Training/Review

|Outdoors

|-

|IV.05

|Radio Speaking Skills and Etiquette

|Outdoors

Line 162:

Line 288:

</div>

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

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

|+

! colspan="2" |<big>~~Developmental~~ Arc V: Basic Response Skills</big>

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

|-

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

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

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

|-

|V.01

|Managing SUVs Tabletop or Exercise

|Either

|-

|V.02

|Knot Techniques

|Either

|-

|V.03

|Survivor Carry Techniques

|Either (Outdoors is best)

|-

|V.04

|ICS Forms Review

|Either

|-

|V.05

|Triage Tabletop or Exercise

|Either

|-

|V.06

|Utility Shutoff Review

|Both

|-

|V.07

|Damaged Building Assessments

|Either

|-

|V.08

|Fire Extinguisher Review

|Outdoors

|-

|V.09

|Staging Area Setup

|Outdoors

|-

|V.10

|Splinting Review

|Either

|-

|V.11

|Building Markings

|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>

== Braiding the Arcs Together ==

[[File:BRAID.jpg|thumb|''I needed a metaphor here, so how's this? It's got...like, survival rope. In the metaphor. The metaphor for braiding together different arcs of your team's development. Look, I don't get paid to be profound okay?'']]

Sometimes the most effective way to plan is to bring the whole team together for a “braiding session.” In this meeting, the team looks at the five arcs side by side and decides which modules they want to tackle in the coming months. Instead of treating arcs as separate tracks, the team weaves them together into a shared path of growth.

'''How to Facilitate a Braiding Session:'''

# '''Lay out the options:''' Print or display all the modules (for example, as cards). Briefly remind the team what each arc is designed to build.

# '''Set the vision:''' Ask the group to picture what they want the team to look like six months or a year from now (e.g., more confident with radios, stronger neighborhood ties, smoother command post setup).

# '''Choose priorities:''' As a group, select a mix of modules from different arcs that best support that vision. For example, combine “NETwiki Page Discussion” (Cohesion) with “Ops Plan Check-In” (Operations) and “Radio Speaking Skills” (Communications).

# '''Build a sequence:''' Decide on a rough order. Some modules might be prerequisites for others; others can run in parallel.

# '''Assign facilitators:''' Encourage different volunteers to take responsibility for leading modules, so that leadership and knowledge are shared.

# '''Capture the plan:''' Record the braided arc in your team’s Ops Plan or NETwiki page so it can guide future meetings.

This process helps ensure the team’s development is purposeful, balanced, and shared, and not just driven by the Team Leader alone.

===== 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 [[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%;"

|+

!Meeting

!style="width:60px"|Date

!Module and Objective

!style="width:110px"|Module Facilitator

|-style="background:#e0d6e7"

|style="text-align:center"|1

|Jan. 15

|'''''Module:''''' NET Response Kit Inventory '''(Arc I – Cohesion)'''

'''''Objective:''''' Start the year by reviewing gear, sharing tips, and identifying common gaps. ''"Nell had an unusual NET response pack. There were suits of mail standing like ghosts in armour here and there, fantastic carvings brought from monkish cloisters, rusty weapons of various kinds..."''

|Nell Trent

|-style="background:#ebd9dd"

|style="text-align:center"|2

|Feb 19

|'''''Module:''''' Neighborhood Profile Discussion '''(Arc II – Ops Planning)'''

'''''Objective:''''' Explore hazards, assets, and demographics of the service area.

|Joe Gargery

|-style="background:#cde7ef"

|style="text-align:center"|3

|March 18

|'''''Module:''''' Radio Speaking Skills & Etiquette '''(Arc IV – Communications)'''

'''''Objective:''''' Practice prowords, phonetic alphabet, and clear transmissions. ''"With that Cockney accent of his, we might get better instruction if he filled his mouth full of marbles first."''

|Sam Weller

|-style="background:#ebd9dd"

|style="text-align:center"|4

|April 15

|'''''Module:''''' Severe Hot Weather Planning '''(Arc II – Ops Planning)'''

'''''Objective:''''' Explore ways the team can support the community during any dangerous heat events this summer. ''"If Miss Havisham is so concerned about the heat, maybe she should wear something besides that grotty wedding gown she never takes off."''

|Aurelia Havisham

|-style="background:#e0d6e7"

|style="text-align:center"|5

|May 20

|'''''Module:''''' Family Preparedness Discussion '''(Arc I – Cohesion)'''

'''''Objective:''''' Ensure volunteers’ households are ready so they can deploy with confidence. ''"Fagin will lead this module. Should be interesting. I just can't imagine how all those weirdly nimble orphans he's taken in will get by after an earthquake."''

|Fagin

|-style="background:#ebd9dd"

|style="text-align:center"|6

|June 17

|'''''Module:''''' Operations Plan Check-In '''(Arc II – Ops Planning)'''

'''''Objective:''''' Review staging area, comms, risks, and update Ops Plan as needed. ''"Should be a quick meeting. Thérèse knitted together a pretty good Ops Plan before she passed away."''

|Joe Gargery

|-style="background:#cde7ef"

|style="text-align:center"|7

|July 15

|'''''Module:''''' FRS/GMRS Radio Mapping '''(Arc IV – Communications)'''

'''''Objective:''''' Survey coverage in the neighborhood and identify dead zones. ''"Before he became the TL, Joe was our ARO. Makes sense for him to lead us through a radio exercise."''

|Joe Gargery

|-style="background:#d2ddd2"

|style="text-align:center"|8

|Aug. 19

|'''''Module:''''' Triage Board Game '''(Arc III – Exercises)'''

'''''Objective:''''' Refresh medical prioritization skills in a low-stress learning format. ''"Some of us wanted to do splinting but Sydney stepped up to facilitate saying it would be a far, far better thing to refresh our triage skills."''

|Sydney Carton

|-style="background:#ebd9dd"

|style="text-align:center"|9

|Sep. 16

|'''''Module:''''' Local Business Outreach '''(Arc II – Ops Planning)'''

'''''Objective:''''' Strengthen ties with key businesses for resources and resilience. ''"Nell insists that local businesses should be resilient and not gamble with their future."''

|Nell Trent

|-style="background:#ebe2bd"

|style="text-align:center"|10

|Oct. 21

|'''''Module:''''' Utility Shutoff Review '''(Arc V – Basic Skills)'''

'''''Objective:''''' Practice safe procedures for gas, electricity, and water shutoffs. ''"We're pretty sure Thérèse was trying to shut off the electricity when she grabbed the wrong lever by mistake."''

|Ernest Defarge

|-style="background:#d2ddd2"

|style="text-align:center"|11

|Nov. 18

|'''''Module:''''' Scenario Village Preparation '''(Arc III – Exercises)'''

'''''Objective:''''' Plan and organize for participation in the comprehensive CERT exercise.''"Wemmick Heights NET has the early December Scenario Village slot, so we're meeting with Alice and Jeremy to plan out our response."''

|Joe Gargery

|-style="background:#e0d6e7"

|style="text-align:center"|12

|Dec. 16

|'''''Module:''''' Non-Disaster Social Event '''(Arc I – Cohesion)'''

'''''Objective:''''' Non-denominational holiday potluck for team members and their families. ''"It will be at Ebenezer's mansion and he is bringing the biggest goose in all of London! NETs are asked not to bring chains to the party as they distress Ebenezer's unusually pale housemate."''

|Ebenezer Scrooge

|}

Joe decided, and the other members agreed, that this plan:

* '''Braids arcs together''' (Cohesion, Ops, Comms, Exercises, Skills).

* Alternates between '''discussion-based, skills-based, and exercise-based modules''' to keep energy fresh.

* Includes at least one '''community-facing activity''' (Business Outreach) and one '''social event'''.

=== Using the Development Arc Cards ===

{| 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:2025.09.06.Team Development Arc Cards.pdf|Team Development Arc Cards]] (prototype)

|2025.09.06

|}

For Team Leaders who want a tactile approach for planning their meeting schedule, PBEM has developed a set of cards that you can print out and pass around to team members as part of a planning discussion. It may be helpful to use the cards to arrange meeting topics on a table and move them around. '''The cards posted here are prototypes and are expected to improve in a short amount of time from their initial publication.'''

== 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.'']]

'''Learning Objective'''

''Team members will agree on clear, realistic logistics for team meetings (cadence, formats, roles, tech, accessibility, and communications) and capture them in a short “Meeting Charter” for the NETwiki/Ops Plan.''

'''Supplemental Resources'''

None.

'''Preparation'''

* Bring your calendar, current contact list, past agendas/attendance notes, and access to the team NETwiki page.

* If you’ll discuss hybrid/virtual: confirm a video platform (e.g., Zoom/Meet), projector/speakers, and a test laptop/FRS radio if you cross-check comms.

* The facilitation on this module is pretty detailed. Facilitator should read over it and decide what parts will work for their team and which parts may not.

* Print or share the “Decisions to Capture” checklist (below).

'''Facilitation'''

# '''Why this matters (3 min):''' Set the frame: predictable, inclusive logistics = better attendance, less burnout, faster activation when it counts.

# '''Meeting cadence & length (10 min):''' Decide

#* Frequency: monthly / every other month / quarterly.

#* Day/time: pick a consistent slot; sanity-check conflicts (holidays, recurring citywide events).

#* Duration: 60–90 minutes; cap standing meetings at 75 minutes when possible.

#* Seasonal adjustments: lighter in July/Aug; add an extra session pre-CDE or Scenario Village.

# '''Formats: in-person, virtual, hybrid (12 min):'''

#* In-person: venue accessibility (ADA entrance, restrooms), transit/parking, lighting & acoustics, child-friendly options, safety after dark.

#* Virtual: platform, host permissions, waiting room, display name standard (e.g., “Team-FirstName”), chat norms, recording policy.

#* Hybrid: room layout (U-shape + camera sightline), one device per room unmuted (others muted to avoid echo), a Remote Buddy role (monitors chat, voices remote hands).

#* Decide which formats match which meeting types (e.g., skills = in-person; planning = virtual; hotwash = hybrid).

# '''Roles & delegation (8 min):''' Consider adopting rotating roles to grow capacity.

#* Facilitator (sets pace, keeps stack)

#* Timekeeper (prompts 5-min warnings)

#* Scribe (captures decisions/tasks to NETwiki)

#* Greeter (welcomes, name tents, sign-in)

#* Tech lead / Remote Buddy (runs AV, watches chat)

#* Safety lead (room safety check, exits, severe-weather call)

# '''Agenda rhythm & decision rules (10 min):'''

#* Standard agenda (60–75 min):

#** Welcome & quick wins (5)

#** Safety moment / weather & hazards (3)

#** Module or skill block (30–40)

#** Ops/Comms updates (BEECN, DAMM, trainings) (10)

#** Tasks & assignments recap (5)

#** Announcements + next meeting preview (2)

#* Decision-making: consent or simple majority; define quorum (e.g., TL or designee + 5 members).

#* Parking lot for off-topic items; schedule follow-ups.

# '''Communications & reminders (7 min):'''

#* Channels: email list, text group, and NETwiki.

#* Reminder cadence:

#** Save-the-date (monthly/quarterly)

#** T-7 days agenda draft

#** T-24 hours quick reminder + materials

#* Attendance: sign-in each meeting; update contact changes immediately.

#* Privacy: don’t post personal phone/emails publicly; keep in a restricted sheet or shared drive.

# '''Accessibility & inclusion (5 min):'''

#* Plain-language agendas; avoid acronyms or define them once.

#* Request language interpretation or materials ahead of time; consider translated handouts for key items.

#* Quiet room or camera-off norms as needed; encourage pronouncing names correctly; code of conduct reminder.

# '''Contingencies (3 min):'''

#* Weather/power outage: who calls it, by when, via which channel.

#* Backup TL/facilitator: named successor for each meeting.

#* Tech fail: pre-agreed Plan B (phone bridge / reschedule window).

# '''Capture decisions & assign owners (2 min):''' Update the Meeting Charter (see template) on the NETwiki; confirm owners and due dates.

</div>

There are a lot of facilitation notes here, so please click ''[Expand]'' to access them (over to the right).

'''Debrief Questions'''

* What meeting barriers kept people away last year? How did we address them today?

* Which logistics changes are most likely to '''increase attendance''' or '''reduce burnout'''?

* Do our virtual/hybrid choices genuinely include remote members (or just tick the box)?

* What will we try for '''two meetings''' and then revisit?

'''Module Outputs'''

~~== Developmental Arc I~~: ~~Team Organization~~ and ~~Cohesion ==~~

'''Decisions to Capture:'''

* Cadence, day/time, duration; seasonal shifts

* Default format(s) per meeting type (in-person/virtual/hybrid)

* Venue(s) with address, access notes, and safety notes

* Platform & settings (host, recording policy, waiting room)

* Rotating role roster for next 3 meetings

* Agenda template and decision rules (quorum, voting/consent)

* Communications plan (channels, reminders, sign-in, privacy)

* Accessibility commitments (interpretation, ADA checks, plain language)

* Contingencies (weather/tech outage, backup facilitator)

* Owners and dates to implement any changes

<hr>

=== NET Response Kit Inventory ===

=== I.02 NET Response Kit Inventory ===

'''''Learning Objective'''''

'''Learning Objective'''

''Team members will understand the contents and purpose of their individual NET response kits, and identify gaps or items that need replenishing.''

'''''~~Facilitation Guide~~'''''

'''Supplemental Resources'''

:''[[Basic NET Kits]]''

:''[https://app.smartsheet.com/b/form/5b3303eec5114f6ba0d6ffa52e496933 NET/BEECN ID Card, Helmet, and/or Vest Request Form]''

'''Preparation'''

* The facilitator should check over their own bag and be prepared to talk about their go-kit first. Review the Debrief Questions and be prepared to provide your own answers to them.

* 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.

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 220:

Line 602:

Encourage volunteers to also talk about their favorite piece of gear that is not standard to the NET kit list.

'''''Debrief Questions'''''

'''Debrief Questions'''

* What items did you discover were missing or expired from your kit?

* Did you see any creative or useful additions from other team members?

* How confident do you feel that your kit would support you for 24–48 hours of response work?

* What steps can the team take to help each other fill common gaps?

~~ ~~'''~~''Supplemental Resources''~~'''

~~:''[[Basic NET Kits]]''~~

'''Module Outputs'''

None.

<hr>

=== Local Fire Station Meeting ===

=== I.03 Local Fire Station Meeting ===

'''''Learning Objective'''''

[[File:2017.09.30.MarkhamEx (2).jpg|thumb|350x350px|''Markham NET in an exercise with their local fire station in 2017.'']]

'''Learning Objective'''

''Team members will build relationships with their local firefighters, learn about station capabilities, and understand how NETs can support fire response during disasters.''

'''''~~Facilitation Guide~~'''''

'''Supplemental Resources'''

:''NETwiki article on [[Portland Fire & Rescue]]''

:''PF&R article on [https://www.portland.gov/fire/fire-stations Fire Stations, Administrative Facilities and Community Meeting Rooms]''

'''Preparation'''

With exceptions, PBEM does not recommend NETs "cold call" their local fire station. Instead, allow PBEM to be the go-between for the first meeting. The NET Team Leader should contact their PBEM District Liaison ({{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}}) to help them schedule a day and time with the NET's nearest fire station.

Do not enter into a meeting with PF&R holding specific expectations of the relationship between your team and your nearest fire station. Some fire stations have more bandwidth than others to engage with local NETs. While NET generally has a positive reputation, firefighter and officer perceptions of volunteers may also vary depending on past experiences they have had with community members (or if they've had little experience at all). Building trust and familiarity with PF&R staff takes place over time, not in a single meeting.

~~The NET Team Leader should first contact their PBEM District Liaison ({{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}}) to help them schedule a day and time with the NET~~'~~s nearest fire station.~~

'''Facilitation'''

Begin the activity with introductions, briefly explaining the NET program and your team’s role in community preparedness. Encourage firefighters to share about their daily work, the equipment housed at the station, and their priorities during major incidents, such as an earthquake. During the tour, prompt your team to observe and ask questions about how the station responds to large-scale emergencies, what resources they can and cannot provide, and how volunteers like NETs might fit into the larger response picture. Keep the tone conversational and respectful of firefighters’ time—calls may interrupt, so be flexible. Close the session by thanking the firefighters, presenting them with your team contact information, and inviting them to attend or speak at a future NET meeting. Afterward, debrief with your team about what they learned and how that information might influence your local disaster planning.

'''''Debrief Questions'''''

'''Debrief Questions'''

* What surprised you about the station’s capabilities or limitations?

* How do firefighters view volunteer support during major incidents?

* Did anything you learned change how you think about your role as a NET?

* What follow-up steps could strengthen this new relationship?

'''Module Outputs'''

None.

'''''Supplemental Resources'''''

<hr>

=== I.04 Team Equipment Cache Evaluation/Checkup ===

[[File:2025.01.19.South Burlingame.Karr (1).jpg|thumb|350x350px|''South Burlingame NET volunteers inventorying their team cache.'']]

'''Learning Objective'''

''Team members will evaluate the status of their team’s equipment cache—or, if none exists, explore the benefits and considerations of establishing one.''

'''Supplemental Resources'''

:''NETwiki article on [[Team Equipment Caches]]''

:[[Media:2025.01. .Tennessee CERT Suggested CERT Trailer Contents.pdf|Tennessee CERT Suggested CERT Trailer Contents]]

:[[Media:2021.05. .TsunamiDisasterCachePlanningGuide.pdf|DOGAMI Earthquake and Tsunami Community Disaster Cache Planning Guide]]

'''Preparation'''

Review the Supplemental Resources to gets ideas about what a cache can do and the purposes it can serve.

'''Facilitation'''

Begin by framing the purpose of a team cache: it ensures essential supplies (tarps, tools, radios, medical kits, signage, etc.) are ready to go when a disaster strikes, rather than relying only on what volunteers bring individually. If your team already has a cache, arrange to meet at the cache site. Walk through the storage space together, checking for:

* Inventory completeness (do the supplies align with the team’s operational needs?)

* Condition of items (expired, broken, or weather-damaged)

* Accessibility (can the cache be reached quickly during an incident?)

* Documentation (is there an up-to-date inventory list stored in multiple places?)

If your team does not yet have a cache, facilitate a discussion instead:

* What would be the most useful items to store collectively?

* Where could a cache be located (partner organization, community center, shed, church, etc.)?

* What are the funding and management considerations (who has keys, who replenishes items, who tracks inventory)?

* Should we consider fundraising in the neighborhood for the cache?

Encourage volunteers to share creative solutions—some teams partner with local organizations that can host supplies, while others use distributed “mini-caches” at members’ homes. Wrap up by assigning follow-up roles: one or two people to update the inventory or research possible cache sites.

'''Debrief Questions'''

* If we already have a cache: what gaps or issues did we discover today?

* If we don’t: what’s the first step toward building one, and who should lead it?

* How can we make sure all team members know what’s in the cache and how to access it?

* What’s one practical action we can take before the next meeting (e.g., replace expired supplies, draft an inventory list, identify a possible host location)?

'''Module Outputs'''

~~:NETwiki article on [[Portland Fire & Rescue]]~~

If the team already has a cache, then this module should produce an updated inventory.

~~:PF&R article on [https://www~~.~~portland.gov/fire/fire-stations Fire Stations, Administrative Facilities and Community Meeting Rooms]~~

<hr>

=== NETwiki Team Page Discussion ===

=== I.05 NETwiki Team Page Discussion ===

'''''Learning Objective'''''

[[File:HAND Team Page.jpg|thumb|600x600px|''Screenshot of the [[Teams/Hosford-Abernethy|Hosford-Abernethy NET page]]. Lookin fly yo.'']]

'''Learning Objective'''

''Team members will collaboratively design and update their team’s NETwiki page to serve as a shared, accessible hub for operations, plans, and team information.''

'''~~''Preparation''~~'''

'''Supplemental Resources'''

:[[Teams|NETwiki Neighborhood Emergency Teams Directory]]

~~Encourage any team member who can to bring their own laptop so they can review the page; and~~/~~or, if possible, put the page up on a screen that everyone in the meeting can see.~~

'''Preparation'''

'''''Facilitation ~~Guide''~~'''

The facilitator should go to the Directory (in Supplemental Resources) and find their team's page. Have a look at other team pages to see how others organized theirs. Encourage any team member who can to bring their own laptop so they can review the page; and/or, if possible, put the page up on a screen that everyone in the meeting can see.

'''Facilitation'''

Begin by projecting or sharing the team’s existing NETwiki page (or a blank one if it hasn’t been created). Explain that the wiki is intended to be a “living document” where the team records important details: operations plans, meeting schedules, contact protocols, and other resources that keep everyone aligned. Emphasize that it’s not just an archive, but a tool for both preparedness and active response.

Line 272:

Line 716:

Encourage the team to treat the page as iterative: it doesn’t need to be perfect in one sitting. Reinforce that consistent use of the wiki will reduce confusion, help onboard new volunteers, and preserve institutional memory as team membership changes.

'''''Debrief Questions'''''

'''Debrief Questions'''

*What information do we want future volunteers (or responders) to easily find on our team’s page?

Line 281:

Line 725:

*How might we use this page during an actual activation or deployment?

~~ ~~'''~~''Supplemental Resources''~~'''

~~:[[Teams~~|~~Neighborhood Emergency Teams Directory ]]~~

'''Module Outputs'''

Once the Team decides who will be the page editor, email that information to {{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}} and PBEM will set up editing permissions for that individual and link them to editing training. There can be more than one editor.

<hr>

=== ~~Team Recruitment Strategy~~ ===

=== I.06 Local Business Outreach ===

'''''Learning ~~objective~~:''''' ''~~Team members~~ will ~~design~~ a ~~recruitment approach that attracts both new Active~~ NET ~~volunteers~~ and ~~Affiliated Team Volunteers~~ (~~ATVs~~), ~~building~~ a ~~sustainable pipeline of engaged responders~~.''

[[File:2020.03.26.PosterDist.PNutterfield (5).jpg|thumb|350x350px|''NET volunteer Paul Nutterfield distributing COVID information posters to businesses in 2020.'']]

'''Learning Objective'''

''Team members will engage local businesses to strengthen neighborhood resilience by sharing preparedness information, building relationships, and identifying potential resources for disaster response.''

'''Supplemental Resources'''

:Information on [[VSF 18: Business Resilience|''VSF 18: Business Resilience'']]

:[[Media:2019.12.30.OEM Business Prep Checklist.pdf|''Business Disaster Prep Checklist'']]

:''ReadyPDX.org''

'''Preparation'''

As resources allow, PBEM will print business cards for NET volunteers to hand out. If you would like to have team business cards for distribution, please email {{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}} ''at least'' two weeks before you plan to use them. Alternatively, you can request other materials to hand out to local businesses (see Supplemental Resources).

'''Facilitation'''

Open the session by noting that local businesses are not only employers and service providers, but also potential partners in resilience. Many have supplies, space, or networks that could be useful in a disaster—but they also face risks like damaged property, disrupted supply chains, or lost revenue. NET teams can play a bridging role by offering preparedness resources and inviting businesses into neighborhood-level planning.

Facilitation steps:

# '''Identify Key Businesses:''' Brainstorm which businesses are most critical in your area—grocery stores, pharmacies, hardware stores, restaurants, gas stations, culturally significant businesses, or large employers. Write them on a board or list.

# '''Define Outreach Goals:''' Clarify what your team hopes to achieve:

## Share a simple preparedness checklist for businesses.

## Build relationships so business owners know the NET exists.

## Ask about what role (if any) they could play in a disaster (e.g., offering space, supplies, refrigeration, or communication hubs).

## Encourage businesses to sign up for alerts at ReadyPDX.org.

# '''Prepare the Approach:''' Role-play or draft a short outreach script. Keep it simple: introduce your team, explain what NET does, offer a resource, and ask one or two open-ended questions (“What concerns you most about a major earthquake?” or “What would help your business reopen quickly?”).

# '''Assign Contacts:''' Divide up outreach tasks among team members. Each volunteer can take responsibility for 1–2 businesses to visit or call (visiting is recommended).

# '''Follow-Up:''' Encourage each volunteer to report back at the next team meeting about how the outreach went. Capture any promising partnerships or ideas in the Team Ops Plan.

~~'''''Preparation:''''' Review~~ the ~~NETwiki page concerning [[Affiliated Team Volunteers (ATVs)]]~~.

Stress that outreach should be respectful of business owners’ time—keep visits brief and always frame the effort as a partnership, not a request for donation or commitment.

'''''Facilitation:''''' Open the session by reminding the team that a healthy NET program relies on steady recruitment—volunteers retire, move, or get busy, so planning ahead ensures the team remains resilient. Share a few proven outreach methods, such as tabling at neighborhood events, giving short presentations at community association meetings, or partnering with local schools, faith groups, or businesses.

'''Debrief Questions'''

* Which businesses are most critical to our neighborhood’s resilience?

* What kinds of support could we realistically expect from local businesses during a disaster?

* How did the businesses we contacted respond—were they interested, cautious, overwhelmed?

* What’s one next step to keep business relationships alive (follow-up visit, joint drill, resource sharing)?

'''Module Outputs'''

If there are prospective partnerships formed with a local business, document that in the Team Operations Plan.

<hr>

=== I.07 Neighborhood Association Meeting ===

[[File:2018.05.20.MHall.MYN (3).jpg|thumb|350x350px|''Map Your Neighborhood training for Alameda in 2018.'']]

'''Learning Objective'''

''Strengthen connections between your NET and your local Neighborhood Association (NA), so both groups can support each other in preparedness, response, and recovery. Team members will learn how to effectively attend and participate in their Neighborhood Association meetings, build relationships, and integrate preparedness priorities into broader community planning.''

'''Supplemental Resources'''

:''[https://www.portland.gov/neighborhoods City of Portland Neighborhood Association Directory]''

:''[https://www.prcprojects.us/civic City of Portland/PSU Civic Life Mapping]''

:[https://app.smartsheet.com/b/form/195273bc5460450dba9f1ae041d0c04d ''Presentation Request Form: "Emergency Preparedness for You, Your Family, and Your Community"'']

:[https://app.smartsheet.com/b/form/a11282c448eb472f86d19d5b86669b5d ''Event Materials Request Form'']

'''Preparation'''

* Find out the NA’s regular meeting schedule, agenda format, and whether they allow outside groups to present.

* Reach out to the NA Chair or Secretary to request an agenda spot or confirm time for NET introductions.

* Prepare a brief introduction: who you are, what the NET program does, and one or two examples of local resilience goals.

* Bring flyers or business cards with NET contact info, meeting times, or signup links (request no less than two weeks before the meeting; use the form in Supplemental Resources).

* If the NA would like to meet the team and also have a one hour disaster preparation presentation, use the form in Supplemental Resources to request a speaker.

'''Facilitation'''

# '''Orient your NET members (10 min, before the meeting).'''

#* Meet briefly to explain the NA’s role in Portland civic life and how NETs fit into that picture.

#* Review talking points: introduce the team, highlight preparedness efforts, and invite partnership.

#* Assign roles: one person introduces, one fields questions, others observe and take notes.

# '''Participate in the NA meeting (30–40 min).'''

#* Respect the NA’s process—observe how they conduct business, when public input is invited, and what issues are on their agenda.

#* When it’s your turn, keep your remarks short (3–5 minutes): introduce the NET, explain how you can support the neighborhood after a disaster, and invite collaboration.

#* Listen for upcoming projects (block parties, safety fairs, clean-ups) where NET participation could add value.

'''Debrief Questions'''

* What did you learn about the NA’s priorities and concerns?

* Were there community members or leaders who seemed especially interested in preparedness?

* Decide on one concrete follow-up: sending info, joining a subcommittee, or returning next month with a module (like Family Preparedness).

'''Module Outputs'''

* Update your NETwiki page with a link to the neighborhood association page.

* Consider adding a recurring task for a NET member to attend future meetings.

* Identify at least one collaborative project to propose to the NA in the next six months (such as building a community resource cache).

<hr>

=== I.08 Team Recruitment Strategy ===

'''Learning Objective'''

[[File:2015.12.24.Mark Ginsberg.jpg|thumb|350x350px|''Mark Ginsberg at a recruitment event, 2015.'']]

''Team members will design a recruitment approach that attracts both new Active NET volunteers and Affiliated Team Volunteers (ATVs), building a sustainable pipeline of engaged responders.''

'''Supplemental Resources'''

:''NETwiki article on [[Affiliated Team Volunteers (ATVs)]]''

:[https://app.smartsheet.com/b/form/a11282c448eb472f86d19d5b86669b5d ''Event Materials Request Form'']

'''Preparation'''

Review the NETwiki page concerning [[Affiliated Team Volunteers (ATVs)]].

'''Facilitation'''

Open the session by reminding the team that a healthy NET program relies on steady recruitment—volunteers retire, move, or get busy, so planning ahead ensures the team remains resilient. Share a few proven outreach methods, such as tabling at neighborhood events, giving short presentations at community association meetings, or partnering with local schools, faith groups, or businesses.

Start the discussion by explaining that recruitment isn’t one-size-fits-all: some community members are ready to commit to full NET training, while others prefer a lighter, support-oriented role as ATVs. Both groups strengthen the team—Active NETs provide certified disaster response capability, and ATVs expand reach, offer surge capacity, and often become future Active NETs.

Line 309:

Line 864:

Once ideas are collected, guide the team to choose one concrete action for each category (NET + ATV) to carry forward this quarter. Assign point people and timelines. Remind the team that recruitment should reflect the diversity of the community and that ATVs can help keep people engaged while waiting for a Basic NET training seat.

'''Debrief Questions:'''

In the conversation, be sure to offer time to diversity and inclusion considerations (e.g., outreach beyond usual circles, language/translation needs, engaging underrepresented groups).

'''Debrief Questions'''

* Which audiences are we currently reaching well, and which are we overlooking?

Line 315:

Line 872:

* What’s one concrete step we can take this quarter to bring in at least one new Active NET and one new ATV?

* How can we track and celebrate new recruits so they stay motivated?

~~ ~~

~~<hr>~~

~~=== Team Equipment Cache Evaluation/Checkup ===~~

~~'''''Learning objective:''''' ''Team members will evaluate the status of their team’s equipment cache—or, if none exists, explore the benefits and considerations of establishing one.''~~

'''~~''Preparation:''~~'''

'''Module Outputs'''

~~'''''Facilitation:''''' Begin by framing the purpose of a team cache: it ensures essential supplies (tarps, tools, radios, medical kits, signage, etc~~.) are ready to go when a disaster strikes, rather than relying only on what volunteers bring individually. If your team already has a cache, arrange to meet at the cache site. Walk through the storage space together, checking for:

None.

* Inventory completeness (do the supplies align with the team’s operational needs?)

* Condition of items (expired, broken, or weather-damaged)

<hr>

* Accessibility (can the cache be reached quickly during an incident?)

* Documentation (is there an up-to-date inventory list stored in multiple places?)

~~If your team does not yet have~~ a ~~cache~~, ~~facilitate~~ a ~~discussion instead:~~

=== 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.''

* What would be the most useful items to store collectively?

'''Supplemental Resources'''

* Where could a cache be located (partner organization, community center, shed, church, etc.)?

* What are the funding and management considerations (who has keys, who replenishes items, who tracks inventory)?

~~Encourage volunteers to share creative solutions—some teams partner with local organizations that can host supplies, while others use distributed “mini-caches” at members’ homes~~. ~~Wrap up by assigning follow-up roles~~: ~~one or two people to update the inventory or research possible cache sites~~.

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

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

'''Preparation'''

* If we already have a ~~cache: what gaps or issues did we discover today?~~

It's a good idea for the facilitator of the module to have this discussion with their own family prior to the NET meeting. Then, the facilitator can share how the conversation went and what gaps in preparation (if any) they discovered.

* If we don’t: what’s the ~~first step toward building one, and who should lead it?~~

* How can we make sure all team members know what’s in the ~~cache and how~~ to ~~access it?~~

* What’s one practical action we can take before the ~~next~~ meeting ~~(e.g~~., ~~replace expired supplies, draft an inventory list, identify a possible host location~~)?

~~ ~~

~~<hr>~~

~~=== Family Preparedness Discussion ===~~

'''Facilitation'''

'''''Learning objective:''' 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.''

~~'''''Facilitation:'''''~~ Start by explaining the principle: “You can’t help your neighbors until your family is safe.” NET volunteers are far more effective (and less distracted) if they know their loved ones are secure, have supplies, and understand the volunteer’s role during an emergency.

Start by explaining the principle: “You can’t help your neighbors until your family is safe.” NET volunteers are far more effective (and less distracted) if they know their loved ones are secure, have supplies, and understand the volunteer’s role during an emergency.

Guide the group through a discussion of what family preparedness means in practice:

Line 362:

Line 908:

Close by reminding the team that family preparedness is not “one and done.” Suggest revisiting this topic annually, and encourage each member to take one concrete action (buying a backup water filter, updating a contact card, having a family meeting) before the next NET gathering.

'''Debrief Questions:'''

'''Debrief Questions'''

* What are the most important things your family would need to know or do if you were deployed?

Line 368:

Line 914:

* How can the team support each other in strengthening family preparedness (sharing checklists, bulk-buying supplies, buddy systems)?

* What’s one action you can commit to this month to improve your family’s readiness?

'''Module Outputs'''

None.

<hr>

~~=== 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.''

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

=== 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.''

'''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 386:

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'''

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

'''Supplemental Resources'''

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

'''Preparation'''

None.

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

'''Facilitation'''

~~'''''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.

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.

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:

Line 422:

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 432:

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 441:

Line 1,022:

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

'''Module Outputs'''

None.

<hr>

</div>

== ~~Developmental~~ Arc II: Response Operations Planning ==

== 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'''

''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.

'''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 469:

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 478:

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 566:

Line 1,163:

*Who will take responsibility for making edits and ensuring the updated version is shared?

~~ ~~

~~<hr>~~

~~=== Local Business Outreach ===~~

~~'''Learning Objective:'''~~

~~Team members will engage local businesses to strengthen neighborhood resilience by sharing preparedness information, building relationships, and identifying potential resources for disaster response.~~

~~'''Facilitation:'''~~

Open the session by noting that local businesses are not only employers and service providers, but also potential partners in resilience. Many have supplies, space, or networks that could be useful in a disaster—but they also face risks like damaged property, disrupted supply chains, or lost revenue. NET teams can play a bridging role by offering preparedness resources and inviting businesses into neighborhood-level planning.

~~Facilitation steps:~~

# '''Identify Key Businesses:''' Brainstorm which businesses are most critical in your area—grocery stores, pharmacies, hardware stores, restaurants, gas stations, culturally significant businesses, or large employers. Write them on a board or list.

~~# '''Define Outreach Goals:''' Clarify what your team hopes to achieve:~~

~~# Share a simple preparedness checklist for businesses.~~

~~# Build relationships so business owners know the NET exists.~~

~~# Ask about what role (if any) they could play in a disaster (e.g., offering space, supplies, refrigeration, or communication hubs).~~

# '''Prepare the Approach:''' Role-play or draft a short outreach script. Keep it simple: introduce your team, explain what NET does, offer a resource, and ask one or two open-ended questions (“What concerns you most about a major earthquake?” or “What would help your business reopen quickly?”).

~~# '''Assign Contacts:''' Divide up outreach tasks among team members. Each volunteer can take responsibility for 1–2 businesses to visit or call.~~

~~# '''Follow-Up:''' Encourage each volunteer to report back at the next team meeting about how the outreach went. Capture any promising partnerships or ideas in the Team Ops Plan.~~

~~Stress that outreach should be respectful of business owners’ time—keep visits brief and always frame the effort as a partnership, not a request for donation or commitment.~~

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

* Which businesses are most critical to our neighborhood’s resilience?

* What kinds of support could we realistically expect from local businesses during a disaster?

* How did the businesses we contacted respond—were they interested, cautious, overwhelmed?

* What’s one next step to keep business relationships alive (follow-up visit, joint drill, resource sharing)?

<hr>

Line 757:

Line 1,322:

<hr>

</div>

== ~~Developmental~~ Arc III: Exercises and Tabletops ==

== Development Arc III: Exercises and Tabletops ==

Line 764:

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 773:

Line 1,348:

</div>

== ~~Developmental~~ Arc IV: Communications ==

== Development Arc IV: Communications ==

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

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

'''Learning Objective:'''

Line 934:

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 2 – Call-Up Basics (Keep It Simple):'''

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

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

Reinforce:

* Use tactical identifiers, not names

* Pause briefly before speaking

* Speak clearly, not loudly

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

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

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

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"''

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

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

Examples:

* “J as in Jelly”

* “B as in Boy”

* “M as in Mountain”

Encourage improvisation — clarity matters more than correctness.

Practice:

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

* Listener repeats back what they heard

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

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

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

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

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

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

* 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.~~

* “Correction…”

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

* “Say again from…”

* Repeating critical info twice (addresses, numbers)

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

Practice:

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

* Intentionally introduce a garbled message

* Ask the listener to request a fill

* Practice clean corrections without frustration

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

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

* '''“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~~:~~'''~~

Review best practices:

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

* Speak numbers slowly

* Group long numbers

* Repeat addresses if important

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

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

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

Practice with:

~~Pair up participants with radios.~~

* Addresses

* Block numbers

* Unit counts

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

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

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

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

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

* Requesting supplies

* Reporting damage

* Checking in on status

Focus coaching on:

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

* Pacing

* Phonetics

* Listener confirmation

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.~~

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:'''

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

* What made messages easiest to understand?

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

* When did pacing matter most?

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

* What helped you as a listener?

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

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

</~~div~~>

'''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) ==

===== Q: Can ATVs participate in these modules with NET volunteers? =====

''A: Absolutely! PBEM just recommends using sound judgement, as always, when engaged in training that introduces even a little risk (e.g. survivor carries).''

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 many Team Leaders have requested guidance on the "why" of meeting. 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 is to structure a team's movement from a baseline of organization to higher level disaster response skills and capacity. '''Arcs give TLs a roadmap rather than running meetings by "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__
 == Team Development Arc Leadership Approach ==
-A NET Team Leader is responsible for developing their team. PBEM recommends NET Team Leaders approach the task with the following in mind:
-* Use team meetings to develop the team (not necessarily individual NETs)
+===== What is a Team Development Arc and how does a Team Leader use them? =====
-* Think of your operations plan
+A single "Arc" is a set of individual meeting modules collected around a theme. There are five themes (each theme being an Arc):
-* '''Begin with the end in mind:''' TLs should visualize what a capable NET team for their neighborhood looks like. For example, by the end of the arc, the team...
-** Can set up a command post quickly and assign roles.
+* '''I.) Team Organization and Cohesion:''' The modules in this arc are designed to develop the team ''as a team'' and to plug the team more into the immediate community they serve''.'' These modules help the NET expand their presence into the neighborhood while also reinforcing the social fabric of the team itself.
-** Knows local hazards and prospective resources.
+* '''II.) Response Operations Planning:''' These modules are related to development and maintenance of a Team's Operations Plan.
-** Can deploy BEECN, DAMM, or other comms with little prompting.
+* '''III.) Exercises and Tabletops:''' Exercises and tabletops serve to build confidence and teamwork, reveal gaps in planning, and improve response capacity.
-** Has regularly practiced light search and rescue and other basic skillsets.
+* '''IV.) Communications:''' Modules for developing best practices around post-disaster communications.
-** Has team cohesion and a predictable meeting rhythm.
+* '''V.) Basic Response Skills:''' Review modules for any basic skillsets introduced in the Basic NET curriculum.
-* '''Delegate:''' A TL is responsible for being the "conductor" at the front of the orchestra, but the conductor does not play an instrument. After a TL develops their team's Development Arcs, they should assign responsibility for most meeting topics to different members of the team
+* '''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.
-* Braid arcs together and pursue simultaneously
+===== 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 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'''.
+===== The relationship between Arcs and team operations planning =====
+Every NET Team should have an Ops Plan that clarifies for the team, after a disaster, such things as where their staging area is, who will take what role, where the neighborhood's most significant hazards are, and so on.
+Many of the individual modules in the Arcs curriculum have a direct bearing on completion of an Ops Plan. For example, researching and exploring your neighborhood's risk profile or reaching out to local businesses. Therefore, completion of some modules will lead towards completion of an Ops Plan (or refreshing an existing Ops Plan). Teams that need more work on their Ops Plan should prioritize modules that will bring them closer to that goal. [[Team Development Arcs#Development Arc II: Response Operations Planning|Development Arc II: Response Operations Planning]] particularly includes modules related to Operations Plan development.
+===== The relationship between Arc modules, team meeting agendas, and delegation =====
+Most modules in this guide take about an hour for a team to complete. Some are shorter, and a few may run longer. That flexibility gives you options when planning agendas. A single module might fill an entire meeting, or you might use part of a module alongside other agenda items. And since modules are optional, you don’t need to use one at every meeting.
-(TBA)
+Modules are also a great tool for delegation. Team Leaders should practice handing off responsibilities, and team members should practice taking them on. This skill is vital in a real response, but it also prevents burnout by making sure the Team Leader isn’t doing all the work during “blue sky” times. PBEM encourages Team Leaders to assign modules to different team members and let them facilitate. This builds confidence, spreads knowledge, and makes meetings more engaging for everyone.
-Maintenance and recycling...
+===== Begin with the end in mind =====
+Whether a Team Leader plans the team's arc alone or in consultation with team members, PBEM encourages planners to envision how a team will change by the time they are done planning their progress. For example, by the end of a year, perhaps a team:
-Individual vs. Team development
+* ...can set up a command post quickly and assign roles
+* ...knows local hazards and prospective neighborhood resources
+* ...can deploy BEECN, DAMM, and other comms with little prompting
+* ...has regularly practiced a few basic skillsets, such as managing SUVs
+<br>
 == Team Development Arcs Table ==
@@ Line 28: / Line 96: @@
 {| class="wikitable sortable" style="width: 70%;"
 |+
-! colspan="2" |<big>Developmental 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;"|
 !style="background-color:#AC96B7;"|Activity
 !style="background-color:#AC96B7;"|Indoors/Outdoors
 |-
-|NET Response Kit Inventory
+|I.01
+|[[Team Development Arcs#I.01Team Meeting Logistics Discussion|Team Meeting Logistics Discussion]]
+|Either
+|-
+|I.02
+|[[Team Development Arcs#I.02 NET Response Kit Inventory|NET Response Kit Inventory]]
 |Either
 |-
-|Local Fire Station Meeting
+|I.03
+|[[Team Development Arcs#I.03 Local Fire Station Meeting|Local Fire Station Meeting]]
 |Indoors
 |-
-|NETwiki Team Page Discussion
+|I.04
+|[[Team Development Arcs#I.04 Team Equipment Cache Evaluation/Checkup|Team Equipment Cache Evaluation/Checkup]]
+|Depends on cache
+|-
+|I.05
+|[[Team Development Arcs#I.05 NETwiki Team Page Discussion|NETwiki Team Page Discussion]]
 |Indoors
 |-
-|Team Recruitment Strategy
+|I.06
+|[[Team Development Arcs#I.06 Local Business Outreach|Local Business Outreach]]
+|Outdoors
+|-
+|I.07
+|[[Team Development Arcs#I.07 Neighborhood Association Meeting|Neighborhood Association Meeting]]
 |Either
 |-
-|Team Equipment Cache Evaluation/Checkup
+|I.08
-|Depends on cache
+|[[Team Development Arcs#I.08 Team Recruitment Strategy|Team Recruitment Strategy]]
+|Either
 |-
-|Family Preparedness Discussion
+|I.09
+|[[Team Development Arcs#I.09 Family Preparedness Discussion|Family Preparedness Discussion]]
 |Either
 |-
-|Fundraising Review
+|I.10
+|[[Team Development Arcs#I.10 Fundraising Review|Fundraising Review]]
 |Either
 |-
-|Non-Disaster Related Social Event
+|I.11
+|[[Team Development Arcs#I.11 Non-Disaster Related Social Event|Non-Disaster Related Social Event]]
 |Either
 |}
@@ Line 62: / Line 152: @@
 {| class="wikitable sortable" style="width: 70%;"
 |+
-! colspan="2" |<big>Developmental Arc II: Response Operations Planning</big>
+!
+! colspan="2" |<big>Development Arc II: Response Operations Planning</big>
 |-
+!style="background-color:#CA9CA9;"|
 !style="background-color:#CA9CA9;"|Activity
 !style="background-color:#CA9CA9;"|Indoors/Outdoors
 |-
+|II.01
+|Operations Plan Check-In
+|Either
+|-
+|II.02
+|Neighborhood Profile Discussion
+|Either
+|-
+|II.03
+|Neighborhood Risk Assessment Discussion
+|Either
+|-
+|II.04
 |VSF Gap Analysis
 |Either
 |-
-|Neighborhood URM Inventory
+|II.05
-|Outdoors
+|Incident Objectives Discussion
-|-
-|Operations Plan Check-In
 |Either
 |-
-|Local Business Outreach
+|II.06
+|Establishing a NET Incident Command Post
 |Outdoors
 |-
+|II.07
 |Severe Cold Weather Planning
 |Either
 |-
+|II.08
 |Severe Hot Weather Planning
 |Either
 |-
-|Post-Earthquake Sanitation Planning
+|II.09
+|Deploying to Down Power Lines
 |Either
 |-
-|Post-Earthquake Decedent Care
+|II.10
-|Either
+|Clearing Storm Drains
+|Outdoors
+|-
+|II.11
+|Neighborhood URM Inventory
+|Outdoors
 |-
-|Neighborhood Profile Discussion
+|II.12
+|Post-Earthquake Sanitation Planning
 |Either
 |-
-|Neighborhood Risk Assessment Discussion
+|II.13
+|Post-Earthquake Decedent Care
 |Either
 |-
-|Incident Objectives Discussion
+|II.14
+|Response Debrief
 |Either
-|-
-|Clearing Storm Drains
-|Outdoors
 |}
 </div>
@@ Line 111: / Line 223: @@
 {| class="wikitable sortable" style="width: 70%;"
 |+
-! colspan="2" |<big>Developmental 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;"|
 !style="background-color:#94AC96;"|Activity
 !style="background-color:#94AC96;"|Indoors/Outdoors
 |-
+|III.01
+|Citywide Deployment Exercise (CDE)
+|Outdoors
+|-
+|III.02
 |Scenario Village Preparation
 |Either
 |-
-|Tabletop: Windstorm
+|III.03
+|[[Team Development Arcs#III.03 FEMA's CERT Tabletops|FEMA's CERT Tabletops]]
+* Earthquake Response
 |Indoors
 |-
+|III.04
 |Disasterville Board Game
 |Indoors
 |-
+|III.05
 |Railway Accident Tabletop
 |Indoors
 |-
+|III.06
 |Triage Boardgame
 |Indoors
-|-
-|Citywide Deployment Exercise (CDE)
-|Outdoors
 |}
 </div>
@@ Line 139: / Line 259: @@
 {| class="wikitable sortable" style="width: 70%;"
 |+
-! colspan="2" |<big>Developmental Arc IV: Communications</big>
+! colspan="3" |<big>Development Arc IV: Communications</big>
 |-
+!style="background-color:#7ABACA;"|
 !style="background-color:#7ABACA;"|Activity
 !style="background-color:#7ABACA;"|Indoors/Outdoors
 |-
-|Personal Accountability Reporting (PAR)
+|IV.01
+|[[Team Development Arcs#IV.01 Personal Accountability Reporting (PAR)|Personal Accountability Reporting (PAR)]]
 |Either
 |-
+|IV.02
 |Damage Assessment Mapping Module (DAMM) Exercise
 |Outdoors
 |-
+|IV.03
 |FRS/GMRS Radio Mapping
 |Outdoors
 |-
+|IV.04
 |BEECN Training/Review
 |Outdoors
 |-
+|IV.05
 |Radio Speaking Skills and Etiquette
 |Outdoors
@@ Line 162: / 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="2" |<big>Developmental Arc V: Basic Response Skills</big>
+! colspan="3" |<big>Development Arc V: Basic Response Skills</big>
 |-
+!style="background-color:#CAAD50;"|
 !style="background-color:#CAAD50;"|Activity
 !style="background-color:#CAAD50;"|Indoors/Outdoors
 |-
+|V.01
 |Managing SUVs Tabletop or Exercise
 |Either
 |-
+|V.02
 |Knot Techniques
 |Either
 |-
+|V.03
 |Survivor Carry Techniques
 |Either (Outdoors is best)
 |-
+|V.04
 |ICS Forms Review
 |Either
 |-
+|V.05
 |Triage Tabletop or Exercise
 |Either
 |-
+|V.06
 |Utility Shutoff Review
 |Both
 |-
+|V.07
 |Damaged Building Assessments
 |Either
 |-
+|V.08
 |Fire Extinguisher Review
 |Outdoors
 |-
+|V.09
 |Staging Area Setup
 |Outdoors
 |-
+|V.10
 |Splinting Review
 |Either
 |-
+|V.11
 |Building Markings
 |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>
+== Braiding the Arcs Together ==
+[[File:BRAID.jpg|thumb|''I needed a metaphor here, so how's this? It's got...like, survival rope. In the metaphor. The metaphor for braiding together different arcs of your team's development. Look, I don't get paid to be profound okay?'']]
+Sometimes the most effective way to plan is to bring the whole team together for a “braiding session.” In this meeting, the team looks at the five arcs side by side and decides which modules they want to tackle in the coming months. Instead of treating arcs as separate tracks, the team weaves them together into a shared path of growth.
+'''How to Facilitate a Braiding Session:'''
+# '''Lay out the options:''' Print or display all the modules (for example, as cards). Briefly remind the team what each arc is designed to build.
+# '''Set the vision:''' Ask the group to picture what they want the team to look like six months or a year from now (e.g., more confident with radios, stronger neighborhood ties, smoother command post setup).
+# '''Choose priorities:''' As a group, select a mix of modules from different arcs that best support that vision. For example, combine “NETwiki Page Discussion” (Cohesion) with “Ops Plan Check-In” (Operations) and “Radio Speaking Skills” (Communications).
+# '''Build a sequence:''' Decide on a rough order. Some modules might be prerequisites for others; others can run in parallel.
+# '''Assign facilitators:''' Encourage different volunteers to take responsibility for leading modules, so that leadership and knowledge are shared.
+# '''Capture the plan:''' Record the braided arc in your team’s Ops Plan or NETwiki page so it can guide future meetings.
+This process helps ensure the team’s development is purposeful, balanced, and shared, and not just driven by the Team Leader alone.
+<br>
+===== 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 [[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%;"
+|+
+!Meeting
+!style="width:60px"|Date
+!Module and Objective
+!style="width:110px"|Module Facilitator
+|-style="background:#e0d6e7"
+|style="text-align:center"|1
+|Jan. 15
+|'''''Module:''''' NET Response Kit Inventory '''(Arc I – Cohesion)'''
+'''''Objective:''''' Start the year by reviewing gear, sharing tips, and identifying common gaps. ''"Nell had an unusual NET response pack. There were suits of mail standing like ghosts in armour here and there, fantastic carvings brought from monkish cloisters, rusty weapons of various kinds..."''
+|Nell Trent
+|-style="background:#ebd9dd"
+|style="text-align:center"|2
+|Feb 19
+|'''''Module:''''' Neighborhood Profile Discussion '''(Arc II – Ops Planning)'''
+'''''Objective:''''' Explore hazards, assets, and demographics of the service area.
+|Joe Gargery
+|-style="background:#cde7ef"
+|style="text-align:center"|3
+|March 18
+|'''''Module:''''' Radio Speaking Skills & Etiquette '''(Arc IV – Communications)'''
+'''''Objective:''''' Practice prowords, phonetic alphabet, and clear transmissions. ''"With that Cockney accent of his, we might get better instruction if he filled his mouth full of marbles first."''
+|Sam Weller
+|-style="background:#ebd9dd"
+|style="text-align:center"|4
+|April 15
+|'''''Module:''''' Severe Hot Weather Planning '''(Arc II – Ops Planning)'''
+'''''Objective:''''' Explore ways the team can support the community during any dangerous heat events this summer. ''"If Miss Havisham is so concerned about the heat, maybe she should wear something besides that grotty wedding gown she never takes off."''
+|Aurelia Havisham
+|-style="background:#e0d6e7"
+|style="text-align:center"|5
+|May 20
+|'''''Module:''''' Family Preparedness Discussion '''(Arc I – Cohesion)'''
+'''''Objective:''''' Ensure volunteers’ households are ready so they can deploy with confidence. ''"Fagin will lead this module. Should be interesting. I just can't imagine how all those weirdly nimble orphans he's taken in will get by after an earthquake."''
+|Fagin
+|-style="background:#ebd9dd"
+|style="text-align:center"|6
+|June 17
+|'''''Module:''''' Operations Plan Check-In '''(Arc II – Ops Planning)'''
+'''''Objective:''''' Review staging area, comms, risks, and update Ops Plan as needed. ''"Should be a quick meeting. Thérèse knitted together a pretty good Ops Plan before she passed away."''
+|Joe Gargery
+|-style="background:#cde7ef"
+|style="text-align:center"|7
+|July 15
+|'''''Module:''''' FRS/GMRS Radio Mapping '''(Arc IV – Communications)'''
+'''''Objective:''''' Survey coverage in the neighborhood and identify dead zones. ''"Before he became the TL, Joe was our ARO. Makes sense for him to lead us through a radio exercise."''
+|Joe Gargery
+|-style="background:#d2ddd2"
+|style="text-align:center"|8
+|Aug. 19
+|'''''Module:''''' Triage Board Game '''(Arc III – Exercises)'''
+'''''Objective:''''' Refresh medical prioritization skills in a low-stress learning format. ''"Some of us wanted to do splinting but Sydney stepped up to facilitate saying it would be a far, far better thing to refresh our triage skills."''
+|Sydney Carton
+|-style="background:#ebd9dd"
+|style="text-align:center"|9
+|Sep. 16
+|'''''Module:''''' Local Business Outreach '''(Arc II – Ops Planning)'''
+'''''Objective:''''' Strengthen ties with key businesses for resources and resilience. ''"Nell insists that local businesses should be resilient and not gamble with their future."''
+|Nell Trent
+|-style="background:#ebe2bd"
+|style="text-align:center"|10
+|Oct. 21
+|'''''Module:''''' Utility Shutoff Review '''(Arc V – Basic Skills)'''
+'''''Objective:''''' Practice safe procedures for gas, electricity, and water shutoffs. ''"We're pretty sure Thérèse was trying to shut off the electricity when she grabbed the wrong lever by mistake."''
+|Ernest Defarge
+|-style="background:#d2ddd2"
+|style="text-align:center"|11
+|Nov. 18
+|'''''Module:''''' Scenario Village Preparation '''(Arc III – Exercises)'''
+'''''Objective:''''' Plan and organize for participation in the comprehensive CERT exercise.''"Wemmick Heights NET has the early December Scenario Village slot, so we're meeting with Alice and Jeremy to plan out our response."''
+|Joe Gargery
+|-style="background:#e0d6e7"
+|style="text-align:center"|12
+|Dec. 16
+|'''''Module:''''' Non-Disaster Social Event '''(Arc I – Cohesion)'''
+'''''Objective:''''' Non-denominational holiday potluck for team members and their families. ''"It will be at Ebenezer's mansion and he is bringing the biggest goose in all of London! NETs are asked not to bring chains to the party as they distress Ebenezer's unusually pale housemate."''
+|Ebenezer Scrooge
+|}
+Joe decided, and the other members agreed, that this plan:
+* '''Braids arcs together''' (Cohesion, Ops, Comms, Exercises, Skills).
+* Alternates between '''discussion-based, skills-based, and exercise-based modules''' to keep energy fresh.
+* Includes at least one '''community-facing activity''' (Business Outreach) and one '''social event'''.
+<br>
+=== Using the Development Arc Cards ===
+{| 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:2025.09.06.Team Development Arc Cards.pdf|Team Development Arc Cards]] (prototype)
+|2025.09.06
+|}
+For Team Leaders who want a tactile approach for planning their meeting schedule, PBEM has developed a set of cards that you can print out and pass around to team members as part of a planning discussion. It may be helpful to use the cards to arrange meeting topics on a table and move them around. '''The cards posted here are prototypes and are expected to improve in a short amount of time from their initial publication.'''
+<br>
+== 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.'']]
+'''<mark>Learning Objective</mark>'''
+''Team members will agree on clear, realistic logistics for team meetings (cadence, formats, roles, tech, accessibility, and communications) and capture them in a short “Meeting Charter” for the NETwiki/Ops Plan.''
+'''<mark>Supplemental Resources</mark>'''
+None.
+'''<mark>Preparation</mark>'''
+* Bring your calendar, current contact list, past agendas/attendance notes, and access to the team NETwiki page.
+* If you’ll discuss hybrid/virtual: confirm a video platform (e.g., Zoom/Meet), projector/speakers, and a test laptop/FRS radio if you cross-check comms.
+* The facilitation on this module is pretty detailed. Facilitator should read over it and decide what parts will work for their team and which parts may not.
+* Print or share the “Decisions to Capture” checklist (below).
+'''<mark>Facilitation</mark>'''
+<div class="mw-collapsible mw-collapsed">
+# '''Why this matters (3 min):''' Set the frame: predictable, inclusive logistics = better attendance, less burnout, faster activation when it counts.
+# '''Meeting cadence & length (10 min):''' Decide
+#* Frequency: monthly / every other month / quarterly.
+#* Day/time: pick a consistent slot; sanity-check conflicts (holidays, recurring citywide events).
+#* Duration: 60–90 minutes; cap standing meetings at 75 minutes when possible.
+#* Seasonal adjustments: lighter in July/Aug; add an extra session pre-CDE or Scenario Village.
+# '''Formats: in-person, virtual, hybrid (12 min):'''
+#* In-person: venue accessibility (ADA entrance, restrooms), transit/parking, lighting & acoustics, child-friendly options, safety after dark.
+#* Virtual: platform, host permissions, waiting room, display name standard (e.g., “Team-FirstName”), chat norms, recording policy.
+#* Hybrid: room layout (U-shape + camera sightline), one device per room unmuted (others muted to avoid echo), a Remote Buddy role (monitors chat, voices remote hands).
+#* Decide which formats match which meeting types (e.g., skills = in-person; planning = virtual; hotwash = hybrid).
+# '''Roles & delegation (8 min):''' Consider adopting rotating roles to grow capacity.
+#* Facilitator (sets pace, keeps stack)
+#* Timekeeper (prompts 5-min warnings)
+#* Scribe (captures decisions/tasks to NETwiki)
+#* Greeter (welcomes, name tents, sign-in)
+#* Tech lead / Remote Buddy (runs AV, watches chat)
+#* Safety lead (room safety check, exits, severe-weather call)
+# '''Agenda rhythm & decision rules (10 min):'''
+#* Standard agenda (60–75 min):
+#** Welcome & quick wins (5)
+#** Safety moment / weather & hazards (3)
+#** Module or skill block (30–40)
+#** Ops/Comms updates (BEECN, DAMM, trainings) (10)
+#** Tasks & assignments recap (5)
+#** Announcements + next meeting preview (2)
+#* Decision-making: consent or simple majority; define quorum (e.g., TL or designee + 5 members).
+#* Parking lot for off-topic items; schedule follow-ups.
+# '''Communications & reminders (7 min):'''
+#* Channels: email list, text group, and NETwiki.
+#* Reminder cadence:
+#** Save-the-date (monthly/quarterly)
+#** T-7 days agenda draft
+#** T-24 hours quick reminder + materials
+#* Attendance: sign-in each meeting; update contact changes immediately.
+#* Privacy: don’t post personal phone/emails publicly; keep in a restricted sheet or shared drive.
+# '''Accessibility & inclusion (5 min):'''
+#* Plain-language agendas; avoid acronyms or define them once.
+#* Request language interpretation or materials ahead of time; consider translated handouts for key items.
+#* Quiet room or camera-off norms as needed; encourage pronouncing names correctly; code of conduct reminder.
+# '''Contingencies (3 min):'''
+#* Weather/power outage: who calls it, by when, via which channel.
+#* Backup TL/facilitator: named successor for each meeting.
+#* Tech fail: pre-agreed Plan B (phone bridge / reschedule window).
+# '''Capture decisions & assign owners (2 min):''' Update the Meeting Charter (see template) on the NETwiki; confirm owners and due dates.
+</div>
+There are a lot of facilitation notes here, so please click ''[Expand]'' to access them (over to the right).
+'''<mark>Debrief Questions</mark>'''
+* What meeting barriers kept people away last year? How did we address them today?
+* Which logistics changes are most likely to '''increase attendance''' or '''reduce burnout'''?
+* Do our virtual/hybrid choices genuinely include remote members (or just tick the box)?
+* What will we try for '''two meetings''' and then revisit?
+'''<mark>Module Outputs</mark>'''
-== Developmental Arc I: Team Organization and Cohesion ==
+'''Decisions to Capture:'''
+* Cadence, day/time, duration; seasonal shifts
+* Default format(s) per meeting type (in-person/virtual/hybrid)
+* Venue(s) with address, access notes, and safety notes
+* Platform & settings (host, recording policy, waiting room)
+* Rotating role roster for next 3 meetings
+* Agenda template and decision rules (quorum, voting/consent)
+* Communications plan (channels, reminders, sign-in, privacy)
+* Accessibility commitments (interpretation, ADA checks, plain language)
+* Contingencies (weather/tech outage, backup facilitator)
+* Owners and dates to implement any changes
+<br>
+<hr>
-=== NET Response Kit Inventory ===
+=== I.02 NET Response Kit Inventory ===
-'''''Learning Objective'''''
+'''<mark>Learning Objective</mark>'''
 ''Team members will understand the contents and purpose of their individual NET response kits, and identify gaps or items that need replenishing.''
-'''''Facilitation Guide'''''
+'''<mark>Supplemental Resources</mark>'''
+:''[[Basic NET Kits]]''
+:''[https://app.smartsheet.com/b/form/5b3303eec5114f6ba0d6ffa52e496933 NET/BEECN ID Card, Helmet, and/or Vest Request Form]''
+'''<mark>Preparation</mark>'''
+* The facilitator should check over their own bag and be prepared to talk about their go-kit first. Review the Debrief Questions and be prepared to provide your own answers to them.
+* 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.
-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 220: / Line 602: @@
 Encourage volunteers to also talk about their favorite piece of gear that is not standard to the NET kit list.
-'''''Debrief Questions'''''
+'''<mark>Debrief Questions</mark>'''
 * What items did you discover were missing or expired from your kit?
 * Did you see any creative or useful additions from other team members?
 * How confident do you feel that your kit would support you for 24–48 hours of response work?
 * What steps can the team take to help each other fill common gaps?
-<br>'''''Supplemental Resources'''''
-:''[[Basic NET Kits]]''
+'''<mark>Module Outputs</mark>'''
+None.
 <br>
 <hr>
-=== Local Fire Station Meeting ===
+=== I.03 Local Fire Station Meeting ===
-'''''Learning Objective'''''
+[[File:2017.09.30.MarkhamEx (2).jpg|thumb|350x350px|''Markham NET in an exercise with their local fire station in 2017.'']]
+'''<mark>Learning Objective</mark>'''
 ''Team members will build relationships with their local firefighters, learn about station capabilities, and understand how NETs can support fire response during disasters.''
-'''''Facilitation Guide'''''
+'''<mark>Supplemental Resources</mark>'''
+:''NETwiki article on [[Portland Fire & Rescue]]''
+:''PF&R article on [https://www.portland.gov/fire/fire-stations Fire Stations, Administrative Facilities and Community Meeting Rooms]''
+'''<mark>Preparation</mark>'''
+With exceptions, PBEM does not recommend NETs "cold call" their local fire station. Instead, allow PBEM to be the go-between for the first meeting. The NET Team Leader should contact their PBEM District Liaison ({{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}}) to help them schedule a day and time with the NET's nearest fire station.
+Do not enter into a meeting with PF&R holding specific expectations of the relationship between your team and your nearest fire station. Some fire stations have more bandwidth than others to engage with local NETs. While NET generally has a positive reputation, firefighter and officer perceptions of volunteers may also vary depending on past experiences they have had with community members (or if they've had little experience at all). Building trust and familiarity with PF&R staff takes place over time, not in a single meeting.
-The NET Team Leader should first contact their PBEM District Liaison ({{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}}) to help them schedule a day and time with the NET's nearest fire station.
+'''<mark>Facilitation</mark>'''
 Begin the activity with introductions, briefly explaining the NET program and your team’s role in community preparedness. Encourage firefighters to share about their daily work, the equipment housed at the station, and their priorities during major incidents, such as an earthquake. During the tour, prompt your team to observe and ask questions about how the station responds to large-scale emergencies, what resources they can and cannot provide, and how volunteers like NETs might fit into the larger response picture. Keep the tone conversational and respectful of firefighters’ time—calls may interrupt, so be flexible. Close the session by thanking the firefighters, presenting them with your team contact information, and inviting them to attend or speak at a future NET meeting. Afterward, debrief with your team about what they learned and how that information might influence your local disaster planning.
-'''''Debrief Questions'''''
+'''<mark>Debrief Questions</mark>'''
 * What surprised you about the station’s capabilities or limitations?
 * How do firefighters view volunteer support during major incidents?
 * Did anything you learned change how you think about your role as a NET?
 * What follow-up steps could strengthen this new relationship?
+'''<mark>Module Outputs</mark>'''
+None.
 <br>
-'''''Supplemental Resources'''''
+<hr>
+=== I.04 Team Equipment Cache Evaluation/Checkup ===
+[[File:2025.01.19.South Burlingame.Karr (1).jpg|thumb|350x350px|''South Burlingame NET volunteers inventorying their team cache.'']]
+'''<mark>Learning Objective</mark>'''
+''Team members will evaluate the status of their team’s equipment cache—or, if none exists, explore the benefits and considerations of establishing one.''
+'''<mark>Supplemental Resources</mark>'''
+:''NETwiki article on [[Team Equipment Caches]]''
+:[[Media:2025.01. .Tennessee CERT Suggested CERT Trailer Contents.pdf|Tennessee CERT Suggested CERT Trailer Contents]]
+:[[Media:2021.05. .TsunamiDisasterCachePlanningGuide.pdf|DOGAMI Earthquake and Tsunami Community Disaster Cache Planning Guide]]
+'''<mark>Preparation</mark>'''
+Review the Supplemental Resources to gets ideas about what a cache can do and the purposes it can serve.
+'''<mark>Facilitation</mark>'''
+Begin by framing the purpose of a team cache: it ensures essential supplies (tarps, tools, radios, medical kits, signage, etc.) are ready to go when a disaster strikes, rather than relying only on what volunteers bring individually. If your team already has a cache, arrange to meet at the cache site. Walk through the storage space together, checking for:
+* Inventory completeness (do the supplies align with the team’s operational needs?)
+* Condition of items (expired, broken, or weather-damaged)
+* Accessibility (can the cache be reached quickly during an incident?)
+* Documentation (is there an up-to-date inventory list stored in multiple places?)
+If your team does not yet have a cache, facilitate a discussion instead:
+* What would be the most useful items to store collectively?
+* Where could a cache be located (partner organization, community center, shed, church, etc.)?
+* What are the funding and management considerations (who has keys, who replenishes items, who tracks inventory)?
+* Should we consider fundraising in the neighborhood for the cache?
+Encourage volunteers to share creative solutions—some teams partner with local organizations that can host supplies, while others use distributed “mini-caches” at members’ homes. Wrap up by assigning follow-up roles: one or two people to update the inventory or research possible cache sites.
+'''<mark>Debrief Questions</mark>'''
+* If we already have a cache: what gaps or issues did we discover today?
+* If we don’t: what’s the first step toward building one, and who should lead it?
+* How can we make sure all team members know what’s in the cache and how to access it?
+* What’s one practical action we can take before the next meeting (e.g., replace expired supplies, draft an inventory list, identify a possible host location)?
+'''<mark>Module Outputs</mark>'''
-:NETwiki article on [[Portland Fire & Rescue]]
+If the team already has a cache, then this module should produce an updated inventory.
-:PF&R article on [https://www.portland.gov/fire/fire-stations Fire Stations, Administrative Facilities and Community Meeting Rooms]
 <br>
 <hr>
-=== NETwiki Team Page Discussion ===
+=== I.05 NETwiki Team Page Discussion ===
-'''''Learning Objective'''''
+[[File:HAND Team Page.jpg|thumb|600x600px|''Screenshot of the [[Teams/Hosford-Abernethy|Hosford-Abernethy NET page]]. Lookin fly yo.'']]
+'''<mark>Learning Objective</mark>'''
 ''Team members will collaboratively design and update their team’s NETwiki page to serve as a shared, accessible hub for operations, plans, and team information.''
-'''''Preparation'''''
+'''<mark>Supplemental Resources</mark>'''
+:[[Teams|NETwiki Neighborhood Emergency Teams Directory]]
-Encourage any team member who can to bring their own laptop so they can review the page; and/or, if possible, put the page up on a screen that everyone in the meeting can see.
+'''<mark>Preparation</mark>'''
-'''''Facilitation Guide'''''
+The facilitator should go to the Directory (in Supplemental Resources) and find their team's page. Have a look at other team pages to see how others organized theirs. Encourage any team member who can to bring their own laptop so they can review the page; and/or, if possible, put the page up on a screen that everyone in the meeting can see.
+'''<mark>Facilitation</mark>'''
 Begin by projecting or sharing the team’s existing NETwiki page (or a blank one if it hasn’t been created). Explain that the wiki is intended to be a “living document” where the team records important details: operations plans, meeting schedules, contact protocols, and other resources that keep everyone aligned. Emphasize that it’s not just an archive, but a tool for both preparedness and active response.
@@ Line 272: / Line 716: @@
 Encourage the team to treat the page as iterative: it doesn’t need to be perfect in one sitting. Reinforce that consistent use of the wiki will reduce confusion, help onboard new volunteers, and preserve institutional memory as team membership changes.
-'''''Debrief Questions'''''
+'''<mark>Debrief Questions</mark>'''
 *What information do we want future volunteers (or responders) to easily find on our team’s page?
@@ Line 281: / Line 725: @@
 *How might we use this page during an actual activation or deployment?
-<br>'''''Supplemental Resources'''''
-:[[Teams|Neighborhood Emergency Teams Directory<br />]]
+'''<mark>Module Outputs</mark>'''
+Once the Team decides who will be the page editor, email that information to {{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}} and PBEM will set up editing permissions for that individual and link them to editing training. There can be more than one editor.
 <br>
 <hr>
-=== Team Recruitment Strategy ===
+=== I.06 Local Business Outreach ===
-'''''Learning objective:''''' ''Team members will design a recruitment approach that attracts both new Active NET volunteers and Affiliated Team Volunteers (ATVs), building a sustainable pipeline of engaged responders.''
+[[File:2020.03.26.PosterDist.PNutterfield (5).jpg|thumb|350x350px|''NET volunteer Paul Nutterfield distributing COVID information posters to businesses in 2020.'']]
+'''<mark>Learning Objective</mark>'''
+''Team members will engage local businesses to strengthen neighborhood resilience by sharing preparedness information, building relationships, and identifying potential resources for disaster response.''
+'''<mark>Supplemental Resources</mark>'''
+:Information on [[VSF 18: Business Resilience|''VSF 18: Business Resilience'']]
+:[[Media:2019.12.30.OEM Business Prep Checklist.pdf|''Business Disaster Prep Checklist'']]
+:''ReadyPDX.org''
+'''<mark>Preparation</mark>'''
+As resources allow, PBEM will print business cards for NET volunteers to hand out. If you would like to have team business cards for distribution, please email {{EmailLink|addr=net@portlandoregon.gov|name=net@portlandoregon.gov}} ''at least'' two weeks before you plan to use them. Alternatively, you can request other materials to hand out to local businesses (see Supplemental Resources).
+'''<mark>Facilitation</mark>'''
+Open the session by noting that local businesses are not only employers and service providers, but also potential partners in resilience. Many have supplies, space, or networks that could be useful in a disaster—but they also face risks like damaged property, disrupted supply chains, or lost revenue. NET teams can play a bridging role by offering preparedness resources and inviting businesses into neighborhood-level planning.
+Facilitation steps:
+# '''Identify Key Businesses:''' Brainstorm which businesses are most critical in your area—grocery stores, pharmacies, hardware stores, restaurants, gas stations, culturally significant businesses, or large employers. Write them on a board or list.
+# '''Define Outreach Goals:''' Clarify what your team hopes to achieve:
+## Share a simple preparedness checklist for businesses.
+## Build relationships so business owners know the NET exists.
+## Ask about what role (if any) they could play in a disaster (e.g., offering space, supplies, refrigeration, or communication hubs).
+## Encourage businesses to sign up for alerts at ReadyPDX.org.
+# '''Prepare the Approach:''' Role-play or draft a short outreach script. Keep it simple: introduce your team, explain what NET does, offer a resource, and ask one or two open-ended questions (“What concerns you most about a major earthquake?” or “What would help your business reopen quickly?”).
+# '''Assign Contacts:''' Divide up outreach tasks among team members. Each volunteer can take responsibility for 1–2 businesses to visit or call (visiting is recommended).
+# '''Follow-Up:''' Encourage each volunteer to report back at the next team meeting about how the outreach went. Capture any promising partnerships or ideas in the Team Ops Plan.
-'''''Preparation:''''' Review the NETwiki page concerning [[Affiliated Team Volunteers (ATVs)]].
+Stress that outreach should be respectful of business owners’ time—keep visits brief and always frame the effort as a partnership, not a request for donation or commitment.
-'''''Facilitation:''''' Open the session by reminding the team that a healthy NET program relies on steady recruitment—volunteers retire, move, or get busy, so planning ahead ensures the team remains resilient. Share a few proven outreach methods, such as tabling at neighborhood events, giving short presentations at community association meetings, or partnering with local schools, faith groups, or businesses.
+'''<mark>Debrief Questions</mark>'''
+* Which businesses are most critical to our neighborhood’s resilience?
+* What kinds of support could we realistically expect from local businesses during a disaster?
+* How did the businesses we contacted respond—were they interested, cautious, overwhelmed?
+* What’s one next step to keep business relationships alive (follow-up visit, joint drill, resource sharing)?
+'''<mark>Module Outputs</mark>'''
+If there are prospective partnerships formed with a local business, document that in the Team Operations Plan.
+<br>
+<hr>
+=== I.07 Neighborhood Association Meeting ===
+[[File:2018.05.20.MHall.MYN (3).jpg|thumb|350x350px|''Map Your Neighborhood training for Alameda in 2018.'']]
+'''<mark>Learning Objective</mark>'''
+''Strengthen connections between your NET and your local Neighborhood Association (NA), so both groups can support each other in preparedness, response, and recovery. Team members will learn how to effectively attend and participate in their Neighborhood Association meetings, build relationships, and integrate preparedness priorities into broader community planning.''
+'''<mark>Supplemental Resources</mark>'''
+:''[https://www.portland.gov/neighborhoods City of Portland Neighborhood Association Directory]''
+:''[https://www.prcprojects.us/civic City of Portland/PSU Civic Life Mapping]''
+:[https://app.smartsheet.com/b/form/195273bc5460450dba9f1ae041d0c04d ''Presentation Request Form: "Emergency Preparedness for You, Your Family, and Your Community"'']
+:[https://app.smartsheet.com/b/form/a11282c448eb472f86d19d5b86669b5d ''Event Materials Request Form'']
+'''<mark>Preparation</mark>'''
+* Find out the NA’s regular meeting schedule, agenda format, and whether they allow outside groups to present.
+* Reach out to the NA Chair or Secretary to request an agenda spot or confirm time for NET introductions.
+* Prepare a brief introduction: who you are, what the NET program does, and one or two examples of local resilience goals.
+* Bring flyers or business cards with NET contact info, meeting times, or signup links (request no less than two weeks before the meeting; use the form in Supplemental Resources).
+* If the NA would like to meet the team and also have a one hour disaster preparation presentation, use the form in Supplemental Resources to request a speaker.
+'''<mark>Facilitation</mark>'''
+# '''Orient your NET members (10 min, before the meeting).'''
+#* Meet briefly to explain the NA’s role in Portland civic life and how NETs fit into that picture.
+#* Review talking points: introduce the team, highlight preparedness efforts, and invite partnership.
+#* Assign roles: one person introduces, one fields questions, others observe and take notes.
+# '''Participate in the NA meeting (30–40 min).'''
+#* Respect the NA’s process—observe how they conduct business, when public input is invited, and what issues are on their agenda.
+#* When it’s your turn, keep your remarks short (3–5 minutes): introduce the NET, explain how you can support the neighborhood after a disaster, and invite collaboration.
+#* Listen for upcoming projects (block parties, safety fairs, clean-ups) where NET participation could add value.
+'''<mark>Debrief Questions</mark>'''
+* What did you learn about the NA’s priorities and concerns?
+* Were there community members or leaders who seemed especially interested in preparedness?
+* Decide on one concrete follow-up: sending info, joining a subcommittee, or returning next month with a module (like Family Preparedness).
+'''<mark>Module Outputs</mark>'''
+* Update your NETwiki page with a link to the neighborhood association page.
+* Consider adding a recurring task for a NET member to attend future meetings.
+* Identify at least one collaborative project to propose to the NA in the next six months (such as building a community resource cache).
+<br>
+<hr>
+=== I.08 Team Recruitment Strategy ===
+'''<mark>Learning Objective</mark>'''
+[[File:2015.12.24.Mark Ginsberg.jpg|thumb|350x350px|''Mark Ginsberg at a recruitment event, 2015.'']]
+''Team members will design a recruitment approach that attracts both new Active NET volunteers and Affiliated Team Volunteers (ATVs), building a sustainable pipeline of engaged responders.''
+'''<mark>Supplemental Resources</mark>'''
+:''NETwiki article on [[Affiliated Team Volunteers (ATVs)]]''
+:[https://app.smartsheet.com/b/form/a11282c448eb472f86d19d5b86669b5d ''Event Materials Request Form'']
+'''<mark>Preparation</mark>'''
+Review the NETwiki page concerning [[Affiliated Team Volunteers (ATVs)]].
+'''<mark>Facilitation</mark>'''
+Open the session by reminding the team that a healthy NET program relies on steady recruitment—volunteers retire, move, or get busy, so planning ahead ensures the team remains resilient. Share a few proven outreach methods, such as tabling at neighborhood events, giving short presentations at community association meetings, or partnering with local schools, faith groups, or businesses.
 Start the discussion by explaining that recruitment isn’t one-size-fits-all: some community members are ready to commit to full NET training, while others prefer a lighter, support-oriented role as ATVs. Both groups strengthen the team—Active NETs provide certified disaster response capability, and ATVs expand reach, offer surge capacity, and often become future Active NETs.
@@ Line 309: / Line 864: @@
 Once ideas are collected, guide the team to choose one concrete action for each category (NET + ATV) to carry forward this quarter. Assign point people and timelines. Remind the team that recruitment should reflect the diversity of the community and that ATVs can help keep people engaged while waiting for a Basic NET training seat.
-'''Debrief Questions:'''
+In the conversation, be sure to offer time to diversity and inclusion considerations (e.g., outreach beyond usual circles, language/translation needs, engaging underrepresented groups).
+'''<mark>Debrief Questions</mark>'''
 * Which audiences are we currently reaching well, and which are we overlooking?
@@ Line 315: / Line 872: @@
 * What’s one concrete step we can take this quarter to bring in at least one new Active NET and one new ATV?
 * How can we track and celebrate new recruits so they stay motivated?
-<br/>
-<hr>
-=== Team Equipment Cache Evaluation/Checkup ===
-'''''Learning objective:''''' ''Team members will evaluate the status of their team’s equipment cache—or, if none exists, explore the benefits and considerations of establishing one.''
-'''''Preparation:'''''
+'''<mark>Module Outputs</mark>'''
-'''''Facilitation:''''' Begin by framing the purpose of a team cache: it ensures essential supplies (tarps, tools, radios, medical kits, signage, etc.) are ready to go when a disaster strikes, rather than relying only on what volunteers bring individually. If your team already has a cache, arrange to meet at the cache site. Walk through the storage space together, checking for:
+None.
-* Inventory completeness (do the supplies align with the team’s operational needs?)
+<br/>
-* Condition of items (expired, broken, or weather-damaged)
+<hr>
-* Accessibility (can the cache be reached quickly during an incident?)
-* Documentation (is there an up-to-date inventory list stored in multiple places?)
-If your team does not yet have a cache, facilitate a discussion instead:
+=== 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.''
-* What would be the most useful items to store collectively?
+'''<mark>Supplemental Resources</mark>'''
-* Where could a cache be located (partner organization, community center, shed, church, etc.)?
-* What are the funding and management considerations (who has keys, who replenishes items, who tracks inventory)?
-Encourage volunteers to share creative solutions—some teams partner with local organizations that can host supplies, while others use distributed “mini-caches” at members’ homes. Wrap up by assigning follow-up roles: one or two people to update the inventory or research possible cache sites.
+:Ready.gov [https://www.ready.gov/plan Make a Plan]
-'''Debrief Questions:'''
+'''<mark>Preparation</mark>'''
-* If we already have a cache: what gaps or issues did we discover today?
+It's a good idea for the facilitator of the module to have this discussion with their own family prior to the NET meeting. Then, the facilitator can share how the conversation went and what gaps in preparation (if any) they discovered.
-* If we don’t: what’s the first step toward building one, and who should lead it?
-* How can we make sure all team members know what’s in the cache and how to access it?
-* What’s one practical action we can take before the next meeting (e.g., replace expired supplies, draft an inventory list, identify a possible host location)?
-<br/>
-<hr>
-=== Family Preparedness Discussion ===
+'''<mark>Facilitation</mark>'''
-'''''Learning objective:''' 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.''
-'''''Facilitation:''''' Start by explaining the principle: “You can’t help your neighbors until your family is safe.” NET volunteers are far more effective (and less distracted) if they know their loved ones are secure, have supplies, and understand the volunteer’s role during an emergency.
+Start by explaining the principle: “You can’t help your neighbors until your family is safe.” NET volunteers are far more effective (and less distracted) if they know their loved ones are secure, have supplies, and understand the volunteer’s role during an emergency.
 Guide the group through a discussion of what family preparedness means in practice:
@@ Line 362: / Line 908: @@
 Close by reminding the team that family preparedness is not “one and done.” Suggest revisiting this topic annually, and encourage each member to take one concrete action (buying a backup water filter, updating a contact card, having a family meeting) before the next NET gathering.
-'''Debrief Questions:'''
+'''<mark>Debrief Questions</mark>'''
 * What are the most important things your family would need to know or do if you were deployed?
@@ Line 368: / Line 914: @@
 * How can the team support each other in strengthening family preparedness (sharing checklists, bulk-buying supplies, buddy systems)?
 * What’s one action you can commit to this month to improve your family’s readiness?
+'''<mark>Module Outputs</mark>'''
+None.
 <br/>
 <hr>
-=== 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.''
-'''''Preparation:''''' Review the [https://friendsofportlandnet.org/ Friends of Portland NET] website.
+=== I.10 Fundraising Review ===
+'''<mark>Learning Objective</mark>'''
+''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 386: / 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>'''
+''Loosen up, nerds! Also, to help get to know each other better.''
+'''<mark>Supplemental Resources</mark>'''
+Oh I don't know. Probably any number of Martha Stewart books. Don't ask the introvert.
+'''<mark>Preparation</mark>'''
+None.
+[[File:2023.08.25.NET Camp.Bob Crispin (6).jpg|thumb|350x350px|''NETs know how to party.'']]
+'''<mark>Facilitation</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.
+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.
+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:
@@ Line 422: / 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 432: / 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 441: / 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>
-== Developmental Arc II: Response Operations Planning ==
+== 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>'''
+''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>'''
-'''''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.
+'''<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 469: / 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 478: / 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 566: / Line 1,163: @@
 *Who will take responsibility for making edits and ensuring the updated version is shared?
-<br>
-<hr>
-=== Local Business Outreach ===
-'''Learning Objective:'''
-Team members will engage local businesses to strengthen neighborhood resilience by sharing preparedness information, building relationships, and identifying potential resources for disaster response.
-'''Facilitation:'''
-Open the session by noting that local businesses are not only employers and service providers, but also potential partners in resilience. Many have supplies, space, or networks that could be useful in a disaster—but they also face risks like damaged property, disrupted supply chains, or lost revenue. NET teams can play a bridging role by offering preparedness resources and inviting businesses into neighborhood-level planning.
-Facilitation steps:
-# '''Identify Key Businesses:''' Brainstorm which businesses are most critical in your area—grocery stores, pharmacies, hardware stores, restaurants, gas stations, culturally significant businesses, or large employers. Write them on a board or list.
-# '''Define Outreach Goals:''' Clarify what your team hopes to achieve:
-# Share a simple preparedness checklist for businesses.
-# Build relationships so business owners know the NET exists.
-# Ask about what role (if any) they could play in a disaster (e.g., offering space, supplies, refrigeration, or communication hubs).
-# '''Prepare the Approach:''' Role-play or draft a short outreach script. Keep it simple: introduce your team, explain what NET does, offer a resource, and ask one or two open-ended questions (“What concerns you most about a major earthquake?” or “What would help your business reopen quickly?”).
-# '''Assign Contacts:''' Divide up outreach tasks among team members. Each volunteer can take responsibility for 1–2 businesses to visit or call.
-# '''Follow-Up:''' Encourage each volunteer to report back at the next team meeting about how the outreach went. Capture any promising partnerships or ideas in the Team Ops Plan.
-Stress that outreach should be respectful of business owners’ time—keep visits brief and always frame the effort as a partnership, not a request for donation or commitment.
-'''Debrief Questions:'''
-* Which businesses are most critical to our neighborhood’s resilience?
-* What kinds of support could we realistically expect from local businesses during a disaster?
-* How did the businesses we contacted respond—were they interested, cautious, overwhelmed?
-* What’s one next step to keep business relationships alive (follow-up visit, joint drill, resource sharing)?
 <br>
 <hr>
@@ Line 757: / Line 1,322: @@
 <hr>
 </div>
-== Developmental Arc III: Exercises and Tabletops ==
+== Development Arc III: Exercises and Tabletops ==
 <div class="mw-collapsible mw-collapsed">
@@ Line 764: / 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 773: / Line 1,348: @@
 </div>
-== Developmental Arc IV: Communications ==
+== Development Arc IV: Communications ==
 <div class="mw-collapsible mw-collapsed">
-=== Personal Accountability Reporting (PAR) ===
+=== IV.01 Personal Accountability Reporting (PAR) ===
 '''Learning Objective:'''
@@ Line 934: / 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 2 – Call-Up Basics (Keep It Simple):'''
+Review the basic call-up pattern: Who you are calling → who you are
+Example: ''“Staging, this is Team Alpha.”''
+Reinforce:
+* Use tactical identifiers, not names
+* Pause briefly before speaking
+* Speak clearly, not loudly
+'''Step 3 – Message Handling Skills (Core Focus):'''
+Explain that most radio problems are message problems, not equipment problems. Introduce the four core skills adapted from GRO practice.
+'''A.) Pacing (speed)'''
+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"''
+'''B.) Phonetics (Flexible, not formal)'''
+Explain: Phonetics simply means using words to make letters clear. There is no requirement to memorize a specific alphabet.
+Examples:
+* “J as in Jelly”
+* “B as in Boy”
+* “M as in Mountain”
+Encourage improvisation — clarity matters more than correctness.
+Practice:
+* Spell names, street names, or intersections using any clear phonetics
+* Listener repeats back what they heard
+'''C.) "I spell"'''
+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
-'''Step 1 – Review the Basics of Radio Etiquette:'''
+'''D.) Fills, Repeats, and Corrections'''
-* Think before you speak: Plan your message in your head before keying the mic.
+Explain that mistakes are normal. What matters is fixing them clearly. Useful techniques:
-* 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.
+* “Correction…”
-* One at a time: Pause before speaking in case someone else is transmitting.
+* “Say again from…”
+* Repeating critical info twice (addresses, numbers)
-'''Step 2 – Introduce Prowords:'''
+Practice:
-Explain that '''prowords''' are standard words that carry agreed-upon meanings in radio traffic. Review and practice common ones:
+* Intentionally introduce a garbled message
+* Ask the listener to request a fill
+* Practice clean corrections without frustration
-* '''“Over”''' – I’m done speaking and expect a reply.
+'''Step 4 – Numbers and Addresses:'''
-* '''“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:'''
+Review best practices:
-Provide the NATO phonetic alphabet (Alpha, Bravo, Charlie, etc.) and stress its importance when spelling out names, addresses, or codes over a noisy channel.
+* Speak numbers slowly
+* Group long numbers
+* Repeat addresses if important
-'''Practice exercise:''' Have each member spell their last name phonetically. Then practice with addresses, street names, or team designators.
+Example: ''"Address is one-two-three Pine Street. I repeat: one-two-three Pine Street."''
-'''Step 4 – Transmission Exercise:'''
+Practice with:
-Pair up participants with radios.
+* Addresses
+* Block numbers
+* Unit counts
-Provide each pair with a short scripted message to relay (e.g., “Requesting medical supplies at 123 Pine Street”).
+'''Step 5 – Paired Message Practice:'''
-Have them practice proper call-up, use of prowords, and phonetic spelling when needed.
+Pair participants with radios. Give each pair short, realistic messages:
-Rotate scripts so participants adapt to new scenarios.
+* Requesting supplies
+* Reporting damage
+* Checking in on status
+Focus coaching on:
-'''Step 5 – Group Drill:'''
+* Pacing
+* Phonetics
+* Listener confirmation
-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.
+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:'''
-* Which habits helped messages come through most clearly?
+* What made messages easiest to understand?
-* What mistakes did we make that caused confusion?
+* When did pacing matter most?
-* How can we reinforce consistent use of prowords and phonetic spelling in future drills?
+* What helped you as a listener?
-* What challenges might we face under stress, and how do we prepare for them?
+* What habits do we want to practice regularly as a team?
-</div>
+'''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) ==
+===== Q: Can ATVs participate in these modules with NET volunteers? =====
+''A: Absolutely! PBEM just recommends using sound judgement, as always, when engaged in training that introduces even a little risk (e.g. survivor carries).''

Anonymous

Search

Team Development Arcs: Difference between revisions

Navigation

Wiki tools

Page tools