A useful festival review should do more than say whether an event was enjoyable. This reusable attendee scorecard helps you compare music festivals on lineup, sound, crowds, queues, facilities, safety, accessibility, camping, staff, and value—while separating personal taste from conditions that may affect almost every visitor.
Overview
When deciding whether a festival is worth the ticket price, start with the difference between preference and performance. A reviewer may dislike electronic music but still give a strong, evidence-based assessment of the lineup’s variety, scheduling, and quality. Another attendee may love a headline act while reporting long entry queues, poor sound coverage, or limited shade. Both experiences can be valid, but they answer different questions.
Use this scorecard to create a consistent festival review. Give each category a score from 1 to 5, where 1 means seriously disappointing, 3 means acceptable or mixed, and 5 means excellent. Add a short note explaining the score and identify whether the issue was personal, shared, or dependent on a specific day or area.
| Category | What to assess | Useful evidence |
|---|---|---|
| Lineup and programming | Artist quality, variety, schedule clashes, and discovery opportunities | Set times, stage coverage, cancellations, and your actual schedule |
| Sound and production | Volume, clarity, sightlines, lighting, screens, and stage design | Observations from different stages and crowd positions |
| Crowd atmosphere | Energy, friendliness, density, and behavior | How the crowd felt at different times and locations |
| Queues and movement | Entry, security, toilets, bars, food, water, and exit flow | Approximate waiting times and bottlenecks |
| Facilities | Toilets, water points, seating, shade, waste management, and charging | Availability, cleanliness, location, and condition |
| Food and drink | Choice, dietary options, quality, payment process, and value | Menus, portions, service speed, and payment experience |
| Safety and support | Visible staff, welfare provision, information, and emergency communication | What was easy to find and how clearly issues were handled |
| Accessibility | Routes, viewing areas, toilets, transport, information, and assistance | Published provisions and what worked in practice |
| Camping and accommodation | Pitch conditions, quiet options, showers, security, and distance | Walking time, facilities, weather impact, and overnight comfort |
| Staff and organization | Clarity, consistency, helpfulness, and response to changes | Examples involving stewards, vendors, transport, or schedule updates |
| Overall value | Whether the full experience matched the total cost and effort | Ticket, travel, food, accommodation, and time commitments |
How to estimate
Record a score for each category, then calculate a simple average:
Overall score = total category points ÷ number of categories scored
For example, if eleven categories add up to 42 points, the average is 42 ÷ 11, or about 3.8 out of 5. Treat that result as a comparison tool, not a universal verdict. A festival with a high average may still be unsuitable if it performs poorly in a category that matters most to you.
For a more personal decision, use weighted scoring. Give each category an importance weight from 1 to 3:
- 1: Nice to have but not decisive.
- 2: Important to the experience.
- 3: Essential for booking.
Multiply each category score by its weight, add the results, and divide by the total of all weights. This prevents a strong lineup from hiding a serious accessibility, camping, safety, or transport concern. Someone attending for one favorite artist might weight programming heavily. A family group, disabled attendee, or traveler staying off-site may give greater weight to facilities, access, accommodation, and getting home.
Also record confidence beside each score: high when you observed the issue repeatedly, medium when you saw it once or heard consistent reports from companions, and low when it is based mainly on an isolated comment. This keeps a memorable incident from becoming an unsupported generalization.
Inputs and assumptions
A reliable festival review depends on clear inputs. Before scoring, note the edition, dates, venue or site layout, ticket type, number of days attended, and whether you camped, commuted, or used nearby accommodation. Conditions can vary substantially between a single-day visit and a full weekend.
Separate facts from impressions. “The main entrance opened late for our arrival window” is more useful than “entry was a disaster.” “The queue moved slowly between the car park and security” identifies a location and process that future attendees can investigate. If weather, a schedule change, or a transport disruption affected your experience, explain that context rather than treating it as a permanent feature of the festival.
For value, calculate the full trip rather than looking only at the advertised ticket:
Total festival cost = ticket and fees + travel + accommodation or camping + food and drinks + local transport + equipment and other extras
Use actual spending where possible. If you are reviewing before booking, create low, expected, and high estimates using the festival’s official ticket information and your own travel assumptions. Do not present an estimate as a current price unless you have checked the relevant official source. For ticket decisions, use official festival ticket links first and treat resale listings separately; a resale premium can change the value calculation.
For comparisons, keep the method consistent. Score two festivals using the same categories, weightings, and cost boundaries. Do not compare a full camping weekend with a local day visit without labeling the different assumptions.
Accessibility deserves its own investigation rather than being inferred from an overall score. Check the organizer’s current information about routes, viewing platforms, toilets, parking, camping, assistance, and communication, then compare it with recent attendee experience. Our Festival Accessibility Guide provides a separate checklist for this research.
Worked examples
Example 1: Comparing two music festivals. Suppose Festival A scores 4 for lineup, 3 for sound, 3 for crowds, 2 for queues, 4 for facilities, and 4 for staff. Its total is 20 out of 30, or 3.3 out of 5. Festival B scores 3, 4, 4, 4, 3, and 3: 21 out of 30, or 3.5. On an unweighted basis, Festival B leads narrowly.
Now assume queues are essential because you plan to move between stages, so you give queues a weight of 3 and every other category a weight of 1. Festival A’s weak queue score has a much larger effect, while Festival B’s stronger result becomes more relevant. The conclusion is not that Festival B is objectively better; it is that Festival B fits this attendee’s priorities more closely.
Example 2: Testing value. A weekend review should list the ticket, fees, round-trip travel, accommodation or camping, meals, drinks, local transport, and any required equipment. If the total is higher than expected, identify which assumptions changed. A cheap ticket may not represent good value if transport and accommodation are costly, while a more expensive event may compare favorably when travel is simple and facilities reduce extra spending.
When publishing the review, include the scorecard, two or three specific examples, the total-cost assumptions, and who the festival may suit. Mention what you did not test—for example, accessible camping if you did not use it—rather than implying that your experience covers every attendee.
When to recalculate
Revisit a festival review whenever an input changes. Recalculate after a new venue, site expansion, ticket structure, camping arrangement, transport plan, or major programming change. A different weather pattern can also change the practical assessment of shade, drainage, walking routes, and camping, so label weather-dependent observations clearly.
Update cost comparisons when ticket phases, fees, travel fares, accommodation rates, food prices, or exchange rates change. If you are monitoring an established event, compare the latest attendee reports with previous editions: has the same queue problem appeared again, did a site change improve movement, and are facilities still suitable for the audience described?
For your next decision, save a blank copy of the scorecard, set your essential categories before reading other reviews, and then compare at least several recent attendee accounts with the organizer’s current information. After attending, complete the scores while details are fresh, retain receipts and approximate wait times, and mark any uncertain claims. This produces a review that helps readers decide—not merely a record of whether you had a good day.