Incident
(a.k.a.) Communications Emergency - Any planned or unplanned occurrence or event, regardless of cause, which requires action by emergency service personnel to prevent or minimize loss of life or damage to property and/or natural resources. 

Net
A Communications Network (Net) is established to handle the information flow (traffic) for an event or incident when there are three or more stations involved or when the volume of traffic is sufficient that it cannot be handled on a first-come first-served basis. A Net will be established to open all incidents. A Net will be opened for events as soon as there are three or more operators and may be opened sooner. 

Net Control Station (NCS)
NCS is the person charged with controlling the information flow during a net. The NCS has authority over all traffic handled by the Net and determines the order in which other stations use the frequency and when they pass their traffic. The NCS is not in charge of the event or incident, only the information flow during the net. 

Net Script
A set of notes or a formal document created as a guideline to aid the NCS in conducting regularly scheduled Nets. 

Tactical Call
A name assigned to a specific station in a net that describes the function, location or assignment of that station. It allows anyone to call the station by its tactical call rather than the IC issued call of the operator and thus minimizes confusion at shift changes or when operators take a break from their duties.

SUGGESTION: Have more that one copy of the script so you can mark it up as you go. That simplifies keeping track of where you are in the net. It also makes it easier to maintain the essential - LOG - of who checked in and who had traffic. 

The second type of net is the Public Service event nets. These are seldom, if ever, scripted and as such it is far better for you to have run many weekly nets (ten to thirty - depending on the individual) before attempting one of these. They range from very simple with a length of one or two hours, to extremely complex, running several hours to multiple days. Logs of the net activity are very important to smooth operation of this type of net.

The third type of net is the incident or emergency net. These range from complex to very complex and tend to be much more fast paced than they should be (SLOW DOWN - you pass more traffic faster that way). It is recommended that you have run many event nets, if at all possible, before attempting and incident net. Maintaining accurate logs for these nets is critical to effective net operation.

The weekly net or very simple event net are the only nets that can be run effectively by one person. All others require at least two people at NCS to run efficiently - one person to talk and one to log. In long term or very complex nets, a third operator is strongly recommended. This third person can handle messages, runner tasks, and relieve the other two operators at regular intervals so all can operate at higher efficiency.

To begin a scheduled weekly net you will: 

• Get a copy of the Net Script if one exists
• READ IT before you start.
• Check with your net manager or EC to find out when (time) and where (frequency) the net is to be run.
• Start the net on time. Remember, there will likely be many people waiting for the net. Don't waste their time by being late.
• Be as concise as possible as you conduct the net.
• SMILE - your ability to be friendly helps these nets run more smoothly.

To begin a scheduled event net you will need: 

• A copy of the roster of participants
• A map or description of where the stations will be located.
• The time and frequency you will start operating on.
• A description of what we are to accomplish.
• You will then: 
• Open the net with a description of the event and how long it is anticipated to run.
• Call for check-ins and issue Tactical Calls based on the operators function or location.
• Be as concise as possible as you conduct the net.
• Keep good logs!
• Handle traffic.

To begin an incident net you will: 

• Get a description of the incident and what support is needed.
• Find out from your EC or AEC where and when the net is to be run
• Find out what resources are needed to support the incident. Remember, you will probably be the staffing net for the first period of time for this incident.
• Open the net with a description of the incident and a statement of what help is needed.
• Be as concise as possible as you conduct the net.
• Keep detailed logs!
• Follow your EC's instructions.
• Handle traffic.

Two important items: 

• If NCS cannot be heard by all stations on a given repeater system -- and there are qualified NCS operators who can be heard by all -- NCS duty should immediately be turned over to the station that can be heard. 

• For all nets - Do your best to remain as calm and relaxed as possible, give it an honest try and ask for help if you need it. Nothing more will ever be asked of you. One last hint - ask for a mentor for your first few nets of each type. This helps you learn faster and insures someone can help you pick things up, should you fumble anything significant.

1) Is the NCS location away from the Command Post?
The noise and commotion at CP degrades your ability to run a good net and the noise you generate only adds to the confusion there.

2) Do you have the best performing antenna for the conditions?
A "rubber duck" is not adequate unless you can see the repeater antenna. That does not mean see the mountain the repeater is on, it means see the antenna.  For HF, polarization of your antennas WILL affect your signal to others.

3) If you are running from battery: Do you have at least enough charge on the battery to run more than one hour?
You should have a battery with 90+% charge but if you are the only choice for NCS then make sure you can run the net long enough to have some one else get ready.

4) Are you using a headset with noise canceling microphone?
Even from home the background noise will affect how well you can hear and be heard.

5) Do you have pencil/pen and paper sufficient to run the net for a full shift? 
You will NOT be able to remember enough about the traffic to be effective unless you write it down.

6) For VHF/UHF: Do you know the characteristics of the repeater system you are on?
Your effectiveness as NCS will be adversely affected if you do not. 

7) Do you have a runner, liaison or logging person to support you? 
For large scale events all three are required. You cannot handle the net and run messages.

8) Do you have a designated relief operator?
Everyone gets tired and NCS must be the most alert operator on the net.

Good communications skills and fluent command of our language 

Good voice quality 

Good hearing capabilities 

Good listening capabilities 

Good ear-to-hand copying skills 

Understands what SERVICE means 

Has knowledge of the Incident Command System 

Willing to take and carry out direct orders 

Is a strong team player 

Is Self-assured but not overbearing 

Decisive, with the maturity to make good judgment calls 

Physically able to tolerate high stress for extended periods 

Constant concern for the safety of participants 

Organizer 

Sense of humor 

Ability to absorb new terminologies quickly 

Decent (readable) penmanship 

Generally neat of appearance 

Consistently demonstrates above average operating techniques 

Knowledge of band characteristics 

• Have the best performing antenna for conditions. A "rubber duck" is not adequate unless you can see the repeater antenna. That does not mean see the mountain the repeater is on, it means see the antenna. For HF, polarization of your antennas WILL affect your signal to others.

• Plan what you are about to say as if you will be quoted. PTT does not mean Push Then Think.

• When asking for reports or soliciting traffic, listen! 

• Take down as many calls as you can identify before you acknowledge anyone!

• A good log is critical to an efficient operation. Create / use a good log! A few calls scribbled on a sheet of paper, in no real order, becomes useless in a few seconds. Make sure your log includes:
• 1)Time of the entry 
• 2)Call / Tactical call 
• 3)Summary of what was said or requested. Be sure not to kill yourself with excessive details. The log is an overview of who did what, where and when.

Slow Down! Wait three or four seconds before you answer any call. This assures any emergency or priority traffic has access to the net without requiring the largest signal.

Acknowledge all stations that you heard, then yield the frequency to a single station. When that station is finished, hand the frequency to the next station on the priority list, without soliciting more traffic. Follow this pattern until you've completed your list, then repeat. The exception to this is in handling routine traffic during an emergency. With routine traffic during an incident net, break between messages to solicit any emergency/priority traffic and handle that first.

The net-name/function and the NCS callsign, should be announced several times at the beginning of the net and every eight to ten minutes during the net. Many NCS' use the repeater IDer to track the time to identify.

When acknowledging checkins, list the callsigns as letters (not phonetically). The purpose of this acknowledgment is to confirm to each checkin that his/her call was heard. Phonetics used on all acknowledgments simply slows the net. NOTE: Phonetics are an excellent way to clarify questions about the call received (was that a B or a D, etc.). Reciting all of the check in information (beyond the call) simply wastes time.

DO NOT make editorial comments about the traffic or information being passed unless it will speed or enhance the information flow! Chattiness, especially early in the net, degrades the effectiveness of the net.

For scheduled nets, NCS' goal should be to run the script top to bottom and handle all of the listed traffic, business/comments as quickly as possible, without rushing. If you are concerned that this makes the net "too cold" you could schedule a "chat session" at the end of the net or just after the net closes. 

If someone tunes up on the net frequency during the net (SSB, CW, etc.), remind them ONE TIME that this constitutes harmful interference and should be done off the net frequency. Repeating this notification will only serve to encourage those attempting to interfere with the net. Some HF nets even schedule one minute for tune-ups.

When there is a double, try to get something unique from one or more of the stations. Then call for clarification from those stations ONLY. The alternative approach is to acknowledge the check-ins you could understand and then call for checkins that tried in the last round but were not acknowledged.

If your net is passing NTS traffic, remind participants to read the variable information in order without the redundant field identifiers such as: "Check", "phone figures", etc.

Most participants will catch on quickly to the pattern. If they do not, take the time to explain. Things get done much faster if everyone uses the same techniques.

Be as concise as possible. Use the fewest words that will completely say what you mean. This will minimize the need for the repeating of instructions.

Take frequent breaks. While you may not recognize the stress that being an NCS produces, it will become evident in your voice. If you are asking yourself when your last break was, you know it is time for one. Turn over the net to your backup at least every two hours and REST. Do not listen to the net. Rest. Then, when rested, listen to the net for a few minutes before resuming your station.

Speak in first person. It is "recognizing ve3xxx" or "roger ve3xxx" NOT "NCS would like to recognize ve3xxx" or worse yet "Net recognizes ve3xxx". This is important because it shows a subconscious acceptance of leadership. The person "bought into" running the net. They subtly reinforce the NCS' authority by telling everyone they accept full responsibility for operating the net.

Control the tone of your voice. Be as calm as possible. Tension tends to make our voices raise in pitch and this change will be picked up by the net. Use a calm tone and members of the net will tend to remain calm.

1) Report to the NCS promptly as they become available. 
2) Ask clearance from NCS before using the frequency. 
3) Answer PROMPTLY when called by NCS. 
4) Use tactical call signs. 
5) Follow established net protocol. 

One way of classifying a net is the level of net discipline used, or the "style" of the net. The two acknowledged styles are:

vOpen (Informal) Nets
During an open net most any type of traffic or communication is permitted. Conversations (rag-chews) are permitted provided they break every so often to allow incident related traffic to flow. 

vDirected Nets
A Directed Net is created when there are a large number of stations needing to use the frequency or the volume of traffic cannot be dealt with on a first-come first-served basis. The NCS will determine who uses the frequency and what traffic will be passed first. Casual conversation is discouraged and tactical call signs will be used as applicable. 

Like anything else, being a good NCS requires practice. Contact your local EC or Net Manager for opportunities in your area!

1) Time of the entry 
2) Call / Tactical call 
3) Summary of what was said or requested. 

Be sure not to kill yourself with excessive details. A good log is critical.

Be friendly yet in control - speak slowly and clearly with an even tone, not a monotone. Sound confident, even if you are not. Above all, don't worry. Just give it an honest try.

Ask SPECIFIC questions, give SPECIFIC instructions! You can make it much harder on yourself with nebulous questions and instructions.

Slow Down! While it may seem counter-intuitive, you will actually handle more traffic in less time when you wait three or four seconds before answering any call.

DO NOT make editorial comments about the traffic or information being passed unless it will speed or enhance the information flow! An ARES or NTS net is not about your opinion, it is about efficient information flow.

Read your owner's manual and understand how to use your microphone. The worst sounding NCS is one that cannot be heard or sounds like a train huffing and puffing into the microphone as they speak. Articulate, don't slur. Speak close to your mike, but talk across it, NOT into it.

When there is a double, try to get something unique from one or more of the stations. Then call for clarification from those stations ONLY. During check-ins, recognize participants by name whenever possible. Acknowledge checkins and ALL messages.

Be sure to frequently identify the purpose of the net (let people know what they are checking in to!) and advise all listeners of the subaudable frequency required if applicable.

Ask for assistance if/when you need it. If this is not a weekly net, delegate responsibilities. You cannot do it all.

Maps are VERY helpful in events or incidents.

If this is an emergency net, remind listeners to listen and tell them where the staffing net is. Someone checking in to say they are listening only slows the net.

Don't be afraid to say "OOPS" if you get flustered and mumble a bit. Pause, take a deep breath, and go back at it. If you make a mistake, remember this is not Brain Surgery. Do your best to CALMLY recover. Nothing more will ever be asked of anyone.

DON'T THINK ON THE AIR! If you need a moment to consider what is needed next, say something like "Stand by" and unkey your mic. Keep transmissions as short as possible. Resist the tendency to ragchew or ramble.

Transmit only facts! If there is need to make an educated guess or speculate, make sure it is VERY clear that it is speculation. First choice is to not speculate at all.

Avoid becoming the source for general information about the event. If it is an emergency, refer incident status questions to the served agency Public Information Officer (PIO).

When necessary, use standard ITU phonetics. There is no such thing as "common spelling". Send all numbers as individual numbers, e.g., 334 is three three four not three hundred thirty four.

Speak in first person. It is "recognizing VE3ZZZ" or "roger VE3ZZZ" NOT "NCS would like to recognize VE3ZZZ" or worse yet "Net recognizes VE3ZZZ". This is important because it shows a subconscious acceptance of leadership. The person "bought into" running the net. They subtly reinforce the NCS' authority by telling everyone they accept full responsibility for operating the net.

For voice nets, use plain English. "Q" signals are for CW.

If the net has been quiet for more than ten minutes, check on operator status. This keeps the net running more smoothly and insures you know about equipment failures as soon as possible.

As NCS it is up to you to plan for your backup and have backup equipment available for your use. Every emergency net and the vast majority of event nets require at least one extra person at the NCS position. Ideally, there will be three people at NCS for any emergency or major event net. This allows one person to act as NCS, one person to handle logging and the third to handle liaison with the served agency and act as runner. The people at NCS will rotate assignments about each hour.

Try to obtain more volunteers than you have positions to fill. Wait! More volunteers than you have need for? Yes. On average, for every ten volunteers you get, there will be at least one that will develop equipment problems, or have transportation problems, or have personal emergencies that develop. If you have only "just enough" volunteers, you actually are short ten percent for the event.

Having one or two "floaters" who can act as relief for almost any of your operators WILL help the event run more smoothly. In addition, having an extra person to act as - runner - handling message transportation to/from your served agency will help your group function more efficiently. The side benefit is that should one of the volunteers prove to not have sufficient training, they can become the backup on that job and have a successful training experience during the event.

• List or note of outstanding messages to/from the location 
• Log of traffic to/from the location.These two items may be one log, properly annotated 
• Status of open queries 
• Local and remote contacts for the location (served agency and others as necessary) 
• Any other information the outgoing operator feels necessary 

NCS
The best way to handle NCS coverage breaks is with a known NCS backup. This person is known to the net and has a duplicate copy of the operational log for the event and thus is able to pick up operation of the net in just a few moments. When there is not sufficient resource to have a backup NCS then the person with the best NCS skills and most complete staff at their location should take over the net. This person will start with a call for emergency traffic, handle that, then go to roll call to establish continuity. After which regular net traffic will resume. NOTE: As this person takes over the net they will no longer be available to handle the previous assignment. A relief operator will need to be dispatched to handle the new NCS' previous assignment!

Non NCS
When a station fails repeatedly to respond to calls from NCS an assessment must be made of the criticality of the traffic. If there is critical traffic holding for that station then a relief operator will need to be dispatched immediately. If the traffic can be held for several minutes then a re-evaluation should be made at that time. If the coverage break was from equipment failure and that can be corrected, then the relief operator may be recalled. If the coverage break was from being inattentive, the relief operator should take over.

• Slow up. Don't respond instantly. Take a deep breath. 
• Do a quick review of what you know about this person. 
• DO THE NEXT THREE STEPS ALL IN ONE STATEMENT. 

1) Acknowledge the problem. Give in to the 'Problem' Whether they are right or wrong! This acknowledges that there is a problem and that you are recognizing that fact. Once you agree that there is a problem, the 'fight' is gone. 

2) Empathize with them! Whether you understand or not, tell them that you can understand how they can feel that way and that, were the situation reversed, you would probably feel the same way. 

3) Ask them to suggest a simple yet reasonable solution. Listen intently! This is where they will reveal the real problem. Everything they have said up to now may have been a loud smokescreen. Somewhere in their suggestion, they will tell you what they really want from you.

• If their suggestion/solution is reasonable, tell them that you will try to put it into play. If it is not, make a counter-suggestion that will satisfy the real problem that they have revealed to you. 
• If the problem cannot be resolved quickly and reasonably, quietly send someone to replace this individual and relieve him from his post. If there are no posts involved in the operation, give up . . . let him win . . . politely explain that the net must continue, thank the person for his services and tell him he doesn't have to stick around. You tried to solve the problem reasonably and he refused. He wins the fight and you win the battle. The rest of the net will respect what you did and morale will remain intact. 

Unfortunately, there are people who prove there is need for more chlorine at their end of the gene pool. To overcome the interference from these individuals you will have to plan for it. Plan by having alternate frequencies announced at the pre-event briefing. Should the interference become intolerable, move to the alternate frequency. When you move to another frequency, do so under pre-announced set of conditions (at the briefing) and without saying anything on the primary frequency. Another very successful method involves the use of your local "fox hunters" to track down the offending station. This will need to be a well coordinated effort that is not announced on the net frequency.

Be willing to learn. 

Accept constructive criticism politely. 

Contact your district Emergency Coordinator and volunteer. 

Contact the person in charge of your local traffic net and volunteer. 

Contact your local Amateur Radio club to see if they have a net. If so volunteer. 

Look for the group that handles public service events in your area. Many times this will not be the ARES group, so volunteer. 

Work with the best NCS you can find. This person will be able to show you (if you care to watch) a lot of subtle, but important techniques. 

Work as NCS as often as you can. 

Your group
You are now at the point where you are accepting management duties. With these duties come the responsibility of becoming one of the people who MUST be concerned with how well each of the people in your group interact with others. The easiest way to start this process is to make VERY brief mental notes to yourself on what person-x did wrong, or better yet what person-x did that was a great help. People respond very well to positive feedback and when you are consistent and accurate with positive feedback you will find your job much easier. Please understand that if you become known as the local "snitch" people will cease to cooperate / interact with you. Thus it is important that you make comment ONLY when there is noticeable negative impact by person-x and that you are very accurate in your assessment. You, and the group, will be well served if you can just take person-x aside and provide them with friendly help to resolve the situation.

Served Agencies
The second portion of liaison is with your served agencies. This can be either quite easy (if the people before you had a good working relationship with the agency) or very difficult should you have to "re-educate" your served agency on the value of ARES. When the re-education (or occasionally initial education) of a served agency is required, it is imperative that you are viewed as a team player that is there to help when and where they need help. This is easiest if you keep a few things in mind: 

• Every public service agency has daily contact with people that are very negative. 
• Police departments and Government agencies have had negative encounters with people that want to be a Police person or fire person but do not have "what it takes". 
• Police and Government agencies are most comfortable when THEY are in charge. 
• They may be embarrassed at having to ask for help. 

The key word in dealing with a served agency is SLOWLY. If you attempt to push, go too quickly (except in response to their requests) or attempt to tell them how to run their business, your efforts will fail.

There is a fine line between being available and being pushy. You will need to be very careful as you approach this line to insure you do not cross it. With that said, there are many agencies that appreciate regular contact and it does prove very helpful.

vStick to the subject. 
Examples, used to make a point, are good. So long as you spend more time with the main material than on examples (commonly called "war stories"). 

vVary your speed of presentation. 
Highly technical information should have a slower presentation rate while simpler material can be covered more quickly. Take extreme care to realize what is simple to some may be quite complex to others. 

vOrganize your material. 
The standard "timing" for course preparation is two hours of preparation time for each hour of presentation time. This will vary with how many times you have taught the material. The first time you do a segment you may need three to four hours of prep. time for each hour of class. 

vHave a specific learning goal in mind for each segment.
The most effective presentations are short, concise and handle one subject. 

vUse charts and diagrams as applicable.
Many people find it easier to learn material when they have "pictures" to help with explanations. The old true-ism states "a picture is worth a thousand words". 

vMake copies of the material for your students. 
Handouts give the student a good place to make notes and insures they will have a place to find those notes later. 

vMake notes to yourself - on your copy - about which examples work best for this segment.
As you teach, you will find specific examples that work very well in emphasizing a given point. The notes will help you remember which one(s) work the best and where. 

vAbove all else, try to have fun while you teach. 
Students pick up, very quickly, how relaxed you are. If you are having fun teaching, your students will probably have fun learning. 

• Yes items - can you answer yes to all of these 
1. If it was a scheduled net, did I start the net on time? 
2. Was I prepared? 
3. Did I use my microphone correctly? 
1. No huff and puff from P, B, etc. 
2. No breath sounds 
3. Volume consistent 
4. No distortion 
5. No (or minimal) background noise 
4. Did I allow enough time for net participants to reply? A consistent four to five second wait is essential. 
5. If on a repeater - Did I listen well and hear stations without asking for multiple unnecessary repeats? 
6. If on a repeater system - Did I properly utilize the unique properties of the repeater system? 
7. If on HF - Did I ask for relays as appropriate? 
8. Did I handle acknowledgments correctly? 
1. Not repeating phonetics 
2. Not repeating checkin information beyond the call and those with traffic 
3. Not missing multiple checkins 
9. Did I speak in first person during acknowledgments? ("Net would like to recognize ...." is not first person) 
10. Did I handle "doubles" properly? 
11. Did I ask specific questions? 
12. Did I give specific instructions? 
• No items - can you answer no to all of these 
1. Did I over identify? 
• Was this a script problem? 
2. Was I overly talkative? 
3. Did I mumble or fumble through more than one item? 
4. Did I seem in a hurry? 
5. Did I make editorial comment on more than one item? 
6. Did I seem to be under stress? 
7. Did I seem to "get lost" and have to think on the air (dead air time)? 

• Overall: Were you comfortable with the net?  If not, what specific items would improve the net?