User:Brett Wuth/Working Notes/2012-12-01 leadership training - Revision history

Brett Wuth at 22:18, 2 December 2012

2012-12-02T22:18:11Z

←Older revision		Revision as of 22:18, 2 December 2012
Line 47:		Line 47:

	Present Objectives		Present Objectives
		+
	{{lesson slide\|00:03\|}}		{{lesson slide\|00:03\|}}
-	~~instructional points~~ in ~~normal font~~	+	'''present outline of ICS org structure'''
		+	* Inicident Commander
		+	* Operations Section Chief
		+	* Planning Section Chief
		+	* Logistics Section Chief
		+	* Finance/Admin Section Chief
		+	* Ground Search Team Unit (Leader, Members)
		+	* Call Out Team
		+	* Agency Executive
		+
		+	{{lesson slide\|\|}}
		+	When position is not filled, the next position up does the job.
		+
		+	* May not be enough work for a dedicated person
		+	* May not be enough people yet
		+
		+	* Expand and collapse as needed
		+
		+
		+	{{lesson slide\|\|}}
		+	Scenario
		+
		+	Sunday morning May 19, 2013, Victoria Day weekend, Beautiful weekend.
		+
		+	PCSAR gets a call from RCMP upon a report of a 5-year girl missing
		+	from a random campsite on the Carbondale river.
		+
		+	PCSAR is tasked. A search manager is in charge. Call-out has been
		+	activated for ground searchers, quads, and road vehicles.
		+
		+
		+	{{lesson slide\|\|}}
		+	Who do you report to?
		+	* when requested
		+	* when signed in
		+	* when assigned field task
		+	* when debriefed
		+	* when available for reassignment
		+	* when released, returning home
		+
		+	{{lesson slide\|\|}}
		+	Principles
		+	* everybody reports to somebody
		+	* everybody report to only one person -- Unity of Command
		+	* everyone on the incident reports up the chain eventually to the same person - Chain of Command
		+
		+	Why?
		+	* Efficiency in an emergency

-	~~''aids, exercises, activities in italic''~~
	{{lesson slides end}}		{{lesson slides end}}

Line 98:		Line 145:
	** Have you tried using radio / phone to contact more senior personnel?		** Have you tried using radio / phone to contact more senior personnel?
	** Ultimately need to organize yourselves		** Ultimately need to organize yourselves
-
-
-	* start with ICS chart
-	* reporting structure, who do you report to?
-	** when requested
-	** when signed in
-	** when assigned field task
-	** when debriefed
-	** when available for reassignment
-	** when released, returning home
-
-	* at all times, each person reports to only one person - unity of command
-
-
-	* use scenarios to walk through the above points
-	** start with simple scenario, use ICS chart
-	*** tasking agency contacts search manager
-	*** search manager contacts call-out
-	*** call-out contacts searchers
-	*** IC, resources arrive on scene
-	*** teams briefed, assigned, head to segment
-	*** return to base, debriefed
-	*** return home

Brett Wuth: /* Notes */

2012-12-02T06:00:43Z

Notes

←Older revision		Revision as of 06:00, 2 December 2012
Line 113:		Line 113:

	* use scenarios to walk through the above points		* use scenarios to walk through the above points
		+	** start with simple scenario, use ICS chart
		+	*** tasking agency contacts search manager
		+	*** search manager contacts call-out
		+	*** call-out contacts searchers
		+	*** IC, resources arrive on scene
		+	*** teams briefed, assigned, head to segment
		+	*** return to base, debriefed
		+	*** return home

Brett Wuth: /* Notes */

2012-12-02T05:55:04Z

Notes

←Older revision		Revision as of 05:55, 2 December 2012
Line 98:		Line 98:
	** Have you tried using radio / phone to contact more senior personnel?		** Have you tried using radio / phone to contact more senior personnel?
	** Ultimately need to organize yourselves		** Ultimately need to organize yourselves
		+
		+
		+	* start with ICS chart
		+	* reporting structure, who do you report to?
		+	** when requested
		+	** when signed in
		+	** when assigned field task
		+	** when debriefed
		+	** when available for reassignment
		+	** when released, returning home
		+
		+	* at all times, each person reports to only one person - unity of command
		+
		+
		+	* use scenarios to walk through the above points

Brett Wuth: /* Reference Material */

2012-12-02T05:24:45Z

Reference Material

←Older revision		Revision as of 05:24, 2 December 2012
Line 78:		Line 78:
	== Reference Material ==		== Reference Material ==
	{{prompt\|If you need to cite sources, do so here.}}		{{prompt\|If you need to cite sources, do so here.}}
-		+	Related lesson plans:
-	[1]	+	* [[2000-12-05 being in charge/Lesson plan]]
		+	* [[2009-03-03 mtg/Overhead tabletop]]

	== Notes ==		== Notes ==

Brett Wuth: /* Notes */

2012-12-02T04:59:29Z

Notes

←Older revision		Revision as of 04:59, 2 December 2012
Line 93:		Line 93:
	** No one knows who you report to.		** No one knows who you report to.
	*** "Who do you report to?" Follow the chain up until you find someone that can tell you who you should report to.		*** "Who do you report to?" Follow the chain up until you find someone that can tell you who you should report to.
		+	* If all you find are people that don't know who they themselves report to ...
		+	** No chain of command
		+	** Have you tried using radio / phone to contact more senior personnel?
		+	** Ultimately need to organize yourselves

Brett Wuth: /* Notes */

2012-12-02T04:56:54Z

Notes

←Older revision		Revision as of 04:56, 2 December 2012
Line 83:		Line 83:
	== Notes ==		== Notes ==
	{{prompt\|Any additional notes, etc.}}		{{prompt\|Any additional notes, etc.}}
		+
		+	* Should always know "Who am I reporting to?"
		+	** If don't know, ask.
		+	** Report to only one person -- Unity of Command
		+	*** not two different people or two different organizations, two different branches
		+	*** not to both your team leader and your team leader's leader
		+	**** give examples using ICS chart
		+	*** "Am I reporting to you and no longer to ... ?" "I need to get a message to ... that I'm not longer reporting to that person."
		+	** No one knows who you report to.
		+	*** "Who do you report to?" Follow the chain up until you find someone that can tell you who you should report to.

Brett Wuth: /* Scope */

2012-12-02T04:45:24Z

Scope

←Older revision		Revision as of 04:45, 2 December 2012
Line 11:		Line 11:
	* working with other SAR groups		* working with other SAR groups
	* working with other agencies		* working with other agencies
		+	* merging field teams

	== Addresses ==		== Addresses ==

Brett Wuth at 04:44, 2 December 2012

2012-12-02T04:44:34Z

←Older revision		Revision as of 04:44, 2 December 2012
Line 1:		Line 1:
-	== ~~Objectives~~ ==	+	{{Lesson plan/Header}}
-	* Students will demonstrate the ability to	+
-	** call for clarity of leadership	+	== Subject ==
-	** assume leadership	+	{{prompt\|What is this lesson plan about?}}
-	** resolve issues of leadership between themselves and others	+
-	** hand-off leadership	+	== Authors ==
-	== ~~Application~~ ==	+	{{prompt\|List who wrote this lesson plan.}}
		+	* Brett Wuth
		+	== Scope ==
		+	{{prompt\|What is included in this lesson, what's not and why.}}
	* working with other SAR groups		* working with other SAR groups
	* working with other agencies		* working with other agencies
		+
	== Addresses ==		== Addresses ==
	* [[Critiques/2010-08-24/Sug21]]		* [[Critiques/2010-08-24/Sug21]]
Line 20:		Line 24:
	** overhead team can make effort to always have team leader designated		** overhead team can make effort to always have team leader designated
	** can practice developing leadership		** can practice developing leadership
-
-	~~{{Lesson plan/Header}}~~
-
-	~~== Subject ==~~
-	~~{{prompt\|What is this lesson plan about?}}~~
-
-	~~== Authors ==~~
-	~~{{prompt\|List who wrote this lesson plan.}}~~
-
-	~~== Scope ==~~
-	~~{{prompt\|What is included in this lesson, what's not and why.}}~~

	== Prerequisites ==		== Prerequisites ==
Line 37:		Line 30:
	== Objectives ==		== Objectives ==
	At the conclusion of this lesson the participants:		At the conclusion of this lesson the participants:
-	# will ~~be able~~ to ~~...~~	+	* will demonstrate the ability to
		+	** call for clarity of leadership
		+	** assume leadership
		+	** resolve issues of leadership between themselves and others
		+	** hand-off leadership

	== Time Plan ==		== Time Plan ==
Line 71:		Line 68:
	Recommended license below. Fill in the year and the author's name(s):		Recommended license below. Fill in the year and the author's name(s):

-	Copyright © ~~YEAR~~, ~~Author~~.	+	Copyright © 2012, Brett Wuth.
	This work is licensed under a		This work is licensed under a
	Creative Commons Attribution-NonCommercial 2.5 Canada License.		Creative Commons Attribution-NonCommercial 2.5 Canada License.

Brett Wuth at 04:42, 2 December 2012

2012-12-02T04:42:08Z

←Older revision		Revision as of 04:42, 2 December 2012
Line 20:		Line 20:
	** overhead team can make effort to always have team leader designated		** overhead team can make effort to always have team leader designated
	** can practice developing leadership		** can practice developing leadership
		+
		+	{{Lesson plan/Header}}
		+
		+	== Subject ==
		+	{{prompt\|What is this lesson plan about?}}
		+
		+	== Authors ==
		+	{{prompt\|List who wrote this lesson plan.}}
		+
		+	== Scope ==
		+	{{prompt\|What is included in this lesson, what's not and why.}}
		+
		+	== Prerequisites ==
		+	{{prompt\|What should students already know/have accomplished before the lesson is presented.}}
		+
		+	== Objectives ==
		+	At the conclusion of this lesson the participants:
		+	# will be able to ...
		+
		+	== Time Plan ==
		+	Total Time: ?? minutes
		+
		+	{{lesson slides start}}
		+	{{lesson slide\|00:00\|3 min}}
		+	Introduce topic title
		+
		+	Introduce Instructor
		+
		+	Present Objectives
		+	{{lesson slide\|00:03\|}}
		+	instructional points in normal font
		+
		+	''aids, exercises, activities in italic''
		+	{{lesson slides end}}
		+
		+	== Aids ==
		+	{{prompt\|What materials are needed or useful in presenting this lesson.}}
		+
		+	== Question bank ==
		+	{{prompt\|List of questions suitable for an review/exam of this section.}}
		+	== Frequently Asked Questions ==
		+	{{prompt\|What are some of the questions that students typically ask. Include the answers.}}
		+
		+	== Feedback ==
		+	{{prompt\|When has this lesson been presented. What was the feedback.}}
		+
		+	== License ==
		+	{{prompt\|What can others do with this lesson?}}
		+
		+	Recommended license below. Fill in the year and the author's name(s):
		+
		+	Copyright © YEAR, Author.
		+	This work is licensed under a
		+	Creative Commons Attribution-NonCommercial 2.5 Canada License.
		+	To view a copy of this license, visit
		+	http://creativecommons.org/licenses/by-nc/2.5/ca/
		+	or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA.
		+
		+	== Reference Material ==
		+	{{prompt\|If you need to cite sources, do so here.}}
		+
		+	[1]
		+
		+	== Notes ==
		+	{{prompt\|Any additional notes, etc.}}

Brett Wuth: /* Addresses */

2012-12-02T04:22:07Z

Addresses

←Older revision		Revision as of 04:22, 2 December 2012
Line 14:		Line 14:
	* [[Critiques/2010-08-24/Sug10]]		* [[Critiques/2010-08-24/Sug10]]
	** clarify roles and command structure/hierarchy when several agencies are involved in/responding to the same incident.		** clarify roles and command structure/hierarchy when several agencies are involved in/responding to the same incident.
		+	* [[Critiques/2009-05-05/Sug3]]
		+	** 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.
		+	** need clear language of team designations, designation of combined team
		+	** need clear designation of combined team leader
		+	** overhead team can make effort to always have team leader designated
		+	** can practice developing leadership