Safety/Security Timeline - Revision history

Taylorvalnes@digitalgrail.org at 16:42, 13 October 2022

2022-10-13T16:42:54Z

← Older revision		Revision as of 11:42, 13 October 2022
Line 3:		Line 3:
	{{Timelines}}		{{Timelines}}

			{{Immediately after accepting the position}}
	==Immediately after accepting the position==
	* Get access to your convention email.
	* Read through the emails to get an idea of what sort of messages you should expect for the next year.
	* Validate the information on the convention website and notify webmaster@<convention email> of any changes or additions you would like.

	==8 months before convention==		==8 months before convention==
Line 29:		Line 25:
	==2 months before convention==		==2 months before convention==
	* Work on schedule for your security team.		* Work on schedule for your security team.
	* Validate [[Safety/Security SOP~~]], and ensure any updates are complete before the end of the first week.~~		{{Timeline SOP\|Accessibility SOP}}
	* Write a paragraph about SOP, location, hours, and purpose. Send it to programguide@<convention email> and scheduling@<email> by the 15th of this month.		* Write a paragraph about SOP, location, hours, and purpose. Send it to programguide@<convention email> and scheduling@<email> by the 15th of this month.

Taylorvalnes@digitalgrail.org at 15:58, 13 October 2022

2022-10-13T15:58:20Z

← Older revision		Revision as of 10:58, 13 October 2022
Line 1:		Line 1:
	[[Category:Safety/Security]]		[[Category:Safety/Security]]
	[[Category:Timelines]]		[[Category:Timelines]]
	~~''***NOTE: These timelines are estimates, you may need to adjust for your specific convention date''~~		{{Timelines}}

Taylorvalnes@digitalgrail.org: /* 2 months before convention */

2022-10-13T14:32:16Z

2 months before convention

← Older revision		Revision as of 09:32, 13 October 2022
Line 29:		Line 29:
	==2 months before convention==		==2 months before convention==
	* Work on schedule for your security team.		* Work on schedule for your security team.
			* Validate [[Safety/Security SOP]], and ensure any updates are complete before the end of the first week.
	* Write a paragraph about SOP, location, hours, and purpose. Send it to programguide@<convention email> and scheduling@<email> by the 15th of this month.		* Write a paragraph about SOP, location, hours, and purpose. Send it to programguide@<convention email> and scheduling@<email> by the 15th of this month.

Taylorvalnes@digitalgrail.org at 12:22, 13 October 2022

2022-10-13T12:22:49Z

@@ Line 1: / Line 1: @@
 [[Category:Safety/Security]]
 [[Category:Timelines]]
 ''***NOTE: These timelines are estimates, you may need to adjust for your specific convention date''
 ==Immediately after accepting the position==
-# Get access to your convention email.
+* Get access to your convention email.
-# Read through the emails to get an idea of what sort of messages you should expect for the next year.
+* Read through the emails to get an idea of what sort of messages you should expect for the next year.
-# Validate the information on the convention website and notify webmaster@<convention email> of any changes or additions you would like.
+* Validate the information on the convention website and notify webmaster@<convention email> of any changes or additions you would like.
 ==8 months before convention==
-Contact the BDU keeper to determine if all BDU’s are clean and stored properly so they are ready for next year
+* Contact the BDU keeper to determine if all BDU’s are clean and stored properly so they are ready for next year
-Find patches for the bdus. Post poll to convention facebook or discord page/get feedback.
+* Find patches for the bdus. Post poll to convention facebook or discord page/get feedback.
-Verify that security blurb and policies for the program guide are correct & up to date.
+* Verify that security blurb and policies for the program guide are correct & up to date.
-Responsibilities at convention
+==7 months before convention==
-Setup Day (typically the day before convention):
+* Work with Logistics to come up with a list of anything needed for the convention.
-Morning Meeting at hotel with contact person from the hotel, some convention heads, Hotel Liason, hotel security, hotel staff that will be on duty all weekend
+* Submit a budget request to Treasurer
-Obtain hotel staff contact phone numbers at meeting
+* Can order once the request is approved.
-Make sure everyone who participates in Staff is being respectful and following all rules. Work with Operations to keep records of all incidents.
+* Order patches if needed

Taylorvalnes@digitalgrail.org at 12:12, 13 October 2022

2022-10-13T12:12:16Z

← Older revision		Revision as of 07:12, 13 October 2022
Line 2:		Line 2:
	[[Category:Timelines]]		[[Category:Timelines]]
	{{PublicDeptNeedsUpdating}}		{{PublicDeptNeedsUpdating}}
			''***NOTE: These timelines are estimates, you may need to adjust for your specific convention date''


			==Immediately after accepting the position==
			# Get access to your convention email.
			# Read through the emails to get an idea of what sort of messages you should expect for the next year.
			# Validate the information on the convention website and notify webmaster@<convention email> of any changes or additions you would like.

			==8 months before convention==
			Contact the BDU keeper to determine if all BDU’s are clean and stored properly so they are ready for next year
			Find patches for the bdus. Post poll to convention facebook or discord page/get feedback.
			Verify that security blurb and policies for the program guide are correct & up to date.
			7 months before convention
			Work with Logistics to come up with a list of anything needed for the convention.
			Submit a budget request to Treasurer
			Can order once the request is approved.
			Order patches if needed
			Should be included in the budget request.
			6 months before convention
			Work on assembling your security team and answer emails.
			5-3 months before convention
			Continue assembling your security team and answering emails.
			2 months before convention
			Work on schedule for your security team.
			Write a paragraph about SOP, location, hours, and purpose. Send it to programguide@<convention email> and scheduling@<email> by the 15th of this month.
			1 month before convention
			Finalize your security team. Make them familiar with convention rules and each has a badge.
			If the convention requires the badges to be purchased, ensure they have done so.
			If the convention is supplying badges for free, ensure they’re all on the list of staff badges.
			Get a list of events, party rooms, panels, etc that need extra security.
			Send anything you need announced during opening and closing ceremonies including slides to the ceremonies position by the end of this month.
			Month of convention
			Set up a meet and greet with security team and convention heads. Walk around hotel to discuss trouble areas.

			Responsibilities at convention
			Setup Day (typically the day before convention):
			Morning Meeting at hotel with contact person from the hotel, some convention heads, Hotel Liason, hotel security, hotel staff that will be on duty all weekend
			Obtain hotel staff contact phone numbers at meeting
			Make sure everyone who participates in Staff is being respectful and following all rules. Work with Operations to keep records of all incidents.

Taylorvalnes@digitalgrail.org: Created page with "Category:Safety/Security Category:Timelines {{PublicDeptNeedsUpdating}}"

2022-10-12T20:07:59Z

Created page with "Category:Safety/Security Category:Timelines {{PublicDeptNeedsUpdating}}"

New page

[[Category:Safety/Security]]
[[Category:Timelines]]
{{PublicDeptNeedsUpdating}}