Training/Committee/Tasks
From PCSAR
(Difference between revisions)
(New page: These tasks and suggestions have been referred to the Training Committee. {{quote-page|Critiques/2010-03-21/Sug13}} {{quote-page|Critiques/2010-03-21/Sug33}} {{quote-page|Critiques/2010-0...) |
m (Training Committee/Tasks moved to Training/Committee/Tasks) |
Revision as of 18:14, 19 January 2011
These tasks and suggestions have been referred to the Training Committee.
Suggestion #13: precise communications - track description
|
Suggestion #33: tracking - preserve intersection and funnel points
|
Suggestion #39: decision making around patient transport
|
|
|
Suggestion #16: too much radio traffic - finish conversation / standby
|
Suggestion #21: being able to state urgency level of comm
|
Suggestion #22: "Stand by" does not mean stop activity
|
Suggestion #37: type 1 search on narrow trail: walk 1 behind the other, 1 look forward, 1 left, 1 right
|
Suggestion #35: Keep sharpie in pack to mark tape
|
Suggestion #36: bystanders asking questions
|
Suggestion #3: Merging teams can cause confusion in command/reporting structure. Suggest clear language of merging vs. working together. Suggest switch to single FRS channel for new team.
|
Suggestion #12: Suggest search areas that are difficult can be reexamined by strategically spotting from point of advantage. E.g. thick brush along creek spotted from other side.
|
Suggestion #19: Suggest encourage members in field to discuss overhead decisions after search as learning opportunity
|
Suggestion #20: Suggest everyone get experience of working comms and command post
|
Suggestion #21: Suggest better learning if everyone can see handling of first approach to subject.
|
Facts about Training/Committee/TasksRDF feed
Committee handling | Suggestion/Committee/List/training + |
Description | precise communications - track description +, tracking - preserve intersection and funnel points +, decision making around patient transport +, Discussion of degree of discretion to work outside assigned segment. Suggest need for clarification of when should talk to command post vs. decide on own. +, Suggest when spotting subject, maintain visual contact until part of party approaches. Can lose perspective as approach. +, too much radio traffic - finish conversation / standby +, being able to state urgency level of comm +, "Stand by" does not mean stop activity +, type 1 search on narrow trail: walk 1 behind the other, 1 look forward, 1 left, 1 right +, Keep sharpie in pack to mark tape +, bystanders asking questions +, Merging teams can cause confusion in command/reporting structure. Suggest clear language of merging vs. working together. Suggest switch to single FRS channel for new team. +, Suggest search areas that are difficult can be reexamined by strategically spotting from point of advantage. E.g. thick brush along creek spotted from other side. +, Suggest encourage members in field to discuss overhead decisions after search as learning opportunity +, Suggest everyone get experience of working comms and command post +, and Suggest better learning if everyone can see handling of first approach to subject. + |
Difficulty to implement | not rated +, hard +, and easy + |
Full page name | Training/Committee/Tasks + |
Sequence number | 13 +, 33 +, 39 +, 14 +, 16 +, 21 +, 22 +, 37 +, 35 +, 36 +, 3 +, 12 +, 19 +, and 20 + |
Suggestion list | Training/Committee + |
Value to PCSAR mandate | high +, medium +, low +, and not rated + |