Voice Procedures for Subnet Control Operators - Revision history

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

2026-02-03T16:54:43Z

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

← Older revision		Revision as of 09:54, 3 February 2026
Line 86:		Line 86:

	=== Calling for Relays ===		=== 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.		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.

	~~# Stations you may not hear. To account~~ for this possibility, expect that other stations may offer to provide a relay by using the proword Relay preceded by the precedence of the traffic they wish to relay. If no precedence is given, you should assume that its precedence is Priority. If you are not sure that your team AROs are aware of their relay responsibility, you should ask if any station has a relay. When an ARO indicates that they have a relay tell them to go ahead if you are not handling traffic of higher precedence, there is no traffic of higher precedence and there is no traffic of equal precedence ahead of the requested relay. Otherwise, tell the relaying station to stand by after obtaining their tactical call sign.		==== [[Procedure for When Some Operators Cannot Hear Net Control Operator]] ====
	~~# Stations that may not have heard you. To account~~ for this possibility, choose a station that you believe to be in a different part of your region with equipment sufficient to be heard by other stations and ask them to relay your announcement or request and stand by for them to either say “Nothing heard” or “Relay”.
			==== [[Procedure for When Net Control Operator Cannot Hear Some Operators]] ====

	=== Appointing a Temporary Subnet Controller ===		=== Appointing a Temporary Subnet Controller ===

BrianScott: changed call sing to call sign

2025-11-08T02:01:50Z

changed call sing to call sign

← Older revision		Revision as of 19:01, 7 November 2025
Line 29:		Line 29:
	A. This is <your FCC call sign, first name> Subnet Control for the <your region name> region.		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 ~~sing~~.		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.]		[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.]

BruceSchafer: /* Recommended Check-In Procedure for Major Exercises and Deployments */ Improved formatting of two subheads

2025-05-26T19:23:55Z

Recommended Check-In Procedure for Major Exercises and Deployments: Improved formatting of two subheads

← Older revision		Revision as of 12:23, 26 May 2025
Line 79:		Line 79:
	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.]		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		====== 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.		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		====== 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.		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.

BruceSchafer: /* Facilitating Communication Between Teams */ Removed letter at the beginning of each subhead

2025-05-25T20:06:31Z

Facilitating Communication Between Teams: Removed letter at the beginning of each subhead

← Older revision		Revision as of 13:06, 25 May 2025
Line 190:		Line 190:
	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).		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).

	==== a. Tactical communication between teams using a frequency proposed by one of the teams. ====		==== 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.		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.

	==== b. Tactical communication between teams using a prearranged frequency ====		==== 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.		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.

	==== c. Routing formal messages within a region ====		==== 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.		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.

	==== d. Routing formal messages between regions ====		==== 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.		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.

BruceSchafer: /* Recommended Check-In Procedure for Major Exercises and Deployments */ Added link to Stations Participating log

2025-05-25T20:03:31Z

Recommended Check-In Procedure for Major Exercises and Deployments: Added link to Stations Participating log

← Older revision		Revision as of 13:03, 25 May 2025
Line 31:		Line 31:
	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 sing.		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 sing.

	[Check in stations. ~~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.]		[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.		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.

BruceSchafer: /* Checking in Stations */ Clarified procedure

2025-05-25T20:01:10Z

Checking in Stations: Clarified procedure

← Older revision		Revision as of 13:01, 25 May 2025
Line 15:		Line 15:
	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.		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.

	Here are two scripts to choose from:		==== 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 a Small Number of Stations]]
	* [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]		* [[Script for Checking in Stations Alphabetically by Tactical Call Signs]]

	~~==== Compiling a Roster of Teams ====~~		==== Recommended Check-In Procedure for Major Exercises and Deployments ====
	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 ====
	This example of check-in language is provided as a convenience. Feel free to modify it as circumstances dictate.		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.		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. Please come now.		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 sing.

	[Check in stations. Record ~~at least the~~ tactical call ~~signs~~ and the team name~~(s) associated with the call sign~~. ~~Recording~~ the operator name and FCC call sign is optional.]		[Check in stations. 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.		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.

BruceSchafer: /* Checking in Stations */ Added choice of two preamble scripts.

2025-05-25T18:51:28Z

Checking in Stations: Added choice of two preamble scripts.

← Older revision		Revision as of 11:51, 25 May 2025
Line 13:		Line 13:
	(2) Over what amount of time you expect the check-ins to occur.		(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. ~~Here is a [[Script for Checking~~ in ~~Stations Alphabetically~~ by ~~Tactical Call Signs]]~~.		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.

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

	==== Compiling a Roster of Teams ====		==== Compiling a Roster of Teams ====

BruceSchafer: /* Checking in Stations */ Added link to script for checking operators by tactical call sing

2025-05-25T18:32:26Z

Checking in Stations: Added link to script for checking operators by tactical call sing

← Older revision		Revision as of 11:32, 25 May 2025
Line 13:		Line 13:
	(2) Over what amount of time you expect the check-ins to occur.		(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.		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. Here is a [[Script for Checking in Stations Alphabetically by Tactical Call Signs]].

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

BruceSchafer: /* Transmitting a Roster to ECC */ Updated info

2025-04-02T19:58:37Z

Transmitting a Roster to ECC: Updated info

← Older revision		Revision as of 12:58, 2 April 2025
Line 92:		Line 92:
	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.		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 ~~ECC~~ ===		=== Transmitting a Roster to the Portland EOC ===
	After completing checking stations into your subnet, you need to switch to Tactical Net on MC-8 to give them your check-in roster. You should do this even if you’re not sure that all stations in your region have checked in. Before leaving the frequency ask one of the AROs on frequency to serve as temporary subnet control. Then transition to Tactical Net and give them the tactical call signs of the AROs that checked into your subnet. Tactical Net may ask you for clarification of what teams are represented by each tactical call sign. When that information is acknowledged, return to your subnet and resume ~~SNC~~ role.		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.		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.

BruceSchafer: /* Handling Traffic from Emergency Coordination Center to NET Teams */ Changed "Coordination" to "Operations"

2024-10-28T16:47:57Z

Handling Traffic from Emergency Coordination Center to NET Teams: Changed "Coordination" to "Operations"

← Older revision		Revision as of 09:47, 28 October 2024
Line 139:		Line 139:
	[Return to your subnet frequency.]		[Return to your subnet frequency.]

	=== Handling Traffic from Emergency ~~Coordination~~ Center to NET Teams ===		=== 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:		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: