Conference website content checklist

A conference site has to sell tickets and answer logistics questions fast: dates, venue, schedule, speakers and conduct rules. Delays come from speaker bios and headshots arriving late, and from a sponsor list that changes every week.

8 pages41 requests27 requiredAnswered by the event manager or programme chair

Where to start

  1. Tickets. The ticketing platform limits how the pricing table can look, so settle it before anything is designed.
  2. Speakers. Names and photos take the longest to collect and decide how much room the home page needs.
  3. Schedule. It depends on the speaker list and changes for months, so build the structure early and fill it later.
  4. Venue and travel. The facts exist already and rarely change, so it can be finished while speaker content is still arriving.
  5. Code of conduct and policies. Someone senior has to approve the wording, and that approval often takes a week or more.

The checklist

Home

Visitors decide in a few seconds whether this event is for them, so the home page needs the date, the city and one clear next step, and the organisers often disagree on which step comes first.

  • Conference name and edition Short text, requiredWrite the name as it appears on badges, for example 'DevOps Days Leeds 2027'. Say whether the year is part of the name, because it changes how the logo and page titles are set.
  • Dates and city Short text, requiredStart date, end date, city and country, in the format you want printed. Add the time zone if any part of the event is online.
  • One-sentence pitch Short text, requiredWho the event is for and what they leave with, in under 20 words. For example: 'Two days of talks on accessible front-end work, for developers and designers.'
  • Hero image Image upload, requiredA wide shot of the main room from a past edition, full of people if possible. At least 2400 pixels wide, with no text on the picture. For a first edition, say so and the designer will suggest alternatives.
  • Primary action Single choice, requiredThe one button the home page leans on. It changes as the event gets closer, so pick the one that applies today.Buy ticketsSubmit a talkJoin the waitlistView the schedule
  • Headline numbers from the last edition Long textAttendees, speakers, countries or sessions from a past edition, with the year. Only list figures you can back up from a ticket export or a report.

Speakers

Speakers are the main reason people buy a ticket, and their photos and bios are the content that arrives last and in the most formats.

  • Confirmed speaker list File upload, requiredA spreadsheet with one row per speaker: name, talk title, company, country and social links. Mark each row as confirmed or pending.
  • Speaker headshots Image upload, requiredOne per speaker, square or portrait, at least 800 pixels on the short side. Name each file after the person, for example 'amara-okafor.jpg'.
  • Speaker bios Long text, requiredAbout 60 words each, in the third person. Ask speakers to write their own and send the final text through one person, so there is a single version.
  • Speakers' permission to be listed Yes or no, requiredConfirm every listed speaker has agreed to have their name, photo and bio on the site. Some need their employer's sign-off first.
  • Call for proposals link LinkThe address of your submission form on Sessionize, Papercall or your own page. Leave empty if the call is closed.
  • Call for proposals deadline Short textThe closing date and time with its time zone, as it should read on the page. Add the date speakers will hear back.

Schedule

Attendees open the schedule on their phones between sessions, and it keeps changing until the last month, so the page needs a single owner and a simple way to update it.

  • Draft schedule File upload, requiredA spreadsheet with day, start time, end time, room, session title and speaker. Mark every slot still undecided as TBC so the designer leaves space.
  • Schedule time zone Short text, requiredName the zone, for example 'Central European Time' or 'UTC-5'. It is needed even for in-person events, because remote attendees convert the times.
  • Tracks or rooms Long text, requiredList each track or room with its name and a one-line theme. The designer uses these for colour coding and filters.
  • Session formats in use Multiple choice, requiredTick every format on the programme. Each one gets its own label and length on the page.KeynoteTalkWorkshopPanelLightning talkBirds of a featherSocial event
  • Who changes the schedule after launch Short text, requiredA name and email address. One person needs to own the master version once sessions start moving.

Tickets

This page earns the revenue, and the ticketing platform limits how the pricing table can look, so the platform choice comes before the design.

  • Ticketing platform Single choice, requiredPick the system that takes payment. The site links to it or embeds it, and the choice decides how much control you have over the page.EventbriteTitoPretixLumaOwn checkoutNot decided
  • Ticket checkout link LinkThe address of the live checkout or waitlist page. If sales have not opened, send the test link or say when it will exist.
  • Ticket types and prices Long text, requiredEach type with its price and what it includes, such as early bird, standard, student or workshop only. Add the date each price ends.
  • Discounts and group rates Long textWho qualifies, how they claim it and what proof is needed. Include group size thresholds and any community or student rates.
  • Cancellation, refund and transfer terms Long text, requiredThe wording buyers see today. Ask who approves it, because it forms part of the sale terms and the rules differ by country.
  • Invoice details for company buyers Long textWhether you issue invoices, which tax ID goes on them and who buyers email. Many attendees need an invoice to claim the cost.

Venue and travel

These facts are known early and rarely change, but they are scattered across contracts and emails, so someone has to gather them in one place.

  • Venue name and address Long text, requiredThe address as the venue prints it, with postcode, plus the entrance attendees should use. It must match the map pin.
  • Venue floor plan File uploadA PDF showing rooms, registration, catering and toilets. If the venue only has a photo of a wall plan, ask for the file behind it.
  • Hotel partners and rate codes Long textEach hotel with distance to the venue, the booking link and any discount code. Include the date the group rate expires.
  • Travel from the airport or station Long textThe simplest route from the nearest airport and main station, with a typical travel time and a taxi or transit option.
  • Accessibility information Long text, requiredStep-free entrances, lifts, accessible toilets, hearing loops, quiet spaces and captioning. Say who attendees contact to arrange support.
  • Visa invitation letters Yes or noSay yes if you issue letters for international attendees who need a visa. If yes, add the contact and the lead time you need.

Sponsors

Sponsors check their own logo on the site the day after they pay, so this page needs the right files and a clear order of tiers.

  • Sponsor logos File upload, requiredVector files (SVG, EPS or PDF) from each sponsor, one folder per company. A PNG pulled from a website will look soft on a large screen.
  • Sponsor tiers and display order Long text, requiredThe tier names, which sponsors sit in each and how large each tier is shown. This is often written into sponsor contracts.
  • Sponsorship prospectus File uploadThe PDF you send to companies that ask about sponsoring. The designer turns it into a page so the packages can be found by search.
  • Sponsor contact Short textA name and email for companies that want to sponsor. Enquiries should reach a person, not a general inbox.

Code of conduct and policies

Attendees and speakers look for this page before they commit, and a policy with no named person to contact is the usual failure.

  • Code of conduct text Long text, requiredThe full text as you want it published. If you adapted a public template, say which one so the credit and licence are kept.
  • Incident reporting contact Short text, requiredAn email address and phone number that someone reads during the event, plus a second person who can step in.
  • Photo and recording policy Long text, requiredWhat attendees, press and speakers may record, and how people opt out of being photographed. Ask who approves the wording.

Brand and legal

Logo files and legal text have the longest lead time, because other people own them.

  • Conference logo files File upload, requiredSVG, EPS or PDF, in full colour and in a single-colour version for dark backgrounds. Include previous editions if the logo changes each year.
  • Brand colours ColourThe main colour from your badges or slides, as a hex code. If you have none, name a printed item to match.
  • Brand fonts FontThe typeface used on badges and slides. If a designer made them, ask for the font name and whether the licence covers web use.
  • Organising entity name Short text, requiredThe company or association that runs the event, as it should appear in the footer and on invoices.
  • Privacy and cookie policy approved Yes or no, requiredSay whether a policy is ready, or whether the designer should start from a standard template for your lawyer to review.

What clients get stuck on

Speaker headshots taken on a phone

Ask for the original file, not a crop from a badge or a screenshot from a social profile. If a speaker cannot send one within a week, use a company press photo with credit and swap it later.

Bios that run to 300 words

Put the word limit in the request and say the text will be cut to fit. Speakers paste what they used last time, so you otherwise receive five lengths and four writing styles for one page.

A schedule that moves after launch

Agree who owns the master schedule and how changes reach the site. If the programme chair already edits a spreadsheet, build the page from that sheet so a change never needs a call to the designer.

Sponsor logos in the wrong format

Sponsors send whatever is on their website. Ask for SVG or EPS and write the deadline into the sponsor pack, because the logo wall is the first thing they check after paying.

A code of conduct with no named contact

A policy that says 'tell the organisers' gives an attendee nobody to write to. Ask for an address that is read during the event and a second person who can take over if the first is busy.

Copy the checklist

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

# Conference website content checklist

## Home
- [ ] Conference name and edition (Short text, required)
- [ ] Dates and city (Short text, required)
- [ ] One-sentence pitch (Short text, required)
- [ ] Hero image (Image upload, required)
- [ ] Primary action (Single choice, required)
- [ ] Headline numbers from the last edition (Long text)

## Speakers
- [ ] Confirmed speaker list (File upload, required)
- [ ] Speaker headshots (Image upload, required)
- [ ] Speaker bios (Long text, required)
- [ ] Speakers' permission to be listed (Yes or no, required)
- [ ] Call for proposals link (Link)
- [ ] Call for proposals deadline (Short text)

## Schedule
- [ ] Draft schedule (File upload, required)
- [ ] Schedule time zone (Short text, required)
- [ ] Tracks or rooms (Long text, required)
- [ ] Session formats in use (Multiple choice, required)
- [ ] Who changes the schedule after launch (Short text, required)

## Tickets
- [ ] Ticketing platform (Single choice, required)
- [ ] Ticket checkout link (Link)
- [ ] Ticket types and prices (Long text, required)
- [ ] Discounts and group rates (Long text)
- [ ] Cancellation, refund and transfer terms (Long text, required)
- [ ] Invoice details for company buyers (Long text)

## Venue and travel
- [ ] Venue name and address (Long text, required)
- [ ] Venue floor plan (File upload)
- [ ] Hotel partners and rate codes (Long text)
- [ ] Travel from the airport or station (Long text)
- [ ] Accessibility information (Long text, required)
- [ ] Visa invitation letters (Yes or no)

## Sponsors
- [ ] Sponsor logos (File upload, required)
- [ ] Sponsor tiers and display order (Long text, required)
- [ ] Sponsorship prospectus (File upload)
- [ ] Sponsor contact (Short text)

## Code of conduct and policies
- [ ] Code of conduct text (Long text, required)
- [ ] Incident reporting contact (Short text, required)
- [ ] Photo and recording policy (Long text, required)

## Brand and legal
- [ ] Conference logo files (File upload, required)
- [ ] Brand colours (Colour)
- [ ] Brand fonts (Font)
- [ ] Organising entity name (Short text, required)
- [ ] Privacy and cookie policy approved (Yes or no, required)

Questions about this checklist

When should a conference site go live?

As soon as you have a date, a city and a way to sign up for news, even with an empty programme. Early visitors arrive from search and social links, and an email signup keeps them until the speakers are announced.

Should the conference schedule be a PDF or a page?

Build it as a page with filters by day and track, and offer a PDF for people who print. Attendees check times on phones between sessions, and a PDF is slow and awkward to read on a small screen.