Preplan/Committee/To prioritize
From PCSAR
(Difference between revisions)
(New page: {{quote-page|Critiques/2009-05-05/Sug3}}) |
|||
Line 1: | Line 1: | ||
{{quote-page|Critiques/2009-05-05/Sug3}} | {{quote-page|Critiques/2009-05-05/Sug3}} | ||
+ | {{quote-page|Critiques/2009-05-05/Sug4}} | ||
+ | {{quote-page|Critiques/2009-05-05/Sug6}} |
Revision as of 00:28, 19 May 2010
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 #4: Suggest get gel pens which won't freeze.
|
|
Facts about Preplan/Committee/To prioritizeRDF feed
Committee handling | Suggestion/Committee/List/training +, and Suggestion/Committee/List/unassigned + |
Description | 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 get gel pens which won't freeze. +, and Debriefing forms don't match urban context. Suggest rework wording. + |
Difficulty to implement | hard +, not rated +, and easy + |
Full page name | Preplan/Committee/To prioritize + |
Sequence number | 3 +, 4 +, and 6 + |
Suggestion list | Preplan/Committee + |
Value to PCSAR mandate | low +, none +, and medium + |