2012-10-02 Mock/Critque

From PCSAR

Revision as of 23:48, 3 October 2012 (edit) Brett Wuth (Talk | contribs) (New page: {{subst:critique report}}) ← Previous diff		Revision as of 23:49, 3 October 2012 (edit) (undo) Brett Wuth (Talk | contribs) Next diff →
Line 1:		Line 1:
-
	{{Critique report/Header}}		{{Critique report/Header}}
-	Suggestions coming from the (date) critique	+	Suggestions coming from the 2012-10-02 critique
-	regarding the (date) incident.	+	regarding the mock of the same date.
	Pincher Creek SAR routinely performs a critique after a Search and		Pincher Creek SAR routinely performs a critique after a Search and
Line 16:		Line 15:
	== Rough notes ==		== Rough notes ==
-		+	* {{link|Image:Members:2012-10-03 18 48 59u-scan.pdf}}
	== Committee / Organization ==		== Committee / Organization ==
	The suggestions are being passed on to the indicated		The suggestions are being passed on to the indicated

---

Revision as of 23:49, 3 October 2012

Suggestions coming from the 2012-10-02 critique regarding the mock of the same date.

Pincher Creek SAR routinely performs a critique after a Search and Rescue incident in order to learn what should be done differently or the same in the next similar incident. Critiques are not about criticism but rather about learning. They are normally chaired by a Search Manager that was not involved in the incident. The suggestions that are brought forward through the critique process are presented in this report.

Contents 1 Participants 2 Rough notes 3 Committee / Organization 3.1 PCSAR Board 3.2 PCSAR Preplan Committee 3.3 PCSAR Equipment Committee 3.4 PCSAR Call-Out Committee 3.5 PCSAR Membership Committee 3.6 PCSAR Training Committee 3.7 Tasking Agency 3.8 Fellow Responding Organizations 4 Suggestions by functional area 4.1 mandate 4.2 first notification / tasking 4.3 call-out 4.4 investigation 4.5 communications 4.6 resources 4.7 (de)briefing 4.8 searching 4.9 extrication 4.10 access/return from segment 4.11 stand down 4.12 CISM 4.13 prevention, public education 4.14 travel 4.15 planning 4.16 logistics 4.17 operations 4.18 media 4.19 family 4.20 post ops 4.21 learning 4.22 misc

Participants

Rough notes

• 2012-10-02 mock critique notes

Committee / Organization

The suggestions are being passed on to the indicated organizations/committees for their consideration. We recognize that not all suggestions may be appropriate, and some may already have been implemented.

PCSAR Board

Mandate Relevant to Incidents:

• Overall ability of PCSAR to accomplish its mission.
• Organizational policies
• Relationships with Tasking Agencies and Fellow Responding Organizations.
• Financing, budget

suggestions identified:

PCSAR Preplan Committee

Mandate Relevant to Incidents:

• Expertise in search and rescue.
• Standard Operating Procedures for incidents.
• Post incident critique, review and follow-up.

suggestions identified:

PCSAR Equipment Committee

Mandate Relevant to Incidents:

• Obtaining and keeping equipment ready.

suggestions identified:

PCSAR Call-Out Committee

Mandate Relevant to Incidents:

• Respond to First Call from Tasking Agency
• Contacting members during an incident.

suggestions identified:

PCSAR Membership Committee

Mandate Relevant to Incidents:

• Recruiting members.
• Tracking members contact information, skills and equipment.

suggestions identified:

PCSAR Training Committee

Mandate Relevant to Incidents:

• Training members.

suggestions identified:

Tasking Agency

Mandate Relevant to Incidents:

• Overall legal responsibility for incident.

suggestions identified:

Fellow Responding Organizations

Mandate Relevant to Incidents:

• Response to incident in accordance with their individual mandate and ability.

suggestions identified:

Suggestions by functional area

mandate

first notification / tasking

call-out

investigation

communications

resources

(de)briefing

searching

extrication

access/return from segment

stand down

CISM

prevention, public education

travel

planning

logistics

operations

media

family

post ops

learning

misc