Bellus: Difference between revisions
Created page with "'''CoRELore''' ---- Planning for CoRE Lore begins nearly at the beginning of the semester. Having run CoRE Lore the previous year, I knew the time requirements and the level o..." (change visibility) |
No edit summary (change visibility) |
||
| Line 7: | Line 7: | ||
'''Phase 1: Start of Semester''' |
'''Phase 1: Start of Semester''' |
||
I began making announcements for CoRE Lore and the initial planning phase started immediately. Finding space and making the arrangements to request and reserve the found space was priority number 1. The newly completed C4 building was chosen for proximity, space and ease of use. One of the multi-purpose rooms on the first floor was reserved for the night of CoRE LoRE |
I began making announcements for CoRE Lore and the initial planning phase started immediately. Finding space and making the arrangements to request and reserve the found space was priority number 1. The newly completed C4 building was chosen for proximity, space and ease of use. One of the multi-purpose rooms on the first floor was reserved for the night of CoRE LoRE |
||
'''Phase 2: Initial planning''' |
'''Phase 2: Initial planning''' |
||
This phase involved starting to gather recipes and thoughts for food at CoRE Lore. We decided that quality would trump quantity, as had not been the case for many previous years. For this to succeed, sheer number of recipes would be key, so every CoRE member would need to contribute at least one recipe. |
This phase involved starting to gather recipes and thoughts for food at CoRE Lore. We decided that quality would trump quantity, as had not been the case for many previous years. For this to succeed, sheer number of recipes would be key, so every CoRE member would need to contribute at least one recipe. |
||
| Line 17: | Line 19: | ||
'''Phase 3: Further planning and refinement''' |
'''Phase 3: Further planning and refinement''' |
||
Here, the recipes were chosen and with the list of guaranteed attending members, the general total actual attendance was approximated, and the recipes scaled appropriately. The recipes were then divvied out to pre-made groups of two to three CoRE members, so that each could be done easily and quickly during the actual event. The ingredient list was created and the general price of the event had its first data point. |
Here, the recipes were chosen and with the list of guaranteed attending members, the general total actual attendance was approximated, and the recipes scaled appropriately. The recipes were then divvied out to pre-made groups of two to three CoRE members, so that each could be done easily and quickly during the actual event. The ingredient list was created and the general price of the event had its first data point. |
||
| Line 23: | Line 26: | ||
'''Phase 4: Do CoreLore''' |
'''Phase 4: Do CoreLore''' |
||
At this point, we cook all the food, prepare all the dishes and bring it out to the guests. Everyone enjoys our hard work, and CoRELore is a success. |
At this point, we cook all the food, prepare all the dishes and bring it out to the guests. Everyone enjoys our hard work, and CoRELore is a success. |
||
Latest revision as of 17:21, 15 May 2012
CoRELore
Planning for CoRE Lore begins nearly at the beginning of the semester. Having run CoRE Lore the previous year, I knew the time requirements and the level of micro-management that would be needed. A multi-phase approach was taken to ensure that all aspects of CoRE Lore would be completed with time to spare.
Phase 1: Start of Semester
I began making announcements for CoRE Lore and the initial planning phase started immediately. Finding space and making the arrangements to request and reserve the found space was priority number 1. The newly completed C4 building was chosen for proximity, space and ease of use. One of the multi-purpose rooms on the first floor was reserved for the night of CoRE LoRE
Phase 2: Initial planning
This phase involved starting to gather recipes and thoughts for food at CoRE Lore. We decided that quality would trump quantity, as had not been the case for many previous years. For this to succeed, sheer number of recipes would be key, so every CoRE member would need to contribute at least one recipe.
In this phase, a rough head-count was established to be able to scale the event. Invitations were sent out to everyone in the core address book via email. The university office of alumni relations was collaborated with to ensure the maximum amount of people were contacted, and their own records were updated with our own list of people and addresses.
Phase 3: Further planning and refinement
Here, the recipes were chosen and with the list of guaranteed attending members, the general total actual attendance was approximated, and the recipes scaled appropriately. The recipes were then divvied out to pre-made groups of two to three CoRE members, so that each could be done easily and quickly during the actual event. The ingredient list was created and the general price of the event had its first data point.
A trip to Wegman’s was made to look at the turkeys and the price of buying any of the multiple versions/configurations of cooked, not cooked, spiced, etc. During this trip, cooking utensils were examined both in CoRE’s inventory, and at Wegman’s so that we would have enough materials to make the event successful.
Phase 4: Do CoreLore
At this point, we cook all the food, prepare all the dishes and bring it out to the guests. Everyone enjoys our hard work, and CoRELore is a success.