Portland NET Wiki - User contributions [en]

Winlink Procedures for Subnet Controllers

2026-06-01T19:12:17Z

BruceSchafer: /* From Field */ Corrected typos in form numbers

=== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ===
Winlink Express includes a template called Winlink Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of the first station that checked in.
** Enter the name of the team represented by the tactical call sign.
** Press Enter to start a new line
** Repeat the above steps for each of the other stations that have checked into your subnet.
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]

=== Handling Winlink Formal Traffic from EOC ===
During an exercise or deployment 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 213 indicates the person who originated the Form 213 (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 Winlink Traffic for the Portland EOC ===
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 completed your ICS 213, click on Submit and close the browser window. You will see the content of the ICSE 213 in the body of a Winlink message.

* 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 the To field of the Winlink message to W7ECC.

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. ''During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised'', you need to mark each message as a "Post Office Message" or change the default message type to "Post Office" so all your subsequent messages will be treated as Post Office Messages.
==== Selecting the Post Office Message type for a particular message. ====

:: i[[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Message. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. In this case if you want your unsent messages to be handled as Post Office messages, double-click on the messages in the Outbox, change the type to Post Office, and Start your gateway session again.

=== 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Voice Procedures for Subnet Control Operators

2026-05-29T16:01:31Z

BruceSchafer: /* Recommended Check-In Procedure for Major Exercises and Deployments */ Linked new form

=== 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 sign. Record their report in one or more rows of a copy of [https://docs.google.com/document/d/1mNd2me-VK364JbsJBel-n4TWf2RZ30CpkOSQkE5Ixlo/edit?usp=sharing this Station Signal Reports form]. 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 [[Subnet Control Operator Standard Operating Procedure]] and proceed with Step 7.

====== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC.

# [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Reporting by Voice]]
# [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Reporting by Winlink]].

Command Net should inform you which of these procedures you should use.

==== Using Voice to Transmit 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]].

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

You should then transition to Command Net and inform them that you have transferred control of your subnet and check out.

=== 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 Command Net and check out.

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

Subnet Control Operator Standard Operating Procedure

2026-05-29T05:53:06Z

BruceSchafer:

# Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
# Resource Net
#* [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
#* Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
# After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
# If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
# Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
# Handle any questions from the teams checked into your subnet.
# Check in with Command Net.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
# Return to your regional subnet frequency and announce your return.
# Handle any urgent questions or traffic.
# Transmit your roster.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
#** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
#** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
# Return to your regional subnet frequency and announce your return.
# Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence.
#* EOC traffic to teams
#* Teams' replies to EOC
#* Team-to-team traffic
#* Team-to-EOC traffic
# Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. (Winlink will keep track of messages you send and receive using it and allow you to create an ICS 309 traffic report later.)
# If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
# You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
#* “EMERGENCY, this is Command” or just “EMERGENCY”
#* “Priority, this is Command” or just “Priority”
#** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
# If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
# You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
# Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
# Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
# If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.
# There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.
# ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
#* If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
#* If the message has a precedence of ''Emergency'',
#** Transcribe the message onto a NET Form 8 or an ICS Form 213.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
#** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
#** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
#** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
#* If the message ''does not'' have a precedence of Emergency,
#** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
#** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
#** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
#** Set the To field in the main Winlink message to W7ECC.
#** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
# ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to the traffic you are currently handling,
#* 23.1 Ask the ARO for the subject and time of the message to which they are replying.
#* 23.2 Find the original message in your log.
#* 23.3 If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
#* 23.4 If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
#* 23.5 Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step 23.1 above. If it is lower in precedence proceed to step 24 below.
# When you have transcribed the available traffic at a particular precedence level,
#* [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#* Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
#* '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
# [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
# Repeat the above steps starting at step 5. (Some of the early steps may seem unnecessary, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
# Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
# Send any remaining Winlink traffic.
# [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Command Net]].
# If the Resource Net is still active, check out of the Resource Net.
# Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
# If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Subnet Control Operator Standard Operating Procedure

2026-05-29T05:37:33Z

BruceSchafer: Changed reference to step 6 to Step 5

# Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
# Resource Net
#* [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
#* Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
# After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
# If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
# Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
# Handle any questions from the teams checked into your subnet.
# Check in with Command Net.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
# Return to your regional subnet frequency and announce your return.
# Handle any urgent questions or traffic.
# Transmit your roster.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
#** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
#** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
# Return to your regional subnet frequency and announce your return.
# Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence.
#* EOC traffic to teams
#* Teams' replies to EOC
#* Team-to-team traffic
#* Team-to-EOC traffic
# Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. (Winlink will keep track of messages you send and receive using it and allow you to create an ICS 309 traffic report later.)
# If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
# You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
#* “EMERGENCY, this is Command” or just “EMERGENCY”
#* “Priority, this is Command” or just “Priority”
#** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
# If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
# You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
# Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
# Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
# If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.
# There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.
# ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
#* If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
#* If the message has a precedence of ''Emergency'',
#** Transcribe the message onto a NET Form 8 or an ICS Form 213.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
#** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
#** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
#** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
#* If the message ''does not'' have a precedence of Emergency,
#** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
#** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
#** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
#** Set the To field in the main Winlink message to W7ECC.
#** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
# ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
#* If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
#* If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
#* Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
# When you have transcribed the available traffic at a particular precedence level,
#* [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#* Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
#* '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
# [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
# Repeat the above steps starting at step 5. (Some of the early steps may seem unnecessary, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
# Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
# Send any remaining Winlink traffic.
# [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Command Net]].
# If the Resource Net is still active, check out of the Resource Net.
# Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
# If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Voice Procedures for Subnet Control Operators

2026-05-29T05:07:38Z

BruceSchafer: /* Checking in Stations */ Added link to SNC SOP in step J

=== 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 [[Subnet Control Operator Standard Operating Procedure]] and proceed with Step 7.

====== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC.

# [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Reporting by Voice]]
# [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Reporting by Winlink]].

Command Net should inform you which of these procedures you should use.

==== Using Voice to Transmit 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]].

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

You should then transition to Command Net and inform them that you have transferred control of your subnet and check out.

=== 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 Command Net and check out.

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

Subnet Control Operator Standard Operating Procedure

2026-05-29T05:01:39Z

BruceSchafer: Fixed problems with numbering

# Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
# Resource Net
#* [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
#* Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
# After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
# If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
# Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
# Handle any questions from the teams checked into your subnet.
# Check in with Command Net.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
# Return to your regional subnet frequency and announce your return.
# Handle any urgent questions or traffic.
# Transmit your roster.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
#** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
#** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
# Return to your regional subnet frequency and announce your return.
# Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence.
#* EOC traffic to teams
#* Teams' replies to EOC
#* Team-to-team traffic
#* Team-to-EOC traffic
# Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. (Winlink will keep track of messages you send and receive using it and allow you to create an ICS 309 traffic report later.)
# If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
# You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
#* “EMERGENCY, this is Command” or just “EMERGENCY”
#* “Priority, this is Command” or just “Priority”
#** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
# If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
# You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
# Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
# Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
# If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.
# There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.
# ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
#* If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
#* If the message has a precedence of ''Emergency'',
#** Transcribe the message onto a NET Form 8 or an ICS Form 213.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
#** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
#** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
#** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
#* If the message ''does not'' have a precedence of Emergency,
#** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
#** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
#** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
#** Set the To field in the main Winlink message to W7ECC.
#** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
# ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
#* If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
#* If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
#* Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
# When you have transcribed the available traffic at a particular precedence level,
#* [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#* Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
#* '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
# [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
# Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
# Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
# Send any remaining Winlink traffic.
# [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Command Net]].
# If the Resource Net is still active, check out of the Resource Net.
# Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
# If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Subnet Control Operator Standard Operating Procedure

2026-05-29T04:57:36Z

BruceSchafer: Replaced unnumbered bullets with numbered

# Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
# Resource Net
#* [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
#* Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
# After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
# If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
# Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
# Handle any questions from the teams checked into your subnet.
# Check in with Command Net.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
# Return to your regional subnet frequency and announce your return.
# Handle any urgent questions or traffic.
# Transmit your roster.
#* Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
#* Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
#** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
#** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
# Return to your regional subnet frequency and announce your return.
# Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence.
*** EOC traffic to teams
*** Teams' replies to EOC
*** Team-to-team traffic
*** Team-to-EOC traffic
# Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. (Winlink will keep track of messages you send and receive using it and allow you to create an ICS 309 traffic report later.)
# If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
# You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
#* “EMERGENCY, this is Command” or just “EMERGENCY”
#* “Priority, this is Command” or just “Priority”
#** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
# If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
# You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
# Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
# Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
# If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

# There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

# ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
#* If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
#* If the message has a precedence of ''Emergency'',
#** Transcribe the message onto a NET Form 8 or an ICS Form 213.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
#** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
#** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
#** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
#* If the message ''does not'' have a precedence of Emergency,
#** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
#** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
#** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
#** Ask for any fills for the message you just received and update your transcription with the additional information.
#** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
#** Set the To field in the main Winlink message to W7ECC.
#** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
# ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
#* If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
#* If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
#* Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
# When you have transcribed the available traffic at a particular precedence level,
#* [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
#* Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
#* '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
# [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
# Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
# Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
# Send any remaining Winlink traffic.
# [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Command Net]].
# If the Resource Net is still active, check out of the Resource Net.
# Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
# If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Citywide Deployment Exercise

2026-05-27T03:49:00Z

BruceSchafer: /* Recordings of NET Training Sessions Relevant to Deployment Exercise */ Editing date

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/817729301396013056/20260513-cde-training-3-management-of-suvs Management of Spontaneous Untrained Volunteers (SUVs),] May 13, 2026
* [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-05-27T03:47:14Z

BruceSchafer: /* Recordings of NET Training Sessions Relevant to Deployment Exercise */ Added recording to SUV management

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/817729301396013056/20260513-cde-training-3-management-of-suvs Managing Spontaneous Untrained Volunteers (SUVs),] May x, 2026
* [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>

Voice Procedures for Subnet Control Operators

2026-05-21T18:30:09Z

BruceSchafer: /* Transferring Control to a New Subnet Controller */ Added checking out with Command Net.

=== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC.

# [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Reporting by Voice]]
# [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Reporting by Winlink]].

Command Net should inform you which of these procedures you should use.

==== Using Voice to Transmit 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]].

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

You should then transition to Command Net and inform them that you have transferred control of your subnet and check out.

=== 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 Command Net and check out.

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

Voice Procedures for Subnet Control Operators

2026-05-21T18:28:19Z

BruceSchafer: /* Closing your Subnet and Checking Out */ Changed check out to Command Net and moved subsection above "Transfering Control..."

=== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC.

# [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Reporting by Voice]]
# [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Reporting by Winlink]].

Command Net should inform you which of these procedures you should use.

==== Using Voice to Transmit 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]].

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

=== 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 Command Net and check out.

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

Subnet Control Operator Standard Operating Procedure

2026-05-21T18:25:48Z

BruceSchafer: Changed check out to Command Net rather than Tactical Net

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Check in with Command Net.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
* Return to your regional subnet frequency and announce your return.
* Handle any urgent questions or traffic.
* Transmit your roster.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
*** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
*** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. (Winlink will keep track of messages you send and receive using it and allow you to create an ICS 309 traffic report later.)
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Command Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Subnet Control Operator Standard Operating Procedure

2026-05-20T20:21:04Z

BruceSchafer: A few small changes

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Check in with Command Net.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
* Return to your regional subnet frequency and announce your return.
* Handle any urgent questions or traffic.
* Transmit your roster.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
*** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
*** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]]. (Winlink will keep track of messages you send and receive using it and allow you to create an ICS 309 traffic report later.)
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Tactical Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Subnet Control Operator Standard Operating Procedure

2026-05-20T20:11:36Z

BruceSchafer: Updated link

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Check in with Command Net.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
* Transition back to your subnet.
* Transmit your roster.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
*** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
*** [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Tactical Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Voice Procedures for Subnet Control Operators

2026-05-20T20:10:14Z

BruceSchafer: /* Transmitting a Roster to the Portland EOC */ Improved formatting

=== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC.

# [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Reporting by Voice]]
# [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Reporting by Winlink]].

Command Net should inform you which of these procedures you should use.

==== Using Voice to Transmit 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.

Voice Procedures for Subnet Control Operators

2026-05-20T20:05:39Z

BruceSchafer: /* Transmitting a Roster to the Portland EOC */ Added link to Winlink check-in procedure and removed that content from this page

=== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC. One involves voice and [[Winlink Procedures for Subnet Controllers#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|the other uses Winlink]]. These procedures are described below. Command Net should inform you which of the following procedures you should use.

==== Using Voice to Transmit 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.

Winlink Procedures for Subnet Controllers

2026-05-20T20:02:36Z

BruceSchafer: Moved subsection on reporting roster by Winlink here

=== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ===
Winlink Express includes a template called Winlink Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of the first station that checked in.
** Enter the name of the team represented by the tactical call sign.
** Press Enter to start a new line
** Repeat the above steps for each of the other stations that have checked into your subnet.
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]

=== Handling Winlink Formal Traffic from EOC ===
During an exercise or deployment 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 Winlink Traffic for the Portland EOC ===
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 completed your ICS 213, click on Submit and close the browser window. You will see the content of the ICSE 213 in the body of a Winlink message.

* 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 the To field of the Winlink message to W7ECC.

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. ''During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised'', you need to mark each message as a "Post Office Message" or change the default message type to "Post Office" so all your subsequent messages will be treated as Post Office Messages.
==== Selecting the Post Office Message type for a particular message. ====

:: i[[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Message. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. In this case if you want your unsent messages to be handled as Post Office messages, double-click on the messages in the Outbox, change the type to Post Office, and Start your gateway session again.

=== 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-05-20T20:00:58Z

BruceSchafer: /* Handling Winlink Formal Traffic from EOC */ added reference to deployment

=== Handling Winlink Formal Traffic from EOC ===
During an exercise or deployment 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 Winlink Traffic for the Portland EOC ===
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 completed your ICS 213, click on Submit and close the browser window. You will see the content of the ICSE 213 in the body of a Winlink message.

* 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 the To field of the Winlink message to W7ECC.

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. ''During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised'', you need to mark each message as a "Post Office Message" or change the default message type to "Post Office" so all your subsequent messages will be treated as Post Office Messages.
==== Selecting the Post Office Message type for a particular message. ====

:: i[[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Message. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. In this case if you want your unsent messages to be handled as Post Office messages, double-click on the messages in the Outbox, change the type to Post Office, and Start your gateway session again.

=== 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Subnet Control Operator Standard Operating Procedure

2026-05-20T19:56:24Z

BruceSchafer: Added checking into Command Net

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Check in with Command Net.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transition to MC-9 -- 146.460 MHz simplex -- check in and participate in a briefing.
* Transition back to your subnet.
* Transmit your roster.
** Consider appointing a temporary SNC before doing so. See [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transmit your roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
*** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
*** [[Voice Procedures for Subnet Control Operators#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Tactical Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Voice Procedures for Subnet Control Operators

2026-05-19T18:58:52Z

BruceSchafer: /* Transmitting a Roster to the Portland EOC */ Added more detail

=== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC. One involves voice and the other uses Winlink. These procedures are described below. Command Net should inform you which of the following procedures you should use.

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of the first station that checked in.
** Enter the name of the team represented by the tactical call sign.
** Press Enter to start a new line
** Repeat the above steps for each of the other stations that have checked into your subnet.
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]

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

Voice Procedures for Subnet Control Operators

2026-05-19T18:56:54Z

BruceSchafer: /* Transmitting a Roster to the Portland EOC */ Added intro paragraph

=== 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 ===
There are two procedures for reporting your roster of teams checked into your regional subnet to the EOC. Command Net should inform you which of the following procedures you should use.

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of the first station that checked in.
** Enter the name of the team represented by the tactical call sign.
** Press Enter to start a new line
** Repeat the above steps for each of the other stations that have checked into your subnet.
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]

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

Subnet Control Operator Standard Operating Procedure

2026-05-19T18:53:37Z

BruceSchafer: Described what to do if additional stations check in.

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Contact Tactical Net and [[Voice Procedures for Subnet Control Operators#Transmitting a Roster to ECC|transmit your roster]]. Consider appointing a temporary SNC before doing so. See
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transmitting a Roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
*** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]].
*** [[Voice Procedures for Subnet Control Operators#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]. If you use this procedure and get additional check-ins later, you can use the voice procedure above to notify EOC of the additional stations in your region.
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Tactical Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Voice Procedures for Subnet Control Operators

2026-05-19T17:38:45Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Minor clarifications

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

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of the first station that checked in.
** Enter the name of the team represented by the tactical call sign.
** Press Enter to start a new line
** Repeat the above steps for each of the other stations that have checked into your subnet.
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]

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

Voice Procedures for Subnet Control Operators

2026-05-19T05:08:38Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Fixed link

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

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of your first operator
** Enter the name of the team represented by the operator
** Press Enter to start a new line
** Repeat the above steps for each of the operators who have checked into your subnet
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]

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

Voice Procedures for Subnet Control Operators

2026-05-19T05:06:50Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Improved formatting

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

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

* Create a new message
* Click on Select a Template.
* Click on the + next to Standard Templates.
* Click on the + next to General Forms.
* Click on Winlink Check-In.txt.
* Click on Select.
* This should open your web browser and display a form.
* Fill in the form.
* When you get to the Comment field
** Enter the tactical call sign of your first operator
** Enter the name of the team represented by the operator
** Press Enter to start a new line
** Repeat the above steps for each of the operators who have checked into your subnet
* 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: W7ECC
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
* See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Transmitting and Receiving Traffic Using a Gateway]]

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

Voice Procedures for Subnet Control Operators

2026-05-19T05:04:31Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Added more details

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

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====
[Rough draft. This section will be completed by May 18, 2026]

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet

** Create a new message
** Click on Select a Template.
** Click on the + next to Standard Templates.
** Click on the + next to General Forms.
** Click on Winlink Check-In.txt.
** Click on Select.
** This should open your web browser and display a form.
** Fill in the form.
** When you get to the Comment field
*** Enter the tactical call sign of your first operator
*** Enter the name of the team represented by the operator
*** Press Enter to start a new line
*** Repeat the above steps for each of the operators who have checked into your subnet
** 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: W7ECC
** See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Preparing Your Winlink Traffic for the EOC.]]
** See [[Winlink Procedures for Subnet Controllers#Preparing Your Winlink Traffic for the Portland EOC|Transmitting and Receiving Traffic Using a Gateway]]

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

Voice Procedures for Subnet Control Operators

2026-05-19T04:48:14Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Added details of preparing a Winlink check-in that provides subnet roster

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

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====
[Rough draft. This section will be completed by May 18, 2026]

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet.

* Finding the check-in template
** Create a new message
** Click on Select a Template.
** Click on the + next to Standard Templates.
** Click on the + next to ICS USA Forms.
** Click on Check-In.txt.
** Click on Select.
** This should open your web browser and display a form.
** Fill in the form.
** When you get to the Comment field
*** Enter the tactical call sign of your first operator
*** Enter the name of the team represented by the operator
*** Press Control and then Enter to start a new line
*** Repeat the above steps for each of the operators who have checked into your subnet
** 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: W7ECC
** Click on Post to Outbox.
* Starting a Winlink session, selecting the EOC gateway

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

Teams/South Burlingame

2026-05-19T03:51:18Z

BruceSchafer: Fixed spelling error

{{Team
| contact = {{EmailLink|SBNET.Team.Leader@gmail.com}}
| tl = 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]

Voice Procedures for Subnet Control Operators

2026-05-17T22:49:05Z

BruceSchafer: /* Using Voice to Transmit a Roster to the Portland EOC */ Added a new subhead and moved two existing ones under it

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

==== Using Voice to Transmit 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.]

==== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ====
[Rough draft. This section will be completed by May 18, 2026]

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet.

* Finding the check-in template
* Filling in the basic information
* Providing the subnet roster in the Comments field.
* Submitting the form
* Placing the message in the Outbox
* Starting a Winlink session

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

Subnet Control Operator Standard Operating Procedure

2026-05-17T22:36:15Z

BruceSchafer: Added sub-bullets with link to the two methods for submitting rosters

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Contact Tactical Net and [[Voice Procedures for Subnet Control Operators#Transmitting a Roster to ECC|transmit your roster]]. Consider appointing a temporary SNC before doing so. See
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** Transmitting a Roster to the Portland EOC. Command Net or Tactical Net should tell you how they wish to receive your roster of teams checked into your subnet. Follow one of these procedures:
*** [[Voice Procedures for Subnet Control Operators#Using Voice to Transmit a Roster to the Portland EOC|Using Voice to Transmit a Roster to the Portland EOC]]
*** [[Voice Procedures for Subnet Control Operators#Using the Winlink Check-in Form to Report a Roster to the Portland EOC|Using the Winlink Check-in Form to Report a Roster to the Portland EOC]]
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Tactical Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Voice Procedures for Subnet Control Operators

2026-05-17T22:26:25Z

BruceSchafer: /* Calling for Relays */ Improved format

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

=== Using Voice to Transmit 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.]

=== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ===
[Rough draft. This section will be completed by May 18, 2026]

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet.

* Finding the check-in template
* Filling in the basic information
* Providing the subnet roster in the Comments field.
* Submitting the form
* Placing the message in the Outbox
* Starting a Winlink session

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

Voice Procedures for Subnet Control Operators

2026-05-17T22:25:07Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Added more bullets

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

=== Using Voice to Transmit 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.]

=== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ===
[Rough draft. This section will be completed by May 18, 2026]

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet.

* Finding the check-in template
* Filling in the basic information
* Providing the subnet roster in the Comments field.
* Submitting the form
* Placing the message in the Outbox
* Starting a Winlink session

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

Voice Procedures for Subnet Control Operators

2026-05-17T22:22:22Z

BruceSchafer: /* Using the Winlink Check-in Form to Report a Roster to the Portland EOC */ Created rough draft of new subsection

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

=== Using Voice to Transmit 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.]

=== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ===
[Rough draft. This section will be completed by May 18, 2026]

Winlink includes a template called Check In. This is a very general form that allows operators to use Winlink to check in during a drill, exercise, or deployment. We sometimes ask subnet control operators to use this form to report the roster of NET teams that have checked into their regional subnet.

* Finding the template
* Filling in the basic information
* Providing the subnet roster in the Comments field.

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

Voice Procedures for Subnet Control Operators

2026-05-17T22:14:37Z

BruceSchafer: /* Transmitting a Roster to the Portland EOC */ Added new subhead

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

=== Using Voice to Transmit 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.]

=== Using the Winlink Check-in Form to Report a Roster to the Portland EOC ===
[This section will be filled in by May 18, 2026]

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

Subnet Control Operator Standard Operating Procedure

2026-05-16T23:49:02Z

BruceSchafer: Improved punctuation

* Enable the Tactical Address for your region in Winlink Express. See [[Using Winlink Tactical Addresses#Enabling a Tactical Address|Enabling a Tactical Address]].
* Resource Net
** [[Check-in and Check-out Procedures#Checking into the Resource Net|Check into Resource Net]] on MC-2 Repeater (147.280 +600 KHz 167.9 Hz), which will typically use a directed check in for Subnet Control operators (SNCs).
** Listen for an announcement of the regional frequencies to be used during the deployment or exercise. They may be different than shown in the frequencies in the table referenced above. Also note whether your region has been combined with another region. If you previously detected a problem with the frequency that is assigned to your region, use the proword “Comment” and when recognized report the problem. Make note of any change of frequency that results.
* After being released from the Resource Net, open your regional subnet. See [[Voice Procedures for Subnet Control Operators#Opening a Subnet|Opening a Subnet]]. The [[ICS 205 with Frequencies for Subnet Control Operators]] gives the ''standard'' frequency for each regional subnet ''but the frequency announced during the Resource Net may be different.''
* If you find that your assigned regional frequency is not available, consider moving to another frequency, possibly the frequency recommended in the [[Frequency Tables#UHF Frequency Table|UHF Frequency Table]]. Resource Net may be able to help you select an alternate frequency. Two possible alternate VHF frequencies are 146.50 MHz and 145.53 MHz. If you change frequencies, be sure to inform both Resource Net and Tactical Net as well as making announcements on your original frequency if possible.
* Check in the AROs for the teams in your regions while compiling a roster. See [[Voice Procedures for Subnet Control Operators#Checking in Stations|Checking in Stations]]. See also [[Voice Procedures for Subnet Control Operators#Compiling a Roster of Teams|Compiling a Roster of Teams]] in the same document. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]] unless you are sure that you can be heard by and you can hear all stations in your region.
* Handle any questions from the teams checked into your subnet.
* Contact Tactical Net and [[Voice Procedures for Subnet Control Operators#Transmitting a Roster to ECC|transmit your roster]]. Consider appointing a temporary SNC before doing so. See
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appointing a Temporary SNC]].
** [[Voice Procedures for Subnet Control Operators#Transmitting a Roster to the Portland EOC|Transmitting a Roster to the Portland EOC]]
* Return to your regional subnet frequency and announce your return.
* Handle message traffic based on [[Message Precedence|precedence]] starting with emergency messages and then priority messages. Emergency messages addressed to the EOC should be transmitted by voice via the Tactical Net. Priority messages should normally transmitted via Winlink. If you receive a surge of Priority messages use the following sub-precedence:
# EOC traffic to teams
# Teams' replies to EOC
# Team-to-team traffic
# Team-to-EOC traffic
* Log voice messages you receive on your Form 6. See [[Logging Procedures for Subnet Control Operators#Instructions for Using a NET Form 6 (ICS 309) for Logging NET Form 8s or ICS Form 213s|Instructions for Using a NET Form 6 for Logging NET Form 8s]].
* If Resource Net or Command Net has given you a time to check into Command Net for an update, ''transition to MC-9 at that time'' and wait for instructions.
* You may receive one or more calls from the EOC Command operator with information or a request to transition to MC-9 at a particular time for a briefing or a formal message. Command will contact you using your tactical call sign, e.g “Westside, this is Command Over”. If Command needs to reach you while your subnet is busy, you may hear one of the following instead.
** “EMERGENCY, this is Command” or just “EMERGENCY”
** “Priority, this is Command” or just “Priority”
*** If possible, respond with something like “All stations standby. Command, go ahead.” If the precedence of your current traffic is higher than the precedence given by Command, you can respond with “Command. Please standby. <tactical call sign> Continue with your Emergency traffic.”
* If your transceiver has two receivers, e.g. an A side and a B side, consider using one of the sides to monitor MC-9, which is the Command Net frequency. If you plan to use one of the sides of your transceiver for Winlink communication, you could use that side for both Winlink and Command by setting MC-9 in memory mode and the gateway frequency in VFO mode and switching back and forth between Memory and VFO mode on that side of the radio.
* You may receive a voice message from the Command operator that is intended to be conveyed to the participating teams. See [[Voice Procedures for Subnet Control Operators#Handling Traffic from Emergency Operations Center to NET Teams|Handling Traffic from Emergency Operations Center to NET Teams]].
* Command Net may contact you to inform you that you have messages waiting for your Tactical Address via Winlink.* See [[Using Winlink Tactical Addresses#Tactical Addresses Established for the Portland NET Program|Tactical Addresses Addresses Established for Portland NET Program]]”, [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]]” and [[Winlink Procedures for Subnet Controllers#Handling Winlink Formal Traffic from EOC|Handling Winlink Formal Traffic from EOC]]”,
* Even if you don’t hear from Command Net you should '''check for Winlink email about every 20 to 30 minutes''' in case there is traffic waiting for you. See the links to procedures in the step above. Use the KI7QIB-12 gateway** at the frequency shown in the Table of Frequencies.
* If you are deployed as part of an exercise and receive a message that does not include words equivalent to “This is an exercise”, add those words before voicing the message to your AROs.

* There is a chance that Command Net will give you a reply to an earlier message. If you receive such a reply, handle it based on its precedence and when you contact the intended team’s ARO, inform the ARO that it is a reply before reading it so the ARO can record the reply in the reply section of the original Form 8.

* ''Handling Formal Traffic to EOC.'' Ask the stations checked into your subnet if they have any traffic for the EOC or replies to any previous requests from EOC. See [[Voice Procedures for Subnet Control Operators#Handling NET Form 8 Traffic from NET Teams Including Triage|Handling NET Form 8 Traffic from NET Teams Including Triage]]. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
** If a station has a new message, ask for its precedence if you don’t already have it. Ask other stations whether they have any traffic of higher precedence.
** If the message has a precedence of ''Emergency'',
*** Transcribe the message onto a NET Form 8 or an ICS Form 213.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
*** Contact Tactical Net on Simplex MC-8 (147.580 MHz) informing it that you have Emergency Traffic.
*** Tactical Net will (a) take your message by voice; (b) tell you that Command Net (MC-9, 146.460 MHz) will call you back on your frequency; or (c) ask you to transmit your message using Winlink. (See steps for non-Emergency messages below.)
*** Note: If a real emergency occurs during an exercise, someone should call 911 and the real emergency should take precedence over all other traffic.
*** Log the message that your transcribed and then read to the EOC as a pair of lines on your NET Form 6.
** If the message ''does not'' have a precedence of Emergency,
*** Use Winlink to create a new message and then select an ICS213 template. See [[Checklists for Winlink Tasks]] details.
*** Ask the first station with the highest precedence traffic to voice the message while you enter it directly into the Winlink ICS213 template.
*** If you are concerned that operators will voice their messages faster than you can type into the template, consider telling them to say “Break” at the end of each field and wait for you.
*** Ask for any fills for the message you just received and update your transcription with the additional information.
*** After you have clicked on Submit and returned to Winlink, change the From field of the message to your region’s tactical call sign by clicking on down arrowhead next to your FCC call sign to get a drop-down menu that should include your region's tactical address. See [[Winlink Procedures for Subnet Controllers#Addressing Winlink Messages|Addressing Winlink Messages]].
*** Set the To field in the main Winlink message to W7ECC.
*** Log the message you transcribed on your NET From 6. You can rely on Winlink to create a log of the messages it sends when you open and start a session later. See [[Checklists for Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS-309]].
* ''Handling Replies to Formal Traffic from EOC.'' If a station has a reply, ask for its precedence if you don’t already have it. If the precedence is equal or greater than to 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.
** If you received the original message by Winlink, see [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]].
** If you received the original message by voice, see [[Winlink Procedures for Subnet Controllers#Handling Replies to EOC Traffic Originally Received by Voice|Handling Replies to EOC Traffic Originally Received by Voice]].
** Ask your stations whether they have any more traffic for EOC. If they do, ask them for the precedence of the traffic. If it is the same or higher precedence as the traffic you just transcribed, ask them to go ahead by returning to step a above. If it is lower in precedence proceed to step d below.
* When you have transcribed the available traffic at a particular precedence level,
** [[Voice Procedures for Subnet Control Operators#Appointing a Temporary Subnet Controller|Appoint a temporary SNC]].
** Change frequency to the frequency of the [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|experimental gateway]]. If the frequency is not in use, use Winlink Express to open a Packet or Vara session to send and receive messages. (Vara is preferred because it will take less time and allow the gateway to become available sooner to the next operator.) If the experimental gateway does not appear to operational see [[Winlink Procedures for Subnet Controllers#What To Do If the EOC Gateway Appears To Be Unavailable.|What To Do If the EOC Gateway Appears To Be Unavailable]].
** '''Exception:''' If you have Emergency traffic -- as described earlier -- you may contact Tactical Net informing it that you have Emergency traffic.
* [[Voice Procedures for Subnet Control Operators#Facilitating Communication Between Teams|Facilitate communication between teams]] while keeping in mind precedence. Consider [[Voice Procedures for Subnet Control Operators#Calling for Relays|calling for relays]].
* Repeat the above steps starting at step 6. (It may seem unnecessary to repeat Step 6 and 7, but during real deployments AROs may become available over an extended period of time and during an exercise there is always a chance that some will arrive late.)
* Either pass control of our regional subnet control operator to another operator or [[Voice Procedures for Subnet Control Operators#Closing your Subnet and checking Out|close your subnet.]]
* Send any remaining Winlink traffic.
* [[Voice Procedures for Subnet Control Operators#Closing your Subnet and Checking Out|Check out of Tactical Net]].
* If the Resource Net is still active, check out of the Resource Net.
* Use Winlink Express’s Setup menu to disable the tactical addresses associated with your simplex region(s). See [[Using Winlink Tactical Addresses#Disabling a Tactical Address|Disabling a Tactical Address]].
* If you receive any incoming messages addressed to your subnet that you have not handled, forward them to the SNC operator that took over your regional subnet. For Winlink traffic use your regions Tactical Address.
----* Command Net will normally contact subnets on their regional frequencies and will not be monitoring MC-9 except during scheduled times. Think of Tactical Net as your communications path to EOC and Command Net as EOC’s communication path to you. On occasion, Command Net may ask you to transition to MC-9.

<nowiki>**</nowiki> The reason we are asking you to use only the special gateway is that after a Cascadia event it is unlikely that our local gateways will be able to use the Internet to exchange messages. Thus we will need to use the same gateway if we expect to receive each other's messages.

Communicating with Other Teams

2026-05-01T19:13:57Z

BruceSchafer: BruceSchafer moved page Communicating with Other Teams to Communicating by Radio with Other Teams

#REDIRECT [[Communicating by Radio with Other Teams]]

Communicating by Radio with Other Teams

2026-05-01T19:13:57Z

BruceSchafer: BruceSchafer moved page Communicating with Other Teams to Communicating by Radio with Other Teams

Note: This page focusing on using Amateur Radio to communicate between teams. There are also situations where FRS or GMRS Radios might be a good choice. See [https://docs.google.com/presentation/d/1b1x0JTvbzP5nHxUaM-Fy2Yar4hmjg9jKIkPNJLn4BYI/edit?slide=id.p2#slide=id.p2 Communicating Between Teams]

* To prepare to make a direct contact with another team,
*# Use your team’s FRS/GMRS standard channel number to look up the new Portland NET simplex UHF frequency in the Amateur Radio 70 cm band for your team in the table below. If you’re not sure which FRS/GMRS channel your team uses, [https://pbem.link/net-team-map this map].
*# Using the [[Frequency Tables#UHF Frequency Table - Frequencies in the 70 cm Amateur Radio Band|UHF Frequency Table]], identify the 70cm frequency that corresponds to your team’s FRS/GMRS channel. The frequencies in the table are not the FRS/GMRS frequencies, they are Amateur Radio frequencies in the 70 cm UHF band that you can use to communicate with amateur radio operators on other teams or perhaps members of your own team.
*# During and exercise or deployment you can propose direct communication with another team using the protocol described below.
*# Note that the table gives an “alias” for each of the frequencies and indicates the channel numbers where the frequencies can be found in the new Multnomah County ARES templates. Make note of the alias for your frequency and consider using a memory channel if you have programmed your radio using one of the new templates.
*# Using a channel number is not required, however, because you can select VFO mode on your radio and select the simplex frequency directly.

* If you wish to make direct contact with another team, wait for a pause in the communication on your regional subnet and give your tactical call sign.
* Be prepared for the possibility that another operator in your region will request a direct contact with you on a particular UHF frequency and accept that request if possible.
* When the subnet controller recognizes you, use something like the following script:
*# You: I would like to make direct contact with <tactical call sign for another station that has checked in>
*# SNC: Roger <Your tactical call sign>. What frequency do you propose to use to make that contact?
*# You: I propose to use <Frequency from the [[Frequency Tables#UHF Frequency Table - Frequencies in the 70 cm Amateur Radio Band|UHF Frequency Table]]> which is known as PNTMxx in the MCARES templates. [PNTM is an abbreviation for Portland Net TeaM. xx is a reference to the two digits in a particular channel alias.]
*# SNC: Roger <Your tactical call sign>
*# SNC: <Other tactical call sign> Are you prepared to move to the proposed frequency and make contact with <Your call sign>
*# Other station: Affirmative Net Control. I understand that I should go to <proposed frequency> when you release us.
*# Note: If you don't hear the other station, simplex communication between you and that station may not be feasible. You may need to ask the SNC for permission to stay on the regional VHF frequency have them relay your communication with the team's ARO back and forth.
*# SNC: That is correct. <Your call sign> and <Other call sign> please transition to <proposed frequency> and make contact if possible. After successfully or unsuccessfully trying to do so, please return to this frequency and check back in.
*# You: <our FCC call sign> as <your tactical call sign> clear this frequency.
*# Other station: <Other station’s FCC call sign> as <their tactical call sign> clear this frequency.
* Proceed to the UHF frequency you proposed and after a brief pause, hail the other station using their tactical call sign followed by your tactical call sign. Note that UHF propagation can be different from VHF propagation so you may not hear the station as well as you did on your regional VHF frequency.
* If the frequency is already in use, return to your regional VHF frequency, report the problem and request advice on what frequency to use.
* Other teams may want to use the same frequency as you have chosen so keep your transmission power to a minimum. If the other operator reports they can hear you well, reduce your power and ask for another signal report. Help the other operator do the same thing.
* Keep your communication as brief as possible because you are risking missing important information being sent to you from the Portland EOC via your regional subnet.
* After successfully or unsuccessfully making contact, give your FCC call sign followed by the proword “clear”,
* Return to your regional VHF frequency and check back in using your tactical call sign.

Communicating by Radio with Other Teams

2026-05-01T19:12:27Z

BruceSchafer: Added note about potential problem with direct simplex communication.

Communicating by Radio with Other Teams

2026-05-01T19:09:02Z

BruceSchafer: Removed obsolete reference to 2023

Note: This page focusing on using Amateur Radio to communicate between teams. There are also situations where FRS or GMRS Radios might be a good choice. See [https://docs.google.com/presentation/d/1b1x0JTvbzP5nHxUaM-Fy2Yar4hmjg9jKIkPNJLn4BYI/edit?slide=id.p2#slide=id.p2 Communicating Between Teams]

* To prepare to make a direct contact with another team,
*# Use your team’s FRS/GMRS standard channel number to look up the new Portland NET simplex UHF frequency in the Amateur Radio 70 cm band for your team in the table below. If you’re not sure which FRS/GMRS channel your team uses, [https://pbem.link/net-team-map this map].
*# Using the [[Frequency Tables#UHF Frequency Table - Frequencies in the 70 cm Amateur Radio Band|UHF Frequency Table]], identify the 70cm frequency that corresponds to your team’s FRS/GMRS channel. The frequencies in the table are not the FRS/GMRS frequencies, they are Amateur Radio frequencies in the 70 cm UHF band that you can use to communicate with amateur radio operators on other teams or perhaps members of your own team.
*# During and exercise or deployment you can propose direct communication with another team using the protocol described below.
*# Note that the table gives an “alias” for each of the frequencies and indicates the channel numbers where the frequencies can be found in the new Multnomah County ARES templates. Make note of the alias for your frequency and consider using a memory channel if you have programmed your radio using one of the new templates.
*# Using a channel number is not required, however, because you can select VFO mode on your radio and select the simplex frequency directly.

* If you wish to make direct contact with another team, wait for a pause in the communication on your regional subnet and give your tactical call sign.
* Be prepared for the possibility that another operator in your region will request a direct contact with you on a particular UHF frequency and accept that request if possible.
* When the subnet controller recognizes you, use something like the following script:
*# You: I would like to make direct contact with <tactical call sign for another station that has checked in>
*# SNC: Roger <Your tactical call sign>. What frequency do you propose to use to make that contact?
*# You: I propose to use <Frequency from the [[Frequency Tables#UHF Frequency Table - Frequencies in the 70 cm Amateur Radio Band|UHF Frequency Table]]> which is known as PNTMxx in the MCARES templates. [PNTM is an abbreviation for Portland Net TeaM. xx is a reference to the two digits in a particular channel alias.]
*# SNC: Roger <Your tactical call sign>
*# SNC: <Other tactical call sign> Are you prepared to move to the proposed frequency and make contact with <Your call sign>
*# Other station: Affirmative Net Control. I understand that I should go to <proposed frequency> when you release us.
*# SNC: That is correct. <Your call sign> and <Other call sign> please transition to <proposed frequency> and make contact if possible. After successfully or unsuccessfully trying to do so, please return to this frequency and check back in.
*# You: <our FCC call sign> as <your tactical call sign> clear this frequency.
*# Other station: <Other station’s FCC call sign> as <their tactical call sign> clear this frequency.
* Proceed to the UHF frequency you proposed and after a brief pause, hail the other station using their tactical call sign followed by your tactical call sign. Note that UHF propagation can be different from VHF propagation so you may not hear the station as well as you did on your regional VHF frequency.
* If the frequency is already in use, return to your regional VHF frequency, report the problem and request advice on what frequency to use.
* Other teams may want to use the same frequency as you have chosen so keep your transmission power to a minimum. If the other operator reports they can hear you well, reduce your power and ask for another signal report. Help the other operator do the same thing.
* Keep your communication as brief as possible because you are risking missing important information being sent to you from the Portland EOC via your regional subnet.
* After successfully or unsuccessfully making contact, give your FCC call sign followed by the proword “clear”,
* Return to your regional VHF frequency and check back in using your tactical call sign.

Winlink Procedures for Subnet Controllers

2026-04-26T22:54:04Z

BruceSchafer: /* Preparing Your Winlink Traffic */ Added detail to the subhead

=== 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 Winlink Traffic for the Portland EOC ===
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 completed your ICS 213, click on Submit and close the browser window. You will see the content of the ICSE 213 in the body of a Winlink message.

* 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 the To field of the Winlink message to W7ECC.

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. ''During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised'', you need to mark each message as a "Post Office Message" or change the default message type to "Post Office" so all your subsequent messages will be treated as Post Office Messages.
==== Selecting the Post Office Message type for a particular message. ====

:: i[[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Message. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. In this case if you want your unsent messages to be handled as Post Office messages, double-click on the messages in the Outbox, change the type to Post Office, and Start your gateway session again.

=== 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:52:54Z

BruceSchafer: /* Preparing Your Winlink Traffic */

=== 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 Winlink 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 completed your ICS 213, click on Submit and close the browser window. You will see the content of the ICSE 213 in the body of a Winlink message.

* 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 the To field of the Winlink message to W7ECC.

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. ''During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised'', you need to mark each message as a "Post Office Message" or change the default message type to "Post Office" so all your subsequent messages will be treated as Post Office Messages.
==== Selecting the Post Office Message type for a particular message. ====

:: i[[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Message. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. In this case if you want your unsent messages to be handled as Post Office messages, double-click on the messages in the Outbox, change the type to Post Office, and Start your gateway session again.

=== 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:30:48Z

BruceSchafer: /* Selecting the Post Office Message type for a particular message. */ Added clarification

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

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
==== Selecting the Post Office Message type for a particular message. ====

:: i[[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Message. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. In this case if you want your unsent messages to be handled as Post Office messages, double-click on the messages in the Outbox, change the type to Post Office, and Start your gateway session again.

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:27:30Z

BruceSchafer: /* Preparing Your Winlink Traffic */ Added more info

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

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
==== Selecting the Post Office Message type for a particular message. ====

:: [[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]
* If you don't specify the Post Office message type your message will be considered a standard Winlink Messsage. In this cased, if the gateway doesn't have access to the Internet, no warning or error message will appear and your messages will remain in the Outbox. To fix this problem, all you have to do is double-click the email in the Outbox and change the type to Post Office.

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:18:29Z

BruceSchafer: /* Preparing Your Winlink Traffic */

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

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
==== Selecting the Post Office Message type for a particular message. ====

:: [[File:Post Office Message.png|500px]]

==== Specifying that messages should default to Post Office type. ====

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:17:07Z

BruceSchafer: /* Preparing Your Traffic */

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

==== If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
===== Selecting the Post Office Message type for a particular message.

:: [[File:Post Office Message.png|500px]]

===== Specifying that messages should default to Post Office type.

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:09:53Z

BruceSchafer: /* Preparing Your Traffic */ Fixed typos

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

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message you send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet access is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
** Selecting the Post Office Message type for a particular message.

:: [[File:Post Office Message.png|500px]]

** Specifying that messages should default to Post Office type.

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-26T22:06:15Z

BruceSchafer: /* Preparing Your Traffic */ Indented images

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

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message they send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet acccess is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
** Selecting the Post Office Message type for a particular message.

:: [[File:Post Office Message.png|500px]]

** Specifying that messages should default to Post Office type.

:: [[File:Set message type default.png|500px]]

:: [[File:Selecting Post Office as default.png|300px]]

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-24T05:46:07Z

BruceSchafer: /* Preparing Your Traffic */ Made additional corrections

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

* If you will be accessing a gateway when gateways are unlikely to have access to the Internet, you need to indicate that your message should have the "Post Office" type so that it stays at the gateway rather than being routed to a Command Message Survey in the Internet "cloud". This will allow it to accessed by other Winlink Express clients by accessing the same gateway. To restrict message to a particular gateway, any message they send must have the Post Office type. During a Citywide Deployment Exercise or after a Cascadia earthquake or disaster when Internet acccess is compromised, you need to assure that you either mark each message as a "Post Office Message" or change the default message type to "Post Office".
** Selecting the Post Office Message type for a particular message.

[[File:Post Office Message.png|500px]]

** Specifying that messages should default to Post Office type.

[[File:Set message type default.png|500px]]

[[File:Selecting Post Office as default.png|300px]]

* Regardless of the message type, you should
** 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 the 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-24T05:35:08Z

BruceSchafer: /* Preparing Your Traffic */ Shrank inserted screen shots

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

* If you will be accessing a gateway when gateways are unlikely to have Internet Access you need to indicate that your message is has a type of "Post Office mode" so that it stays at the gateway rather be routed to a Command Message Survey in the Internet "cloud". To do so, any message they send to the W7ECC gateway must be Post Office type. During a Citywide Deployment Exercise or after an Cascadia earthquake or disaster when Internet acccess is compromised you need to assure that you either mark each message as as "Post Office Message" or change their default message type to "Post Office".
** Selecting the Post Office Message type for a particular message.
[[File:Post Office Message.png|500px]]
** Specifying that messages should default to Post Office type.
[[File:Set message type default.png|500px]]

[[File:Selecting Post Office as default.png|300px]]
* 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.

Winlink Procedures for Subnet Controllers

2026-04-24T05:26:35Z

BruceSchafer: /* Preparing Your Traffic */ Added one more screen shot

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

* If you will be accessing a gateway when gateways are unlikely to have Internet Access you need to indicate that your message is has a type of "Post Office mode" so that it stays at the gateway rather be routed to a Command Message Survey in the Internet "cloud". To do so, any message they send to the W7ECC gateway must be Post Office type. During a Citywide Deployment Exercise or after an Cascadia earthquake or disaster when Internet acccess is compromised you need to assure that you either mark each message as as "Post Office Message" or change their default message type to "Post Office".
** Selecting the Post Office Message type for a particular message. [[File:Post Office Message.png]]
** Specifying that messages should default to Post Office type. [[File:Set message type default.png]][[File:Selecting Post Office as default.png]]
* 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 “[[Checklists for Winlink Tasks#Steps for Updating a Table of Available Gateways|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.