Live Event Festival Presale Announcement Checklist
Build a deployment readiness checklist for multi-tiered festival ticket presale email blasts.
Deploy this template when coordinating exclusive lineup releases and presale access emails for music and arts festivals. It ensures accurate artist tiering, working access codes, and ticketing platform resilience.
Role: Senior Entertainment CRM Director specializing in live music festivals, venue promotion, and high-velocity ticketing drops.
Context
- Festival Name: {{festival_name}}
- Headlining Talent: {{headline_acts}}
- Ticket Pricing Breakdown: {{ticket_tier_structure}}
- Presale Access Window: {{presale_access_window}}
- Geographic Segments: {{geographic_segments}}
- Ticketing Destination: {{ticketing_partner_url}}
Task
Create a verification and deployment checklist for the upcoming presale announcement email campaign for {{festival_name}}, ensuring artist billing accuracy, dynamic presale code distribution, and ticket link integrity across {{geographic_segments}}.
Method
- Review artist roster spelling, font hierarchies, and headliner billing for {{headline_acts}} against legal talent contracts.
- Confirm that dynamic presale passcodes and custom redemption parameters properly append to {{ticketing_partner_url}}.
- Validate that the countdown timers and timezone displays align precisely with {{presale_access_window}}.
- Check that pricing, VIP perks, and installment options match {{ticket_tier_structure}}.
- Ensure geo-segmentation rules isolate past attendees in {{geographic_segments}} from national cold lists.
- Test transactional load balancing parameters to prevent server timeouts at the ticketing destination.
- Verify deliverability safeguards including sender domain authentication (SPF, DKIM, DMARC) prior to high-volume broadcast.
Constraints
- Checklists MUST enforce explicit verification steps for dynamic unique access codes.
- You MUST NOT approve copy containing unconfirmed artist billing or unverified early-bird prices.
- Limit checklist items to clear operational checks executable within a 60-minute pre-launch window.
- Include explicit contingency steps in case the external ticketing link experiences downtime.
Output format
1. Launch Criticals Table
Summary of festival assets and presale schedule.
2. Presale Email Operations Checklist
Grouped into: Talent & Billing Compliance, Presale Code Logic, Ticketing URL & Server Load, and Deliverability Safeguards. Format: [ ] Step Number | Check Item | Required Evidence | Owner.
3. Emergency Fallback Procedure
Bulleted 4-step contingency action plan for broken links or inventory sell-out scenarios.
Self-review
- Are all 6 variables ({{festival_name}}, {{headline_acts}}, {{ticket_tier_structure}}, {{presale_access_window}}, {{geographic_segments}}, {{ticketing_partner_url}}) integrated into specific verification items?
- Does the checklist verify artist contract font hierarchy standards?
- Are the deliverability and server load checks tailored to sudden peak traffic?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.