Guests Procedures - Revision history

Amberaudio: added example emails to guests

2023-09-06T07:53:46Z

added example emails to guests

← Older revision		Revision as of 00:53, 6 September 2023
Line 47:		Line 47:
	As part of the final scheduling process, all guests should be sent their schedule so that they know what they are expecting for the weekend and if they have any changes.		As part of the final scheduling process, all guests should be sent their schedule so that they know what they are expecting for the weekend and if they have any changes.

			== Example Emails for Reaching Out to Potential Guests ==
			The following emails should only be sent if the guest has been approved:

			=== Reaching out to a guest we've had in the past ===
			Hello {name}!

			SNAFU Con has returned and would love to have you return with us!

			This year our dates are {dates}.

			Since you have been a guest of ours in the past, we are more than happy to send you a contract with the same terms as before. It is attached to this message, feel free to look it over and we can discuss any potential changes. Once it is signed we will announce your appearance and begin planning your panel times. Please feel free to reply to this email if you have any questions.

			Looking forward to seeing you!

			{signature}

			=== Replying to a guest who reached out to us first ===
			Hi {name}!

			Thank you so much for your interest in being a guest at SNAFU Con!

			This year the convention is {dates}.

			The Convention Chair is considering you as a guest and we would be happy to discuss your terms and requirements. Please send us your requirements for consideration.

			Thanks!

			{signature}

			=== Cold contacting a guest we are interested in who has not previously reached out to us ===
			Hello {name},

			My name is {name} and I am reaching out on behalf of the Sierra Nevada Anime Fans Unite! Convention (SNAFU Con). This is an anime and gaming convention that happens annually in Reno, NV.

			This year our convention dates are {dates} at {location}.

			We would love to talk with you about attending the convention as a guest this year. If you would be interested, please let us know what your requirements are to be a convention guest so that we can explore further.

			Looking forward to working with you!

			{signature}

	==When guests@snafucon.com Receives An Email==		==When guests@snafucon.com Receives An Email==

Beta: add cat

2023-08-21T23:28:14Z

add cat

← Older revision		Revision as of 16:28, 21 August 2023
Line 1:		Line 1:
			[[Category:Guest_Department]]
	==General Guest Policies==		==General Guest Policies==
	* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.		* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.

Beta: add a very general procedure

2018-09-06T16:02:21Z

add a very general procedure

← Older revision		Revision as of 09:02, 6 September 2018
Line 2:		Line 2:
	* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.		* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.
	** Those authorized to do so: Beta. Llama. Thomas.		** Those authorized to do so: Beta. Llama. Thomas.
	* All humans who send an email to the guests queue should receive a timely reply (as opposed to mailing lists, bots and mass emails).		* All humans who send an email to the guests queue should receive a timely reply (as opposed to mailing lists, bots and mass emails which can be ignored).
	* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote		* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote (May be changing to just a row in the decision spreadsheet)
	* All guest notes must be approved or denied in a timely manner		* All guest notes must be approved or denied in a timely manner
	* All denied guests must receive a ''polite'' denial email		* All denied guests must receive a ''polite'' denial email
	* All approved guests must be sent to contracts department for processing		* All guests must be contracted before they can be announced / Guests cannot be announced until the convention has received a signed contract from the guest.
	* All guests must be contracted before they can be announced / Guests ~~can not~~ be announced until the convention has received a signed contract from the guest.
	* All guests will be announced in a timely manner after they are contracted		* All guests will be announced in a timely manner after they are contracted
	* For all staff members who need guest information, the Guest File Evernote folder must be shared.		* For all staff members who need guest information, the Guest File Evernote folder must be shared.
	* No staff member is to make publicly available ~~the~~ information in ~~the note excepting~~ the Guest Bio and Head Shot.		* No staff member is to make publicly available any information we have received from guests (in Evernote, spreadsheet, database, etc.) except for the Guest Bio and Head Shot.
	* Any staff member who needs guest information that is not in the Evernote file must be authorized before contacting the guest directly. If staff member is not authorized to contact the guest then staff member must request the information from the relevant department head who is authorized who will contact the guest on their behalf.		* Any staff member who needs guest information that is not in the Evernote file must be authorized before contacting the guest directly. If staff member is not authorized to contact the guest then staff member must request the information from the relevant department head who is authorized who will contact the guest on their behalf.
	* Staff members will put forth their best effort to keep the current year Evernote file as updated as possible.		* Staff members will put forth their best effort to keep the current year Evernote file (or replacement) as updated as possible.
	* All Staff members will follow up with guest or other relevant staff members in a timely manner.		* All Staff members will follow up with guest or other relevant staff members in a timely manner.
	* If a flight is provided, it will always be the cheapest possible option that will still work within the guest's limitations (such as work, time, or distance)		* If a flight is provided, it will always be the cheapest possible option that will still work within the guest's limitations (such as work, time, or distance)
	* All staff are to treat the guests as they are to treat everyone - professionally and with utmost respect.		* All staff are to treat the guests as they are to treat everyone - professionally and with utmost respect.
	* Merchant documents ~~must~~ be handled through the contracting department.		* Merchant documents should be handled through the contracting department.
	* No staff member is to ever publicly speak poorly about a guest. However, if there is an incident with, or a ~~complain~~ about a guest, it must be reported to the convention chairs.		* No staff member is to ever publicly speak poorly about a guest. However, if there is an incident with, or a complaint about a guest, it must be reported to the convention chairs ASAP.

			== General Procedure ==
			Methods of contact:
			* Guests email us
			* Representatives/managers email us
			* We email guests or representatives/managers.

			We generally do everything by email. When we have a prospective guest, we will create a record for them in a spreadsheet designed to help make the decision as to whether we can bring them in. We will also create an Evernote record if they are likely to be approved now or in the future. Decisions are based on how popular a guest seems, how much we want to work with them, and how expensive (or inexpensive) they are.

			Spreadsheet is located in Bitrix24\Guests\Guests Decision Worksheet.xls

			When a guest is approved, we have a contract template located in Bitrix24\Guests\Guests Contracts\2018 Guest Contract Template.dotx
			The contract template MUST BE OPENED WITH MICROSOFT WORD. Libra office and Open Office will not work as how we want. The template has drop-down select boxes for the most common things we do for guests so that the language is already set and we don't need to bother the contracts department unless we need to do something special. Most guests can have a standard contract built from the template.

			New contracts are saved in the Bitrix24\Guests\Guests Contracts\GUEST-NAME\ folder.

			Once the contract looks how we want and is approved, it's made into a PDF form and sent to the guest. As part of this process we also ask for an updated headshot and bio.

			After we've received a signed contract:
			* the signed pdf is added to the bitrix24 folder and Evernote
			* the guest is posted on the website and posted on social media (if we have headshot and bio)
			* we put them in the registration system
			* we add their panels to the panel system and get them scheduled
			* any flights are purchased if needed

			A list of guests who need hotel rooms are given to the venue.

			As part of the final scheduling process, all guests should be sent their schedule so that they know what they are expecting for the weekend and if they have any changes.



	==When guests@snafucon.com Receives An Email==		==When guests@snafucon.com Receives An Email==

Beta: Remove Nathan from procedures

2018-08-26T04:18:51Z

Remove Nathan from procedures

Beta: /* Email Example */ add single line breaks

2017-03-22T19:34:47Z

Email Example: add single line breaks

← Older revision		Revision as of 12:34, 22 March 2017
Line 63:		Line 63:

	(Your name)		(Your name)
	SNAFU Con Guests Department		SNAFU Con Guests Department<br />
	http://snafucon.com		http://snafucon.com<br />
	guests@snafucon.com		guests@snafucon.com

Treyntowin: fixed spelling and vocabulary

2016-06-13T00:28:41Z

fixed spelling and vocabulary

← Older revision		Revision as of 17:28, 12 June 2016
Line 20:		Line 20:

	==When guests@snafucon.com Receives An Email==		==When guests@snafucon.com Receives An Email==
	This task can be handled by any ~~trustable~~ lackey who can write somewhat business-like (no typos). So - higher level general staff, or upper staff, cleared through Beta, Llama, or Sammich (as the best 3 business writers on staff).		This task can be handled by any trustworthy lackey who can write somewhat business-like (no typos). So - higher level general staff, or upper staff, cleared through Beta, Llama, or Sammich (as the best 3 business writers on staff).

	#Once an email comes in, review the Evernote SNAFU Con Guest File for the guest.		#Once an email comes in, review the Evernote SNAFU Con Guest File for the guest.
Line 28:		Line 28:
	## Add new tag "SNAFU Con (year)"		## Add new tag "SNAFU Con (year)"
	## Update the note with new contact info and/or any new info from the email		## Update the note with new contact info and/or any new info from the email
	## If head shot, bio, panels, or requirements are not updated new, make sure to ~~not~~ that in the file in each of those headers (Example: "Requirements (2014 Information):"		## If head shot, bio, panels, or requirements are not updated new, make sure to note that in the file in each of those headers (Example: "Requirements (2014 Information):"
	## Delete the contracts from the file and remove any emails from the previous year unless they seem to be particularly relevant.		## Delete the contracts from the file and remove any emails from the previous year unless they seem to be particularly relevant.
	## Add new contact email to "Relevant Emails" section		## Add new contact email to "Relevant Emails" section

Treyntowin: Clarified grammar.

2016-06-13T00:23:23Z

Clarified grammar.

← Older revision		Revision as of 17:23, 12 June 2016
Line 2:		Line 2:
	* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.		* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.
	** Those authorized to do so: Nathan. Beta. Llama.		** Those authorized to do so: Nathan. Beta. Llama.
	* All humans who email to the guests queue will receive a timely reply (~~obvious mass messages or~~ mailing lists ~~may be ignored~~).		* All humans who send an email to the guests queue will receive a timely reply (as opposed to mailing lists, bots and mass emails).
	* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote		* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote
	* All guest notes must be approved or denied in a timely manner		* All guest notes must be approved or denied in a timely manner

Beta: update procedures to match what we learned in 2015

2016-06-12T10:35:49Z

update procedures to match what we learned in 2015

← Older revision		Revision as of 03:35, 12 June 2016
Line 40:		Line 40:
	#*Head shot		#*Head shot
	#*Contact Info		#*Contact Info
	~~##Add "1week@fut.io" as a One-Time BCC on your reply if you need the guest to reply to you ,*Note: May not need to use FUT - review RT reminders then update procedures~~
	##Wait for guest reply		##Wait for guest reply
	#If guest does reply		#If guest does reply
	##Update the guest note with the information given		##Update the guest note with the information given
	#If guest does not reply within 1 week~~, FUT will email you a reminder about the email. Move~~ on to the next step. Do not email guest again unless directed to do so.		#If guest does not reply within 1 week move on to the next step. Do not email guest again unless directed to do so.
	#~~Send chair~~@ ~~an email with~~ the ~~guest name to~~ notify that the guest note exists in Evernote and needs review		#Ping @nathan and @kylie in the Guests hipchat room notify Nathan that the guest note exists in Evernote and needs review
	#Change RT ticket status to Stalled. (This will not remove it from the Guest Queue)		#Change RT ticket status to Stalled. (This will not remove it from the Guest Queue)
	#* NOTE: FUT will still send you a reminder email - you can ignore it. It may reopen your ticket, so you will want to reset the ticket to stalled. However, if you know how to use FUT, you can cancel the reminder before it comes in.
	#Follow up with Nathan every so often until you receive approval/denial of guest.		#Follow up with Nathan every so often until you receive approval/denial of guest.
	#If guest is approved, ~~close~~ your ticket - you are done.		#If guest is approved
	#If guest is denied~~, reply~~ to guest using a customized standard ("Canned") response in RT ~~and close~~ the ticket. You are done.		##Reply to the guest and let them know they were approved and that they will be contacted by our Contracts department
			##Make sure @llama is contacting the guest to get the guest contracted (Maybe CC the approval email to Llama or contracts@, but you still want to ping him in [[HipChat]])
			##Close your ticket - you are done.
			#If guest is denied
			##Reply to guest using a customized standard ("Canned") response in RT
			##Close the ticket. You are done.

	===Email Example===		===Email Example===
Line 91:		Line 94:
	#Create contract using previous years as templates		#Create contract using previous years as templates
	#Attach the doc file to the Evernote Note (Dropbox no longer required for this step)		#Attach the doc file to the Evernote Note (Dropbox no longer required for this step)
			#Get Nathan and Beta to approve contract (if a reasonable period of time has passed without approval, consider it approved and push forward)
	#Create a signable PDF of the contract (Can save to dropbox - no need to save into Evernote)		#Create a signable PDF of the contract (Can save to dropbox - no need to save into Evernote)
	#Reach out to guest via email with their signable PDF contract attached		#Reach out to guest via email with their signable PDF contract attached
	~~#CC: 1week@fut.io - NOTE: FUT will email the guest on your behalf if they do not reply-all back to you. You may choose to use BCC or edit the FUT pending alerts.~~
	#Keep following up with guests until you have a signed contract		#Keep following up with guests until you have a signed contract
	#~~attach~~ signed contract to Evernote file		#Attach signed contract to Evernote file (Note: We may also have a location to upload it to [[BACON]] at some point but that is not a thing yet.)
	#~~email~~: registration@, sm@, programming@, chair@ with the names of the contracted guests and a reminder that the information for them is in the Evernote file		#Email: registration@, sm@, programming@, chair@ with the names of the contracted guests and a reminder that the information for them is in the Evernote file (Alternatively, you may ping the relevant heads in hipchat.)
	#If guest has a table, make sure they also fill out a merchant contract. Do not wait for this contract to alert everyone about the guest.		#If guest has a table, make sure they also fill out a merchant contract. Do not wait for this contract to alert everyone about the guest.
	#*Note: As of 2014, YOU are responsible for guest merchants checkin/checkout at-con		#*Note: As of 2014, YOU are responsible for guest merchants checkin/checkout at-con
Line 110:		Line 113:
	#If individual has a BACON account, but was not a guest before:		#If individual has a BACON account, but was not a guest before:
	##Click "Make a current user into a guest."		##Click "Make a current user into a guest."
	##Yell at the administrators when you realize that it's a broken link		##Yell at the administrators when you realize that it's a broken link (is this still accurate?)
	#If the individual is new to us:		#If the individual is new to us:
	##Click "Create a new guest"		##Click "Create a new guest"
Line 130:		Line 133:
	##If the guest already has a profile, set them to active and update it		##If the guest already has a profile, set them to active and update it
	##New guests can be added at the bottom		##New guests can be added at the bottom
	##Pay attention to the Order numbers. Update all guests so that the newest guest is on top and the oldest contracted guest is on the bottom. Alternatively, you can order them alphabetically.		##'''Pay attention to the Order numbers.''' Update all guests so that the newest guest is on top and the oldest contracted guest is on the bottom. Alternatively, you can order them alphabetically but we traditionally post by contract date order.
	##Once you have updated all guest bios as necessary, click "Submit" at the bottom (or click in a small field and hit "Enter" on your keyboard)		##Once you have updated all guest bios as necessary, click "Submit" at the bottom (or click in a small field and hit "Enter" on your keyboard)
	##Click "Return to website management index." to go back to the index.		##Click "Return to website management index." to go back to the index.
Line 145:		Line 148:
	#Get the list of panels from the Evernote file.		#Get the list of panels from the Evernote file.
	#If there isn't a list of panels:		#If there isn't a list of panels:
	##Contact the guest via email and request their panels. ~~CC (or BCC): 1week@fut.io~~		##Contact the guest via email and request their panels.
	##Continue to follow up with guest until panels are received		##Continue to follow up with guest until panels are received
	#Enter desired panels in BACON		#Enter desired panels in BACON
Line 153:		Line 156:
	#Keep guests apprised of any necessary schedule changes		#Keep guests apprised of any necessary schedule changes
	#A few weeks before the convention, email all guests their final schedules again.		#A few weeks before the convention, email all guests their final schedules again.

			NOTE: You should probably provide the guest with your cell number or a way of contacting you at the con for panel-related concerns/needs.

	===Design===		===Design===
Line 175:		Line 180:
	#Issue separate checks for per diem fees		#Issue separate checks for per diem fees
	#Sign the checks		#Sign the checks
	#Put appearance checks in individual envelopes - one envelope per guest		#Put '''appearance checks''' in individual envelopes - one envelope per guest
	#Place these envelopes in a large yellow envelope and label it for Nathan		#Place these envelopes in a large yellow envelope and label it for Nathan
	#*Appearance fees are to be given to the guests by Nathan halfway through the con.		#*Appearance fees are to be given to the guests by Nathan halfway through the con.
	#*If there are any guests with appearance fees over $600, attach the guest's envelope to a [http://www.irs.gov/pub/irs-pdf/fw9.pdf Form W-9].		#*If there are any guests with appearance fees over '''$600''', attach the guest's envelope to a [http://www.irs.gov/pub/irs-pdf/fw9.pdf Form W-9].
	#**Form W-9 must be filled out and returned for guest to receive appearance fees.		#**Form W-9 must be filled out and returned for guest to receive appearance fees.
	#Put the per diem checks in separate envelopes - one envelope per guest		#Put the '''per diem checks''' in separate envelopes - one envelope per guest
	#*This envelope will be attached to the guest con bag and badge as per diem fees are due to the guest at the beginning of the con. In 2014 we put the badges in this envelope but it caused confusion.		#*This envelope will be attached to the guest con bag and badge as per diem fees are due to the guest at the beginning of the con. In 2014 we put the badges in this envelope but it caused confusion.
	#Follow up with registration to ensure that guest con bags are complete		#Follow up with registration to ensure that guest con bags are complete

Beta: add example email

2016-01-11T00:31:26Z

add example email

← Older revision		Revision as of 17:31, 10 January 2016
Line 52:		Line 52:
	#If guest is denied, reply to guest using a customized standard ("Canned") response in RT and close the ticket. You are done.		#If guest is denied, reply to guest using a customized standard ("Canned") response in RT and close the ticket. You are done.

			===Email Example===
			Hello (Name),

			Thank you for your email! The chair is considering you as a guest for this year. Can you please send me your requirements so that I can give them to the chair for consideration.

			Thank you,

			(Your name)
			SNAFU Con Guests Department
			http://snafucon.com
			guests@snafucon.com

	==Guest Choices Which Weren't Emailed==		==Guest Choices Which Weren't Emailed==

Beta: I can't write what I want to write right now.

2015-09-04T18:08:40Z

I can't write what I want to write right now.

← Older revision		Revision as of 11:08, 4 September 2015
Line 1:		Line 1:
	==General Guest Policies==		==General Guest Policies==
			* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.
			** Those authorized to do so: Nathan. Beta. Llama.
	* All humans who email to the guests queue will receive a timely reply (obvious mass messages or mailing lists may be ignored).		* All humans who email to the guests queue will receive a timely reply (obvious mass messages or mailing lists may be ignored).
	* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote		* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote

← Older revision		Revision as of 21:18, 25 August 2018
Line 1:		Line 1:
	==General Guest Policies==		==General Guest Policies==
	* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.		* Absolutely no one is allowed to speak on the con's behalf as to whether a guest will be accepted/denied except those authorized to do so.
	** Those authorized to do so: ~~Nathan.~~ Beta. Llama.		** Those authorized to do so: Beta. Llama. Thomas.
	* All humans who send an email to the guests queue ~~will~~ receive a timely reply (as opposed to mailing lists, bots and mass emails).		* All humans who send an email to the guests queue should receive a timely reply (as opposed to mailing lists, bots and mass emails).
	* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote		* All guests who are suggested or email us requesting guest status will have a guest file note created in Evernote
	* All guest notes must be approved or denied in a timely manner		* All guest notes must be approved or denied in a timely manner
Line 11:		Line 11:
	* For all staff members who need guest information, the Guest File Evernote folder must be shared.		* For all staff members who need guest information, the Guest File Evernote folder must be shared.
	* No staff member is to make publicly available the information in the note excepting the Guest Bio and Head Shot.		* No staff member is to make publicly available the information in the note excepting the Guest Bio and Head Shot.
	* Any staff member who needs guest information that is not in the Evernote file must be authorized before contacting the guest directly. If staff member is not authorized to contact the guest then staff member must request the information from the relevant department head who is authorized~~, or Nathan~~ who will contact the guest on their behalf.		* Any staff member who needs guest information that is not in the Evernote file must be authorized before contacting the guest directly. If staff member is not authorized to contact the guest then staff member must request the information from the relevant department head who is authorized who will contact the guest on their behalf.
	* Staff members will put forth their best effort to keep the current year Evernote file as updated as possible.		* Staff members will put forth their best effort to keep the current year Evernote file as updated as possible.
	* All Staff members will follow up with guest or other relevant staff members in a timely manner.		* All Staff members will follow up with guest or other relevant staff members in a timely manner.
Line 44:		Line 44:
	##Update the guest note with the information given		##Update the guest note with the information given
	#If guest does not reply within 1 week move on to the next step. Do not email guest again unless directed to do so.		#If guest does not reply within 1 week move on to the next step. Do not email guest again unless directed to do so.
	#Ping ~~@nathan and @kylie~~ in the Guests hipchat room notify ~~Nathan~~ that the guest note exists in Evernote and needs review		#Ping people in the Guests hipchat room notify us that the guest note exists in Evernote and needs review
	#Change RT ticket status to Stalled. (This will not remove it from the Guest Queue)		#Change RT ticket status to Stalled. (This will not remove it from the Guest Queue)
	#Follow up ~~with Nathan~~ every so often until you receive approval/denial of guest.		#Follow up every so often until you receive approval/denial of guest.
	#If guest is approved		#If guest is approved
	##Reply to the guest and let them know they were approved and that they will be contacted by our Contracts department		##Reply to the guest and let them know they were approved and that they will be contacted by our Contracts department
Line 79:		Line 79:

	==Guest Approval Process==		==Guest Approval Process==
	The head of guests or the chair decided on the guests~~. We have no head so Nathan makes the decision~~.		The head of guests or the chair decided on the guests.

	~~Nathan's~~ Procedure after decision:		Procedure after decision:
	#Tell person handling email whether guest is approved/denied		#Tell person handling email whether guest is approved/denied
	#If guest is approved, CC approval email to Contracts Department for contracting		#If guest is approved, CC approval email to Contracts Department for contracting
Line 94:		Line 94:
	#Create contract using previous years as templates		#Create contract using previous years as templates
	#Attach the doc file to the Evernote Note (Dropbox no longer required for this step)		#Attach the doc file to the Evernote Note (Dropbox no longer required for this step)
	#Get ~~Nathan and~~ Beta to approve contract (if a reasonable period of time has passed without approval, consider it approved and push forward)		#Get Beta to approve contract (if a reasonable period of time has passed without approval, consider it approved and push forward)
	#Create a signable PDF of the contract (Can save to dropbox - no need to save into Evernote)		#Create a signable PDF of the contract (Can save to dropbox - no need to save into Evernote)
	#Reach out to guest via email with their signable PDF contract attached		#Reach out to guest via email with their signable PDF contract attached
Line 181:		Line 181:
	#Sign the checks		#Sign the checks
	#Put '''appearance checks''' in individual envelopes - one envelope per guest		#Put '''appearance checks''' in individual envelopes - one envelope per guest
	#Place these envelopes in a large yellow envelope and label it ~~for Nathan~~		#Place these envelopes in a large yellow envelope and label it
	#*Appearance fees are to be given to the guests ~~by Nathan~~ halfway through the con.		#*Appearance fees are to be given to the guests halfway through the con.
	#*If there are any guests with appearance fees over '''$600''', attach the guest's envelope to a [http://www.irs.gov/pub/irs-pdf/fw9.pdf Form W-9].		#*If there are any guests with appearance fees over '''$600''', attach the guest's envelope to a [http://www.irs.gov/pub/irs-pdf/fw9.pdf Form W-9].
	#**Form W-9 must be filled out and returned for guest to receive appearance fees.		#**Form W-9 must be filled out and returned for guest to receive appearance fees.
Line 197:		Line 197:

	==At Con==		==At Con==
	===~~Chair / Nathan~~===		===Liaison===
	#Introduce yourself to guests		#Introduce yourself to guests
	#~~Nathan - you~~ should update this procedure with what you do at-con because I only have a vague idea and I don't want to tell you what you do because I know you know it better than I do.		#Someone should update this procedure with what you do at-con because I only have a vague idea and I don't want to tell you what you do because I know you know it better than I do.

	===Programming===		===Programming===