Festival Operations Manual
Expert operational guidance compiled from the Winter Festival team's collective expertise. This skill provides actionable protocols for common scenarios faced during festival operations.
🎭 Customer Experience (Madame Zelda's Expertise)
Handling Difficult Customers
- Always acknowledge their frustration first - Validate their feelings before proposing solutions
- Offer alternatives, never just say "no" - Frame solutions positively
- 20+ minute wait? Bump them up with a "VIP reading" - Turns complaints into compliments
- Dealing with skeptics? Use the "mysterious stranger" fortune style - it wins them over
- Kids under 10? Use the "adventure quest" style - parents love it and kids stay engaged
Keeping the Line Moving
- Fortunes should be 2-3 minutes max - Balance quality with efficiency
- Chatty customers? Offer an "extended reading" slot for later in the day
- During rush periods: Always have 5 pre-written fortunes ready for quick service
- Queue management: Use visual time estimates to set expectations
VIP Experience Tips
- Personalize greetings when possible
- Maintain mysterious ambiance even during busy times
- End each reading with a call-back element ("Remember the card I drew for you...")
🛡️ Security & Vendor Relations (Marcus's Expertise)
Vendor Management Protocols
Pre-Setup Requirements
- Food vendors: Check health permits BEFORE setup - Not negotiable, not after
- Verify insurance certificates - Must be current and cover festival dates
- Confirm electrical/utility needs - Prevent last-minute infrastructure issues
Noise Complaint Escalation Protocol
Important: Follow this exact sequence - document each step
- First warning: Verbal - Friendly reminder of noise limits
- Second warning: Written - Document time, nature of complaint, expected compliance
- Third incident: Shutdown - No exceptions, remove vendor for the day
Vendor Disputes
- Never take sides publicly - Maintain neutral mediator role
- Mediate in the back office - Keep disputes out of public view
- Document everything - Helps prevent future conflicts
Payment Protocols
- 50% upfront - Required before setup begins
- Balance day-of - Collect before gates open if possible
- No exceptions - Protects festival from no-shows
Security Response Codes
🟡 Code Yellow: Lost Child
- Immediately notify all exits - No one leaves without checking
- Broadcast description - Alert all staff with: age, clothing, distinguishing features
- Check common locations first: bathrooms, food court, game areas
- Stay with child if found - Never leave them alone until reunited with guardian
- Verify guardian: Ask child first, check ID if needed
🔵 Code Blue: Medical Emergency
- Clear path to medical tent - Priority movement
- Call 911 immediately - Don't wait to assess severity
- Assign one person to guide EMS - Meet them at entrance
- Secure the scene - Keep crowd back, maintain dignity
⚪ Code White: Weather Emergency
- Announce shelter locations - Use all communication channels
- Secure loose items - Prevent injuries from flying debris
- Account for all staff - Buddy system check-ins
- Monitor conditions - Designated weather watcher
🟠 Code Orange: Suspicious Activity
- Security team converges - Never confront alone
- Observe and report - Document appearance, behavior, location
- Maintain distance - Safety first
- Notify festival director - Keep leadership informed
📦 Lost & Found Operations (Maria's Expertise)
Intake Process (CRITICAL: Follow Every Step)
- Photo EVERYTHING before storing - Helps with remote claims
- Tag with complete details:
- Item description (be specific: "Blue iPhone 13 with cracked screen")
- Location found (specific booth/area)
- Time found (exact time helps narrow claims)
- Finder's name (for follow-up/rewards)
- High-value items → Locked cabinet - Phones, wallets, jewelry, keys
- Perishables disposed after 2 hours - Food safety and storage space
Claiming Process (Prevent Fraud)
- Ask claimants to describe BEFORE showing - Prevents false claims
- Check ID for high-value items - Match name to contents when possible
- Log all claims - Both successful and unsuccessful (patterns help)
- Unclaimed items after 30 days → Charity - Clear documented process
Common Loss Patterns (Check These First!)
- Ice rink = Mittens and scarves - Kids take them off, forget them
- Food court = Phones and wallets - People set them down while eating
- Kids areas = Stuffed animals - URGENT priority, kids are devastated
- Bathrooms = Jackets and bags - Hung on hooks and forgotten
- Entrance/Exit = Single gloves - Falls out of pockets
Pro Tips
- Check lost & found bin hourly during peak times
- Proactively announce "stuffed animal found" near kids areas
- Keep commonly lost items visible (mittens, hats) for quick matching
- Take photos of distinctive items for social media posts
📢 Marketing & Communications (Elena's Expertise)
Last-Minute Request Timeline
Poster Changes
- Minimum 2 hours needed - Print shop turnaround time
- Rush fees apply - Budget consideration
- Digital alternative: Can update digital boards in 15 minutes
Social Media Posts
- 15 minutes if content provided - Have copy and images ready
- 30 minutes if we create content - Photography and writing time
- 1 hour for approval chain - If director/sponsor sign-off needed
Press Inquiries
- Route to Festival Director - Never speak on record yourself
- Collect contact info: Name, outlet, deadline, topic
- Flag urgency level - Breaking news vs. feature story timing
Sponsor Logo Additions
- Check contract first - Some sponsors have exclusivity clauses
- Verify brand guidelines - Colors, sizing, placement rules
- Get written approval - Protects both parties
Emergency Communication Protocol
Weather Delays
- Post to ALL channels simultaneously:
- Social media (Facebook, Instagram, Twitter)
- Email blast to ticket holders
- Update website homepage
- Text alerts (if system enabled)
- Include: New timing, what to expect, how to get updates
Event Cancellations
- Priority order (CRITICAL):
- Email ticket holders FIRST - They have financial stake
- Update website - Create dedicated cancellation page
- Public announcement - Social media and press
- Refund process communication - Within 24 hours
- Include: Reason, refund process, rescheduling info
Good News Announcements
- Social media first - Immediate engagement
- Email newsletter follows - More detailed storytelling
- Press release - For major milestones
Communication Channel Selection Guide
- Urgent + Paid customers = Email + Text
- Urgent + General public = Social media
- Not urgent + Detailed info = Email newsletter
- Media relations = Press release + phone call
- Internal group chat
🎯 Quick Reference: Common Scenarios
"A vendor is playing music too loud and neighbors are complaining"
→ Follow noise complaint escalation protocol (see Security section)
→ First: Verbal warning
→ Second: Written warning
→ Third: Shutdown
"A child is lost at the festival"
→ CODE YELLOW immediately
→ Notify all exits, broadcast description
→ Check bathrooms, food court, game areas first
→ Stay with child when found until guardian verified
"Someone claims they lost their phone"
→ Ask them to describe it BEFORE showing
→ Can they unlock it? (Best proof)
→ Check ID matches any info in phone
→ Log the claim either way
"We need to delay opening by 30 minutes due to weather"
→ Post to ALL channels simultaneously
→ Email ticket holders first if possible
→ Clear communication on new timing
→ Update all staff
"A customer has been waiting 25 minutes"
→ Offer "VIP reading" to skip ahead
→ Acknowledge the wait and thank them for patience
→ Make the experience extra special
"Two vendors are arguing over booth space"
→ Move them to back office immediately
→ Never take sides publicly
→ Document the agreement in writing
→ Follow up to ensure resolution holds
1---2name: festival-operations3description: Expert knowledge for running winter festival operations covering customer experience, security, vendor relations, lost & found, and marketing communications4---5
6# Festival Operations Manual
7
8Expert operational guidance compiled from the Winter Festival team's collective expertise. This skill provides actionable protocols for common scenarios faced during festival operations.
9
10## 🎭 Customer Experience (Madame Zelda's Expertise)
11
12### Handling Difficult Customers
13- **Always acknowledge their frustration first** - Validate their feelings before proposing solutions
14- **Offer alternatives, never just say "no"** - Frame solutions positively
15- **20+ minute wait?** Bump them up with a "VIP reading" - Turns complaints into compliments
16- **Dealing with skeptics?** Use the "mysterious stranger" fortune style - it wins them over
17- **Kids under 10?** Use the "adventure quest" style - parents love it and kids stay engaged
18
19### Keeping the Line Moving
20- **Fortunes should be 2-3 minutes max** - Balance quality with efficiency
21- **Chatty customers?** Offer an "extended reading" slot for later in the day
22- **During rush periods:** Always have 5 pre-written fortunes ready for quick service
23- **Queue management:** Use visual time estimates to set expectations
24
25### VIP Experience Tips
26- Personalize greetings when possible
27- Maintain mysterious ambiance even during busy times
28- End each reading with a call-back element ("Remember the card I drew for you...")
29
30## 🛡️ Security & Vendor Relations (Marcus's Expertise)
31
32### Vendor Management Protocols
33
34#### Pre-Setup Requirements
35- **Food vendors: Check health permits BEFORE setup** - Not negotiable, not after
36- **Verify insurance certificates** - Must be current and cover festival dates
37- **Confirm electrical/utility needs** - Prevent last-minute infrastructure issues
38
39#### Noise Complaint Escalation Protocol
40**Important:** Follow this exact sequence - document each step
411. **First warning: Verbal** - Friendly reminder of noise limits
422. **Second warning: Written** - Document time, nature of complaint, expected compliance
433. **Third incident: Shutdown** - No exceptions, remove vendor for the day
44
45#### Vendor Disputes
46- **Never take sides publicly** - Maintain neutral mediator role
47- **Mediate in the back office** - Keep disputes out of public view
48- **Document everything** - Helps prevent future conflicts
49
50#### Payment Protocols
51- **50% upfront** - Required before setup begins
52- **Balance day-of** - Collect before gates open if possible
53- **No exceptions** - Protects festival from no-shows
54
55### Security Response Codes
56
57#### 🟡 Code Yellow: Lost Child
58- **Immediately notify all exits** - No one leaves without checking
59- **Broadcast description** - Alert all staff with: age, clothing, distinguishing features
60- **Check common locations first:** bathrooms, food court, game areas
61- **Stay with child if found** - Never leave them alone until reunited with guardian
62- **Verify guardian:** Ask child first, check ID if needed
63
64#### 🔵 Code Blue: Medical Emergency
65- **Clear path to medical tent** - Priority movement
66- **Call 911 immediately** - Don't wait to assess severity
67- **Assign one person to guide EMS** - Meet them at entrance
68- **Secure the scene** - Keep crowd back, maintain dignity
69
70#### ⚪ Code White: Weather Emergency
71- **Announce shelter locations** - Use all communication channels
72- **Secure loose items** - Prevent injuries from flying debris
73- **Account for all staff** - Buddy system check-ins
74- **Monitor conditions** - Designated weather watcher
75
76#### 🟠 Code Orange: Suspicious Activity
77- **Security team converges** - Never confront alone
78- **Observe and report** - Document appearance, behavior, location
79- **Maintain distance** - Safety first
80- **Notify festival director** - Keep leadership informed
81
82## 📦 Lost & Found Operations (Maria's Expertise)
83
84### Intake Process (CRITICAL: Follow Every Step)
851. **Photo EVERYTHING before storing** - Helps with remote claims
862. **Tag with complete details:**
87 - Item description (be specific: "Blue iPhone 13 with cracked screen")
88 - Location found (specific booth/area)
89 - Time found (exact time helps narrow claims)
90 - Finder's name (for follow-up/rewards)
913. **High-value items → Locked cabinet** - Phones, wallets, jewelry, keys
924. **Perishables disposed after 2 hours** - Food safety and storage space
93
94### Claiming Process (Prevent Fraud)
95- **Ask claimants to describe BEFORE showing** - Prevents false claims
96- **Check ID for high-value items** - Match name to contents when possible
97- **Log all claims** - Both successful and unsuccessful (patterns help)
98- **Unclaimed items after 30 days → Charity** - Clear documented process
99
100### Common Loss Patterns (Check These First!)
101- **Ice rink = Mittens and scarves** - Kids take them off, forget them
102- **Food court = Phones and wallets** - People set them down while eating
103- **Kids areas = Stuffed animals** - URGENT priority, kids are devastated
104- **Bathrooms = Jackets and bags** - Hung on hooks and forgotten
105- **Entrance/Exit = Single gloves** - Falls out of pockets
106
107### Pro Tips
108- Check lost & found bin hourly during peak times
109- Proactively announce "stuffed animal found" near kids areas
110- Keep commonly lost items visible (mittens, hats) for quick matching
111- Take photos of distinctive items for social media posts
112
113## 📢 Marketing & Communications (Elena's Expertise)
114
115### Last-Minute Request Timeline
116
117#### Poster Changes
118- **Minimum 2 hours needed** - Print shop turnaround time
119- **Rush fees apply** - Budget consideration
120- **Digital alternative:** Can update digital boards in 15 minutes
121
122#### Social Media Posts
123- **15 minutes if content provided** - Have copy and images ready
124- **30 minutes if we create content** - Photography and writing time
125- **1 hour for approval chain** - If director/sponsor sign-off needed
126
127#### Press Inquiries
128- **Route to Festival Director** - Never speak on record yourself
129- **Collect contact info:** Name, outlet, deadline, topic
130- **Flag urgency level** - Breaking news vs. feature story timing
131
132#### Sponsor Logo Additions
133- **Check contract first** - Some sponsors have exclusivity clauses
134- **Verify brand guidelines** - Colors, sizing, placement rules
135- **Get written approval** - Protects both parties
136
137### Emergency Communication Protocol
138
139#### Weather Delays
140- **Post to ALL channels simultaneously:**
141 - Social media (Facebook, Instagram, Twitter)
142 - Email blast to ticket holders
143 - Update website homepage
144 - Text alerts (if system enabled)
145- **Include:** New timing, what to expect, how to get updates
146
147#### Event Cancellations
148- **Priority order (CRITICAL):**
149 1. **Email ticket holders FIRST** - They have financial stake
150 2. **Update website** - Create dedicated cancellation page
151 3. **Public announcement** - Social media and press
152 4. **Refund process communication** - Within 24 hours
153- **Include:** Reason, refund process, rescheduling info
154
155#### Good News Announcements
156- **Social media first** - Immediate engagement
157- **Email newsletter follows** - More detailed storytelling
158- **Press release** - For major milestones
159
160### Communication Channel Selection Guide
161- **Urgent + Paid customers = Email + Text**
162- **Urgent + General public = Social media**
163- **Not urgent + Detailed info = Email newsletter**
164- **Media relations = Press release + phone call**
165- **Internal only = Staff group chat**
166
167## 🎯 Quick Reference: Common Scenarios
168
169### "A vendor is playing music too loud and neighbors are complaining"
170→ Follow noise complaint escalation protocol (see Security section)
171→ First: Verbal warning
172→ Second: Written warning
173→ Third: Shutdown
174
175### "A child is lost at the festival"
176→ **CODE YELLOW immediately**
177→ Notify all exits, broadcast description
178→ Check bathrooms, food court, game areas first
179→ Stay with child when found until guardian verified
180
181### "Someone claims they lost their phone"
182→ Ask them to describe it BEFORE showing
183→ Can they unlock it? (Best proof)
184→ Check ID matches any info in phone
185→ Log the claim either way
186
187### "We need to delay opening by 30 minutes due to weather"
188→ Post to ALL channels simultaneously
189→ Email ticket holders first if possible
190→ Clear communication on new timing
191→ Update all staff
192
193### "A customer has been waiting 25 minutes"
194→ Offer "VIP reading" to skip ahead
195→ Acknowledge the wait and thank them for patience
196→ Make the experience extra special
197
198### "Two vendors are arguing over booth space"
199→ Move them to back office immediately
200→ Never take sides publicly
201→ Document the agreement in writing
202→ Follow up to ensure resolution holds