[CoARES-D10] Net script

Fri, 27 Feb 2004 11:36:37 -0500

Randy,
	I like this idea of mixing things up, I think it would increase
participation and hone skills (especially listening skills) which are vital
to "real" events. Perhaps we have a couple outlines; the current script, a
script where checkins with traffic are taken first, or last, or where all
traffic is handled before any general checkins (forces people to listen to
all the announcements). 
	Having different methods of running would be a good thing, and
perhaps start out the different ones for awhile with "Please listen
carefully to NCS, the net is being run in a different format tonight". 

This would force the following:

1. The NCS would have to think things through more, and control the flow.
2. The participants would have to listen to what's going on more.
3. Some methods would force traffic through during the time when people are
listening.
4. For both the NCS and the participants would be operating in a mode more
like a real event, which is much of the purpose of the net to begin with -
training.

Let's shuffle things around and keep people on their feet! :)

-Barry N0WOZ

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of On Track
Investigations, Randy Long
Sent: Thursday, February 26, 2004 7:43 PM
To: Pat Lambert - W0IPL; ARES D-10
Subject: RE: [CoARES-D10] Net script

Lets add a couple...

* Train our NCS and not just throw them to the wolves with  a net script

* Have training for our net participants so they understand procedures

* Remove unnecessary verbiage from the script

* Leave the script  as flexible for NCS to do things differently so
participants learn that they need to listen. Perhaps call it "NCS
Discretion".

Allowing NCS to be flexible and permitting change in the program does  a
multitude of things. Here are just a few:
1. Makes NCS think before altering the script.
2. Requires net participants to listen.
3. Often creates more participation, because of people anticipating "what's
going to be different this time?"
4. Allows NCS and net participants to be more flexible should an event
require it.

Remembering that people are creatures of habit. If its frequently different
on the weekly net, and people learn to be flexible and go with the flow,
listening to NCS, they will be more inclined to do it should there be an
activation. We break the cycle or at least recondition the "Auto-Pilot
Response".

Just some thoughts on that topic...

Randy

 -----Original Message-----
From: 	[email protected]
[mailto:[email protected]]  On Behalf Of Pat Lambert - W0IPL
Sent:	Thursday, February 26, 2004 6:31 PM
To:	ARES D-10
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
[email protected]
http://mailman.qth.net/mailman/listinfo/coares-d10

_______________________________________________
CoARES-D10 mailing list
[email protected]
http://mailman.qth.net/mailman/listinfo/coares-d10