NET Incident Command System (ICS) Forms: Difference between revisions

Jump to navigation Jump to search

NET Incident Command System (ICS) Forms (view source)

Revision as of 15:40, 5 November 2022

1,392 bytes added ,  5 November 2022
m
no edit summary
mNo edit summary
mNo edit summary
Line 3: Line 3:
* '''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.'''
* '''Documentation of liability exposure for volunteers.'''
* '''Documentation of liability exposure for volunteers.'''
* '''Improved communication between functional areas and between shifts.'''
* '''Improved communication between functional areas and functional teams, and between shifts.'''
* '''Thorough documentation facilitates reimbursements from FEMA.'''
* '''Thorough documentation facilitates reimbursements from FEMA.'''


Line 14: Line 14:
<span style="color:#ffffff">...</span>
<span style="color:#ffffff">...</span>


It is accepted and understood that ICS forms are not required for documenting operations. In a pinch, a sheet of ordinary notebook paper will suffice, or even the back of a paper plate. The benefit of the forms is that they '''''guide''''' NET volunteers to documenting the most relevant information and help them to accomplish their work. In this respect, ICS forms are not so much cumbersome paperwork as they are a helpful tool.
It is accepted and understood that ICS forms are '''''not required''''' for documenting operations. In a pinch, a sheet of ordinary notebook paper will suffice, or even the back of a paper plate. The benefit of using forms is that they guide NET volunteers to document the most relevant information. In this respect, ICS forms are not so much cumbersome paperwork as they are a helpful tool.


== The Role of the Scribe ==
== The Role of the Scribe ==
Line 24: Line 24:


'''Completed forms should never be thrown away.''' Forms serve as a response record and will be important when requesting reimbursement from FEMA.
'''Completed forms should never be thrown away.''' Forms serve as a response record and will be important when requesting reimbursement from FEMA.
== 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), and tweak the existing ones to better suit NET volunteers. NET ICS Forms differ from FEMA's CERT ICS forms in the following ways.
=== 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.
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 ===
Unlike FEMA ICS Forms, NET Form types are grouped and the groups are color coded. Cognitive scientists specializing in learning 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.
=== Weatherproof Paper ===
Oregon's notoriously damp weather means that PBEM discourages printing forms on regular paper if possible. In a disaster, volunteers may well find themselves working outdoors and rain will very quickly render forms on regular paper into a mess of useless 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.


== Documentation Flow ==
== Documentation Flow ==
Line 34: Line 52:


Form 4, the Assignment Briefing, is filled out by the Team Leader when she/he is 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 Team Leader when they return to the NET staging area. The Team Leader reviews the reverse side, transferring relevant details to his/ her Tracking Log. The Assignment Briefing is then archived with the team’s Logistics section.
Form 4, the Assignment Briefing, is filled out by the Team Leader when she/he is 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 Team Leader when they return to the NET staging area. The Team Leader reviews the reverse side, transferring relevant details to his/ her Tracking Log. The Assignment Briefing is then archived with the team’s Logistics section.
=== Optional: Tracking Numbers ===
As an option, NETs may use the tracking number spaces provided on some forms. Tracking numbers are not used with standard ICS forms; this is a NET embellishment.
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 are intended as a means of connecting 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.


== NET ICS Form Instructions and Descriptions ==
== NET ICS Form Instructions and Descriptions ==
Retrieved from "https://volunteerpdx.net/index.php/Special:MobileDiff/1350"

Navigation menu