Fully qualified event name and "short name" as applicable. Include high level Served Agency (SA) information as applicable. This is how we will refer to the event / incident from now on.
Full list of event location(s) and any special requirements those locations may have. Special note must be made of any unique access requirements or antenna considerations for any location(s)
Full list of event date(s) and time(s) or range. If specific functions are on separate days, be sure to note these. For example: Setup on day 1, event on day two and tear-down debrief on day 3.
List the objectives for this event / incident. These should also include the objectives of groups outside of Amateur Radio. This allows our operators to better understand the scope of the occurence.
Include URLs of the served agency(ies) that will provide additional information to anyone that needs it.
You may wish to have the E-mail addresses in a form that is "non-harvestable" by internet data machines.
The following are the groups / organizations participating in this event / incident.
NOTE: If the phone numbers of all SA contacts, names, etc. are not public information, either do not put that information in this document or restrict posting this document to password protected sites only.
List date and times of all pre-event and post-event meetings. Don't forget the debriefing meeting!
How are you going to handle things. What process or approach will be used to support this event? Are there any unique modes that will be used? Any unique equipment or antennas? Will this be a heavy digital operation?
How much staff time will it take to handle the event/incident. Be sure to include time for generation of After Action reports.
How many operators will it take. List the minimum to adequately support the operation and also the optimal number to function well. Remember to plan for a minimum of two extra operators PER SHIFT !
Be sure to include any special or unique resource information for this incident/event!
Note any special insurance issues!
Note any pre-planned staging areas, clearly state any non-public access requirements and any unique requirements for staging.
|NCS Op's||Name||FirstName||Location and relief person information.|
|Incident Command||Contact Name||FirstName||Details|
|Staging Area||Contact Name||FirstName||Staging area location - if used.|
|Location 1||Contact Name||FirstName||Detail number 1|
|Location 2 has a much longer name than the others.||Contact Name||FirstName||Detail number 2. As you can see, some details require more space than others and with the HTML table processor, it works well.|
|Location 3||Contact Name||FirstName||Detail number 3|
|Location 4||Contact Name||FirstName||Detail number 4|
|Location 5||None Yet||Note how the background color can highlight items needing attention|
|Location 6||None Yet|
List the URL for, or links to appropriate maps for this event.
Overview route maps are suggested for events like the MS-150 but individual assignment location maps are very helpful to operators that are not familiar with the area. Please remember, just because someone lives within a mile or two of a location doesn't mean that person knows exactly where it is.
Mapping software will easily create BMPs or the recommended JPGs.
List all frequencies and repeaters that will be used for this incident/event. Be sure to include tone requirements and any special operational information needed.
Let the repeater drop between exchanges.
List all special equipment that will be required to support any individual site and anything unique for the total operation.
Common items are:
The full "GoBag" is available in HTML or PDF forms.
ABSOLUTELY NO VOX!
List all special operator instructions that will be required to support any individual site and anything unique for the total operation.
List expected operator responses as applicable.