5,013
edits
NET Incident Command System (ICS) Forms: Difference between revisions
From WikiNET
NET Incident Command System (ICS) Forms (view source)
Revision as of 14:31, 16 November 2022
, 16 November 2022→Form Design and Printing Considerations
mNo edit summary |
|||
| Line 1: | Line 1: | ||
[[File:2015.10.24.Op Whitestag.EJones (14).jpg|thumb| | [[File:2015.10.24.Op Whitestag.EJones (14).jpg|thumb|''Using NET ICS Forms during Operation Whitestag at [[Scenario Village]]. Photo by Ernest Jones, October 24 2015.'']]ICS forms provide a template to NET volunteers for documenting activities during a deployment. Though efforts to save life and property take priority over documentation, <span style="background:#FFFF00">'''documenting activities is nonetheless important and should be a routine part of NET training, drills, and response.'''</span> Documentation serves several crucial functions: | ||
* Documentation passed to other emergency responders helps them understand the status of resources, allowing them to deploy their own resources effectively and appropriately. '''Good documentation saves time, and therefore, lives.''' | * Documentation passed to other emergency responders helps them understand the status of resources, allowing them to deploy their own resources effectively and appropriately. '''Good documentation saves time, and therefore, lives.''' | ||
| Line 28: | Line 28: | ||
== Form Design and Printing Considerations == | == Form Design and Printing Considerations == | ||
NET ICS Forms are based on, but are not identical to, standard CERT ICS Forms provided by FEMA in the CERT textbook. Over the years, exercises using FEMA forms have prompted NET volunteers to add forms to the forms packet (such as Form 2b and 5b) | NET ICS Forms are based on, but are not identical to, standard CERT ICS Forms provided by FEMA in the CERT textbook. Over the years, exercises using FEMA forms have prompted NET volunteers to add forms to the forms packet (such as Form 2b and 5b) and tweak existing ones to better suit NET volunteers. NET ICS Forms differ from FEMA's CERT ICS forms in the following ways. | ||
=== Tracking Numbers === | === Tracking Numbers === | ||
As an option, NETs may use the tracking number spaces provided on some forms. Forms 2a through 5b provide a space for an arbitrarily assigned tracking number. Tracking numbers are for internal team use; therefore, a NET Team Leader can decide on whatever number convention works best (e.g. 0001, or simply “1”, etc). Tracking numbers connect forms to each other where those forms are used on a specific mission; in other words, the tracking number is the same as a “mission number”. Assigning mission numbers may make it easier for teams and emergency professionals reviewing documents to connect events. | As an option, NETs may use the tracking number spaces provided on some forms. Forms 2a through 5b provide a space for an arbitrarily assigned tracking number. Tracking numbers are for internal team use; therefore, a NET Incident Team Leader can decide on whatever number convention works best (e.g. 0001, or simply “1”, etc). Tracking numbers connect forms to each other where those forms are used on a specific mission; in other words, the tracking number is the same as a “mission number”. Assigning mission numbers may make it easier for teams and emergency professionals reviewing documents to connect events. | ||
For example, let’s say that a Team Leader sends one functional team to conduct search and rescue in a house (tracking number #001) and another functional team to establish radio communication (tracking number #002). Any forms associated with those respective missions (e.g. a medical treatment log or an assignment briefing) will also include their mission tracking number. Later, when reviewing documents, a Team Leader knows that any document with the number “#001” on it is associated with the house search and rescue mission. | For example, let’s say that a Team Leader sends one functional team to conduct search and rescue in a house (tracking number #001) and another functional team to establish radio communication (tracking number #002). Any forms associated with those respective missions (e.g. a medical treatment log or an assignment briefing) will also include their mission tracking number. Later, when reviewing documents, a Team Leader knows that any document with the number “#001” on it is associated with the house search and rescue mission. | ||
=== Form Heading Colors === | === Form Heading Colors === | ||
Unlike FEMA ICS Forms, NET Form types are grouped and the groups are color coded. Cognitive scientists | Unlike FEMA ICS Forms, NET Form types are grouped and the groups are color-coded. Cognitive scientists know that color-coding highlights organization and guides cognitive processing. In this way color-coding reduces extraneous mental processing demands, and that can be helpful in the midst of an emergency response. | ||
However, printing the forms in color is only a recommendation and NOT a requirement. Printer ink is expensive. Therefore, all forms are printable in black and white. | However, printing the forms in color is only a recommendation and NOT a requirement. Printer ink is expensive. You're probably out of cyan ink right now. Therefore, all forms are printable in black and white. | ||
=== Weatherproof Paper === | === Weatherproof Paper === | ||
Oregon's notoriously damp weather means | Oregon's notoriously damp weather means PBEM discourages printing forms on regular paper if possible. In a disaster, volunteers may find themselves working outdoors and rain will quickly render forms on regular paper into a mess of illegible pulp. Therefore, PBEM recommends printing ICS forms on [https://www.riteintherain.com/ Rite in the Rain] paper or other waterproof paper. | ||
This advice applies only to forms for an actual response. PBEM encourages printing forms on regular paper for use during exercises and training. | This advice applies only to forms for an actual response. PBEM encourages printing forms on regular paper for use during exercises and training. | ||
== Documentation Flow == | == Documentation Flow == | ||
[[File:NET ICS Form Flow.jpg|alt=Diagram of the relationship between Forms 1, 3, and 4. Click to enlarge. Illustration by Hugh Newell.|thumb|355x355px|'' | [[File:NET ICS Form Flow.jpg|alt=Diagram of the relationship between Forms 1, 3, and 4. Click to enlarge. Illustration by Hugh Newell.|thumb|355x355px|''Figure 1: Diagram of the relationship between Forms 1, 3, and 4. '''Click to enlarge.''' Illustration by [https://www.instagram.com/hughnewell/?hl=en Hugh Newell].'']] | ||
The most important forms to a NET are forms 1 through 4 | The most important forms to a NET are forms 1 through 4. Forms 5 through 8 supplement work at specific stations (e.g. radio, medical, logistics, etc). Any form filled out and no longer of use should be kept for handing in to PBEM. | ||
Forms 1, 3, and 4 flow in a way that outlines an anticipated NET response ( | Forms 1, 3, and 4 flow in a way that outlines an anticipated NET response (Figure 1). The first form, [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms#NET_Form_1:_Damage_Assessment_Form Damage Assessment], is used by NET volunteers traveling to the NET Staging Area; volunteers record observed damage and other trouble spots along the way. | ||
Form 3, the Team Leader Assignment Tracking Log, acts as a “dashboard” for the Team Leader. Working with his/her team, the | Form 3, the [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms#NET_Form_3:_Team_Leader_Assignment_Tracking Team Leader Assignment Tracking Log], acts as a “dashboard” for the Incident Team Leader. Working with his/her team, the ITL transfers any potential area of response from Damage Assessment forms collected from the team onto the Tracking Log. This tool thereby helps the ITL easily track each functional team deployed from the NET staging area. | ||
Form 4, the Assignment Briefing, is filled out by the | Form 4, the [https://volunteerpdx.net/index.php/NET_Incident_Command_System_(ICS)_Forms#NET_Form_4:_Assignment_Briefing Assignment Briefing], is filled out by the ITL when ready to deploy a functional team to respond to an item on the Tracking Log. On the front, the Assignment Log has spaces for giving the functional team the information they need to get to the scene quickly and safely. The functional team then records their response actions on the reverse side, and turn the form in to the ITL when they return to the NET Staging Area. The ITL reviews the reverse side, transferring relevant details to their Tracking Log. ITL then archives the Assignment Briefing with the Documentation Unit. | ||
== NET ICS Form Instructions and Descriptions == | == NET ICS Form Instructions and Descriptions == | ||
