In the realm of emergency management and response, specific forms play crucial roles in the orchestration of resources and services during incidents. One such document, the ICS 213 RR TX form, stands as a cornerstone in this meticulous process. This form, delineated as a Resource Request Message, serves as a structured method for requesting resources, providing a streamlined avenue for communication between various entities involved in emergency response efforts. It mandates the requester to fill out detailed information including the incident name, date and time, various tracking numbers, and a comprehensive description of the resources needed, including quantity, item description, cost, and demobilization details. The form also requires the requester to provide purpose, priority, contact information, and approval signatures, making it a critical tool for efficient incident management. Moreover, the ICS 213 RR TX form embodies the intersection of thoroughness and urgency, encapsulating essential data points that facilitate the expeditious provisioning of resources, thereby highlighting its significance in emergency response frameworks.
| Question | Answer |
|---|---|
| Form Name | Ics 213 Rr Tx Form |
| Form Length | 1 pages |
| Fillable? | No |
| Fillable fields | 0 |
| Avg. time to fill out | 15 sec |
| Other names | ics 213 rr example, TX, ics form 213 rr examples, Demob |
RESOURCE REQUEST MESSAGE |
|
|
|
|
|
Fax to # ( ) |
|
Note to Requestor: |
fill in all shaded areas for expedited service |
|
|
|
|
|
|
|
|
INCIDENT NAME: |
DATE & TIME: |
|
|
FORM REQUEST #: |
|
|
|
|
|
|
|
COUNTY / MOC TRACKING #:
CITY / HOSPITAL TRACKING #:
DDC TRACKING #:
R
E
Q
ORDER NOTES: Use additional forms when requesting different resource sources of supply
Qty. Item† Unit†† Detailed Item Description |
Cost |
Demob |
(kind, type, vital characteristics, brand, spec, size, etc.) BE DESCRIPTIVE |
(if known) |
Item? ††† |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
† Item Name |
†† Unit of Measure: (case, ea, pallet, etc) |
††† Demob: Will the item need to be included in Demobilization? |
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
U |
|
*Purpose for Request (REQUIRED): |
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*Point of Contact Name: |
|
|
*Point of Contact Telephone #: |
|
|
*Facility Name: |
|
|
||||
E |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
*Physical Address: |
|
|
|
|
*City: |
|
|
*County: |
*State: |
*Zip |
||
S |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
T |
|
*Requested by (Name & Position): |
|
|
*Requestor Telephone #: |
|
|
*Requestor |
|
*Priority: |
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
O |
|
Supervisor |
|
|
|
|
|
|
|
|
|
Date: |
|
|
|
|
Signature/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
X |
|
|
|
|
|
|
Time: |
|
|
|||
R |
|
Approval: |
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Supervisor Notes: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Section Chief |
|
|
|
|
|
|
|
|
|
Date: |
|
|
|
|
Signature/ |
|
X |
|
|
|
|
|
|
|
|
|
|
|
|
Approval: |
|
|
|
|
|
|
|
Time: |
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Section Chief Notes: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Request filled by: |
|
|
|
|
Local |
MACC/MOC |
PHR |
DDC |
SOC |
Route to: |
|
|
|
|
Logs
Finance
Requestor
Documentation
Additional Notes/ Details:
Requestor fills out items in yellow and keeps copy; each branch or section fills out their listed portion and keeps copy. This document, when used in conjunction with a unique WebEOC user account, can be considered an electronically signed copy.
*Required |
TWIRP BOARD v2.6 |