Festival website content checklist

A festival site announces the line-up in phases, sells tickets and answers the practical questions: how to get there, what to bring, where to camp. Expect late artist details and a site map that keeps changing until the week of the event.

8 pages41 requests27 requiredAnswered by the festival director or production manager

Where to start

  1. Brand and legal. Logo files and licence confirmation have the longest lead time because other people own them.
  2. Tickets. Revenue depends on this page, and the ticket platform decides how closely it can match the design.
  3. Line-up. It is the most shared page and depends on photo rights from agents, which take weeks.
  4. Getting there and the site. The site map and travel facts exist already and can be gathered while artists are still being confirmed.
  5. Safety and accessibility. It needs sign-off from the safety lead and the director, so give them time with it.

The checklist

Home

The home page changes with every announcement phase, so it has to be planned as a set of states, not as one fixed layout.

  • Festival name and edition Short text, requiredThe name as printed on wristbands and posters. Say whether the year or edition number is part of the name.
  • Dates and location Short text, requiredStart date, end date, and the town or site name, in the format you want printed. Add gate opening times if they differ by day.
  • One-line description Short text, requiredWhat kind of festival it is and where, in under 20 words. For example: 'Three days of folk and roots music in a Welsh valley, with camping on site.'
  • Hero image Image upload, requiredA wide crowd or stage shot from a past year, at least 2400 pixels wide, with no text on the picture. If it is a first edition, send the best site or artist image you have.
  • Primary action Single choice, requiredThe one button the home page leans on. Pick what applies today, and the designer will plan for the next phase.Buy ticketsSee the line-upSign up for the announcementApply to trade
  • Announcement dates Long textThe dates each batch of artists will be revealed and what the site should show between them. The home page is rebuilt for each phase.

Line-up

This is the page people share. It depends on contracts, billing order and photo rights, and artists' agents send material late.

  • Confirmed artists File upload, requiredA spreadsheet with artist name, stage, day, genre, country and links. Mark each artist as announced or not yet announced.
  • Artist press photos Image upload, requiredSupplied by the artist or their agent, at least 1600 pixels on the long side. Ask for the credit line that goes with each photo.
  • Permission to use artist photos Yes or no, requiredConfirm the artists or their agents have allowed the photos for promotion. Some agencies limit use to a set period.
  • Billing order Long text, requiredThe order and relative size names should appear in. Billing is often contractual, so ask the booker whether any artist has a clause on size or position.
  • Artist short bios Long textAround 40 words per artist, taken from their press kit with permission. Skip it if you only want names and photos.

Programme and stages

Set times arrive late and change, so the page needs a way to show provisional times without looking broken.

  • Stage names and descriptions Long text, requiredEach stage with its name, a one-line description and what it books. Guests use these to choose which day to attend.
  • Set times File uploadA spreadsheet with stage, artist, start and end. Mark everything provisional until it is confirmed, so the site can show a holding message.
  • Non-music programme Long textTalks, workshops, comedy, children's activities and food events, each with a time and a location on site.
  • Categories for filtering Multiple choiceTick the labels you want visitors to filter by. Use only the ones that describe at least a few acts.RockElectronicFolkHip hopJazzClassicalComedyFamily

Tickets

Ticket pages get the most traffic and the most mistakes, because prices, add-ons and age rules live in different documents.

  • Ticketing platform Single choice, requiredPick the system that takes payment. The site links to it, so the choice decides how closely the page can match your brand.EventbriteDiceTicket TailorOwn checkoutNot decided
  • Ticket checkout link LinkThe address of the live checkout. If sales are not open, send the test link or the date it will be created.
  • Ticket types and prices Long text, requiredEach ticket with its price and what it covers, such as weekend, day, VIP or child. Add the date each release ends.
  • Age policy and under-18 rules Long text, requiredEntry age, whether under-18s need an adult and what ID is checked on the gate. Ask who approves the wording, since rules differ by country.
  • Resale and transfer terms Long text, requiredWhether tickets can be resold or put in another name, and the official channel if so. Buyers search for this before they buy.
  • Add-ons on sale Multiple choiceTick everything sold with a ticket. Each one needs a price and a short description from you.CampingCampervan pitchGlampingParkingShuttle busLockersAccessible camping

Getting there and the site

People plan travel and packing from this page, so it has to be accurate and has to match what the gate staff will say.

  • Site address and map pin Long text, requiredThe address a satnav accepts, plus the coordinates of the main gate. A town centre pin sends people to the wrong place.
  • Site map File upload, requiredThe current version as PDF or SVG, showing stages, toilets, water, medical and camping. Mark it as draft if the layout can still move.
  • Travel options Long text, requiredTrain station and shuttle times, coach services, driving directions and taxi rank. Say which route you recommend.
  • What to bring and what is banned Long text, requiredBag size, glass, alcohol, tents, chairs, drones and power banks. Copy the list from the safety plan so gate staff and the site agree.
  • Camping information Long textPitch types, arrival and departure times, fire rules and whether tents can be pre-pitched. Leave empty if there is no camping.

Safety and accessibility

Families and disabled guests read this page before buying, and a gap here costs ticket sales and trust.

  • Accessibility provision Long text, requiredViewing platforms, accessible toilets, step-free routes, quiet areas and charging for medical equipment. Be specific about which stages have what.
  • Access ticket process Long text, requiredHow someone applies for a carer or access ticket, who reviews it and how long it takes. Include the form or email.
  • Welfare and medical information Long text, requiredWhere the medical tent and welfare team are, what they handle, and how to ask for help on site.
  • Weather and cancellation policy Long text, requiredWhat happens in heavy rain, wind or a full cancellation, and what ticket holders can expect. Ask who approves the wording.
  • Event licence confirmed Yes or no, requiredConfirm the licence or permit is in place, and say who approves any licence details shown on the site. Check the rules where the festival operates.

Traders, sponsors and volunteers

Three groups apply or check their listing on this page, and each needs its own deadline and contact.

  • Trader application link LinkThe address of the form for food and craft traders. Add the closing date and any fee in the next field if it is not on the form.
  • Trader criteria Long textWhat you look for in a stall, which categories are full, and what traders must show, such as hygiene ratings or insurance.
  • Sponsor logos File uploadVector files (SVG, EPS or PDF) from each sponsor, one folder per company, with the tier noted in the file name.
  • Volunteer roles and shifts Long textEach role, its shift length, any perks such as a ticket, and the minimum age. Say how many people you still need.

Brand and legal

Logo files and legal text have the longest lead time, because designers and lawyers own them.

  • Festival logo files File upload, requiredSVG, EPS or PDF in colour and single-colour versions, plus any logo variants used on stage banners and wristbands.
  • Brand colours ColourThe main colour from your poster or wristband, as a hex code. If you have none, say which item to match.
  • Brand fonts FontThe typeface on the poster. Festival posters often use a display font that is licensed for print only, so ask the poster designer.
  • Organiser legal name Short text, requiredThe company that runs the festival, as it should appear in the footer and the ticket terms.
  • Permission to show past attendee photos Yes or no, requiredConfirm the photographer has agreed to the use, and that the festival is happy with crowd shots where faces are clear.
  • Privacy and cookie policy approved Yes or no, requiredSay whether a policy exists. If not, the designer will start from a standard template for you to have reviewed.

What clients get stuck on

Artist photos with no usage terms

Agents send photos with a credit line and sometimes a time limit. Ask for both in the same email, and keep a list of what expires so the gallery does not go stale after the festival.

Set times that exist only as rumours

Times get agreed by phone and reach the site late. Decide how provisional times appear, such as 'Saturday, time to be confirmed', and agree who sends the final list and when.

A site map that is a photo of a plan

Ask the production team for the layout file, not a photo of a printout. A readable map needs vector artwork, and without it you redraw it every time a stage moves.

Access information that is vague

A line saying 'the site is accessible' fails the people who read it hardest. Ask the safety lead for specifics, such as which stages have platforms, and have the festival director approve them.

Cancellation wording that nobody owns

Ticket terms and weather plans sit with the director, the insurer and the ticket platform. Ask one person to approve the final text, then use it everywhere so no page contradicts another.

Copy the checklist

Plain Markdown you can paste into a doc or an email.

# Festival website content checklist

## Home
- [ ] Festival name and edition (Short text, required)
- [ ] Dates and location (Short text, required)
- [ ] One-line description (Short text, required)
- [ ] Hero image (Image upload, required)
- [ ] Primary action (Single choice, required)
- [ ] Announcement dates (Long text)

## Line-up
- [ ] Confirmed artists (File upload, required)
- [ ] Artist press photos (Image upload, required)
- [ ] Permission to use artist photos (Yes or no, required)
- [ ] Billing order (Long text, required)
- [ ] Artist short bios (Long text)

## Programme and stages
- [ ] Stage names and descriptions (Long text, required)
- [ ] Set times (File upload)
- [ ] Non-music programme (Long text)
- [ ] Categories for filtering (Multiple choice)

## Tickets
- [ ] Ticketing platform (Single choice, required)
- [ ] Ticket checkout link (Link)
- [ ] Ticket types and prices (Long text, required)
- [ ] Age policy and under-18 rules (Long text, required)
- [ ] Resale and transfer terms (Long text, required)
- [ ] Add-ons on sale (Multiple choice)

## Getting there and the site
- [ ] Site address and map pin (Long text, required)
- [ ] Site map (File upload, required)
- [ ] Travel options (Long text, required)
- [ ] What to bring and what is banned (Long text, required)
- [ ] Camping information (Long text)

## Safety and accessibility
- [ ] Accessibility provision (Long text, required)
- [ ] Access ticket process (Long text, required)
- [ ] Welfare and medical information (Long text, required)
- [ ] Weather and cancellation policy (Long text, required)
- [ ] Event licence confirmed (Yes or no, required)

## Traders, sponsors and volunteers
- [ ] Trader application link (Link)
- [ ] Trader criteria (Long text)
- [ ] Sponsor logos (File upload)
- [ ] Volunteer roles and shifts (Long text)

## Brand and legal
- [ ] Festival logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Organiser legal name (Short text, required)
- [ ] Permission to show past attendee photos (Yes or no, required)
- [ ] Privacy and cookie policy approved (Yes or no, required)

Questions about this checklist

How should a festival site handle a line-up that is announced in stages?

Plan the line-up page as a set of states: before any announcement, after each batch, and the full bill. Build the layout so new names slot in without a redesign, and agree the announcement dates up front.

Do festival websites need a separate page for each stage?

Only if each stage has its own programme and enough text to stand alone. For most festivals a single programme page with a filter by stage is easier to keep current and is faster on a phone.