programmingops
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
programmingops [2014/05/06 16:57] – Added room counts, updated areas for improvement for 2015 mara | programmingops [2017/01/14 14:24] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 5: | Line 5: | ||
[[https:// | [[https:// | ||
- | ====== Areas for Improvement / 2015 Recommendations ====== | + | ==== Areas for Improvement / 2015 Recommendations ==== |
+ | - Replace printed name tents with dry erase name tents (Example: http:// | ||
- Have ProgramOps do room scheduling in advance of the convention rather than Programming. | - Have ProgramOps do room scheduling in advance of the convention rather than Programming. | ||
- | - Standardize A/V available in each room. Ideal is having | + | - Standardize A/V available in each room. Ideal would be to have a projector and microphone in each room, but this is likely |
- Work with Programming to get the programming data sent to ProgramOps to match the format listed below. | - Work with Programming to get the programming data sent to ProgramOps to match the format listed below. | ||
- Start date & time need to be combined into one field.\\ | - Start date & time need to be combined into one field.\\ | ||
Line 17: | Line 18: | ||
- For all speakers, include the name their registration is listed under. | - For all speakers, include the name their registration is listed under. | ||
- Have Programming designate which presenters do or do not need name tents. | - Have Programming designate which presenters do or do not need name tents. | ||
- | - Stop counting attendance at events. | + | - Stop counting attendance at events. |
- Create electronic counters for each room so as not to need people to visit each room to take attendance counts during each event.\\ | - Create electronic counters for each room so as not to need people to visit each room to take attendance counts during each event.\\ | ||
- Set up Google mail to forward a copy of all email sent to Programming or Track heads after the schedule is frozen to Program Ops. This is to ensure that Program Ops receives any notifications from presenters who need to cancel at the last minute.\\ | - Set up Google mail to forward a copy of all email sent to Programming or Track heads after the schedule is frozen to Program Ops. This is to ensure that Program Ops receives any notifications from presenters who need to cancel at the last minute.\\ | ||
Line 26: | Line 27: | ||
- Revisit speaker packets to see if they are still necessary, and if so, whether they are necessary for all types of speakers. | - Revisit speaker packets to see if they are still necessary, and if so, whether they are necessary for all types of speakers. | ||
- Look into replacing name tents with reusable, dry-erase boards sized appropriately. | - Look into replacing name tents with reusable, dry-erase boards sized appropriately. | ||
+ | - Revisit warning system/ | ||
====== Program Ops Responsibilities | ====== Program Ops Responsibilities | ||
- | The Program Ops person is a staff member on the Operations (Ops) team who handles the direct operational running of the convention. Program Ops responsibilities include ensuring all convention events start & finish on time, providing real time updates to the schedule during the convention if event times or locations are changed, counting attendance at all scheduled events, and publishing the same immediately after the convention. | + | The Program Ops person is a staff member on the Operations (Ops) team who handles the direct operational running of the convention |
===== Required Skills & Availability ===== | ===== Required Skills & Availability ===== | ||
Line 89: | Line 91: | ||
- Request green room information from the head of Hospitality for inclusion in GoH welcome letters.\\ | - Request green room information from the head of Hospitality for inclusion in GoH welcome letters.\\ | ||
- Request a list of GoH liaisons from the appropriate department head.\\ | - Request a list of GoH liaisons from the appropriate department head.\\ | ||
- | - Request a copy of the official map to be put in the scheduling book from the person responsible for the program book.\\ | + | - Request a copy of the official map to be put in the scheduling book from the person responsible for the program book. Modify as needed to use for individual participant maps.\\ |
- Update the welcome letters to reflect current green room & liaison information.\\ | - Update the welcome letters to reflect current green room & liaison information.\\ | ||
- Generate samples of the information that will be provided in each packet and provide to the heads of Ops, Programming, | - Generate samples of the information that will be provided in each packet and provide to the heads of Ops, Programming, |
programmingops.1399395457.txt.gz · Last modified: 2017/01/14 14:24 (external edit)