[CoARES-D10] Net script

[Brent Shaw]

I was apparently typing my first response while Pat was composing his.  I will summarize my suggestion:

The net script provides general guidelines, but the NCS should have the freedom to tweak it to his/her preferences and everybody else needs to listen to the instructions.  Using a concrete standard week after week promotes an autopilot response, which may not be useful in real-world situations (but can be efficient, admittedly).  Since it is a training net,  I think having to listen more carefully is better practice than assuming everything is always the same.

Brent

-----Original Message-----
From: Pat Lambert - W0IPL <w0ipl@earthlink.net>
Sent: Feb 26, 2004 6:30 PM
To: ARES D-10 <coares-d10@mailman.qth.net>
Subject: [CoARES-D10] Net script

So far, what I see for suggestions are:

*- Separate checkins with traffic
*- Do not recall AECs etc. for traffic, if they indicated they did not 
have traffic
*- Make sure everyone has the latest level of net script (the last 
update  changed the order of information given (new= call, name, 
location, if you have traffic)
*- Clarify how we call for traffic (having a separate segment of 
checkins would handle that)
*- Standardize how we define our net process / script
*- Have multiple "models" (net scripts) for the various types of net we have

How many did I miss? How many did I misunderstand?

I love it! Let's keep this going!

Thanks
  Pat


_______________________________________________
CoARES-D10 mailing list
CoARES-D10@mailman.qth.net
http://mailman.qth.net/mailman/listinfo/coares-d10