Portland NET Wiki - User contributions [en]

Checklists for Winlink Tasks

2026-04-17T18:37:41Z

BruceSchafer: /* Steps for Sending Peer-to-Peer Messages */ Added Packet option

=== Steps for Creating an ICS 213 for Transmission ===

# Start a new by either clicking on the in the upper left below your call sign OR click on Message and then New Message.
# Click on Select a Template.
# Click on the + next to Standard Templates.
# Click on the + next to ICS USA Forms.
# Click on ICS213.txt.
# Click on Select.
# This should open your web browser and display a form.
# Fill in the form.
# Click on Submit at the bottom.
# Click on OK. (You may want to close the browser tab that you just used for the template.)
# Navigate back to Winlink.
# You should see the content of the form reformatted in the body of your message.
# Fill out the To field with the call sign of the station that should receive the message or fill in a standard email address. Separate multiple call signs or addresses with semicolons.
# Click on Post to Outbox.

=== Steps to Adding a “Favorite Template,” which creates short-cut buttons when you create a new message ===

# Start at the main Winlink window.
# Click on Message at the top of the screen.
# From the drop down menu, click on Set favorite templates...
# You should see a new window titled Set Favorite Templates
# If you remember the name of your first favorite, type it into the first Display name field under "Favorite Template 1. Otherwise, skip that field for now.
# Click on the "+" to expand the list.
# Click on Browse on the right.
# One of your favorites is likely to be the ICS 213 template. Click on "+" next to "ICS USA Forms". You should see a list of ICS forms.
# Click on "ICS213.txt"
# Click on Select at the top.
# Now that you've picked a favorite, type or edit its name as Display name Feel free to abbreviate to reduce the size of the short-cut button you're creating.
# Repeat the steps 5 through 11 above using other Favorite Template fields to add more short cuts as needed.
# Make sure you click on "Save" at the bottom when you're done.
# To verify that the button(s) have been created,
## Click on Message
## Click on New Message from the drop-down menu.
## You should see your new buttons between Select Template"and Attachments You can click on one of them if you want to use one of these templates to create a message. To use a template without a shortcut button, click on "Select Template" and navigate through the list of templates.

=== Steps to “Attach a File”, allowing you to attach files such a CSV files containing a roll-up received from teams in your NET simplex region ===
1. Open up Message, then New Message.

2. Click on the Attach: button below the Subject field

3. A popup screen will open that says “Attachments” in the header

4. Click on Add – this should bring up a list of files

5. Double click on the file you want to attach – the file name and size should now show in the popup screen

6. Click on Finished – this should return you back to the New Message screen

7. Fill in the other fields and in the message and Post to Outbox

=== Steps to “Create a Personal Folder,” allowing you to create folders for storing messages by categories. ===
Example: You may need to create one folder for Emergency messages yet to be sent, Priority messages, etc. rather than putting them all in your Outbox

1. Click on the Personal Folders heading on the left side of the Winlink home page

2. Type in the name of the Personal Folder

3. Click Update

=== Steps for Moving a Message to a Folder ===

# Select the target folder from the drop-down list to the right of “Move To:” at the top of Winlink window.
# Highlight the messages you want to move.
# Right click on the highlighted messages.
# Click on Move to folder Selected Above.

=== Steps for Editing a Message Already in Your Outbox ===

# Click on Outbox in the left column under System Folders
# Click on the message you want to edit.
# Do one of the following

* Right click in the body of the message and then click on Edit
* Click on Message in the menu at the top and click on Edit

# Make your changes.
# Click on Post to Outbox

=== Steps for Updating a Table of Available Gateways ===

# Open a Packet Winlink or VARA FM Winlink Session.
# Click on Channel Selection.
# If you have Internet access click on Update Table via Telnet
# Otherwise click on Update Table via Radio.

=== Steps for Sending Peer-to-Peer Messages ===

# Click on '''Message''' and then '''New Message.'''
# In the new windows to the right of “Send as” use the drop down menu to select ''Peer-to-Peer Message''”.
# Fill in the rest of the fields.
# Click on '''Post to Outbox.'''
# Select ''Packet PTP'' or ''Vara FM PTP'' near the upper right of the main screen.
# Click on '''Open Session'''.
# In the new window, fill in the other station’s call sign to the right of ''Direct.''
# Make sure your transceiver is set on the frequency being used by the receiving station.
# Click on '''Start.'''

=== Steps for Generating an ICS-309 ===
The following steps will create a communication log as a PDF file that can be printed or emailed.

#Click on Message then Generate ICS-309 Communications Log

# Set the filters
## Check Inbox, Sent and Read.
## Check the box next to Personal Folders if you placed any sent or received mail there, and select the appropriate folders.
## Check the boxes next to the Start Date/Time fields and the Stop Date/Time fields; then fill in the appropriate date and time values, restricting the time frame to that of the exercise or deployment.
# Select option to Combine Recipients into a Single Entry.
# Fill in Task ID, Task Name, Operational period, and Operator name, as appropriate.
# Enter your call sign as the Station ID.
# Select the folder where you want that resulting PDF to be placed by clicking on Browse to the right of Output pdf file
# Click on Generate ICS-309
# Use Windows File Explorer to navigate to the folder where you placed the ICS-309 and open it to verify it is correct in two ways: (a) Covers both the messages you sent and received and (b) does not include anything outside the time frame of the exercise or deployment.

Checklists for Winlink Tasks

2026-04-17T18:02:30Z

BruceSchafer: /* Steps for Generating an ICS-309 */ Improved formatting

=== Steps for Creating an ICS 213 for Transmission ===

# Start a new by either clicking on the in the upper left below your call sign OR click on Message and then New Message.
# Click on Select a Template.
# Click on the + next to Standard Templates.
# Click on the + next to ICS USA Forms.
# Click on ICS213.txt.
# Click on Select.
# This should open your web browser and display a form.
# Fill in the form.
# Click on Submit at the bottom.
# Click on OK. (You may want to close the browser tab that you just used for the template.)
# Navigate back to Winlink.
# You should see the content of the form reformatted in the body of your message.
# Fill out the To field with the call sign of the station that should receive the message or fill in a standard email address. Separate multiple call signs or addresses with semicolons.
# Click on Post to Outbox.

=== Steps to Adding a “Favorite Template,” which creates short-cut buttons when you create a new message ===

# Start at the main Winlink window.
# Click on Message at the top of the screen.
# From the drop down menu, click on Set favorite templates...
# You should see a new window titled Set Favorite Templates
# If you remember the name of your first favorite, type it into the first Display name field under "Favorite Template 1. Otherwise, skip that field for now.
# Click on the "+" to expand the list.
# Click on Browse on the right.
# One of your favorites is likely to be the ICS 213 template. Click on "+" next to "ICS USA Forms". You should see a list of ICS forms.
# Click on "ICS213.txt"
# Click on Select at the top.
# Now that you've picked a favorite, type or edit its name as Display name Feel free to abbreviate to reduce the size of the short-cut button you're creating.
# Repeat the steps 5 through 11 above using other Favorite Template fields to add more short cuts as needed.
# Make sure you click on "Save" at the bottom when you're done.
# To verify that the button(s) have been created,
## Click on Message
## Click on New Message from the drop-down menu.
## You should see your new buttons between Select Template"and Attachments You can click on one of them if you want to use one of these templates to create a message. To use a template without a shortcut button, click on "Select Template" and navigate through the list of templates.

=== Steps to “Attach a File”, allowing you to attach files such a CSV files containing a roll-up received from teams in your NET simplex region ===
1. Open up Message, then New Message.

2. Click on the Attach: button below the Subject field

3. A popup screen will open that says “Attachments” in the header

4. Click on Add – this should bring up a list of files

5. Double click on the file you want to attach – the file name and size should now show in the popup screen

6. Click on Finished – this should return you back to the New Message screen

7. Fill in the other fields and in the message and Post to Outbox

=== Steps to “Create a Personal Folder,” allowing you to create folders for storing messages by categories. ===
Example: You may need to create one folder for Emergency messages yet to be sent, Priority messages, etc. rather than putting them all in your Outbox

1. Click on the Personal Folders heading on the left side of the Winlink home page

2. Type in the name of the Personal Folder

3. Click Update

=== Steps for Moving a Message to a Folder ===

# Select the target folder from the drop-down list to the right of “Move To:” at the top of Winlink window.
# Highlight the messages you want to move.
# Right click on the highlighted messages.
# Click on Move to folder Selected Above.

=== Steps for Editing a Message Already in Your Outbox ===

# Click on Outbox in the left column under System Folders
# Click on the message you want to edit.
# Do one of the following

* Right click in the body of the message and then click on Edit
* Click on Message in the menu at the top and click on Edit

# Make your changes.
# Click on Post to Outbox

=== Steps for Updating a Table of Available Gateways ===

# Open a Packet Winlink or VARA FM Winlink Session.
# Click on Channel Selection.
# If you have Internet access click on Update Table via Telnet
# Otherwise click on Update Table via Radio.

=== Steps for Sending Peer-to-Peer Messages ===

# Click on '''Message''' and then '''New Message.'''
# In the new windows to the right of “Send as” use the drop down menu to select ''Peer-to-Peer Message''”.
# Fill in the rest of the fields.
# Click on '''Post to Outbox.'''
# Select ''Vara FM PTP'' near the upper right of the main screen.
# Click on '''Open Session'''.
# In the new window, fill in the other station’s call sign to the right of ''Direct.''
# Make sure your transceiver is set on the frequency being used by the receiving station.
# Click on '''Start.'''

=== Steps for Generating an ICS-309 ===
The following steps will create a communication log as a PDF file that can be printed or emailed.

#Click on Message then Generate ICS-309 Communications Log

# Set the filters
## Check Inbox, Sent and Read.
## Check the box next to Personal Folders if you placed any sent or received mail there, and select the appropriate folders.
## Check the boxes next to the Start Date/Time fields and the Stop Date/Time fields; then fill in the appropriate date and time values, restricting the time frame to that of the exercise or deployment.
# Select option to Combine Recipients into a Single Entry.
# Fill in Task ID, Task Name, Operational period, and Operator name, as appropriate.
# Enter your call sign as the Station ID.
# Select the folder where you want that resulting PDF to be placed by clicking on Browse to the right of Output pdf file
# Click on Generate ICS-309
# Use Windows File Explorer to navigate to the folder where you placed the ICS-309 and open it to verify it is correct in two ways: (a) Covers both the messages you sent and received and (b) does not include anything outside the time frame of the exercise or deployment.

Checklists for Winlink Tasks

2026-04-17T17:57:51Z

BruceSchafer: /* Steps for Sending Peer-to-Peer Messages */ Added steps

=== Steps for Creating an ICS 213 for Transmission ===

# Start a new by either clicking on the in the upper left below your call sign OR click on Message and then New Message.
# Click on Select a Template.
# Click on the + next to Standard Templates.
# Click on the + next to ICS USA Forms.
# Click on ICS213.txt.
# Click on Select.
# This should open your web browser and display a form.
# Fill in the form.
# Click on Submit at the bottom.
# Click on OK. (You may want to close the browser tab that you just used for the template.)
# Navigate back to Winlink.
# You should see the content of the form reformatted in the body of your message.
# Fill out the To field with the call sign of the station that should receive the message or fill in a standard email address. Separate multiple call signs or addresses with semicolons.
# Click on Post to Outbox.

=== Steps to Adding a “Favorite Template,” which creates short-cut buttons when you create a new message ===

# Start at the main Winlink window.
# Click on Message at the top of the screen.
# From the drop down menu, click on Set favorite templates...
# You should see a new window titled Set Favorite Templates
# If you remember the name of your first favorite, type it into the first Display name field under "Favorite Template 1. Otherwise, skip that field for now.
# Click on the "+" to expand the list.
# Click on Browse on the right.
# One of your favorites is likely to be the ICS 213 template. Click on "+" next to "ICS USA Forms". You should see a list of ICS forms.
# Click on "ICS213.txt"
# Click on Select at the top.
# Now that you've picked a favorite, type or edit its name as Display name Feel free to abbreviate to reduce the size of the short-cut button you're creating.
# Repeat the steps 5 through 11 above using other Favorite Template fields to add more short cuts as needed.
# Make sure you click on "Save" at the bottom when you're done.
# To verify that the button(s) have been created,
## Click on Message
## Click on New Message from the drop-down menu.
## You should see your new buttons between Select Template"and Attachments You can click on one of them if you want to use one of these templates to create a message. To use a template without a shortcut button, click on "Select Template" and navigate through the list of templates.

=== Steps to “Attach a File”, allowing you to attach files such a CSV files containing a roll-up received from teams in your NET simplex region ===
1. Open up Message, then New Message.

2. Click on the Attach: button below the Subject field

3. A popup screen will open that says “Attachments” in the header

4. Click on Add – this should bring up a list of files

5. Double click on the file you want to attach – the file name and size should now show in the popup screen

6. Click on Finished – this should return you back to the New Message screen

7. Fill in the other fields and in the message and Post to Outbox

=== Steps to “Create a Personal Folder,” allowing you to create folders for storing messages by categories. ===
Example: You may need to create one folder for Emergency messages yet to be sent, Priority messages, etc. rather than putting them all in your Outbox

1. Click on the Personal Folders heading on the left side of the Winlink home page

2. Type in the name of the Personal Folder

3. Click Update

=== Steps for Moving a Message to a Folder ===

# Select the target folder from the drop-down list to the right of “Move To:” at the top of Winlink window.
# Highlight the messages you want to move.
# Right click on the highlighted messages.
# Click on Move to folder Selected Above.

=== Steps for Editing a Message Already in Your Outbox ===

# Click on Outbox in the left column under System Folders
# Click on the message you want to edit.
# Do one of the following

* Right click in the body of the message and then click on Edit
* Click on Message in the menu at the top and click on Edit

# Make your changes.
# Click on Post to Outbox

=== Steps for Updating a Table of Available Gateways ===

# Open a Packet Winlink or VARA FM Winlink Session.
# Click on Channel Selection.
# If you have Internet access click on Update Table via Telnet
# Otherwise click on Update Table via Radio.

=== Steps for Sending Peer-to-Peer Messages ===

# Click on '''Message''' and then '''New Message.'''
# In the new windows to the right of “Send as” use the drop down menu to select ''Peer-to-Peer Message''”.
# Fill in the rest of the fields.
# Click on '''Post to Outbox.'''
# Select ''Vara FM PTP'' near the upper right of the main screen.
# Click on '''Open Session'''.
# In the new window, fill in the other station’s call sign to the right of ''Direct.''
# Make sure your transceiver is set on the frequency being used by the receiving station.
# Click on '''Start.'''

=== Steps for Generating an ICS-309 ===
The following steps will create a communication log as a PDF file that can be printed or emailed.

1. Click on Message then Generate ICS-309 Communications Log

2. Set the filters

a. Check Inbox, Sent and Read.

b. Check the box next to Personal Folders if you placed any sent or received mail there, and select the appropriate folders.

c. Check the boxes next to the Start Date/Time fields and the Stop Date/Time fields; then fill in the appropriate date and time values, restricting the time frame to that of the exercise or deployment.

3. Select option to Combine Recipients into a Single Entry

4. Fill in Task ID, Task Name, Operational period, and Operator name, as appropriate

5. Enter your call sign as the Station ID

6. Select the folder where you want that resulting PDF to be placed by clicking on Browse to the right of Output pdf file

7. Click on Generate ICS-309

8. Use Windows File Explorer to navigate to the folder where you placed the ICS-309 and open it to verify it is correct in two ways: (a) Covers both the messages you sent and received and (b) does not include anything outside the time frame of the exercise or deployment.

Checklists for Winlink Tasks

2026-04-17T17:56:45Z

BruceSchafer: /* Steps for Sending Peer-to-Peer Messages = */ Corrected syntax

=== Steps for Creating an ICS 213 for Transmission ===

# Start a new by either clicking on the in the upper left below your call sign OR click on Message and then New Message.
# Click on Select a Template.
# Click on the + next to Standard Templates.
# Click on the + next to ICS USA Forms.
# Click on ICS213.txt.
# Click on Select.
# This should open your web browser and display a form.
# Fill in the form.
# Click on Submit at the bottom.
# Click on OK. (You may want to close the browser tab that you just used for the template.)
# Navigate back to Winlink.
# You should see the content of the form reformatted in the body of your message.
# Fill out the To field with the call sign of the station that should receive the message or fill in a standard email address. Separate multiple call signs or addresses with semicolons.
# Click on Post to Outbox.

=== Steps to Adding a “Favorite Template,” which creates short-cut buttons when you create a new message ===

# Start at the main Winlink window.
# Click on Message at the top of the screen.
# From the drop down menu, click on Set favorite templates...
# You should see a new window titled Set Favorite Templates
# If you remember the name of your first favorite, type it into the first Display name field under "Favorite Template 1. Otherwise, skip that field for now.
# Click on the "+" to expand the list.
# Click on Browse on the right.
# One of your favorites is likely to be the ICS 213 template. Click on "+" next to "ICS USA Forms". You should see a list of ICS forms.
# Click on "ICS213.txt"
# Click on Select at the top.
# Now that you've picked a favorite, type or edit its name as Display name Feel free to abbreviate to reduce the size of the short-cut button you're creating.
# Repeat the steps 5 through 11 above using other Favorite Template fields to add more short cuts as needed.
# Make sure you click on "Save" at the bottom when you're done.
# To verify that the button(s) have been created,
## Click on Message
## Click on New Message from the drop-down menu.
## You should see your new buttons between Select Template"and Attachments You can click on one of them if you want to use one of these templates to create a message. To use a template without a shortcut button, click on "Select Template" and navigate through the list of templates.

=== Steps to “Attach a File”, allowing you to attach files such a CSV files containing a roll-up received from teams in your NET simplex region ===
1. Open up Message, then New Message.

2. Click on the Attach: button below the Subject field

3. A popup screen will open that says “Attachments” in the header

4. Click on Add – this should bring up a list of files

5. Double click on the file you want to attach – the file name and size should now show in the popup screen

6. Click on Finished – this should return you back to the New Message screen

7. Fill in the other fields and in the message and Post to Outbox

=== Steps to “Create a Personal Folder,” allowing you to create folders for storing messages by categories. ===
Example: You may need to create one folder for Emergency messages yet to be sent, Priority messages, etc. rather than putting them all in your Outbox

1. Click on the Personal Folders heading on the left side of the Winlink home page

2. Type in the name of the Personal Folder

3. Click Update

=== Steps for Moving a Message to a Folder ===

# Select the target folder from the drop-down list to the right of “Move To:” at the top of Winlink window.
# Highlight the messages you want to move.
# Right click on the highlighted messages.
# Click on Move to folder Selected Above.

=== Steps for Editing a Message Already in Your Outbox ===

# Click on Outbox in the left column under System Folders
# Click on the message you want to edit.
# Do one of the following

* Right click in the body of the message and then click on Edit
* Click on Message in the menu at the top and click on Edit

# Make your changes.
# Click on Post to Outbox

=== Steps for Updating a Table of Available Gateways ===

# Open a Packet Winlink or VARA FM Winlink Session.
# Click on Channel Selection.
# If you have Internet access click on Update Table via Telnet
# Otherwise click on Update Table via Radio.

=== Steps for Sending Peer-to-Peer Messages ===

=== Steps for Generating an ICS-309 ===
The following steps will create a communication log as a PDF file that can be printed or emailed.

1. Click on Message then Generate ICS-309 Communications Log

2. Set the filters

a. Check Inbox, Sent and Read.

b. Check the box next to Personal Folders if you placed any sent or received mail there, and select the appropriate folders.

c. Check the boxes next to the Start Date/Time fields and the Stop Date/Time fields; then fill in the appropriate date and time values, restricting the time frame to that of the exercise or deployment.

3. Select option to Combine Recipients into a Single Entry

4. Fill in Task ID, Task Name, Operational period, and Operator name, as appropriate

5. Enter your call sign as the Station ID

6. Select the folder where you want that resulting PDF to be placed by clicking on Browse to the right of Output pdf file

7. Click on Generate ICS-309

8. Use Windows File Explorer to navigate to the folder where you placed the ICS-309 and open it to verify it is correct in two ways: (a) Covers both the messages you sent and received and (b) does not include anything outside the time frame of the exercise or deployment.

Checklists for Winlink Tasks

2026-04-17T17:54:02Z

BruceSchafer: /* Steps for Sending Peer-to-Peer Messages = */ Corrected syntax

=== Steps for Creating an ICS 213 for Transmission ===

# Start a new by either clicking on the in the upper left below your call sign OR click on Message and then New Message.
# Click on Select a Template.
# Click on the + next to Standard Templates.
# Click on the + next to ICS USA Forms.
# Click on ICS213.txt.
# Click on Select.
# This should open your web browser and display a form.
# Fill in the form.
# Click on Submit at the bottom.
# Click on OK. (You may want to close the browser tab that you just used for the template.)
# Navigate back to Winlink.
# You should see the content of the form reformatted in the body of your message.
# Fill out the To field with the call sign of the station that should receive the message or fill in a standard email address. Separate multiple call signs or addresses with semicolons.
# Click on Post to Outbox.

=== Steps to Adding a “Favorite Template,” which creates short-cut buttons when you create a new message ===

# Start at the main Winlink window.
# Click on Message at the top of the screen.
# From the drop down menu, click on Set favorite templates...
# You should see a new window titled Set Favorite Templates
# If you remember the name of your first favorite, type it into the first Display name field under "Favorite Template 1. Otherwise, skip that field for now.
# Click on the "+" to expand the list.
# Click on Browse on the right.
# One of your favorites is likely to be the ICS 213 template. Click on "+" next to "ICS USA Forms". You should see a list of ICS forms.
# Click on "ICS213.txt"
# Click on Select at the top.
# Now that you've picked a favorite, type or edit its name as Display name Feel free to abbreviate to reduce the size of the short-cut button you're creating.
# Repeat the steps 5 through 11 above using other Favorite Template fields to add more short cuts as needed.
# Make sure you click on "Save" at the bottom when you're done.
# To verify that the button(s) have been created,
## Click on Message
## Click on New Message from the drop-down menu.
## You should see your new buttons between Select Template"and Attachments You can click on one of them if you want to use one of these templates to create a message. To use a template without a shortcut button, click on "Select Template" and navigate through the list of templates.

=== Steps to “Attach a File”, allowing you to attach files such a CSV files containing a roll-up received from teams in your NET simplex region ===
1. Open up Message, then New Message.

2. Click on the Attach: button below the Subject field

3. A popup screen will open that says “Attachments” in the header

4. Click on Add – this should bring up a list of files

5. Double click on the file you want to attach – the file name and size should now show in the popup screen

6. Click on Finished – this should return you back to the New Message screen

7. Fill in the other fields and in the message and Post to Outbox

=== Steps to “Create a Personal Folder,” allowing you to create folders for storing messages by categories. ===
Example: You may need to create one folder for Emergency messages yet to be sent, Priority messages, etc. rather than putting them all in your Outbox

1. Click on the Personal Folders heading on the left side of the Winlink home page

2. Type in the name of the Personal Folder

3. Click Update

=== Steps for Moving a Message to a Folder ===

# Select the target folder from the drop-down list to the right of “Move To:” at the top of Winlink window.
# Highlight the messages you want to move.
# Right click on the highlighted messages.
# Click on Move to folder Selected Above.

=== Steps for Editing a Message Already in Your Outbox ===

# Click on Outbox in the left column under System Folders
# Click on the message you want to edit.
# Do one of the following

* Right click in the body of the message and then click on Edit
* Click on Message in the menu at the top and click on Edit

# Make your changes.
# Click on Post to Outbox

=== Steps for Updating a Table of Available Gateways ===

# Open a Packet Winlink or VARA FM Winlink Session.
# Click on Channel Selection.
# If you have Internet access click on Update Table via Telnet
# Otherwise click on Update Table via Radio.

== Steps for Sending Peer-to-Peer Messages ==

=== Steps for Generating an ICS-309 ===
The following steps will create a communication log as a PDF file that can be printed or emailed.

1. Click on Message then Generate ICS-309 Communications Log

2. Set the filters

a. Check Inbox, Sent and Read.

b. Check the box next to Personal Folders if you placed any sent or received mail there, and select the appropriate folders.

c. Check the boxes next to the Start Date/Time fields and the Stop Date/Time fields; then fill in the appropriate date and time values, restricting the time frame to that of the exercise or deployment.

3. Select option to Combine Recipients into a Single Entry

4. Fill in Task ID, Task Name, Operational period, and Operator name, as appropriate

5. Enter your call sign as the Station ID

6. Select the folder where you want that resulting PDF to be placed by clicking on Browse to the right of Output pdf file

7. Click on Generate ICS-309

8. Use Windows File Explorer to navigate to the folder where you placed the ICS-309 and open it to verify it is correct in two ways: (a) Covers both the messages you sent and received and (b) does not include anything outside the time frame of the exercise or deployment.

Checklists for Winlink Tasks

2026-04-17T17:53:36Z

BruceSchafer: /* Steps for Updating a Table of Available Gateways */ Added new Peer-to-Peer sectin

=== Steps for Creating an ICS 213 for Transmission ===

# Start a new by either clicking on the in the upper left below your call sign OR click on Message and then New Message.
# Click on Select a Template.
# Click on the + next to Standard Templates.
# Click on the + next to ICS USA Forms.
# Click on ICS213.txt.
# Click on Select.
# This should open your web browser and display a form.
# Fill in the form.
# Click on Submit at the bottom.
# Click on OK. (You may want to close the browser tab that you just used for the template.)
# Navigate back to Winlink.
# You should see the content of the form reformatted in the body of your message.
# Fill out the To field with the call sign of the station that should receive the message or fill in a standard email address. Separate multiple call signs or addresses with semicolons.
# Click on Post to Outbox.

=== Steps to Adding a “Favorite Template,” which creates short-cut buttons when you create a new message ===

# Start at the main Winlink window.
# Click on Message at the top of the screen.
# From the drop down menu, click on Set favorite templates...
# You should see a new window titled Set Favorite Templates
# If you remember the name of your first favorite, type it into the first Display name field under "Favorite Template 1. Otherwise, skip that field for now.
# Click on the "+" to expand the list.
# Click on Browse on the right.
# One of your favorites is likely to be the ICS 213 template. Click on "+" next to "ICS USA Forms". You should see a list of ICS forms.
# Click on "ICS213.txt"
# Click on Select at the top.
# Now that you've picked a favorite, type or edit its name as Display name Feel free to abbreviate to reduce the size of the short-cut button you're creating.
# Repeat the steps 5 through 11 above using other Favorite Template fields to add more short cuts as needed.
# Make sure you click on "Save" at the bottom when you're done.
# To verify that the button(s) have been created,
## Click on Message
## Click on New Message from the drop-down menu.
## You should see your new buttons between Select Template"and Attachments You can click on one of them if you want to use one of these templates to create a message. To use a template without a shortcut button, click on "Select Template" and navigate through the list of templates.

=== Steps to “Attach a File”, allowing you to attach files such a CSV files containing a roll-up received from teams in your NET simplex region ===
1. Open up Message, then New Message.

2. Click on the Attach: button below the Subject field

3. A popup screen will open that says “Attachments” in the header

4. Click on Add – this should bring up a list of files

5. Double click on the file you want to attach – the file name and size should now show in the popup screen

6. Click on Finished – this should return you back to the New Message screen

7. Fill in the other fields and in the message and Post to Outbox

=== Steps to “Create a Personal Folder,” allowing you to create folders for storing messages by categories. ===
Example: You may need to create one folder for Emergency messages yet to be sent, Priority messages, etc. rather than putting them all in your Outbox

1. Click on the Personal Folders heading on the left side of the Winlink home page

2. Type in the name of the Personal Folder

3. Click Update

=== Steps for Moving a Message to a Folder ===

# Select the target folder from the drop-down list to the right of “Move To:” at the top of Winlink window.
# Highlight the messages you want to move.
# Right click on the highlighted messages.
# Click on Move to folder Selected Above.

=== Steps for Editing a Message Already in Your Outbox ===

# Click on Outbox in the left column under System Folders
# Click on the message you want to edit.
# Do one of the following

* Right click in the body of the message and then click on Edit
* Click on Message in the menu at the top and click on Edit

# Make your changes.
# Click on Post to Outbox

=== Steps for Updating a Table of Available Gateways ===

# Open a Packet Winlink or VARA FM Winlink Session.
# Click on Channel Selection.
# If you have Internet access click on Update Table via Telnet
# Otherwise click on Update Table via Radio.

== Steps for Sending Peer-to-Peer Messages ===

=== Steps for Generating an ICS-309 ===
The following steps will create a communication log as a PDF file that can be printed or emailed.

1. Click on Message then Generate ICS-309 Communications Log

2. Set the filters

a. Check Inbox, Sent and Read.

b. Check the box next to Personal Folders if you placed any sent or received mail there, and select the appropriate folders.

c. Check the boxes next to the Start Date/Time fields and the Stop Date/Time fields; then fill in the appropriate date and time values, restricting the time frame to that of the exercise or deployment.

3. Select option to Combine Recipients into a Single Entry

4. Fill in Task ID, Task Name, Operational period, and Operator name, as appropriate

5. Enter your call sign as the Station ID

6. Select the folder where you want that resulting PDF to be placed by clicking on Browse to the right of Output pdf file

7. Click on Generate ICS-309

8. Use Windows File Explorer to navigate to the folder where you placed the ICS-309 and open it to verify it is correct in two ways: (a) Covers both the messages you sent and received and (b) does not include anything outside the time frame of the exercise or deployment.

File:Team Earthquake Plan - South Burlingame.pdf

2026-04-11T03:27:36Z

BruceSchafer: BruceSchafer uploaded a new version of File:Team Earthquake Plan - South Burlingame.pdf

File:Team Earthquake Plan - South Burlingame - V2.pdf

2026-04-11T03:19:12Z

BruceSchafer: Version 2 of Earthquake Plan for South Burlingame team

== Summary ==
Version 2 of Earthquake Plan for South Burlingame team

Teams/South Burlingame

2026-04-11T03:06:00Z

BruceSchafer: Updated TL email address

{{Team
| tl = {{EmailLink|addr=SBNET.Team.Leader@gmail.com|name=Merilee Karr}}
}}
{{Neighborhood
| district = 4
}}

{{TeamPageBanner}}

= Overview =

[[File:SBNA-NET-Logo-e1478026920131.png|link=]]

'''Anyone living or working within South Burlingame is welcome to join us.'''

We are the South Burlingame Neighborhood Emergency Team (NET), and we’re a group of your neighbors trained by the Portland Bureau of Emergency Management and Portland Fire & Rescue to assist our community in the event of disaster. Our goal is to be an asset to the community during a time of crisis. We’re busy working with the South Burlingame Disaster Preparedness Team to hold block parties, developing a neighborhood / business emergency preparedness program, and creating a neighborhood emergency medical supply storage program. Your contribution to these and other projects is welcome and needed.

<gallery style="packed" heights="300px" widths="300px">
NETs-at-Neighborhood-Night-Out.jpg
South-Burlingame-boundaries.jpg
South-Burlingame-Team-Photo-at-SV-2016.jpg
</gallery>

= Photos =

* [https://goo.gl/photos/xoAbWbaMm2fXhnAZ7 Our Outreach Photos]
* [https://goo.gl/photos/eoPTzcxP3xDF9pFV8 Our Training Photos]
* [https://goo.gl/photos/85EEGdEcEteC2WWb7 Scenario Village 2016 Photos]
* [https://goo.gl/photos/NRwQqCz6oMg5Yn147 Our Staging Area Photos]

= Resources We Find Helpful =

* [http://disastersafety.org/ibhs-business-protection/ofb-ez-business-continuity/ Free Business Continuity Toolkit ]
* [http://www.newyorker.com/magazine/2015/07/20/the-really-big-one New Yorker article “The Really Big One”]
* [https://www.fema.gov/media-library-data/1e04d512b273e2133cb865833cc0e32d/FEMA_checklist_parent_508_071513.pdf FEMA’s “Are You Ready” Emergency Supply Checklist]
* [http://portlandoregon.gov/pbem/article/394125 Twin-Bucket Emergency Toilet How-To]
* [http://www.dovelewis.org/medical-services/emergency-prepardenss/ DoveLewis Animal Preparedness Guidelines]
* [http://www.preporegon.org Planning for Resilience and Emergency Preparedness (PREP)]
* [http://swni.org/sburlingame South Burlingame Neighborhood Association]
* [https://www.powells.com/book/paradise-built-in-hell-the-extraordinary-communities-that-arise-in-disaster-9780143118077/1-1 A Paradise Built in Hell: The Extraordinary Communities that Arise in Disaster]

Citywide Deployment Exercise

2026-04-10T02:23:47Z

BruceSchafer: /* Recordings of NET Training Sessions Relevant to Deployment Exercise */ Added link to recording of recent Size-Up Zoom training

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
'''May 30, 2026 from 1 pm to 4 pm'''

== Registration ==
Team registration is open and team leads have been provided a registration link. If you are a NET Team Leader and don't have the team registration information, please send an email to [mailto:Netdeploymentexercise@gmail.com netdeploymentexercise@gmail.com]

Individuals can register using [https://docs.google.com/forms/d/e/1FAIpQLSeAkkAsUkcGSjK0pwvDHywDA6IIRAMdgS9aykNKTjDalqjYZg/viewform?usp=preview this form]. If you are a member of Portland NET and don't see your team listed you can choose a team that is. Please do not attempt to register using MyImpact aka MIPS.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://vimeo.com/1181592777 Size-Up], April 8, 2026.
* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =
* [[Media:Past CDEs.pdf|List of Previous Citywide Deployment Exercises]]

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Citywide Deployment Exercise

2026-04-10T02:13:10Z

BruceSchafer: /* Next Citywide Deployment Exercise */ Added bold

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
'''May 30, 2026 from 1 pm to 4 pm'''

== Registration ==
Team registration is open and team leads have been provided a registration link. If you are a NET Team Leader and don't have the team registration information, please send an email to [mailto:Netdeploymentexercise@gmail.com netdeploymentexercise@gmail.com]

Individuals can register using [https://docs.google.com/forms/d/e/1FAIpQLSeAkkAsUkcGSjK0pwvDHywDA6IIRAMdgS9aykNKTjDalqjYZg/viewform?usp=preview this form]. If you are a member of Portland NET and don't see your team listed you can choose a team that is. Please do not attempt to register using MyImpact aka MIPS.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =
* [[Media:Past CDEs.pdf|List of Previous Citywide Deployment Exercises]]

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Citywide Deployment Exercise

2026-04-10T02:12:06Z

BruceSchafer: /* Registration */ Added link for individual registration.

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
May 30, 2026 from 1 pm to 4 pm

== Registration ==
Team registration is open and team leads have been provided a registration link. If you are a NET Team Leader and don't have the team registration information, please send an email to [mailto:Netdeploymentexercise@gmail.com netdeploymentexercise@gmail.com]

Individuals can register using [https://docs.google.com/forms/d/e/1FAIpQLSeAkkAsUkcGSjK0pwvDHywDA6IIRAMdgS9aykNKTjDalqjYZg/viewform?usp=preview this form]. If you are a member of Portland NET and don't see your team listed you can choose a team that is. Please do not attempt to register using MyImpact aka MIPS.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =
* [[Media:Past CDEs.pdf|List of Previous Citywide Deployment Exercises]]

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Winlink Procedures for Subnet Controllers

2026-03-26T04:18:57Z

BruceSchafer: /* Transmitting and Receiving Traffic Using a Gateway */ Removed obsolete language about being disconnected from Internet

=== Handling Winlink Formal Traffic from EOC ===
During the exercise you may receive formal messages from EOC in the form of Winlink messages with attached ICS 213s. Normally, Winlink will automatically open a web browser window or tab to display the message in a format that looks much like a printed ICS 213. If it doesn’t and you receive a message that has a subject starting with “213-”, you should also see a paperclip icon in the left-most field of the summary line in your Inbox. If you click on the paperclip icon, Winlink should open the message in a browser window. When you are ready to enter a reply to the message, you should use the steps described in Instructions for sending a REPLY to a ICS213. Note, however, you should not have more than one reply open at once as it's easy to confuse Winlink about which message is being replied to and it may lose a reply if you have more than one open at a time.

When you receive a formal message from EOC, please route it to the appropriate teams by contacting the corresponding AROs and reading the message to them as a NET Form 8.

=== Handling Replies to Winlink Formal Traffic ===
When an ARO informs you that they have a reply to such a message, ask for its precedence if you don’t already have it. If the precedence is equal to or greater than the traffic you are currently handling,

* Ask the ARO for the subject and time of the message to which they are replying.
* Find the original message in your log.
* Assuming you received the original message by Winlink use these substeps. Otherwise see Handling Replies to EOC Traffic Originally Received by Voice.
** Find the original message in your Winlink Inbox or your Read Items folder.
** Follow steps 2 through 5 of [[#Instructions for sending a REPLY to an ICS213|Instructions for Sending a Reply to an ICS213.]] As part of step 5, type the reply directly into the Winlink template while you have the ARO read it to you. Ask for any fills you need. Note: Winlink Express will allow you to create multiple replies to the same ICS 213 message. You will find this useful as you will probably have more than one team reply to each message from EOC. Do not, however, have more than one reply open at a time as this will confuse Winlink Express.
** Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign.

* You will notice that Winlink will automatically fill in the To field of the Winlink message (not the attached ICS 213) with the address in the From field of the original Winlink message, whether it was an FCC call sign or a Winlink tactical address.
* Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign.
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later.

When you are ready to transmit the replies in your Outbox to the EOC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].

=== Special Procedure for Handling Multiple Replies to a Winlink Message from the Emergency Operations Center ===
If you have several teams checked into your subnet and you have read their AROs a Winlink message from the EOC, you should consider whether you will are likely to receive several replies in a row to this message. If so, it may be more efficient to use one ICS 213 reply than to use several separate replies. You will find a procedure of accomplishing this below. You should only use this procedure when the following three conditions are true:

# The message from EOC did not have a precedence of Emergency.
# It is reasonable to expect that more than one ARO will have a reply ready in a short amount time. (The most likely situation when this would be true is when the AROs are in a position of answering the message themselves rather than routing the message to their Incident Team Leader. For example, a simplex request asking for the weather conditions in the neighborhoods.)
# You are not handling replies to other messages at the same time.

If any of the the above conditions is not true, use separate ICS 213 replies for each reply as described in [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]] above.

If all three conditions above are true, you may want to use the following steps to combine multiple replies into one ICS 213 reply.

*Find the original message in your Winlink Inbox or your Read Items folder.
* Follow steps 2 through 5 of [[#Instructions for sending a REPLY to an ICS213|Instructions for Sending a Reply to an ICS213.]] As part of step 5, type the name of the team replying to message followed by a colon. Then type the reply directly into the Winlink template while you have the ARO read it to you. When the ARO reads field 10 (the name and position of the person replying), add that information after the reply rather than in field 10 of your reply template.
* Ask for any fills you need.
* Repeat step 5 for reach team's reply.
* Once you have all the replies or you expect some time will elapse before you get any more replies, fill in Field 10 with your name and position and click on Submit.
* Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later.
When you are ready to transmit the replies in your Outbox to the EOC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].

=== Handling Replies to EOC Traffic Originally Received by Voice ===

# Use Winlink to create a new message. The reason we’re not asking you to put the replies from the teams in the reply section of a Winlink ICS 213 in this case is that Winlink Express doesn’t allow you to fill in the reply section unless you previously received the ICS 213 by Winlink. In this case you received the original message by voice.
# If the reply is to a message that came from the EOC, put W7ECC in the To field of the Winlink message. (You can leave the Subject field blank because the next step will fill it in automatically.)
# Then select the ICS 213 template. See Checklists for Winlink Tasks for details. '''Note:''' Avoid having more than one Winlink template open at once. If you need to open another one, be sure and Save or Submit the first one before opening another.
## In the To field of the 213, put the person that sent the original message.
## In the From field put your Simplex Region name followed by the word “Region”.
## In the Subject field of the 213 template, Put the word “Reply” followed by the subject of the original message.
## In the Message body of the 213, put the name of the team providing the reply followed by a colon and the reply. If you receive multiple replies to the same message in rapid succession, add each to the message body field of the same ICS 213, labeling each with the corresponding team name. Otherwise, submit the message and post it to your Outbox.
## When you are ready to transmit the replies in your Outbox to the EOC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].

=== Addressing Winlink Messages ===
Winlink messages can be addressed to and from FCC call signs as long as the person associated with that call sign has registered with Winlink.org. Winlink also allows the From and To fields of messages to contact tactical addresses as long as these addresses are registered in advance.

==== From Field ====
In this case, we're talking about the From field of the Winlink message, which will typically be different than the From field of of an ICS Form 213 being sent by Winlink. The From field of the Winlink message should indicate which station is sending the message by Winlink while the From field in an ICS Form 212 indicates the person who originated the Form 21e (or equivalent NET Form 8).

For NET exercises we recommend that you use tactical addresses for the From field instead instead of your FCC call sign Using a tactical addresses instead of your FCC has several advantages. In particular, they can be associated with the name of regional subnets. Using a regional tactical address as your From address will help assure that replies are directed to the subnet controller for the region on duty when replies to that message after a shift change.

When you start a new message, Winlink Express will automatically fill in your Winlink address in the From field. Notice, that next to your call sign is a down arrowhead. If you click on it, Winlink will list any tactical addresses that you have enabled. If you click on a tactical address it will replace your FCC call sign in the From field.

==== To Field ====
Messages intended for the Portland Emergency Operations Center should be addressed to W7ECC regardless of the name in the To field of the ICS 213 or or other form associated with the message. Staff at the EOC will route the message to the appropriate person based on the To field of any ICS form being used.

==== Tactical Addresses for Regional Subnet Control Operators. ====
During an exercise or deployment, there may be shift changes. If a Winlink message is addressed to the FCC call sign of a particular subnet control operator and that operator completes a shift before receiving it, the message will not be received by the next operator for the same region. By using a tactical address for a particular subnet, the messages will be available to the next controller who enables that address on their copy of Winlink Express using the password associated with the address. Here is a list of the tactical addresses for the NET simplex regions:

* Alameda North: PDXNETAN-1
* Alameda South: PDXNETAS-2
* Columbia: PDXNETCO-1
* New Northeast: PDXNETNN-1
* Outer East: PDXNETOE-1
* River North: PDXNETRN-1
* River South: PDXNETRS-1
* Southeast: PDXNETSE-1
* Westside: PDXNETWE-1

For more on Tactical Addresses including how to set them up using Winlink Express see [[Using Winlink Tactical Addresses]]

=== Preparing Your Traffic ===
If you have Emergency or Priority messages, prepare these messages by creating Winlink messages using the ICS 213 template. Alternative: Transcribe Emergency messages onto a NET Form 8 rather than entering it into a Winlink ICS 213 template.

Note: If the message you are transcribing does not have approval information, put “...” in the corresponding fields of the Winlink Form so it allows you to submit it.

After you have filled out the template, clicked on Submit and closed the browser window, you will see the content of the 213 in the body of a Winlink message. Please

* Update the From field by clicking on the the "V" shape next to your FCC call sign and selecting your region's tactical address. If no tactical address is shown, see the section above regarding enabling a tactical address.
* Set To field of the Winlink message to W7ECC.

=== Contacting EOC When You Have Emergency Traffic ===
If you have Emergency Traffic, contact Tactical Net on MC-8 informing it about these messages before transcribing Priority messages. Tactical Net may

* take your Emergency messages by voice;
* give you immediate access to the Winlink gateway to transmit your Emergency traffic; or
* tell you that Command Net will call you back on your frequency to either take your message by voice or give you time on the Winlink gateway to transmit them by Winlink.

Note: If you transmit an Emergency message by voice, you should delete it from your Winlink Outbox so you don’t accidentally send a duplicate copy. If you are asked to use a Winlink gateway to transmit your Emergency messages, you should temporarily move any Priority messages already in your Outbox to another folder and then move them back to your Outbox box when you have been given a gateway to send them.

If you have previously posted Emergency messages in your Outbox that have not yet been transmitted and you have just transcribed a new Priority message, it is best not to put it directly in your Outbox as you shouldn’t tie up the gateway transmitting messages of two or more precedence levels. Instead of posting the lower precedence message directly to your Outbox, click on Save in Drafts. You can move the messages in your Draft folder to your Outbox after you have transmitted your higher priority messages. Alternatively, you can copy messages in your Draft folder to personal folders named “Priority”, “HealthWelfare” and “Routine” and later copy messages of a particular precedence to your Outbox.

If you have Priority messages and you have already handled any Emergency messages, you should post your Priority messages to your Winlink Outbox or copy any Priority messages you have previously saved in other folders to your Outbox and then follow the instructions in ''Transmitting and Receiving Traffic Using a Gateway'' below.

If you have Health & Welfare or Routine messages you can prepare them in the same way as described above, but do not put them in your Winlink Outbox until EOC has told you that it is taking messages at those precedence. Instead select “Save in Drafts” and wait until it is time to transmit them to move them to your Outbox.

=== Preparing Traffic for Another Regional Subnet ===
If a Team ARO has a net Form 8 that is intended for another team, consider its precedence.

* If it is an Emergency Message you should transcribe it on a NET Form 8 or and ICS 213 and then contact the regional subnet for the team for which the message is intended. As you will probably not know which subnet that team has checked into you should contact Tactical Net on MC-8 and request the regional subnet associated with the team.
* If the message is a Priority message, you should transcribe the message into a Winlink ICS Form 213 as described above. Then contact Tactical Net to obtain the regional subnet associated with the destination of the message. Then use the table of Regional Tactical Addresses above to address the Winlink message.

=== Transmitting and Receiving Traffic Using a Gateway ===
After listening to the gateway frequency until it appears to no longer be busy, open and start a Packet Winlink or Vara FM Winlink session. If the exercise instructions indicate that a pair of experimental gateways have been set up at Portland Emergency Coordination Center, use one of the following gateways. Otherwise choose any gateway after asking Winlink Express to update its table of gateways. See “Steps for Updating a Table of Available Gateways” in Checklists for Winlink Tasks.
{| class="wikitable"
|Function
|Name
|Frequency (MHz)
|-
|Experimental Packet Gateway
|KI7QIB-12
|145.030
|-
|Experimental Vara Gateway
|KI7QIB-12
|145.030
|}
Try once or twice to send your message and then stop using the gateway regardless of whether you succeeded so they can be allocated to another subnet control operator.

==== What To Do If the EOC Gateway Appears To Be Unavailable. ====
If you don’t succeed in using one of the experimental gateways, try these alternatives and log which alternative you end up using:

# Contact Tactical Net and request voice transmission if you have messages with a precedence of Emergency.
# Use another gateway if you are relatively certain that the gateways can access the Internet to exchange mail with the Common Message Servers.
# If you have Internet access, use Telnet Winlink.
# Transmit by regular email. For instance, W77ECC@winlink.org. Put the following at the beginning of the subject to facilitate obtaining “white list” status for your message: //WL2K
# Hand deliver if that’s possible.

After successfully contacting a gateway, check your Inbox for new messages including messages from EOC and respond accordingly. Use the precedence of such messages to determine when you will forward them to the intended team or person. When voicing a message add “This is an Exercise.” to the beginning of the body of each message unless such words are already included. If you receive a message that it is a reply to a previous message, inform the associated ARO that it is a reply and give the subject, date and time of the original message before reading the reply so the ARO can record the reply in the reply section of the original Form 8.

=== Instructions for sending a REPLY to an ICS213 ===
1. Close the open browser Window to return to Winlink Express.

2. Back in Winlink Express, Double CLICK on the the Message line for the 213.

[[File:Selecting Message.png]]

3. This will open up the plain text version of the message.

4. Now click on the REPLY menu item.

[[File:Selecting Reply.png]]

The Reply to message template will open up in the browser.

5. Now type in the response and when done click SUBMIT.
=== Instructions for Generating an ICS 309 ===
After an exercise or at the end of a deployment shift you should generate an ICS 309 using Winlink Express. This report will list all traffic you have sent and received using Winlink Express. See [[Checklists for_Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS 309]]. Any Winlink traffic listed on the resulting ICS 309 does not need to be listed on a NET Form 8. You should still use NET Form 8 or a regular ICS 309 to list traffic you sent or received by voice, however.

Citywide Deployment Exercise

2026-02-17T03:10:41Z

BruceSchafer: /* Previous Exercises */ Added link to PDF providing list of past CDEs

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
May 30, 2026 from 1 pm to 4 pm

== Registration ==
Team registration is open and team leads have been provided a registration link. If you are a NET Team Leader and don't have the team registration information, please send an email to [mailto:Netdeploymentexercise@gmail.com netdeploymentexercise@gmail.com]

Individual registration will open in April.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =
* [[Media:Past CDEs.pdf|List of Previous Citywide Deployment Exercises]]

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

File:Past CDEs.pdf

2026-02-17T03:04:57Z

BruceSchafer: List of past Citywide Deployment Exercises

== Summary ==
List of past Citywide Deployment Exercises

Script for Checking in Stations Alphabetically by Tactical Call Signs

2026-02-03T16:59:33Z

BruceSchafer: Fixed capitalization

This is <your call sign, your first name>, subnet control operator for this <deployment or exercise>. in the <your region name(s)> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.

Our format during this deployment is the following:

* First, we’ll check in operators. This check-in process may include some relays. During this process please make notes on how well you can hear other stations.
* After the check-in process is complete, we will conduct formal communications.
* When the deployment period comes into an end, I will then ask you to check out.
* After all stations have checked out, I will close the net.
'''[Preface to checking stations in]'''

In a minute, I will start checking stations in. I will check in stations in our region by tactical call sign rather than FCC call sign. Your tactical call sign should be based on your team name followed by a digit. For example, South Heights 1. Be prepared to change the digit after your team name if someone else checks in with your first choice before you do. After I recognize you, give your FCC call sign and say the word “Out”.

As you hear other stations check in, please log their tactical call signs and how well you can hear them. If you hear a station that I don’t acknowledge, please wait until I ask for relays before telling me who I missed.

'''[Start of Check in]'''

Tonight I’m going to ask you to check in alphabetically by your ''tactical call sign''.

Let’s start with stations with tactical call signs that start with the letter Alpha through November? After I recognize you, give your FCC call sign and say the word “Out”. Please come now with your tactical call sign

[Record each station on your [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] and acknowledge each station as they check in. Expect operators to acknowledge your acknowledgement by giving their FCC call sign, which you can also log if you like.]

Are there any check-ins with tactical call signs that start with Oscar through Zulu?

[Acknowledge, as above.]

Are there any missed or late check-ins with tactical call signs that start with Alpha through Zulu?

[Acknowledge, as above.]

[To cover the possibility that you cannot hear some of the operators, ask for a relay using [[Procedure for When Net Control Operator Cannot Hear Some Operators]]]

[To cover the possibility that some operators cannot hear you use [[Procedure for When Some Operators Cannot Hear Net Control Operator]].]

Thanks everyone for checking in.

'''[End of Check in]'''

Script for Checking in a Small Number of Stations

2026-02-03T16:58:35Z

BruceSchafer: Fixed capitalization

This is <your call sign, your first name>, subnet control operator for this <deployment or exercise> in the <your region name(s)> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.

Our format during this deployment is the following:

* First, we’ll check in operators. This check-in process may include some relays. During this process please make notes on how well you can hear other stations.
* After the check-in process is complete, we will conduct formal communications.
* When the deployment period comes into an end, I will then ask you to check out.
* After all stations have checked out, I will close the net.

'''[Preface to checking stations in]'''

In a minute, I will start checking stations in. I will check in stations in our region by tactical call sign rather than FCC call sign. Your tactical call sign should be based on your team name followed by a digit. For example, South Heights 1. Be prepared to change the digit after your team name if someone else checks in with your first choice before you do. After I recognize you, give your FCC call sign and say the word “Out”.

As you hear other stations check in, please log their tactical call signs and how well you can hear them. If you hear a station that I don’t acknowledge, please wait until I ask for relays before telling me who I missed.

'''[Start of Check in]'''

Let’s start the check-ins. After I recognize you, give your FCC call sign and say the word “Out”. Please come now with your tactical call sign.

[Record each station on your [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] and acknowledge each station as they check in. Expect operators to acknowledge your acknowledgement by giving their FCC call sign, which you can also log if you like.]

If anyone heard a station that I did not acknowledge, please say the proword Relay.

[Handle any relays.]

Are there any missed or late check-ins? Please come now with your tactical call sign.

[Acknowledge, as above.]

[To cover the possibility that you cannot hear some of the operators, ask for a relay using [[Procedure for When Net Control Operator Cannot Hear Some Operators]]]

[To cover the possibility that some operators cannot hear you use [[Procedure for When Some Operators Cannot Hear Net Control Operator]].]

Thanks everyone for checking in.

'''[End of Check in]'''

Script for Checking in a Small Number of Stations

2026-02-03T16:57:38Z

BruceSchafer: Added links to relay procedures

This is <your call sign, your first name>, subnet control operator for this <deployment or exercise> in the <your region name(s)> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.

Our format during this deployment is the following:

* First, we’ll check in operators. This check-in process may include some relays. During this process please make notes on how well you can hear other stations.
* After the check-in process is complete, we will conduct formal communications.
* When the deployment period comes into an end, I will then ask you to check out.
* After all stations have checked out, I will close the net.

'''[Preface to checking stations in]'''

In a minute, I will start checking stations in. I will check in stations in our region by tactical call sign rather than FCC call sign. Your tactical call sign should be based on your team name followed by a digit. For example, South Heights 1. Be prepared to change the digit after your team name if someone else checks in with your first choice before you do. After I recognize you, give your FCC call sign and say the word “Out”.

As you hear other stations check in, please log their tactical call signs and how well you can hear them. If you hear a station that I don’t acknowledge, please wait until I ask for relays before telling me who I missed.

'''[Start of Check in]'''

Let’s start the check-ins. After I recognize you, give your FCC call sign and say the word “Out”. Please come now with your tactical call sign.

[Record each station on your [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] and acknowledge each station as they check in. Expect operators to acknowledge your acknowledgement by giving their FCC call sign, which you can also log if you like.]

If anyone heard a station that I did not acknowledge, please say the proword Relay.

[Handle any relays.]

Are there any missed or late check-ins? Please come now with your tactical call sign.

[Acknowledge, as above.]

[To cover the possibility that you cannot hear some of the operators, ask for a relay using [[Procedure for when Net Control Operator Cannot Hear Some Operators]]]

[To cover the possibility that some operators cannot hear you use [[Procedure for When Some Operators Cannot Hear Net Control Operator]].]

Thanks everyone for checking in.

'''[End of Check in]'''

Voice Procedures for Subnet Control Operators

2026-02-03T16:54:43Z

BruceSchafer: /* Calling for Relays */ Added links to pages giving detailed procedures for relaying

=== Opening a Subnet ===
At the beginning of a subnet, you should say

“This is <FCC call sign, first name> Subnet Control for today’s Citywide Deployment Exercise in the <your region name> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.”

=== Checking in Stations ===
The following are considerations for checking stations into your net. The specific language to use is provided in a subsequent section, ''Recommended Check-In Procedure'' below.

There are at least two things to consider when choosing a check-in procedure:

(1) How many operators you expect.

(2) Over what amount of time you expect the check-ins to occur.

If you are operating a subnet involving many teams during a scheduled exercise you may find that calling for all check-ins will cause a pile up and a lot of doubling. More likely, however, the check-ins will naturally spread out over quite a few minutes for two reasons (a) The operators will probably need to check into a Resource Net first and arrive on your frequency over several minutes. (b) During an actual deployment operators will become ready to check in over an extended period of time. So, unless your subnet is scheduled to open at a particular time and you expect many operators to be ready to check in at that time you probably don’t need to divide the check ins ranges of call-sign suffixes although you are free to do so if you wish. In fact, your challenge may be quite the opposite: Your operators will arrive over an extended period of time and any information you provide before checking people in will only be heard by a few operators.

==== Compiling a Roster of Teams ====
To facilitate communication between teams and between teams and the ECC you should create a table of ARO tactical call signs and the NET teams or neighborhoods that each team ARO represents. See [[Logging Procedures for Subnet Control Operators#Instructions for using Stations Participating Form|Instructions for using Stations Participating Form]].

==== Recommended Check-In Procedure for Short Simplex Exercises ====
Here are two scripts to choose from:

* [[Script for Checking in a Small Number of Stations]]
* [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]

==== Recommended Check-In Procedure for Major Exercises and Deployments ====
This example of check-in language is provided as a convenience. Feel free to modify it as circumstances dictate.

A. This is <your FCC call sign, first name> Subnet Control for the <your region name> region.

When I call for check-ins, please give your tactical call sign. When I recognize you, please give your first name, your full team name slowly and then your FCC call sign slowly using ITU phonetics. Your team name should only be the name of the team or neighborhood hosting the deployment and should include the names of other teams that may be participating at that location. Please come now. Please come now with your tactical call sign.

[Check in stations. Using the [https://docs.google.com/document/d/1M3TuoKgcmAiWSjhj5dgOAZCkpmaA2fIUSbXxQPXPYf8/edit?tab=t.0 Stations Participating Log], record each tactical call sign and then ask for the name of the team that is providing the staging area and record that name. You can also recording the operator name and FCC call sign but that is optional.]

B. [Choose a station already checked in] There may be stations that cannot hear me that would like to check in. <Tactical call sign>, please call for check-ins on my behalf, mentioning the name(s) of this region. If you receive a response, please acknowledge the information by repeating it. I will then confirm that I have heard it or ask for a “say again”. <Tactical call sign> please proceed with a call for check-ins.

C. There are probably other operators who have not arrived on this frequency yet so we’ll wait a few minutes. In the meantime, if any station has questions, please come now with your tactical call sign.

[Respond to any questions and then repeat your request for questions. If you don’t get any questions, say:]

Nothing heard. This is <FCC call sign> operating as <your tactical call sign based on your region name> standing by.

[Wait a few minutes. And then go back to Step A above]

[After you think you have checked in almost all of your stations proceed as follows]

D. This is <your FCC call sign, your first name>, subnet control for today’s Citywide Exercise in the <your region name> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.

Our purpose is to facilitate communication capabilities between individuals, teams, subnets, and the Emergency Coordination Center. Our format is the following

We will start by finishing check-ins.

After all stations in our region are checked in, I will leave this frequency briefly to provide my roster of check-ins to the Command Net. When I do so, I will be asking for volunteers to serve as temporary Subnet Control. If you are willing to do so, please consider helping out and speak up when I call for volunteers.

I will call for formal traffic on a regular basis. When I do so, please provide counts of messages you have that you have not previously given me. As you know, the precedence levels are emergency, priority, health & welfare and routine. When I call for your traffic, please give the number of messages you have at each precedence level. I will then take messages with highest precedence first.

You may also have tactical messages such as questions, requests or information. Please assign such traffic precedence as well. If you have emergency messages while I am handling priority traffic, you may interrupt me by giving the prowords “Emergency”. Likewise, use the proword Priority if you have Priority messages while I’m handling messages of lower precedence. In each case please wait to be recognized before proceeding with your message. If I don’t recognize you it may be that we doubled or there are propagation issues. If that is the case, wait for a pause and give the proword again. If you hear another station giving such a proword that I am not recognizing, please use the proword “Relay” so that I can recognize you and ask you to provide a relay.

During today’s exercise please use your tactical call sign but give your FCC call sign at the end of each communication.

If you need to leave the subnet before it ends, please check out with me first. Likewise, inform me if you need to leave the subnet temporarily.

E. Are there any other stations that would like to check in? Please give your tactical call sign. When I recognize you, please give your first name, your full team name slowly and then your FCC call sign slowly using ITU phonetics. Please come now.

[Check in stations as before]

F. [Same as Step B above]

G. I will now read the roster of stations who have checked in so far. When I read your tactical call sign, please respond by repeating that call sign two times so other stations can determine whether they can hear you. If any station hears a response that I did not acknowledge please give the proword Relay.

[Read list of tactical call signs, pausing for each station to reply with the same call sign twice. Confirm that you have heard by saying “Thank you <tactical call sign>”.]

H. [If you did not receive a response from a station that previously checked in, choose a station that did respond and ask them to repeat the tactical call sign that did not check in.]

I. I will now read the roster of stations again. This time, when I read your tactical call sign, please respond by saying “I can hear” followed by the tactical calls of the stations that you can hear fairly well including Net Control. Then end by saying “This is” followed by your own tactical call sign, your FCC call sign and the proword “Out”. I will acknowledge each response. If any station hears a response that I did not acknowledge please give the proword “Relay.”

[Read list of tactical call signs, pausing for each station to reply with the list of tactical call signs they can hear followed by their own tactical and FCC call signs. Confirm that you have heard by saying “Thank you <tactical call sign>”.

J. [If time permits you can allow stations that are checked in to ask questions. Don’t forget to return to the main sequence – Step 7 – to do things like contacting Tactical Net to report your roster.]

====== What To Do If Stations Attempt to Check-In That Are Not Part of the Exercise ======
Most amateur radio nets attempt to be very open to guests. During exercises and deployments, however, it is usually inappropriate for guests to check in. If a station attempts to check in that is not part of the exercise or deployment you should politely explain that the circumstances do not allow the extra time that would be required to communicate with guests.

====== What To Do If More Than One Operator from the Same Team Tries to Check In ======
A slightly different circumstance occurs when more than one operator from a particular team attempts to check in. If this happens you should explain that only one operator should represent a particular team at a time. You can also mention that they should use the same tactical call sign if they decide to change the operator representing their team during the exercise.

=== Calling for Relays ===
The strength of communication will vary from exercise to exercise and operator to operator based on factors like location, elevation, available transmission power and sensitivity and selectivity of receivers. Note that there are many combinations of these factors in a region including a subnet controller who may be in a different location and team AROs in varying locations depending on who is available and the nature of the exercise or deployment. This unpredictability of simplex communication means that you and the other operators must be ready to ask for and provide relays. There are at least two cases to consider -- stations you cannot hear and stations that cannot hear you.

==== [[Procedure for When Some Operators Cannot Hear Net Control Operator]] ====

==== [[Procedure for When Net Control Operator Cannot Hear Some Operators]] ====

=== Appointing a Temporary Subnet Controller ===
There are several circumstances when you may need to leave the subnet and to appoint an interim subset control. Examples of such circumstances are when you are called away by the ECC, when you need to send Winlink messages, and when you need to take a break. In these cases you should consider three criteria (a) The apparent skill level of operators checked into your subnet (b) their ability to hear and be heard by other stations in your region. The latter will be influenced by the equipment they have at their disposal and (c) their location within your region. Choose an alternate who is a good fit for the role and is willing to take it on and inform the operators of your decision. When you return, wait for a break in the communication, announce your return and resume your role as subnet control operator.

=== Transmitting a Roster to the Portland EOC ===
After completing checking stations into your subnet, you need to switch to Tactical Net on MC-8 to give them your check-in roster. You should do this even if you’re not sure that all stations in your region have checked in. Before leaving the frequency ask one of the AROs on frequency to serve as temporary subnet control. Then transition to Tactical Net and give them the tactical call signs of the AROs that checked into your subnet. Tactical Net may ask you for clarification of what teams are represented by each tactical call sign. When that information is acknowledged, return to your subnet and resume your subnet controller role.

If additional teams check into your net later, you will need to contact Tactical Net again and provide them the additional stations. Likewise if teams check out before the end of the deployment or exercise.

Here is a sample script for reporting your roster:

I now need to leave this frequency to report my roster of checked-in stations to the Tactical Net operator at the Emergency Coordination Center. I will return to this frequency in about 5 minutes.

[Transition to MC-8 to contact Tactical Net]

[If you hear activity, wait for a quiet time or for Tactical Net to ask for additional check-ins]

[You] <Give your region name as your tactical call sign.>

[Tactical Net]: <Your tactical call sign> Go ahead

[You] I have a team roster to report.

[Tactical Net]: Ready to copy.

[You] Please copy,

[You]<The tactical call sign of your first check in> representing <Team name> Break [long pause while Tactical Net records the information]

[Tactical Net]: Continue.

[You] <Second tactical call sign> representing <Team name>. Break.

[Tactical Net] Continue.

[You] <Third tactical call sign> representing <Team Name> Break

[Continue as above until the last tactical call sign. For the last one say the following instead of “Break”]

[You] End of roster. How copy?

[Tactical Net] I roger your roster.

[At this point Tactical net may have questions such as which teams are represented by which call signs if that wasn’t clear enough to them while you read your roster.]

[Tactical Net] <Your tactical call sign> You are released to return to your subnet.

[You] <your FCC call sign> as <your tactical call sign> Clear.

[Return to your subnet frequency.]

=== Handling Traffic from Emergency Operations Center to NET Teams ===
You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams in one of the following formats:

# A formal message on a NET Form 8 or ICS 213. See this sample Form 8 for an example.
## The message does not appear to need a reply.
## The message requests a reply or implies the need for one.
# A tactical message that is not conveyed via an ICS form. For example, “Incident Command has informed us that water trucks will start becoming available by this time tomorrow.”
## The message does not appear to need a reply.
## The message requests a reply or implies the need for one.

Be sure to log the voice message on your NET Form 6.

Note: If you receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

Consistent with the precedence of the message relative to other traffic you are handling and according to the format of the message you received (see above),

# Inform the AROs checked into your subnet that they should prepare to copy a formal message onto a Form 8 and proceed accordingly.
## No further action is required by you.
## Be prepared to receive a reply to the formal message from each ARO in your region after some delay at the team level. See Handling Replies to ECC Traffic Originally Received by Voice in Winlink Procedures for Subnet Control Operators. .
# Inform your AROs that they should prepare to copy a tactical message that they should pass onto their teams’ leadership and then read the message to them. You may need to clarify to the AROs that they are not required to transcribe such tactical messages on a NET Form 8 as any way of transcribing such messages is acceptable as long as they have a way of delivering the message to the appropriate team member(s).
## No further action is required by you.
## Be prepared to receive a reply to the tactical message from each ARO in your region after some delay. Each time you receive such a reply, use Winlink Express to compose a new plain text message (without using a template). Select your Winlink Tactical Address in the From field. Fill in the To field with PDXECCMSGC-1. In the Subject field, put “Reply to voice message” followed by the date and time of the original message.

=== Handling NET Form 8 Traffic from NET Teams Including Triage ===
Both formal messages and tactical messages should be triaged by precedence during exercises and deployments. Unless PBEM specifies otherwise, standard ARRL precedence levels should be used:

Ask stations in your subnet if they have formal traffic ready to transmit. (Such traffic should be on NET Form 8.) If so, ask them to provide counts of available messages not previously forwarded by the four precedence levels. Use the [[Logging Procedures for Subnet Control Operators#Instructions for using the Traffic Count Worksheet|Traffic Count Worksheet]] to keep track of the number and precedence of messages that are ready for your to handle. Take Emergency messages from all your stations before moving on to take Priority messages. Likewise, take Priority messages before Health & Welfare and take any Routine messages last and only if you have time.

If some of the traffic is addressed to someone at the Emergency Coordination Center (ECC) see [[Winlink Procedures for Subnet Controllers#Preparing Your Traffic and Notifying ECC|Preparing Your Traffic and Notifying ECC]].

Traffic from teams may include replies to messages from ECC that you delivered to them earlier. See [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].

=== Closing your Subnet and Checking Out ===
At the end of an exercise or deployment you should close your subnet. One method for doing so is to call the role of tactical call signs and expect each station to respond with <FCC call sign> operating as <tactical call sign> Clear. You should then close the net by saying “This is <FCC call sign> closing this <regional name> Region Subnet Clear at <nowiki><time> local time.”</nowiki>

You should then transition to Tactical Net and check out.

=== Transferring Control to a New Subnet Controller ===
If you transfer responsibility for your subnet to another controller without closing the net, you should say “This is <your FCC call sign> transferring control of this <region name> Region Subnet to <FCC call sign of new operator>.”

The new operator should say “This is <FCC call sign>, <First Name> taking control of this <region name> Region subnet.”

Like all other events, the change of control operator should be logged with the same information as you announced over the air.

=== Facilitating Communication Between Teams ===
Teams may need to contact other teams to share information or coordinate their activities. These contacts may be (a) tactical communication using a frequency proposed by one of the teams; (b) tactical communication using a prearranged frequency; (c) formal messages between teams in the same region using NET Form 8; or (d) formal messages between teams in different regions. During the exercise you should expect some teams to use option (a).

==== Tactical communication between teams using a frequency proposed by one of the teams. ====
The two teams usually won’t choose a frequency in advance. In this case, the team seeking to initiate the communication should find a frequency that appears to be available and ask the subnet controller for help in communicating the proposed frequency to the other team and asking if they are willing to change frequencies. The team may want to propose a UHF frequency or possibly a VHF frequency unless cell service is available. Unless additional Amateur Radio operators are available to handle the direct communication, one or both of the operators may need to temporarily check out of the subnet and then check back in when they are finished with their direct tactical communication. In this case they should keep their direct communication as short as possible so they won’t miss important communications from the ECC.

==== Tactical communication between teams using a prearranged frequency ====
Tactical communication may be somewhat easier if the teams involved have agreed to use a particular frequency for such situations. If that is the case they may proceed to attempt to establish communication using the agreed upon frequency, assuming the other team is monitoring the frequency. Otherwise one team may need to use the regional frequency to let the other team know that they want to establish direct communication. Also, if either operator is currently checked into a regional subnet, that operator should find an alternate operator to take over with subnet communications or the alternate operator may handle the inter-team communication. If the former is chosen, the operator currently checked into the subnet should inform the subnet controller before leaving the subnet frequency. If no alternate operator is available and communication with the other team is particularly important, the operator can request to be checked out of the subnet and then check back in when they have complicated their direct communication.

==== Routing formal messages within a region ====
The other major case is when a team has a formal message that they want to route to another team. In some cases they may be able to do this using the tactical communication method above. In other cases it may be better to route a formal message via their subnet controller. If the team to receive the message is in the same region the subnet controller may be able to read the message to them. Or, if there is a strong simplex communication path between the two teams, the subnet controller may give the originating team permission to use the subnet frequency to read the message to the receiving team.

==== Routing formal messages between regions ====
The situation is even more complicated if the team to receive the messages is checked into a different regional subnet than the originating team. In that case, the subnet controller may need to route the message through the ECC radio room via the Tactical Net. Alternatively, the controller could transcribe the message into a Winlink ICS 213 and route it to the other subnet via a Winlink gateway. The receiving subnet controller could then read the message to the receiving team.

Procedure for when Net Control Operator Cannot Hear Some Operators

2026-02-03T16:53:31Z

BruceSchafer: BruceSchafer moved page Procedure for when Net Control Operator Cannot Hear Some Operators to Procedure for When Net Control Operator Cannot Hear Some Operators: Fix

#REDIRECT [[Procedure for When Net Control Operator Cannot Hear Some Operators]]

Procedure for When Net Control Operator Cannot Hear Some Operators

2026-02-03T16:53:31Z

BruceSchafer: BruceSchafer moved page Procedure for when Net Control Operator Cannot Hear Some Operators to Procedure for When Net Control Operator Cannot Hear Some Operators: Fix

During the check-in process
# Ask all operators to report any check-ins that you have missed by using the proword “Relay.”
# Acknowledge the relay by saying “Relay, go ahead.”
# Record the check-in and the station that relayed it as you will need it later for further communication with the relayed station.
# If you need additional information from the relayed station ask the relaying station to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until no one offers another relay.
After check-in when you need information or are ready to receive traffic from your stations

# If you previously checked in someone via relay because you could not hear them directly, ask the station that provided relay to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster that you cannot hear directly.

After check-in when you have information or traffic to share with the stations in your subnet

# If you previously checked in someone via relay because you could not hear them directly, ask the station that provided relay to confirm that the previously relayed stations have received the information you have shared or need any fills. Suggest to the relaying station that they can provide any fills if they are comfortable doing so.
# Wait for the relaying station to obtain the confirmation or a request for clarification or a fill.
# If the relaying station reports that additional information or fills are needed, provide them and ask the relaying station to confirm the information has been received or provide the fills if they are needed.
# When the relaying station is finished, expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster have confirmed they have received the information.

Procedure for When Some Operators Cannot Hear Net Control Operator

2026-02-03T05:42:25Z

BruceSchafer: Corrected format error.

During the check-in process
# Pick a relatively strong station that you don’t think is near you to serve as the temporary delegated subnet control operator.
# Say the following: “<tactical call sign*> Please ask for any stations that I did not acknowledge to check in now, and then come back to me and let me know who you heard.” * Say the station’s tactical call sign rather than the words tactical call sign.
# Wait for the delegated station to talk to the stations and report back to you.
# Record and acknowledge any relayed check ins as well as the tactical call sign of the station providing the relay as you will need to ask for relays for any additional communication with the relayed station. .
# If there were relayed check-ins and you need additional information from the relayed stations ask the delegated station to call back the relayed station(s) and request the needed information.
# Wait for the delegated station to obtain the requested information and report back to you.
# Acknowledge the requested information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps as necessary to assure that you have heard from all stations in your region.
After check-in when you need information or are ready to receive traffic from your stations
# If you previously checked in someone via relay because they could not hear you, ask the station that provided relay to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster that you cannot hear directly.

After check-in when you have information or traffic to share with the stations in your subnet

# If you previously checked in someone via relay because they could not hear you, ask the station that provided relay to confirm that the previously relayed stations have received the information you have shared or need any fills. Suggest to the relaying station that they can provide any fills if they are comfortable doing so.
# Wait for the relaying station to obtain the confirmation or a request for clarification or a fill.
# If the relaying station reports that additional information or fills are needed, provide them and ask the relaying station to confirm the information has been received or provide the fills if they are needed.
# When the relaying station is finished, expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster have confirmed they have received the information.

Procedure for When Net Control Operator Cannot Hear Some Operators

2026-02-03T05:40:24Z

BruceSchafer: Corrected spelling errors.

Procedure for When Some Operators Cannot Hear Net Control Operator

2026-02-03T05:39:23Z

BruceSchafer: Added procedures for the period after the check-in process.

During the check-in process
# Pick a relatively strong station that you don’t think is near you to serve as the temporary delegated subnet control operator.
# Say the following: “<tactical call sign*> Please ask for any stations that I did not acknowledge to check in now, and then come back to me and let me know who you heard.” * Say the station’s tactical call sign rather than the words tactical call sign.
# Wait for the delegated station to talk to the stations and report back to you.
# Record and acknowledge any relayed check ins as well as the tactical call sign of the station providing the relay as you will need to ask for relays for any additional communication with the relayed station. .
# If there were relayed check-ins and you need additional information from the relayed stations ask the delegated station to call back the relayed station(s) and request the needed information.
# Wait for the delegated station to obtain the requested information and report back to you.
# Acknowledge the requested information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps as necessary to assure that you have heard from all stations in your region.After check-in when you need information or are ready to receive traffic from your stations

# If you previously checked in someone via relay because they could not hear you, ask the station that provided relay to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster that you cannot hear directly.

After check-in when you have information or traffic to share with the stations in your subnet

# If you previously checked in someone via relay because they could not hear you, ask the station that provided relay to confirm that the previously relayed stations have received the information you have shared or need any fills. Suggest to the relaying station that they can provide any fills if they are comfortable doing so.
# Wait for the relaying station to obtain the confirmation or a request for clarification or a fill.
# If the relaying station reports that additional information or fills are needed, provide them and ask the relaying station to confirm the information has been received or provide the fills if they are needed.
# When the relaying station is finished, expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster have confirmed they have received the information.

Procedure for When Net Control Operator Cannot Hear Some Operators

2026-02-03T05:35:33Z

BruceSchafer: Corrected some grammar issues

During the check-in process
# Ask all operators to report any check-ins that you have missed by using the proword “Relay.”
# Acknowledge the relay by saying “Relay, go ahead.”
# Record the check-in and the station that relayed it as you will need it later for further communication with the relayed station.
# If you need additional information from the relayed station ask the relaying station to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until no one offers another relay.
After check-in when you need information or are ready to receive traffic from your stations

# If you previously checked in someone via relay because you could not here them directly, ask the station that provided relay to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster that you cannot hear directly.

After check-in when you have information or traffic to share with the stations in your subnet

# If you previously checked in someone via relay because you could not here them directly, ask the station that provided relay to confirm that the previously relayed stations have received the information you have shared or need any fills. Suggest to the relaying station that they can provide any fills if they are comfortable doing so.
# Wait for the relaying station to obtain the confirmation or a request for clarification or a fill.
# If the relaying station reports that additional information or fills are needed, provide them and ask the relaying station to confirm the information has been received or provide the fills if they are needed.
# When the relaying station is finished, expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster have confirmed they have received the information.

Procedure for When Net Control Operator Cannot Hear Some Operators

2026-02-03T05:10:05Z

BruceSchafer: Added instructions for relaying after the check-in process.

During the Check-in Process
# Ask all operators to report any check-ins that you have missed by using the proword “Relay.”
# Acknowledge the relay by saying “Relay, go ahead.”
# Record the check-in and the station that relayed it as you will need it later for further communication with the relayed station.
# If you need additional information from the relayed station ask the relaying station to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until no one offers another relay.
After Check-in when needing information or are ready to receive traffic from your stations

# If you previously checked in someone via relay because you could not here them directly, ask the station that provided relay to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster that you cannot hear directly.

After Check-in when you have information or traffic to share with the stations in your subnet

# If you previously checked in someone via relay because you could not here them directly, ask the station that provided relay to confirm that the previously relayed stations have received the information you have shared or need any fills. Suggest to the relaying station that they can provide any fills if they are comfortable doing so.
# Wait for the relaying station to obtain the confirmation or a request for clarification or a fill.
# If the relaying station reports that additional information or fills are needed, provide them and ask the relaying station to confirm the information has been received or provide the fills if they are needed.
# When the relaying station is finished, expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until you have requested information from all stations on your roster have confirmed they have received the information.

Procedure for When Net Control Operator Cannot Hear Some Operators

2026-02-03T04:51:52Z

BruceSchafer: Took out language specific to February exercise

# Ask all operators to report any check-ins that you have missed by using the proword “Relay.”
# Acknowledge the relay by saying “Relay, go ahead.”
# Record the check-in and the station that relayed it as you will need it later for further communication with the relayed station.
# If you need additional information from the relayed station ask the relaying station to request the information on your behalf.
# Wait for the relaying station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until no one offers another relay.

Radio Communication Procedures

2026-02-03T02:03:29Z

BruceSchafer: /* Team Amateur Radio Operator (ARO) Procedures */ Updated name of linked page

=== General Radio Operator (GRO) Procedures for using FRS/GMRS Radios ===

* [[Media:PBEM NET GRO Task List.pdf|GRO Task List]]
* [[Guidelines for Using FRS and GMRS Radios]]
* [https://drive.google.com/file/d/1x1aUoJViv2Cgwmf6F39VUW0aQENx8w1d/view?usp=drive_link Training slides]
* [https://drive.google.com/file/d/1QBPEMkTlSy84icVLBb5bPtA8TofQuy4v/view?usp=drive_link Exercise 1 Script]
* [https://drive.google.com/file/d/1foFWiKwrmhI0ck59eWjDAu058FO5xKfS/view?usp=drive_link Exercise 2 Script]
* [https://drive.google.com/file/d/1QgQshXQGgimikfkGf1dRWyfrY-FmxYJn/view?usp=drive_link Sample NET Form 8 used with Exercise 2]
* [https://pbem.link/net-team-map Map of FRS/GMRS channels used by NET Teams] [Note the ''''Ch. #'''' filter buttons above the map.]
* [https://docs.google.com/presentation/d/1b1x0JTvbzP5nHxUaM-Fy2Yar4hmjg9jKIkPNJLn4BYI/edit?usp=sharing Communicating between teams]
* [[How to Create a NET Radio Map]] (one-page summary)
* [[FRS/GMRS Radio Mapping Guide]] (step-by-step guidance)

=== Amateur Radio Operator (ARO) Resources ===
* [[Obtaining an Amateur Radio License]]
* [[Enrolling in NET ARO Email Communications]]
* [[Participating in Weekly NET ARO Radio Communications]]
* [[Participating in Monthly NET ARO Simplex Exercises]]
=== BEECN Radio Procedures ===
* [[Operations at Fire Stations|Amateur Radio Operations at Fire Stations]]
** [[Media:MCARES 2023 Frequency Template for BEECN VHF Radios.pdf|Channel Assignments Used in BEECN VHF Radios]]
* [[Operations at BEECN_Sites#Radio_voice_procedure|Radio Voice Procedure]]
** [[BEECN Radio Traffic#BEECN Tactical Radio Traffic Reporting Priorities|BEECN Tactical Radio Traffic Reporting Priorities]]
** [[Operations at BEECN Sites#APPENDIX:_BEECN_Channel_Guide|BEECN UHF Radio Channels]]

=== Team Amateur Radio Operator (ARO) Procedures ===
* [[Media:PBEM NET ARO Task List.pdf|ARO Task List]]
* [[ARO Standard Operating Procedures]]
* [[Becoming an Official NET Amateur Radio Operator]]
* [[Check-in and Check-out Procedures]]
* [[Communicating with Net Control Operator]]
* [[Communicating with Other Teams]]
* [[Frequency Tables]]
* [[Message Precedence]]
* [[ITU Phonetic Alphabet]]
* [https://docs.google.com/presentation/d/1FBOXf9_7sEz3vsR5JxyOTcMMyDhKOoFYGmJphuORTiA/edit?usp=sharing Logging Voice Traffic]
* [[Latitude and Longitude]]
* [[Operating Simplex]]
* [[Prowords for Traffic Handling]]
* [[Radio Communication with Emergency Coordination Center]]
* [[Relays During Radio Communication]]
* [[Reporting Message Counts]]
* [[Readability and Signal Strength]]
* [[Simplex Advice]]
* [[Simplex Regions]]
* [[Tactical Call Signs]]
* [[Tactical Communication Examples]]
* [[Use of FCC Call Signs when Tactical Call Signs Are Being Used]]
* [[Voicing a NET Form 8 or its Reply]]

=== Subnet Control (SNC) Procedures ===
[[File:Communication Topology.png|400px]]

Radio Communication between ECC and Staging Areas.

[[Radio Communication Topology|Click here for full size diagram]].

==== Standard Operating Procedure ====

* [[Subnet Control Operator Standard Operating Procedure]]
* [[Definitions of Amateur Radio Nets That We Use]]
* [[ICS 205 with Frequencies for Subnet Control Operators]]

==== Voice Procedures ====
* [[Logging Procedures for Subnet Control Operators]]
* [[Media:PBEM NET ARO NCO Certification Task List.pdf|Net Control Operator Task List for Advanced Certification]]
* [[Voice Procedures for Subnet Control Operators]]
** [[Script for Checking in a Small Number of Stations]]
** [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]

==== Winlink Procedures ====
* [[Checklists for Winlink Tasks]]
* [[Using Winlink Tactical Addresses]]
* [[Winlink Procedures for Subnet Controllers]]
* [[Media:PBEM NET ARO Winlink Certification Task List.pdf|Winlink Task List for Advanced Certification]]

=== Other Resources for NET Amateur Radio Operators ===
* [https://docs.google.com/document/d/1gxNjgJA2mfCdY1jhmpZCbCd80niYwu9Q0S6Pr00a9dY/edit?usp=sharing Sources of Amateur Radio Training, Learning, Supplies and Equipment for Portland Neighborhood Emergency Teams]
* [https://multnomahares.org/resources/frequency-lists-and-radio-programming-templates/ Multnomah County ARES Frequency Lists and Radio Programming Templates]
* [https://chirpmyradio.com/projects/chirp/wiki/Home CHIRP Radio Programming Software]
* [[NET Radio Training Liaisons]]

Relays

2026-02-03T02:02:31Z

BruceSchafer: BruceSchafer moved page Relays to Relays During Radio Communication: Make page name more descriptive

#REDIRECT [[Relays During Radio Communication]]

Relays During Radio Communication

2026-02-03T02:02:31Z

BruceSchafer: BruceSchafer moved page Relays to Relays During Radio Communication: Make page name more descriptive

The strength of communication will vary from exercise to exercise and operator to operator based on factors like location, elevation, available transmission power and sensitivity and selectivity of receivers. Note that there are many combinations of these factors in a region including a subnet controller who may be in a different location and team AROs in varying locations depending on who is available and the nature of the exercise or deployment. This unpredictability of simplex communication means that you and the other operators must be ready to ask for and provide relays. There are three cases to consider.

# You can hear the subnet controller but they cannot hear you but you can be heard by other AROs. Ideally this case will be covered by the subnet controller asking for relays and another station offering to relay your check-in or your responses. If the subnet controller needs more information, they will ask the relaying station to request it from you. This scenario is sometimes referred to as the subnet controller handing the “talking stick” to the relaying station.
# You can hear other AROs checking in or providing information but you can’t hear the subnet controller. To cover this possibility the subnet controller may choose another station and ask them to relay your announcement or request. When this happens you will be responding to the other station because the subnet controller has passed the talking stick to them and they are temporarily acting as the temporary subnet controller.
# Neither the subnet controller nor any of the other AROs in the region can hear you even though you can hear some of them. In this case your best alternative is to attempt to check into another regional subnet.

Relays During Radio Communication

2026-02-03T02:01:38Z

BruceSchafer: Created initial content for new page

Script for Checking in Stations Alphabetically by Tactical Call Signs

2026-02-03T01:57:50Z

BruceSchafer: Added link to new procedure

This is <your call sign, your first name>, subnet control operator for this <deployment or exercise>. in the <your region name(s)> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.

Our format during this deployment is the following:

* First, we’ll check in operators. This check-in process may include some relays. During this process please make notes on how well you can hear other stations.
* After the check-in process is complete, we will conduct formal communications.
* When the deployment period comes into an end, I will then ask you to check out.
* After all stations have checked out, I will close the net.
'''[Preface to checking stations in]'''

In a minute, I will start checking stations in. I will check in stations in our region by tactical call sign rather than FCC call sign. Your tactical call sign should be based on your team name followed by a digit. For example, South Heights 1. Be prepared to change the digit after your team name if someone else checks in with your first choice before you do. After I recognize you, give your FCC call sign and say the word “Out”.

As you hear other stations check in, please log their tactical call signs and how well you can hear them. If you hear a station that I don’t acknowledge, please wait until I ask for relays before telling me who I missed.

'''[Start of Check in]'''

Tonight I’m going to ask you to check in alphabetically by your ''tactical call sign''.

Let’s start with stations with tactical call signs that start with the letter Alpha through November? After I recognize you, give your FCC call sign and say the word “Out”. Please come now with your tactical call sign

[Record each station on your [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] and acknowledge each station as they check in. Expect operators to acknowledge your acknowledgement by giving their FCC call sign, which you can also log if you like.]

Are there any check-ins with tactical call signs that start with Oscar through Zulu?

[Acknowledge, as above.]

Are there any missed or late check-ins with tactical call signs that start with Alpha through Zulu?

[Acknowledge, as above.]

[To cover the possibility that you cannot hear some of the operators, ask for a relay using [[Procedure for when Net Control Operator Cannot Hear Some Operators]]]

[To cover the possibility that some operators cannot hear you use [[Procedure for When Some Operators Cannot Hear Net Control Operator]].]

Thanks everyone for checking in.

'''[End of Check in]'''

Procedure for When Some Operators Cannot Hear Net Control Operator

2026-02-03T01:57:31Z

BruceSchafer: Created initial content for new page

# Pick a relatively strong station that you don’t think is near you to serve as the temporary delegated subnet control operator.
# Say the following: “<tactical call sign*> Please ask for any stations that I did not acknowledge to check in now, and then come back to me and let me know who you heard.” * Say the station’s tactical call sign rather than the words tactical call sign.
# Wait for the delegated station to talk to the stations and report back to you.
# Acknowledge any relayed check ins.
# If there were relayed check-ins, ask the delegated station to call back the relayed station(s) and request whether they have grid power and to give a summary of the weather at their location.
# Wait for the delegated station to obtain the requested information and report back to you.
# Acknowledge the requested information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps as necessary to assure that you have heard from all stations in your region.

Script for Checking in Stations Alphabetically by Tactical Call Signs

2026-02-03T01:54:58Z

BruceSchafer: Added link to new procedure

This is <your call sign, your first name>, subnet control operator for this <deployment or exercise>. in the <your region name(s)> region. This subnet is operating on <subnet frequency> without a repeater. Make sure your transceiver is not using a repeater offset as an offset will keep us from hearing your transmissions.

Our format during this deployment is the following:

* First, we’ll check in operators. This check-in process may include some relays. During this process please make notes on how well you can hear other stations.
* After the check-in process is complete, we will conduct formal communications.
* When the deployment period comes into an end, I will then ask you to check out.
* After all stations have checked out, I will close the net.
'''[Preface to checking stations in]'''

In a minute, I will start checking stations in. I will check in stations in our region by tactical call sign rather than FCC call sign. Your tactical call sign should be based on your team name followed by a digit. For example, South Heights 1. Be prepared to change the digit after your team name if someone else checks in with your first choice before you do. After I recognize you, give your FCC call sign and say the word “Out”.

As you hear other stations check in, please log their tactical call signs and how well you can hear them. If you hear a station that I don’t acknowledge, please wait until I ask for relays before telling me who I missed.

'''[Start of Check in]'''

Tonight I’m going to ask you to check in alphabetically by your ''tactical call sign''.

Let’s start with stations with tactical call signs that start with the letter Alpha through November? After I recognize you, give your FCC call sign and say the word “Out”. Please come now with your tactical call sign

[Record each station on your [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] and acknowledge each station as they check in. Expect operators to acknowledge your acknowledgement by giving their FCC call sign, which you can also log if you like.]

Are there any check-ins with tactical call signs that start with Oscar through Zulu?

[Acknowledge, as above.]

Are there any missed or late check-ins with tactical call signs that start with Alpha through Zulu?

[Acknowledge, as above.]

[To cover the possibility that you cannot hear some of the operators, ask for a relay using [[Procedure for when Net Control Operator Cannot Hear Some Operators]]]

[To cover the possibility that some operators cannot hear you, follow this procedure.]

Thanks everyone for checking in.

'''[End of Check in]'''

Procedure for When Net Control Operator Cannot Hear Some Operators

2026-02-03T01:53:55Z

BruceSchafer: Created initial content for new page

# Ask all operators to report any check-ins that you have missed by using the proword “Relay.”
# Acknowledge the relay by saying “Relay, go ahead.”
# Record the check-in and ask the operator to request that relayed station to report whether they have grid power and to give a summary of the weather at their location.
# Wait for the delegated station to obtain the requested information and report back to you.
# Acknowledge the receipt of the information.
# Expect to the relaying operator to give their tactical and FCC call signs and the word “Out”
# Repeat the above steps until no one offers another relay.

Citywide Deployment Exercise

2026-01-30T02:59:52Z

BruceSchafer: /* Registration */ Added a comma

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
May 30, 2026 from 1 pm to 4 pm

== Registration ==
Team registration is open and team leads have been provided a registration link. If you are a NET Team Leader and don't have the team registration information, please send an email to [mailto:Netdeploymentexercise@gmail.com netdeploymentexercise@gmail.com]

Individual registration will open in April.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Citywide Deployment Exercise

2026-01-30T02:59:02Z

BruceSchafer: /* Registration */ Added email link

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
May 30, 2026 from 1 pm to 4 pm

== Registration ==
Team registration is open and team leads have been provided a registration link. If you are a NET Team Leader and don't have the team registration information please send an email to [mailto:Netdeploymentexercise@gmail.com netdeploymentexercise@gmail.com]

Individual registration will open in April.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Citywide Deployment Exercise

2026-01-30T02:47:25Z

BruceSchafer: /* Preparation */ Added new subsections giving the date and time and mentioning registration

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

Typically, Team Leaders may register their teams first, then individual volunteers sign up to participate at one of the neighborhood sites. Registration announcements are sent in PBEM Volunteer Bulletin emails.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Next Citywide Deployment Exercise =
== Date and Time ==
May 30, 2026 from 1 pm to 4 pm

== Registration ==
Team registration is open.
Individual registration will open in April.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =

== After Action Reports ==

* [https://volunteerpdx.net/images/0/0c/2025.11.09_CDE_After_Action_Report.pdf 2025.11.09]
* [https://volunteerpdx.net/images/4/44/2025.05.31_CDE_After_Action_Report.pdf 2025.05.31]
* [https://volunteerpdx.net/images/e/ef/2024.10.30_CDE_After_Action_Report.pdf 2024.10.30]
* [https://volunteerpdx.net/images/b/b9/2024.04.27_CDE_After_Action_Report.pdf 2024.04.27]
* [https://volunteerpdx.net/images/e/e2/2023.10.08_CDE_After_Action_Report.pdf 2023.10.08]
* [https://volunteerpdx.net/images/0/0b/2023.05.13_CDE_After_Action_Report.pdf 2023.05.13]
* [https://volunteerpdx.net/images/9/9e/2022.10.22_CDE_After_Action_Report.pdf 2022.10.22]
* [https://volunteerpdx.net/images/f/fa/2022.05.07_CDE_After_Action_Report.pdf 2022.05.07]
* [https://volunteerpdx.net/images/5/5c/2021.11.07_CDE_After_Action_Report.pdf 2021.11.07]
* [https://volunteerpdx.net/images/b/bf/2021.05.15_CDE_After_Action_Report.pdf 2021.05.15]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms NET Incident Command System (ICS) Forms]
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf Incident Team Leader (ITL) Instructions]

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook for Proctors}}
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Radio Communication Procedures

2026-01-25T04:32:39Z

BruceSchafer: /* Other Resources for NET Amateur Radio Operators */ Added link to CHIRP

=== General Radio Operator (GRO) Procedures for using FRS/GMRS Radios ===

* [[Media:PBEM NET GRO Task List.pdf|GRO Task List]]
* [[Guidelines for Using FRS and GMRS Radios]]
* [https://drive.google.com/file/d/1x1aUoJViv2Cgwmf6F39VUW0aQENx8w1d/view?usp=drive_link Training slides]
* [https://drive.google.com/file/d/1QBPEMkTlSy84icVLBb5bPtA8TofQuy4v/view?usp=drive_link Exercise 1 Script]
* [https://drive.google.com/file/d/1foFWiKwrmhI0ck59eWjDAu058FO5xKfS/view?usp=drive_link Exercise 2 Script]
* [https://drive.google.com/file/d/1QgQshXQGgimikfkGf1dRWyfrY-FmxYJn/view?usp=drive_link Sample NET Form 8 used with Exercise 2]
* [https://pbem.link/net-team-map Map of FRS/GMRS channels used by NET Teams] [Note the ''''Ch. #'''' filter buttons above the map.]
* [https://docs.google.com/presentation/d/1b1x0JTvbzP5nHxUaM-Fy2Yar4hmjg9jKIkPNJLn4BYI/edit?usp=sharing Communicating between teams]
* [[How to Create a NET Radio Map]] (one-page summary)
* [[FRS/GMRS Radio Mapping Guide]] (step-by-step guidance)

=== Amateur Radio Operator (ARO) Resources ===
* [[Obtaining an Amateur Radio License]]
* [[Enrolling in NET ARO Email Communications]]
* [[Participating in Weekly NET ARO Radio Communications]]
* [[Participating in Monthly NET ARO Simplex Exercises]]
=== BEECN Radio Procedures ===
* [[Operations at Fire Stations|Amateur Radio Operations at Fire Stations]]
** [[Media:MCARES 2023 Frequency Template for BEECN VHF Radios.pdf|Channel Assignments Used in BEECN VHF Radios]]
* [[Operations at BEECN_Sites#Radio_voice_procedure|Radio Voice Procedure]]
** [[BEECN Radio Traffic#BEECN Tactical Radio Traffic Reporting Priorities|BEECN Tactical Radio Traffic Reporting Priorities]]
** [[Operations at BEECN Sites#APPENDIX:_BEECN_Channel_Guide|BEECN UHF Radio Channels]]

=== Team Amateur Radio Operator (ARO) Procedures ===
* [[Media:PBEM NET ARO Task List.pdf|ARO Task List]]
* [[ARO Standard Operating Procedures]]
* [[Becoming an Official NET Amateur Radio Operator]]
* [[Check-in and Check-out Procedures]]
* [[Communicating with Net Control Operator]]
* [[Communicating with Other Teams]]
* [[Frequency Tables]]
* [[Message Precedence]]
* [[ITU Phonetic Alphabet]]
* [https://docs.google.com/presentation/d/1FBOXf9_7sEz3vsR5JxyOTcMMyDhKOoFYGmJphuORTiA/edit?usp=sharing Logging Voice Traffic]
* [[Latitude and Longitude]]
* [[Operating Simplex]]
* [[Prowords for Traffic Handling]]
* [[Radio Communication with Emergency Coordination Center]]
* [[Reporting Message Counts]]
* [[Readability and Signal Strength]]
* [[Simplex Advice]]
* [[Simplex Regions]]
* [[Tactical Call Signs]]
* [[Tactical Communication Examples]]
* [[Use of FCC Call Signs when Tactical Call Signs Are Being Used]]
* [[Voicing a NET Form 8 or its Reply]]

=== Subnet Control (SNC) Procedures ===
[[File:Communication Topology.png|400px]]

Radio Communication between ECC and Staging Areas.

[[Radio Communication Topology|Click here for full size diagram]].

==== Standard Operating Procedure ====

* [[Subnet Control Operator Standard Operating Procedure]]
* [[Definitions of Amateur Radio Nets That We Use]]
* [[ICS 205 with Frequencies for Subnet Control Operators]]

==== Voice Procedures ====
* [[Logging Procedures for Subnet Control Operators]]
* [[Media:PBEM NET ARO NCO Certification Task List.pdf|Net Control Operator Task List for Advanced Certification]]
* [[Voice Procedures for Subnet Control Operators]]
** [[Script for Checking in a Small Number of Stations]]
** [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]

==== Winlink Procedures ====
* [[Checklists for Winlink Tasks]]
* [[Using Winlink Tactical Addresses]]
* [[Winlink Procedures for Subnet Controllers]]
* [[Media:PBEM NET ARO Winlink Certification Task List.pdf|Winlink Task List for Advanced Certification]]

=== Other Resources for NET Amateur Radio Operators ===
* [https://docs.google.com/document/d/1gxNjgJA2mfCdY1jhmpZCbCd80niYwu9Q0S6Pr00a9dY/edit?usp=sharing Sources of Amateur Radio Training, Learning, Supplies and Equipment for Portland Neighborhood Emergency Teams]
* [https://multnomahares.org/resources/frequency-lists-and-radio-programming-templates/ Multnomah County ARES Frequency Lists and Radio Programming Templates]
* [https://chirpmyradio.com/projects/chirp/wiki/Home CHIRP Radio Programming Software]
* [[NET Radio Training Liaisons]]

Logging Procedures for Subnet Control Operators

2026-01-03T01:38:29Z

BruceSchafer: /* Instructions for using the NET Version of the ICS 214 Unit Log */ Added some clarifications

The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately. A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.

Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.

* [[Media:ICS-214 Unit Log Fillable.pdf|NET Version of ICS 214 Unit Log]]
* NET Form 6 and the similar ICS 309 Communications Log
** [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] for logging transmission of NET Form 8 or other forms by voice.
** ICS Form 309 for Winlink traffic which can be [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generated by Winlink Express]]
* [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]]. This is an unofficial form that should help you capture information about the stations participating in your subnet more efficiently than the above two forms.
* [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]]. This unofficial form should help you keep track of counts of the traffic that the stations in your region have ready to transmit as well as traffic that you have already handled.

Note: For some short exercises you may not need all four forms. For instance, if you are serving as an SNC during an exercise that does not involve formal traffic you would not need to use Form 6 or a Traffic Count Worksheet.

=== Background ===
The [[Media:ICS-214 Unit Log Fillable.pdf|NET Version of ICS 214 Unit Log]] is designed to record a roster of those involved in a particular unit and the activities of those people. The form’s header provides space for recording the incident name, date and time, leadership and operational period. Below the header are rows for recording a roster of those associated with a particular unit, in this case a communications unit. The lower part of the form is for recording the activities of the unit. This makes it useful for providing information about what happened and when – both for those who participated in those activities and those who arrive later. In addition, the information is useful for those interested in reviewing the activities of the unit and looking for opportunities for improving readiness and efficiency for similar future activities.

The [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] is based on the ICS 309 Communication Log form which is intended primarily for logging formal traffic - messages on forms. Limiting its use to such traffic should provide two benefits:

* The station’s operator should be able to more easily find records of forms previously transmitted, especially when a reply to such a form is about to be received.
* Those reviewing the logs later are more likely to have a clear picture of what messages were sent and received by the station.

The [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] is an unofficial form designed to complement the two forms discussed above to help keep track of the stations that communication unit is in contact with as well as information like the readability of the radio communications with those stations. As it is not an official ICS form, it can be customized to the particular situation. In a pinch, use scratch paper instead. Using this form instead of recording check-ins on Form 6 or 214 will use less space and keep the information about each station together for easy reference.

The [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] is an experimental form for tracking counts of available formal messages as well as counts of messages handled so far. Feel free to customize it to meet your needs. The goal is to handle traffic based on precedence and give all stations in your region a chance to pass traffic that is equal to the precedence being passed by other stations. The worksheet should help you handle the available traffic by relative precedence and keep track of available traffic that you have not yet handled.

=== Instructions for using the [[Media:ICS-214 Unit Log Fillable.pdf|NET Version of the ICS 214 Unit Log]] ===
Each NET Subnet Conrol Operator (SNC) should use an ICS Form 214 to record the activities of their station in their role as Unit Leader. In other situations like a radio trailer or radio room, multiple stations and operators at the same location are all part of the same Communications Unit and would share a single ICS Form 214. Similarly, multiple operators working together at a remote site like an evacuation center would share a Form 214..

Assuming you are serving as a NET SNC:
* Log your name as the Unit Leader in Box 5. The date and time your station’s activation should go in boxes 2 and 3.
* Also record your Name and Time In in Section 7 - "Personnel Roster Assigned". Do the same for any other operators or scribes serving with you.
* Record “ICS Position” as “Amateur Radio Operator” or "Scribe" or an abbreviation like “ARO” or "ARO Scribe".
* Record “Home Base” as “Portland NET”.
* When someone goes off duty, record the time in “Time Out”
* If the incident command declares a new operational period, close the 214 and open a new one.
* When a station is closed or a new operational period starts, log the closing as the last item in Major Events.
* See [[Media:ICS Form 214 Unit Log NET Instructions.pdf|Instructions for NET version of ICS Form 214 Unit Log]] for additional details.

* See the following sample ICS 214.
[[File:ICS 214 SNC Sample.png|500px]]

=== Overview of using [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) Communication Log ===

* Use NET Form 6 / ICS 309 for formal traffic only, not activities. One Form 6 should be used by each operator.
* Subnet controllers should record most activities on an ICS 214 rather than the NET Form 6 or ICS 309 with the following exceptions:
** Check-ins, readability, etc. should go on the [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] or scratch paper.
** Message counts should go on a [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] or scratch paper.
* Use Winlink Express to [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generate an ICS 309 PDF]] for any Winlink traffic.
[[File:Sample Form 6 SNC.png|500px]]

=== Instructions for Using a [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) for Logging NET Form 8s or ICS Form 213s ===

* When a NET Form 8 is being logged, the right-hand field should start with the tactical call sign of the originating station, which may be the same as the team name.
* The originating station is followed by the date and time from the fields on the Form 8, followed by the Subject field from the Form 8.
* The Subject of a Form 8 should begin with message precedence, which should be copied into the right-hand field with the rest of the subject.
* For replies, the word “Reply” should be first followed by the information in the same column for the original message.
* FCC call signs should not be used in the From and To fields of NET Form 6 (ICS 309) , Instead use tactical call signs as illustrated below.
* In the example above the transmission of the messages that originated from North Heights and South Heights to ECC and the receipt of traffic from ECC are not shown here because they were transmitted via Winlink which can generate a separate log.

=== Instructions for using [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] ===

* Each time a station checks in, record the time, the station’s tactical call sign and the operator’s FCC call sign.
* If the operator is representing a team at a staging area, record the name of the team.
** Note: During some exercises, several teams combine to participate in the exercise. You do not need to record the names of all the NET teams or Portland neighborhoods representing at the staging area. ''Record only the name of the neighborhood or team that is hosting the combined teams during the exercise.''
* Also record the station’s readability. See [[Readability and Signal Strength]].
* When the station checks out, record that time in the corresponding column.

[[File:SNC's Stations Participating Form.png|500px]]

=== Instructions for using the [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] ===

* Each time a station reports available traffic, use a new row to record the number of messages available at each precedence level.
* Each time you handle a message for that station, use a tally mark to indicate an increase in the number messages handled at the message’s precedence level. For instance, if one Priority message was previously handled for a station and you just handled a second one, the tally in the Handled column for Priority messages would change from “l” to “ll”. See the [[wikipedia:Tally_marks|Wikipedia article on Tally Marks]] for a discussion of tally marks.
* If a station provides new counts of available traffic, start a new row and draw a line through the row that is now out of date.
* Start a new Worksheet for each shift or when worksheet has become obsolete.
* See the following sample worksheet.
[[File:Sample Traffic Count Worksheet.png|500px]]

Frequency Tables

2025-12-04T01:09:38Z

BruceSchafer: /* VHF Frequency Table - Frequencies in the 2 meter Amateur Radio Band */ Updated column head to reference both 2023 & 2025 templates

=== VHF Frequency Table - Frequencies in the 2 meter Amateur Radio Band ===
__FORCETOC__
{| class="wikitable"
|
|
|
|
| colspan="2" |'''2021 MCARES Template'''
| colspan="2" |'''2023/25 MCARES Template'''
|-
|'''Region(s)'''
|'''Frequency'''
|'''Description'''
|'''Alias'''
|'''Large'''

'''“Standard”'''
|'''Small'''
'''“MHT”'''
|'''Large'''
'''"Standard"'''
|'''Small'''
'''"MHT"'''
|-
|Alameda North

& New Northeast
|146.42 MHz
|PBEM NET Tac 4
|PNTC04
|392
|68
|392
|67
|-
|Alameda South
|146.54 MHz
|PBEM NET Tac 5
|PNTC05
|393
|69
|393
|68
|-
|Columbia
|145.62 MHz.
|PBEM NET Tac 6
|PNTC06
|394
|70
|394
|69
|-
|Outer East
|145.53 MHz
|PBEM NET Tac 8
|PNTC08
|396
|72
|396
|71
|-
|River North
|146.56 MHz
|PBEM NET Tac 9
|PNTC09
|397
|73
|397
|72
|-
|River South
|145.79 MHz
|PBEM NET Tac 10
|PNTC10
|398
|74
|398
|73
|-
|Southeast
|145.74 MHz
|PBEM NET Tac 11
|PNTC11
|399
|75
|399
|74
|-
|Westside
|146.58 MHz
|PBEM NET Tac 12
|PNTC12
|400
|76
|400
|75
|}
VHF Backup frequency: 146.50 MHz, PNTC07, 395 (large), 71 (2021 small). 70 (2023 small)

Large and Small refer to Standard and MHT 2021 and 2023 Multnomah County ARES frequency templates -- See <nowiki>https://www.multnomahares.org/resources/frequency-lists-and-radio-programming-templates/</nowiki>

=== UHF Frequency Table - Frequencies in the 70 cm Amateur Radio Band ===
{| class="wikitable"
|
|
| colspan="2" |'''Channels MCARES Templates'''
|
|
|-
|'''Description'''
|'''Alias'''
|'''Large “Standard”'''
|'''Small “MHT”'''
|'''Frequency MHz'''
|'''Recommended For Use By'''
|-
|NET Team 2
|PNTM02
|402
|102
|431.400
|Teams using FRS Ch. 2
|-
|NET Team 3
|PNTM03
|403
|103
|431.425
|Teams using FRS Ch. 3
|-
|NET Team 4
|PNTM04
|404
|104
|431.450
|Teams using FRS Ch. 4
|-
|NET Team 5
|PNTM05
|405
|105
|431.475
|Teams using FRS Ch. 5
|-
|NET Team 6
|PNTM06
|406
|106
|431.500
|Teams using FRS Ch. 6
|-
|NET Team 7
|PNTM07
|407
|107
|431.525
|Teams using FRS Ch. 7
|-
|NET Team 8
|PNTM08
|408
|108
|431.550
|1st backup for VHF frequency for Alameda North

& New Northeast*
|-
|NET Team 9
|PNTM09
|409
|109
|431.575
|1st backup for VHF frequency for Alameda South Region*
|-
|NET Team 10
|PNTM10
|410
|110
|431.600
|1st backup for VHF frequency for Columbia Region*
|-
|NET Team 11
|PNTM11
|411
|111
|431.625
|1st backup for VHF frequency for Outer East Region
and Westside Regions*
|-
|NET Team 12
|PNTM12
|412
|112
|431.650
|1st backup for VHF frequency for River North Region*
|-
|NET Team 13
|PNTM13
|413
|113
|431.675
|1st backup for VHF frequency for River South Region*
|-
|NET Team 14
|PNTM14
|414
|114
|431.700
|1st backup for VHF frequency for Southeast Region*
|-
|NET Team 15
|PNTM15
|415
|115
|431.725
|Teams using FRS Ch. 15
|-
|NET Team 16
|PNTM16
|416
|116
|431.750
|Teams using FRS Ch. 16
|-
|NET Team 17
|PNTM17
|417
|117
|431.775
|Teams using FRS Ch. 17
|-
|NET Team 18
|PNTM18
|418
|118
|431.800
|Teams using FRS Ch. 18
|-
|NET Team 19
|PNTM19
|419
|119
|431.825
|Teams using FRS Ch. 19
|-
|NET Team 20
|PNTM20
|420
|120
|431.850
|2nd backup for VHF frequency for Alameda North,
Alameda South, and New Northeast Regions*
|-
|NET Team 21
|PNTM21
|421
|121
|431.875
|2nd backup for VHF frequency for Columbia,
Outer East and River North Regions*
|-
|NET Team 22
|PNTM22
|422
|122
|431.900
|2nd backup for VHF frequency for River South,
Southeast and Westside Regions*
|}
Large and Small refer to Standard and MHT [https://www.multnomahares.org/resources/frequency-lists-and-radio-programming-templates/ Multnomah County ARES frequency templates]

<nowiki>*</nowiki> No teams appear to be currently using the corresponding FRS/GMRS channel so the 70-cm Amateur Radio frequency should be available for regional use during a deployment.

Citywide Deployment Exercise

2025-11-24T17:31:30Z

BruceSchafer: /* After Action Reports */ Updated link with GoogleDriveLink format

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

The '''last exercise''' was held on Saturday, May 31, 2025 from 1 to 4 pm. We expect to hold the next one on Sunday, November 9, 2025 from 1-4PM.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =

== After Action Reports ==

* [https://portlandprepares.org/wp-content/uploads/2021/07/Spring-CDE-After-Action-Report.pdf May 15, 2021]
* {{GoogleDriveLink|id=1qGa0YKFCf8kgKQdDdqt9IaLzfDXekill|name=November 7, 2021}}
* [https://portlandprepares.org/wp-content/uploads/2022/05/Spring-2022-After-Action-Report.pdf May 7, 2022]
* [https://portlandprepares.org/wp-content/uploads/2022/11/Fall-2022-CDE-After-Action-Report.docx.pdf October 22, 2022]
* [https://portlandprepares.org/wp-content/uploads/2023/05/After-Action-Report-Spring-23.pdf May 13, 2023]
* [https://portlandprepares.org/wp-content/uploads/2023/11/Fall-2023.pdf October 8, 2023]
* {{GoogleDriveLink|id=1hMVwZCYGgiMu3sS3cBjWkRxJlgx63vN_|name=April 27, 2024}}
* {{GoogleDriveLink|id=1-YNBzr7CyktkwTtOUEJyDvPwoNNPi2_N|name=October 30, 2024}}
* {{GoogleDriveLink|id=1vm2ZAStopGFCqi8vBmBNm0YL0927_C6W|name=May 31, 2025}}
* {{GoogleDriveLink|id=1uEqiwKSc_mSoduBLbMXfDArQpX99MScO|name=November 9, 2025}}

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms Forms] (PBEM Wiki page describing and providing links to all approved forms.)
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf ITL Instructions] (Instructions for Incident Team Leaders)

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook}} (Instructions for Proctors)
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Citywide Deployment Exercise

2025-11-24T17:30:00Z

BruceSchafer: /* After Action Reports */ Added latest AAR

Twice each year, Portland NET teams participate in a Citywide Deployment Exercise (CDE). This helps us improve our skills, make important revisions to our Operations & Communications Plans, and inform our training plans.

The '''last exercise''' was held on Saturday, May 31, 2025 from 1 to 4 pm. We expect to hold the next one on Sunday, November 9, 2025 from 1-4PM.

[https://secure.givelively.org/donate/friends-of-portland-net/citywide-deployment-exercises-cde Donate to Support the Citywide Deployment Exercises]

These exercises were created and orchestrated by NET volunteers. If you have questions or suggestions, or if you’d like to be part of the next planning committee, email {{EmailLink|addr=NETDeploymentExercise@gmail.com|name=NETDeploymentExercise@gmail.com}}.

= Preparation =

== Recordings of NET Training Sessions Relevant to Deployment Exercise ==

* [https://portlandnet.tumblr.com/post/799491704971476992/net-citywide-deployment-exercise NET Citywide Deployment Exercise, November 2025 Training Preparation Series]
* [https://portlandnet.tumblr.com/post/743253357230211072/20240221-citywide-deployment-exercise-cde Light Search and Rescue Operations — New in February 2024]
* [https://portlandnet.tumblr.com/post/650539519121260544/20210430-cde-roles-of-the-itl-scribe-radio The Roles of the ITL, Scribe, FRS Radio Lead and Zoom Tips]
* [https://portlandnet.tumblr.com/post/650501951283429376/20210505-44-citywide-deployment-exercise The Role of the Incident Team Leader]
* [https://portlandnet.tumblr.com/post/651084268008865792/20210512-45-cde-frs-radio-communications-and FRS Radio Lead, Message Handling and A Radio Play In One Act]
* [https://portlandnet.tumblr.com/post/652982241275838464/20210602-47-integrating-frsgmrs-and-amateur Integrating FRS/GMRS and Amateur Radio Communications]
* [https://portlandnet.tumblr.com/post/657553129867509760/20210721-52-management-of-suvs-spontaneous Management of SUVs (Spontaneous Untrained Volunteers)]
* [https://portlandnet.tumblr.com/post/666049132608339968/20211020-55-deployment-shift-management-cde Deployment Shift Management]
* [https://portlandnet.tumblr.com/post/666762120092893184/20211027-56-personnel-accountability Personnel Accountability]
* [https://portlandnet.tumblr.com/post/666931161511215104/20211103-57-triage-site-management Triage Site Management]
* [https://portlandnet.tumblr.com/post/682807738534903808/20220427-68-using-ics-forms-in-the-field Using NET ICS Forms in the Field]
* [https://portlandnet.tumblr.com/post/683422346722295808/20220504-69-setting-up-a-medical-triage-area Setting Up a Medical Treatment Area]
* [https://portlandnet.tumblr.com/post/683826722453520384/20220507-citywide-deployment-exercise-cde]

Forms:

* Video: [https://youtu.be/ka3xXu7J4PE Using Form 1B — Individual Situation Report *]
* Video: [https://youtu.be/KPniq_hMVz0 Using Form 1C — Team Situation Report *]
* {{GoogleDriveLink|id=1IXwY8oSAfyBSURKjRS4atw8UFFJ6Ddfn|name=Written Instructions on above Forms}}
* [https://tinyurl.com/pdx-net-pbem-forms Link to all approved NET Forms]

<nowiki>*</nowiki> These videos refer to the forms as experimental because they were when the videos were created in 2019. They were approved by PBEM during the summer of 2022.

== Skill Refreshers ==

Read these skill refreshers before the exercise.

* [https://docs.google.com/document/d/107nl7IXadBWTam3iMKGJ3KSHUKkH_CAM9Azi9Tz-QiQ/edit?usp=sharing ICS Structure Refresher]
* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms ICS Forms Refresher]
* {{GoogleDriveLink|id=1ZfozJWBFLBClAL2vVfZro5BNlCpUEsDPpO68aqSn7G0|name=Volunteer Management Refresher}}

== Cheat Sheets ==

Sometimes our brains get a little mushy when we’re presented with a high-stress situation (like a major earthquake). Keep these handy cheat sheets in your pack to help you remember your training!

* {{GoogleDriveLink|id=1uCFmxXamTwXMgwA_7Vwj4K7-XZ23QtMP|name=Amateur Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=1-iA3cdWrJ2n1B4zvjvQ0I28-0YcmyWx4OgO4c2py1sM|name=FRS Radio Voice Procedure Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqWkdDU3JZQUtYdENOY0hoWS1vRVVWVFppOTg0|name=ICS Forms Cheat}}
* {{GoogleDriveLink|id=0B_aKchyb1gDqUUxMbUNHRDVuQU5nempqcnpvazdpSlhRbFRz|name=ICS Staffing Recommendations Cheat}}
* {{GoogleDriveLink|id=16GNm2lvN4eigx6Y7-4Bg4GTvZQrnwkAN|name=Mission Sequence Cheat}}
* {{GoogleDriveLink|id=1S9u3hKVNVjdvIUqSMPmUhDm0BDJ4cRnOtsx-mYOxkwg|name=Phonetic Alphabet Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jZlNnUU5IS04zaDQ|name=Triage Cheat}}
* {{GoogleDriveLink|id=0ByYCXGDZLM4jeXd2ZmZWZ1hsTGM|name=Patient Assessment Cheat}}
* {{GoogleDriveLink|id=0ByFa8oKZ_b6fYU1BZ0o2TDRrQmM|name=CERT Scott’s Cheats}}

== Other Resources ==

Here are some other tools your team may find useful in planning and preparing for the exercise:

* [http://pdx.maps.arcgis.com/apps/webappviewer/index.html?id=57d23ac6eaf94c9784b31231dd710a2f PBEM GIS Mapping Tool] – This interactive map shows neighborhood boundaries, schools, hospitals, URM buildings, and hazards and may be useful for planning training scenarios. You’ll need to zoom in to see details.

If you have additional deployment resources to share, email them to {{EmailLink|addr=netdeploymentexercise@gmail.com|name=netdeploymentexercise@gmail.com}}

= Previous Exercises =

== After Action Reports ==

* [https://portlandprepares.org/wp-content/uploads/2021/07/Spring-CDE-After-Action-Report.pdf May 15, 2021]
* {{GoogleDriveLink|id=1qGa0YKFCf8kgKQdDdqt9IaLzfDXekill|name=November 7, 2021}}
* [https://portlandprepares.org/wp-content/uploads/2022/05/Spring-2022-After-Action-Report.pdf May 7, 2022]
* [https://portlandprepares.org/wp-content/uploads/2022/11/Fall-2022-CDE-After-Action-Report.docx.pdf October 22, 2022]
* [https://portlandprepares.org/wp-content/uploads/2023/05/After-Action-Report-Spring-23.pdf May 13, 2023]
* [https://portlandprepares.org/wp-content/uploads/2023/11/Fall-2023.pdf October 8, 2023]
* {{GoogleDriveLink|id=1hMVwZCYGgiMu3sS3cBjWkRxJlgx63vN_|name=April 27, 2024}}
* {{GoogleDriveLink|id=1-YNBzr7CyktkwTtOUEJyDvPwoNNPi2_N|name=October 30, 2024}}
* {{GoogleDriveLink|id=1vm2ZAStopGFCqi8vBmBNm0YL0927_C6W|name=May 31, 2025}}
* [https://drive.google.com/file/d/1uEqiwKSc_mSoduBLbMXfDArQpX99MScO/view?usp=sharing November 9, 2025]

== Exercise Materials ==

These materials are intended for Exercise Coordinators and Amateur Radio Operators who are planning the exercise for their team.

* [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms Forms] (PBEM Wiki page describing and providing links to all approved forms.)
* [https://portlandprepares.org/wp-content/uploads/2021/05/ITL-Instructions.pdf ITL Instructions] (Instructions for Incident Team Leaders)

* {{GoogleDriveLink|id=1iAQXILf9oRqBUKMjDc3jOTxqowZNYIpr|name=Exercise Coordinators Handbook}} (Instructions for Proctors)
* {{GoogleDriveLink|id=1WBMnqpTWnj7lIJe2CBZPzFD5zc3zWy8a|name=Global Exercise Materials}} (Google folder containing training refreshers, email templates, forms, and more)
* [https://docs.google.com/document/d/1EVBULNRzsgYclqnMSKgEOi0aS1FrVM97jJKFH_0YOk4/edit?usp=sharing Exercise Coordinator Guidebook] (Tips and timeline to help Exercise Coordinators prepare for the exercise)
* {{GoogleDriveLink|id=1gm1QyZSCj-xTxBT2-bydhv34RPlQNfkXu2vpDitKfkQ|name=NET Deployment Best Practices}} (Tips from many NET teams covering all aspects of deployment, including command post setup, resource tracking, volunteer management, radio communications and more!)
* {{GoogleDriveLink|id=1NSRttElvWJOqT5XhiQHgMygcOlcZbHXh|name=Radio Operator Materials}} (ARO exercise instructions, training presentation slides, etc.)

== Photos ==

<gallery>
CDE 2023 Oct.jpg|Oct 2023|link=https://docs.google.com/document/d/1S6KPtTJ6ighTilFKb5y0PH2HVRp-kfTYt8CAvEz_1Rg/edit?usp=sharing
CDE 2023 May.jpg|May 2023|link=https://docs.google.com/document/d/1_it_36a7rsJddeH8AEqLmSFlR-HkLm6hzaAOnMiL6yU/edit?usp=sharing
CDE 2019 Oct.jpg|Oct 2019|link=https://photos.google.com/u/1/share/AF1QipPaNVTzfR6n4LdXGB1MZmvreEMraow8--3KawCuWcT8dgSbal3MI178qebhnXqXNA?key=OHJld05DYlh0QjBuMXotUTJ3UlRhMW95NXhNNHhn
CDE 2019 Apr.jpg|Apr 2019|link=https://photos.app.goo.gl/64wC1fcNJQy4tQiZ6
CDE 2018 Oct.jpg|Oct 2018|link=https://photos.google.com/share/AF1QipP4207Ck_3vQoTlHR5LJBnKkyXxhp1EhbvGJjDh0POh37d6iyDP5-OmXKLBrxyaAQ?key=bmVBZXM3Y3poaFFmOGUyZGJLb3dZNGxrd1BTcDh3
CDE 2018 Apr.jpg|Apr 2018|link=https://photos.app.goo.gl/7oQWwueCniknflBj1
CDE 2017 Oct.jpg|Oct 2017|link=https://photos.app.goo.gl/gvUKASnv6sVtzksA3
CDE 2017 Jul.jpg|Jul 2017|link=https://photos.app.goo.gl/SiSxNpGwzxWRkn1n1
</gallery>

Obtaining an Amateur Radio License

2025-11-20T19:07:46Z

BruceSchafer: Replaced word

There are three levels of Amateur Radio licenses in the United States:

* Technician
* General
* Extra
The Amateur Radio community and the FCC cooperate to develop large pools of questions for each of the license exams. A particular exam will have a random selection of questions from the corresponding pool. These question pools are updated every few years and the exams therefore change, making exam manuals and online courses somewhat outdated until they are updated to match the new question pool.

There are a variety of resources available that will help you obtain an FCC Amateur Radio License.

=== '''Books''' ===
* [https://home.arrl.org/action/Shop/Products#filter=%7B%22Facet%22%3Anull,%22SubFacet%22%3Anull,%22Category%22%3A%7B%22Name%22%3A%22Licensing%22,%22Value%22%3A%22LICENSING%22%7D,%22SubCategory%22%3Anull%7D&searchTerm=&searchItemNameTerm=&searchDescriptionTerm=&productClass= ARRL books]
* [https://www.gordonwestradioschool.com/main/page_w5yi_training_resources.html Gordon West books]

Note: The Technician License exam question pool changed on July 1, 2022 with about 25% new or revised questions. If you have a Technician license exam book that was published before the question pool changed, you want to buy or borrow a newer edition.

=== '''Classes''' ===
* [https://docs.google.com/document/d/1y4jPSAD3oEaityDMZJdXFZkIMS4jht_hoxvJW6E9OWg/edit Portland NET Technician “exam cram” held in the fall and spring] (Note: As of late 2025 these sessions have not be held for two years but we hope to resume them at some point.)
* [https://otvarc.org/services/education/ Oregon Tualatin Valley Amateur Radio Club]
* Recordings and slides from Technician Amateur Radio online license classes previously offered by Portland NET AROs.
** [https://drive.google.com/file/d/1ehr0DEaT1VzWt6RjhTTVBQd7zh6tkXrW/view?usp=drive_link Course Schedule]
** Session 1: [https://youtu.be/RcmOH63lM_o Video]
** Session 2, [https://youtu.be/1lzvVogHQzQ Video]
** Session 3, [https://youtu.be/1wrJV61GIck Video]
** Session 4, [https://youtu.be/voNXbvUenQU Video]
** Session 5, [https://youtu.be/71skdDYsyes Video]

* Amateur Radio license classes by Dave Casler, KE0OG
** [https://learn.arrl.org/courses/?pathPage=%2Farrl%2Fcourses%2F35902 Technician]
** [https://learn.arrl.org/courses/?pathPage=%2Farrl%2Fcourses%2F36256 General]
** [https://learn.arrl.org/courses/?pathPage=%2Farrl%2Fcourses%2F37720 Extra]
Note: These online courses require that you be a member of ARRL and sign in.
* Amateur Radio license classes by Gary, W4EEY
** [https://www.youtube.com/playlist?list=PLZ_9BZQ8gpzhaGSV3CmTjNkPWFCDMe0xJ Technician]
** [https://www.youtube.com/playlist?list=PLZ_9BZQ8gpzg-3DOjH18r2XWiTomBar3y General]
** [https://www.youtube.com/playlist?list=PLZ_9BZQ8gpzidcIsQVA__Gz-uzxo1uyTb Extra]

=== '''Amateur Radio License Practice Exams''' ===
* You may find it helpful to take some practice exams in advance of taking an actual exam. These are available free from HamStudy.org. You will find the information at [https://hamstudy.org/tech2022 hamstudy.org/tech2022]
* There are two types of practicing:
** Study mode: You are given a sequence of questions from the pool of questions. When you answer a question incorrectly you will see the same question again later.
** Practice exams: You are given 35 questions that are randomly selected from the question pool just like an actual exam. After you complete the 35 questions you are given your score. You can then take a different exam made up of a different random selection of questions and continue that process until you're confident you're ready to take an actual exam.
* For a more complete and accurate explanation see [https://blog.hamstudy.org/faq/ blog.hamstudy.org/faq]

* [https://www.qrz.com/ QRZ.com] has study material and online flashcards
* FCC license exams (Technician, General and Amateur Extra)
** Online exams given by Oregon volunteers. See [https://aa7hw.org/ aa7hw.org]
** Portland NET. See [https://tinyurl.com/PNET-Ham-Exam tinyurl.com/PNET-Ham-Exam]
** Online exams given by groups around the country. See [https://hamstudy.org/sessions/remote hamstudy.org/sessions/remote]
** [https://otvarc.org/services/amateur-exams/ Oregon Tualatin Valley Amateur Radio Club first Saturday of each month except in June when it’s at SEA-PAC in Seaside]

Obtaining an Amateur Radio License

2025-11-20T19:06:55Z

BruceSchafer: Added note

There are three levels of Amateur Radio licenses in the United States:

* Technician
* General
* Extra
The Amateur Radio community and the FCC cooperate to develop large pools of questions for each of the license exams. A particular exam will have a random selection of questions from the corresponding pool. These question pools are updated every few years and the exams therefore change, making exam manuals and online courses somewhat outdated until they are updated to match the new question pool.

There are a variety of resources available that will help you obtain an FCC Amateur Radio License.

=== '''Books''' ===
* [https://home.arrl.org/action/Shop/Products#filter=%7B%22Facet%22%3Anull,%22SubFacet%22%3Anull,%22Category%22%3A%7B%22Name%22%3A%22Licensing%22,%22Value%22%3A%22LICENSING%22%7D,%22SubCategory%22%3Anull%7D&searchTerm=&searchItemNameTerm=&searchDescriptionTerm=&productClass= ARRL books]
* [https://www.gordonwestradioschool.com/main/page_w5yi_training_resources.html Gordon West books]

Note: The Technician License exam question pool changed on July 1, 2022 with about 25% new or revised questions. If you have a Technician license exam book that was published before the question pool changed, you want to buy or borrow a newer edition.

=== '''Classes''' ===
* [https://docs.google.com/document/d/1y4jPSAD3oEaityDMZJdXFZkIMS4jht_hoxvJW6E9OWg/edit Portland NET Technician “exam cram” held in the fall and spring] (Note: As of late 2025 these sessions have not be held for several years but we hope to resume them at some point.)
* [https://otvarc.org/services/education/ Oregon Tualatin Valley Amateur Radio Club]
* Recordings and slides from Technician Amateur Radio online license classes previously offered by Portland NET AROs.
** [https://drive.google.com/file/d/1ehr0DEaT1VzWt6RjhTTVBQd7zh6tkXrW/view?usp=drive_link Course Schedule]
** Session 1: [https://youtu.be/RcmOH63lM_o Video]
** Session 2, [https://youtu.be/1lzvVogHQzQ Video]
** Session 3, [https://youtu.be/1wrJV61GIck Video]
** Session 4, [https://youtu.be/voNXbvUenQU Video]
** Session 5, [https://youtu.be/71skdDYsyes Video]

* Amateur Radio license classes by Dave Casler, KE0OG
** [https://learn.arrl.org/courses/?pathPage=%2Farrl%2Fcourses%2F35902 Technician]
** [https://learn.arrl.org/courses/?pathPage=%2Farrl%2Fcourses%2F36256 General]
** [https://learn.arrl.org/courses/?pathPage=%2Farrl%2Fcourses%2F37720 Extra]
Note: These online courses require that you be a member of ARRL and sign in.
* Amateur Radio license classes by Gary, W4EEY
** [https://www.youtube.com/playlist?list=PLZ_9BZQ8gpzhaGSV3CmTjNkPWFCDMe0xJ Technician]
** [https://www.youtube.com/playlist?list=PLZ_9BZQ8gpzg-3DOjH18r2XWiTomBar3y General]
** [https://www.youtube.com/playlist?list=PLZ_9BZQ8gpzidcIsQVA__Gz-uzxo1uyTb Extra]

=== '''Amateur Radio License Practice Exams''' ===
* You may find it helpful to take some practice exams in advance of taking an actual exam. These are available free from HamStudy.org. You will find the information at [https://hamstudy.org/tech2022 hamstudy.org/tech2022]
* There are two types of practicing:
** Study mode: You are given a sequence of questions from the pool of questions. When you answer a question incorrectly you will see the same question again later.
** Practice exams: You are given 35 questions that are randomly selected from the question pool just like an actual exam. After you complete the 35 questions you are given your score. You can then take a different exam made up of a different random selection of questions and continue that process until you're confident you're ready to take an actual exam.
* For a more complete and accurate explanation see [https://blog.hamstudy.org/faq/ blog.hamstudy.org/faq]

* [https://www.qrz.com/ QRZ.com] has study material and online flashcards
* FCC license exams (Technician, General and Amateur Extra)
** Online exams given by Oregon volunteers. See [https://aa7hw.org/ aa7hw.org]
** Portland NET. See [https://tinyurl.com/PNET-Ham-Exam tinyurl.com/PNET-Ham-Exam]
** Online exams given by groups around the country. See [https://hamstudy.org/sessions/remote hamstudy.org/sessions/remote]
** [https://otvarc.org/services/amateur-exams/ Oregon Tualatin Valley Amateur Radio Club first Saturday of each month except in June when it’s at SEA-PAC in Seaside]

Logging Procedures for Subnet Control Operators

2025-11-08T18:35:25Z

BruceSchafer: Updated link to ICS 214 and to its instructinos

The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately. A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.

Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.

* [[Media:ICS-214 Unit Log Fillable.pdf|NET Version of ICS 214 Unit Log]]
* NET Form 6 and the similar ICS 309 Communications Log
** [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] for logging transmission of NET Form 8 or other forms by voice.
** ICS Form 309 for Winlink traffic which can be [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generated by Winlink Express]]
* [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]]. This is an unofficial form that should help you capture information about the stations participating in your subnet more efficiently than the above two forms.
* [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]]. This unofficial form should help you keep track of counts of the traffic that the stations in your region have ready to transmit as well as traffic that you have already handled.

Note: For some short exercises you may not need all four forms. For instance, if you are serving as an SNC during an exercise that does not involve formal traffic you would not need to use Form 6 or a Traffic Count Worksheet.

=== Background ===
The [[Media:ICS-214 Unit Log Fillable.pdf|NET Version of ICS 214 Unit Log]] is designed to record a roster of those involved in a particular unit and the activities of those people. The form’s header provides space for recording the incident name, date and time, leadership and operational period. Below the header are rows for recording a roster of those associated with a particular unit, in this case a communications unit. The lower part of the form is for recording the activities of the unit. This makes it useful for providing information about what happened and when – both for those who participated in those activities and those who arrive later. In addition, the information is useful for those interested in reviewing the activities of the unit and looking for opportunities for improving readiness and efficiency for similar future activities.

The [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] is based on the ICS 309 Communication Log form which is intended primarily for logging formal traffic - messages on forms. Limiting its use to such traffic should provide two benefits:

* The station’s operator should be able to more easily find records of forms previously transmitted, especially when a reply to such a form is about to be received.
* Those reviewing the logs later are more likely to have a clear picture of what messages were sent and received by the station.

The [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] is an unofficial form designed to complement the two forms discussed above to help keep track of the stations that communication unit is in contact with as well as information like the readability of the radio communications with those stations. As it is not an official ICS form, it can be customized to the particular situation. In a pinch, use scratch paper instead. Using this form instead of recording check-ins on Form 6 or 214 will use less space and keep the information about each station together for easy reference.

The [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] is an experimental form for tracking counts of available formal messages as well as counts of messages handled so far. Feel free to customize it to meet your needs. The goal is to handle traffic based on precedence and give all stations in your region a chance to pass traffic that is equal to the precedence being passed by other stations. The worksheet should help you handle the available traffic by relative precedence and keep track of available traffic that you have not yet handled.

=== Instructions for using the [[Media:ICS-214 Unit Log Fillable.pdf|NET Version of the ICS 214 Unit Log]] ===

* Each NET SNC should use ICS Form 214 to record the activities of their station. In other situations like a radio trailer or radio room, multiple stations and operators at the same location are all part of the same Communications Unit and would share a single ICS Form 214. Similarly, multiple operators working together at a remote site like an evacuation center would share a Form 214..
* Log your name and the date and time your station’s activation at the top.
* Also record your Name and Time In in the roster section. Do the same for any other operators or scribes serving with you.
* Record “ICS Position” as “Amateur Radio Operator” or "Scribe" or an abbreviation like “ARO” or "ARO Scribe".
* Record “Home Base” as “Portland NET”.
* When someone goes off during, record the time in “Time Out”
* If the incident command declares a new operational period, close the 214 and open a new one.
* When a station is closed or a new operational period starts, log the closing as the last item in Major Events.
* See
[[Media:ICS Form 214 Unit Log NET Instructions.pdf|Instructions for NET version of ICS Form 214 Unit Log]] for additional details.
* See the following sample ICS 214.
[[File:ICS 214 SNC Sample.png|500px]]

=== Overview of using [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) Communication Log ===

* Use NET Form 6 / ICS 309 for formal traffic only, not activities. One Form 6 should be used by each operator.
* Subnet controllers should record most activities on an ICS 214 rather than the NET Form 6 or ICS 309 with the following exceptions:
** Check-ins, readability, etc. should go on the [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] or scratch paper.
** Message counts should go on a [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] or scratch paper.
* Use Winlink Express to [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generate an ICS 309 PDF]] for any Winlink traffic.
[[File:Sample Form 6 SNC.png|500px]]

=== Instructions for Using a [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) for Logging NET Form 8s or ICS Form 213s ===

* When a NET Form 8 is being logged, the right-hand field should start with the tactical call sign of the originating station, which may be the same as the team name.
* The originating station is followed by the date and time from the fields on the Form 8, followed by the Subject field from the Form 8.
* The Subject of a Form 8 should begin with message precedence, which should be copied into the right-hand field with the rest of the subject.
* For replies, the word “Reply” should be first followed by the information in the same column for the original message.
* FCC call signs should not be used in the From and To fields of NET Form 6 (ICS 309) , Instead use tactical call signs as illustrated below.
* In the example above the transmission of the messages that originated from North Heights and South Heights to ECC and the receipt of traffic from ECC are not shown here because they were transmitted via Winlink which can generate a separate log.

=== Instructions for using [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] ===

* Each time a station checks in, record the time, the station’s tactical call sign and the operator’s FCC call sign.
* If the operator is representing a team at a staging area, record the name of the team.
** Note: During some exercises, several teams combine to participate in the exercise. You do not need to record the names of all the NET teams or Portland neighborhoods representing at the staging area. ''Record only the name of the neighborhood or team that is hosting the combined teams during the exercise.''
* Also record the station’s readability. See [[Readability and Signal Strength]].
* When the station checks out, record that time in the corresponding column.

[[File:SNC's Stations Participating Form.png|500px]]

=== Instructions for using the [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] ===

* Each time a station reports available traffic, use a new row to record the number of messages available at each precedence level.
* Each time you handle a message for that station, use a tally mark to indicate an increase in the number messages handled at the message’s precedence level. For instance, if one Priority message was previously handled for a station and you just handled a second one, the tally in the Handled column for Priority messages would change from “l” to “ll”. See the [[wikipedia:Tally_marks|Wikipedia article on Tally Marks]] for a discussion of tally marks.
* If a station provides new counts of available traffic, start a new row and draw a line through the row that is now out of date.
* Start a new Worksheet for each shift or when worksheet has become obsolete.
* See the following sample worksheet.
[[File:Sample Traffic Count Worksheet.png|500px]]

Logging Procedures for Subnet Control Operators

2025-11-08T18:23:30Z

BruceSchafer: /* Instructions for using the Traffic Count Worksheet */

The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately. A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.

Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.

* [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 – Unit Log]
* NET Form 6 and the similar ICS 309 Communications Log
** [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] for logging transmission of NET Form 8 or other forms by voice.
** ICS Form 309 for Winlink traffic which can be [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generated by Winlink Express]]
* [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]]. This is an unofficial form that should help you capture information about the stations participating in your subnet more efficiently than the above two forms.
* [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]]. This unofficial form should help you keep track of counts of the traffic that the stations in your region have ready to transmit as well as traffic that you have already handled.

Note: For some short exercises you may not need all four forms. For instance, if you are serving as an SNC during an exercise that does not involve formal traffic you would not need to use Form 6 or a Traffic Count Worksheet.

=== Background ===
The [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 Unit Log form] is designed to record a roster of those involved in a particular unit and the activities of those people. The form’s header provides space for recording the incident name, date and time, leadership and operational period. Below the header are rows for recording a roster of those associated with a particular unit, in this case a communications unit. The lower part of the form is for recording the activities of the unit. This makes it useful for providing information about what happened and when – both for those who participated in those activities and those who arrive later. In addition, the information is useful for those interested in reviewing the activities of the unit and looking for opportunities for improving readiness and efficiency for similar future activities.

The [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] is based on the ICS 309 Communication Log form which is intended primarily for logging formal traffic - messages on forms. Limiting its use to such traffic should provide two benefits:

* The station’s operator should be able to more easily find records of forms previously transmitted, especially when a reply to such a form is about to be received.
* Those reviewing the logs later are more likely to have a clear picture of what messages were sent and received by the station.

The [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] is an unofficial form designed to complement the two forms discussed above to help keep track of the stations that communication unit is in contact with as well as information like the readability of the radio communications with those stations. As it is not an official ICS form, it can be customized to the particular situation. In a pinch, use scratch paper instead. Using this form instead of recording check-ins on Form 6 or 214 will use less space and keep the information about each station together for easy reference.

The [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] is an experimental form for tracking counts of available formal messages as well as counts of messages handled so far. Feel free to customize it to meet your needs. The goal is to handle traffic based on precedence and give all stations in your region a chance to pass traffic that is equal to the precedence being passed by other stations. The worksheet should help you handle the available traffic by relative precedence and keep track of available traffic that you have not yet handled.

=== Instructions for using an [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS Form 214] ===

* Each NET SNC should use ICS Form 214 to record the activities of their station. In other situations like a radio trailer or radio room, multiple stations and operators at the same location are all part of the same Communications Unit and would share a single ICS Form 214. Similarly, multiple operators working together at a remote site like an evacuation center would share a Form 214..
* Log your name and the date and time your station’s activation at the top.
* Also record your Name and Time In in the roster section. Do the same for any other operators or scribes serving with you.
* Record “ICS Position” as “Amateur Radio Operator” or "Scribe" or an abbreviation like “ARO” or "ARO Scribe".
* Record “Home Base” as “Portland NET”.
* When someone goes off during, record the time in “Time Out”
* If the incident command declares a new operational period, close the 214 and open a new one.
* When a station is closed or a new operational period starts, log the closing as the last item in Major Events.
* See [https://drive.google.com/file/d/1FhGwY9uo3D7FTATwe7aqgQ30Welx2kL0/view?usp=share_link ICS 214 Unit Log Instructions] for additional details.
* See the following sample ICS 214.
[[File:ICS 214 SNC Sample.png|500px]]

=== Overview of using [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) Communication Log ===

* Use NET Form 6 / ICS 309 for formal traffic only, not activities. One Form 6 should be used by each operator.
* Subnet controllers should record most activities on an ICS 214 rather than the NET Form 6 or ICS 309 with the following exceptions:
** Check-ins, readability, etc. should go on the [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] or scratch paper.
** Message counts should go on a [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] or scratch paper.
* Use Winlink Express to [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generate an ICS 309 PDF]] for any Winlink traffic.
[[File:Sample Form 6 SNC.png|500px]]

=== Instructions for Using a [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) for Logging NET Form 8s or ICS Form 213s ===

* When a NET Form 8 is being logged, the right-hand field should start with the tactical call sign of the originating station, which may be the same as the team name.
* The originating station is followed by the date and time from the fields on the Form 8, followed by the Subject field from the Form 8.
* The Subject of a Form 8 should begin with message precedence, which should be copied into the right-hand field with the rest of the subject.
* For replies, the word “Reply” should be first followed by the information in the same column for the original message.
* FCC call signs should not be used in the From and To fields of NET Form 6 (ICS 309) , Instead use tactical call signs as illustrated below.
* In the example above the transmission of the messages that originated from North Heights and South Heights to ECC and the receipt of traffic from ECC are not shown here because they were transmitted via Winlink which can generate a separate log.

=== Instructions for using [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] ===

* Each time a station checks in, record the time, the station’s tactical call sign and the operator’s FCC call sign.
* If the operator is representing a team at a staging area, record the name of the team.
** Note: During some exercises, several teams combine to participate in the exercise. You do not need to record the names of all the NET teams or Portland neighborhoods representing at the staging area. ''Record only the name of the neighborhood or team that is hosting the combined teams during the exercise.''
* Also record the station’s readability. See [[Readability and Signal Strength]].
* When the station checks out, record that time in the corresponding column.

[[File:SNC's Stations Participating Form.png|500px]]

=== Instructions for using the [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] ===

* Each time a station reports available traffic, use a new row to record the number of messages available at each precedence level.
* Each time you handle a message for that station, use a tally mark to indicate an increase in the number messages handled at the message’s precedence level. For instance, if one Priority message was previously handled for a station and you just handled a second one, the tally in the Handled column for Priority messages would change from “l” to “ll”. See the [[wikipedia:Tally_marks|Wikipedia article on Tally Marks]] for a discussion of tally marks.
* If a station provides new counts of available traffic, start a new row and draw a line through the row that is now out of date.
* Start a new Worksheet for each shift or when worksheet has become obsolete.
* See the following sample worksheet.
[[File:Sample Traffic Count Worksheet.png|500px]]

Logging Procedures for Subnet Control Operators

2025-11-08T18:22:50Z

BruceSchafer: /* Overview of using NET Form 6 (ICS 309) Communication Log */ Updated link to Traffic Count Worksheet

The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately. A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.

Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.

* [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 – Unit Log]
* NET Form 6 and the similar ICS 309 Communications Log
** [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] for logging transmission of NET Form 8 or other forms by voice.
** ICS Form 309 for Winlink traffic which can be [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generated by Winlink Express]]
* [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]]. This is an unofficial form that should help you capture information about the stations participating in your subnet more efficiently than the above two forms.
* [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]]. This unofficial form should help you keep track of counts of the traffic that the stations in your region have ready to transmit as well as traffic that you have already handled.

Note: For some short exercises you may not need all four forms. For instance, if you are serving as an SNC during an exercise that does not involve formal traffic you would not need to use Form 6 or a Traffic Count Worksheet.

=== Background ===
The [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 Unit Log form] is designed to record a roster of those involved in a particular unit and the activities of those people. The form’s header provides space for recording the incident name, date and time, leadership and operational period. Below the header are rows for recording a roster of those associated with a particular unit, in this case a communications unit. The lower part of the form is for recording the activities of the unit. This makes it useful for providing information about what happened and when – both for those who participated in those activities and those who arrive later. In addition, the information is useful for those interested in reviewing the activities of the unit and looking for opportunities for improving readiness and efficiency for similar future activities.

The [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] is based on the ICS 309 Communication Log form which is intended primarily for logging formal traffic - messages on forms. Limiting its use to such traffic should provide two benefits:

* The station’s operator should be able to more easily find records of forms previously transmitted, especially when a reply to such a form is about to be received.
* Those reviewing the logs later are more likely to have a clear picture of what messages were sent and received by the station.

The [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] is an unofficial form designed to complement the two forms discussed above to help keep track of the stations that communication unit is in contact with as well as information like the readability of the radio communications with those stations. As it is not an official ICS form, it can be customized to the particular situation. In a pinch, use scratch paper instead. Using this form instead of recording check-ins on Form 6 or 214 will use less space and keep the information about each station together for easy reference.

The [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] is an experimental form for tracking counts of available formal messages as well as counts of messages handled so far. Feel free to customize it to meet your needs. The goal is to handle traffic based on precedence and give all stations in your region a chance to pass traffic that is equal to the precedence being passed by other stations. The worksheet should help you handle the available traffic by relative precedence and keep track of available traffic that you have not yet handled.

=== Instructions for using an [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS Form 214] ===

* Each NET SNC should use ICS Form 214 to record the activities of their station. In other situations like a radio trailer or radio room, multiple stations and operators at the same location are all part of the same Communications Unit and would share a single ICS Form 214. Similarly, multiple operators working together at a remote site like an evacuation center would share a Form 214..
* Log your name and the date and time your station’s activation at the top.
* Also record your Name and Time In in the roster section. Do the same for any other operators or scribes serving with you.
* Record “ICS Position” as “Amateur Radio Operator” or "Scribe" or an abbreviation like “ARO” or "ARO Scribe".
* Record “Home Base” as “Portland NET”.
* When someone goes off during, record the time in “Time Out”
* If the incident command declares a new operational period, close the 214 and open a new one.
* When a station is closed or a new operational period starts, log the closing as the last item in Major Events.
* See [https://drive.google.com/file/d/1FhGwY9uo3D7FTATwe7aqgQ30Welx2kL0/view?usp=share_link ICS 214 Unit Log Instructions] for additional details.
* See the following sample ICS 214.
[[File:ICS 214 SNC Sample.png|500px]]

=== Overview of using [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) Communication Log ===

* Use NET Form 6 / ICS 309 for formal traffic only, not activities. One Form 6 should be used by each operator.
* Subnet controllers should record most activities on an ICS 214 rather than the NET Form 6 or ICS 309 with the following exceptions:
** Check-ins, readability, etc. should go on the [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] or scratch paper.
** Message counts should go on a [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] or scratch paper.
* Use Winlink Express to [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generate an ICS 309 PDF]] for any Winlink traffic.
[[File:Sample Form 6 SNC.png|500px]]

=== Instructions for Using a [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) for Logging NET Form 8s or ICS Form 213s ===

* When a NET Form 8 is being logged, the right-hand field should start with the tactical call sign of the originating station, which may be the same as the team name.
* The originating station is followed by the date and time from the fields on the Form 8, followed by the Subject field from the Form 8.
* The Subject of a Form 8 should begin with message precedence, which should be copied into the right-hand field with the rest of the subject.
* For replies, the word “Reply” should be first followed by the information in the same column for the original message.
* FCC call signs should not be used in the From and To fields of NET Form 6 (ICS 309) , Instead use tactical call signs as illustrated below.
* In the example above the transmission of the messages that originated from North Heights and South Heights to ECC and the receipt of traffic from ECC are not shown here because they were transmitted via Winlink which can generate a separate log.

=== Instructions for using [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] ===

* Each time a station checks in, record the time, the station’s tactical call sign and the operator’s FCC call sign.
* If the operator is representing a team at a staging area, record the name of the team.
** Note: During some exercises, several teams combine to participate in the exercise. You do not need to record the names of all the NET teams or Portland neighborhoods representing at the staging area. ''Record only the name of the neighborhood or team that is hosting the combined teams during the exercise.''
* Also record the station’s readability. See [[Readability and Signal Strength]].
* When the station checks out, record that time in the corresponding column.

[[File:SNC's Stations Participating Form.png|500px]]

=== Instructions for using the [https://drive.google.com/file/d/10cVLW0D1HFXOXEX2_WJ7caQuyV9GVCwS/view?usp=drive_link Traffic Count Worksheet] ===

* Each time a station reports available traffic, use a new row to record the number of messages available at each precedence level.
* Each time you handle a message for that station, use a tally mark to indicate an increase in the number messages handled at the message’s precedence level. For instance, if one Priority message was previously handled for a station and you just handled a second one, the tally in the Handled column for Priority messages would change from “l” to “ll”. See the [[wikipedia:Tally_marks|Wikipedia article on Tally Marks]] for a discussion of tally marks.
* If a station provides new counts of available traffic, start a new row and draw a line through the row that is now out of date.
* Start a new Worksheet for each shift or when worksheet has become obsolete.
* See the following sample worksheet.
[[File:Sample Traffic Count Worksheet.png|500px]]

Logging Procedures for Subnet Control Operators

2025-11-08T18:22:01Z

BruceSchafer: /* Background */ Updated link to Traffic Count Worksheet

The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately. A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.

Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.

* [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 – Unit Log]
* NET Form 6 and the similar ICS 309 Communications Log
** [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] for logging transmission of NET Form 8 or other forms by voice.
** ICS Form 309 for Winlink traffic which can be [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generated by Winlink Express]]
* [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]]. This is an unofficial form that should help you capture information about the stations participating in your subnet more efficiently than the above two forms.
* [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]]. This unofficial form should help you keep track of counts of the traffic that the stations in your region have ready to transmit as well as traffic that you have already handled.

Note: For some short exercises you may not need all four forms. For instance, if you are serving as an SNC during an exercise that does not involve formal traffic you would not need to use Form 6 or a Traffic Count Worksheet.

=== Background ===
The [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 Unit Log form] is designed to record a roster of those involved in a particular unit and the activities of those people. The form’s header provides space for recording the incident name, date and time, leadership and operational period. Below the header are rows for recording a roster of those associated with a particular unit, in this case a communications unit. The lower part of the form is for recording the activities of the unit. This makes it useful for providing information about what happened and when – both for those who participated in those activities and those who arrive later. In addition, the information is useful for those interested in reviewing the activities of the unit and looking for opportunities for improving readiness and efficiency for similar future activities.

The [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] is based on the ICS 309 Communication Log form which is intended primarily for logging formal traffic - messages on forms. Limiting its use to such traffic should provide two benefits:

* The station’s operator should be able to more easily find records of forms previously transmitted, especially when a reply to such a form is about to be received.
* Those reviewing the logs later are more likely to have a clear picture of what messages were sent and received by the station.

The [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] is an unofficial form designed to complement the two forms discussed above to help keep track of the stations that communication unit is in contact with as well as information like the readability of the radio communications with those stations. As it is not an official ICS form, it can be customized to the particular situation. In a pinch, use scratch paper instead. Using this form instead of recording check-ins on Form 6 or 214 will use less space and keep the information about each station together for easy reference.

The [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]] is an experimental form for tracking counts of available formal messages as well as counts of messages handled so far. Feel free to customize it to meet your needs. The goal is to handle traffic based on precedence and give all stations in your region a chance to pass traffic that is equal to the precedence being passed by other stations. The worksheet should help you handle the available traffic by relative precedence and keep track of available traffic that you have not yet handled.

=== Instructions for using an [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS Form 214] ===

* Each NET SNC should use ICS Form 214 to record the activities of their station. In other situations like a radio trailer or radio room, multiple stations and operators at the same location are all part of the same Communications Unit and would share a single ICS Form 214. Similarly, multiple operators working together at a remote site like an evacuation center would share a Form 214..
* Log your name and the date and time your station’s activation at the top.
* Also record your Name and Time In in the roster section. Do the same for any other operators or scribes serving with you.
* Record “ICS Position” as “Amateur Radio Operator” or "Scribe" or an abbreviation like “ARO” or "ARO Scribe".
* Record “Home Base” as “Portland NET”.
* When someone goes off during, record the time in “Time Out”
* If the incident command declares a new operational period, close the 214 and open a new one.
* When a station is closed or a new operational period starts, log the closing as the last item in Major Events.
* See [https://drive.google.com/file/d/1FhGwY9uo3D7FTATwe7aqgQ30Welx2kL0/view?usp=share_link ICS 214 Unit Log Instructions] for additional details.
* See the following sample ICS 214.
[[File:ICS 214 SNC Sample.png|500px]]

=== Overview of using [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) Communication Log ===

* Use NET Form 6 / ICS 309 for formal traffic only, not activities. One Form 6 should be used by each operator.
* Subnet controllers should record most activities on an ICS 214 rather than the NET Form 6 or ICS 309 with the following exceptions:
** Check-ins, readability, etc. should go on the [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] or scratch paper.
** Message counts should go on a [https://docs.google.com/document/d/1FsFca0Yq1xIHZlihSXuZG-Fo5M-C8MzAfMyrGgdugH0/edit?usp=sharing Traffic Count Worksheet] or scratch paper.
* Use Winlink Express to [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generate an ICS 309 PDF]] for any Winlink traffic.
[[File:Sample Form 6 SNC.png|500px]]

=== Instructions for Using a [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) for Logging NET Form 8s or ICS Form 213s ===

* When a NET Form 8 is being logged, the right-hand field should start with the tactical call sign of the originating station, which may be the same as the team name.
* The originating station is followed by the date and time from the fields on the Form 8, followed by the Subject field from the Form 8.
* The Subject of a Form 8 should begin with message precedence, which should be copied into the right-hand field with the rest of the subject.
* For replies, the word “Reply” should be first followed by the information in the same column for the original message.
* FCC call signs should not be used in the From and To fields of NET Form 6 (ICS 309) , Instead use tactical call signs as illustrated below.
* In the example above the transmission of the messages that originated from North Heights and South Heights to ECC and the receipt of traffic from ECC are not shown here because they were transmitted via Winlink which can generate a separate log.

=== Instructions for using [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] ===

* Each time a station checks in, record the time, the station’s tactical call sign and the operator’s FCC call sign.
* If the operator is representing a team at a staging area, record the name of the team.
** Note: During some exercises, several teams combine to participate in the exercise. You do not need to record the names of all the NET teams or Portland neighborhoods representing at the staging area. ''Record only the name of the neighborhood or team that is hosting the combined teams during the exercise.''
* Also record the station’s readability. See [[Readability and Signal Strength]].
* When the station checks out, record that time in the corresponding column.

[[File:SNC's Stations Participating Form.png|500px]]

=== Instructions for using the [https://drive.google.com/file/d/10cVLW0D1HFXOXEX2_WJ7caQuyV9GVCwS/view?usp=drive_link Traffic Count Worksheet] ===

* Each time a station reports available traffic, use a new row to record the number of messages available at each precedence level.
* Each time you handle a message for that station, use a tally mark to indicate an increase in the number messages handled at the message’s precedence level. For instance, if one Priority message was previously handled for a station and you just handled a second one, the tally in the Handled column for Priority messages would change from “l” to “ll”. See the [[wikipedia:Tally_marks|Wikipedia article on Tally Marks]] for a discussion of tally marks.
* If a station provides new counts of available traffic, start a new row and draw a line through the row that is now out of date.
* Start a new Worksheet for each shift or when worksheet has become obsolete.
* See the following sample worksheet.
[[File:Sample Traffic Count Worksheet.png|500px]]

Logging Procedures for Subnet Control Operators

2025-11-08T18:21:06Z

BruceSchafer: Updated link to Traffic Count Worksheet

The primary purpose for logging is to keep track of the activities of your station to allow you to operate more efficiently and accurately. A secondary purpose is to record information that may be used later to identify opportunities for improving procedures. In some cases, logs may be gathered and compared in order to understand how messages moved from originating stations to their final destination by one or more “hops”. Similarly, logs can be used to understand how replies were routed during a deployment.

Because your role as a subnet controller (SNC) includes a variety of procedures, no one form efficiently covers everything you should log. I recommend you spread logging across the following four forms.

* [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 – Unit Log]
* NET Form 6 and the similar ICS 309 Communications Log
** [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] for logging transmission of NET Form 8 or other forms by voice.
** ICS Form 309 for Winlink traffic which can be [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generated by Winlink Express]]
* [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]]. This is an unofficial form that should help you capture information about the stations participating in your subnet more efficiently than the above two forms.
* [[Media:Traffic Count Worksheet.pdf|Traffic Count Worksheet]]. This unofficial form should help you keep track of counts of the traffic that the stations in your region have ready to transmit as well as traffic that you have already handled.

Note: For some short exercises you may not need all four forms. For instance, if you are serving as an SNC during an exercise that does not involve formal traffic you would not need to use Form 6 or a Traffic Count Worksheet.

=== Background ===
The [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS 214 Unit Log form] is designed to record a roster of those involved in a particular unit and the activities of those people. The form’s header provides space for recording the incident name, date and time, leadership and operational period. Below the header are rows for recording a roster of those associated with a particular unit, in this case a communications unit. The lower part of the form is for recording the activities of the unit. This makes it useful for providing information about what happened and when – both for those who participated in those activities and those who arrive later. In addition, the information is useful for those interested in reviewing the activities of the unit and looking for opportunities for improving readiness and efficiency for similar future activities.

The [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] is based on the ICS 309 Communication Log form which is intended primarily for logging formal traffic - messages on forms. Limiting its use to such traffic should provide two benefits:

* The station’s operator should be able to more easily find records of forms previously transmitted, especially when a reply to such a form is about to be received.
* Those reviewing the logs later are more likely to have a clear picture of what messages were sent and received by the station.

The [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] is an unofficial form designed to complement the two forms discussed above to help keep track of the stations that communication unit is in contact with as well as information like the readability of the radio communications with those stations. As it is not an official ICS form, it can be customized to the particular situation. In a pinch, use scratch paper instead. Using this form instead of recording check-ins on Form 6 or 214 will use less space and keep the information about each station together for easy reference.

The [https://docs.google.com/document/d/1FsFca0Yq1xIHZlihSXuZG-Fo5M-C8MzAfMyrGgdugH0/edit?usp=sharing Traffic Count Worksheet] is an experimental form for tracking counts of available formal messages as well as counts of messages handled so far. Feel free to customize it to meet your needs. The goal is to handle traffic based on precedence and give all stations in your region a chance to pass traffic that is equal to the precedence being passed by other stations. The worksheet should help you handle the available traffic by relative precedence and keep track of available traffic that you have not yet handled.

=== Instructions for using an [https://drive.google.com/file/d/1_ryKuDUKzB1gc6DLsuMdG__a4nTuEYn1/view?usp=drive_link ICS Form 214] ===

* Each NET SNC should use ICS Form 214 to record the activities of their station. In other situations like a radio trailer or radio room, multiple stations and operators at the same location are all part of the same Communications Unit and would share a single ICS Form 214. Similarly, multiple operators working together at a remote site like an evacuation center would share a Form 214..
* Log your name and the date and time your station’s activation at the top.
* Also record your Name and Time In in the roster section. Do the same for any other operators or scribes serving with you.
* Record “ICS Position” as “Amateur Radio Operator” or "Scribe" or an abbreviation like “ARO” or "ARO Scribe".
* Record “Home Base” as “Portland NET”.
* When someone goes off during, record the time in “Time Out”
* If the incident command declares a new operational period, close the 214 and open a new one.
* When a station is closed or a new operational period starts, log the closing as the last item in Major Events.
* See [https://drive.google.com/file/d/1FhGwY9uo3D7FTATwe7aqgQ30Welx2kL0/view?usp=share_link ICS 214 Unit Log Instructions] for additional details.
* See the following sample ICS 214.
[[File:ICS 214 SNC Sample.png|500px]]

=== Overview of using [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) Communication Log ===

* Use NET Form 6 / ICS 309 for formal traffic only, not activities. One Form 6 should be used by each operator.
* Subnet controllers should record most activities on an ICS 214 rather than the NET Form 6 or ICS 309 with the following exceptions:
** Check-ins, readability, etc. should go on the [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] or scratch paper.
** Message counts should go on a [https://docs.google.com/document/d/1FsFca0Yq1xIHZlihSXuZG-Fo5M-C8MzAfMyrGgdugH0/edit?usp=sharing Traffic Count Worksheet] or scratch paper.
* Use Winlink Express to [[Checklists for Winlink Tasks#Steps to Generate an ICS-309.2C allowing you to create a communication log as a PDF file that can be printed or emailed|generate an ICS 309 PDF]] for any Winlink traffic.
[[File:Sample Form 6 SNC.png|500px]]

=== Instructions for Using a [https://drive.google.com/file/d/1BRPQuQdaSTWl02mbv8lLl4RAVw3H0c9V/view?usp=sharing NET Form 6] (ICS 309) for Logging NET Form 8s or ICS Form 213s ===

* When a NET Form 8 is being logged, the right-hand field should start with the tactical call sign of the originating station, which may be the same as the team name.
* The originating station is followed by the date and time from the fields on the Form 8, followed by the Subject field from the Form 8.
* The Subject of a Form 8 should begin with message precedence, which should be copied into the right-hand field with the rest of the subject.
* For replies, the word “Reply” should be first followed by the information in the same column for the original message.
* FCC call signs should not be used in the From and To fields of NET Form 6 (ICS 309) , Instead use tactical call signs as illustrated below.
* In the example above the transmission of the messages that originated from North Heights and South Heights to ECC and the receipt of traffic from ECC are not shown here because they were transmitted via Winlink which can generate a separate log.

=== Instructions for using [[Media:Stations Participating Log.pdf|Stations Participating Stations Log]] ===

* Each time a station checks in, record the time, the station’s tactical call sign and the operator’s FCC call sign.
* If the operator is representing a team at a staging area, record the name of the team.
** Note: During some exercises, several teams combine to participate in the exercise. You do not need to record the names of all the NET teams or Portland neighborhoods representing at the staging area. ''Record only the name of the neighborhood or team that is hosting the combined teams during the exercise.''
* Also record the station’s readability. See [[Readability and Signal Strength]].
* When the station checks out, record that time in the corresponding column.

[[File:SNC's Stations Participating Form.png|500px]]

=== Instructions for using the [https://drive.google.com/file/d/10cVLW0D1HFXOXEX2_WJ7caQuyV9GVCwS/view?usp=drive_link Traffic Count Worksheet] ===

* Each time a station reports available traffic, use a new row to record the number of messages available at each precedence level.
* Each time you handle a message for that station, use a tally mark to indicate an increase in the number messages handled at the message’s precedence level. For instance, if one Priority message was previously handled for a station and you just handled a second one, the tally in the Handled column for Priority messages would change from “l” to “ll”. See the [[wikipedia:Tally_marks|Wikipedia article on Tally Marks]] for a discussion of tally marks.
* If a station provides new counts of available traffic, start a new row and draw a line through the row that is now out of date.
* Start a new Worksheet for each shift or when worksheet has become obsolete.
* See the following sample worksheet.
[[File:Sample Traffic Count Worksheet.png|500px]]