Skip to main content

Conference agenda template

A running order of sessions with times, rooms and speakers, generated per event or per track from your session list.

Google Docs PDF export No watermark
Start automating See how it automates

Free plan, no credit card. Bring your own design or start from this layout.

The actual template Conference agenda template shown in Google Docs

What’s in this template

Every block is bound to a field in your data. The layout stays exactly as designed; only the values change from one run to the next.

  • Header with the event name, dates and venue {{event.name}} · {{event.dates}}
  • Day heading for each day of the programme loop: {{days}}
  • Session rows with time, title and room loop: {{sessions}}
  • Speaker line under each session {{session.speakers}}
  • Breaks and catering slots in the running order {{session.type}}
  • Track key and room map notes {{event.tracks}}
  • Footer with wifi, hashtag and contacts {{event.footer}}

How this template fills itself

Connect Airtable, Google Sheets, a SQL database, a CSV or a REST API, map each field to a placeholder, and generate. One run can produce a single document or one per matching record.

Events & programs: A running order of sessions with times, rooms and speakers, generated per event or per track from your session list.

Sessions · Airtable

TimeSessionRoom
09:30Opening keynoteMain Hall
11:00Scaling data teamsRoom B
14:15Workshop: pipelinesStudio 2

Template: Google Slides or Docs

{{event.name}}

Agenda · {{event.dates}}

loop: {{days}} → day heading

loop: {{sessions}} → time, title, room

{{session.speakers}}

one agenda per event, or one per track when you filter the session list

Generated output

DocsPDF

DataConf 2026

Agenda · 12–13 May 2026

Day 1 — Thursday 12 May

09:30 · Opening keynote · Main Hall

Priya Raman, Head of Data

Start automating

Who uses this template

Conference organisers

Rebuild the printed and emailed agenda from the session list every time the schedule moves, instead of editing a document by hand.

Read the guide

Events teams inside companies

Produce a clean agenda for an internal summit or offsite straight from the sessions table you already keep.

Read the guide

Teams running events on Airtable

Keep sessions, speakers and rooms in the base and generate the agenda from it on demand.

Read the guide

A conference agenda is a list before it is a document: sessions, times, rooms and speakers, in order. The part that makes it painful is that the list keeps moving right up to the day before, and every move has to be reflected in the printed programme, the track handouts and the PDF you email out.

Shape the session list, not the document

Keep one row per session with a start time, a title, a room, a track and a speaker reference, and let the template do the grouping. Days become a loop over the dates, sessions become a loop inside it, and breaks are just rows with a different type so they land in the right place in the running order. When something moves, you edit the row, not the layout. Because the agenda is a Google Doc, a day with twenty-two sessions simply runs onto another page instead of breaking a design someone spent an afternoon fixing.

Related templates

All events & programs →
Event program template: the actual Google Slides template Google Slides

Event program template

A designed programme booklet for an event, generated per event from the session and speaker list.

View template
Multi-day itinerary template: the actual Google Docs template Google Docs

Multi-day itinerary template

A day-by-day schedule of travel, sessions and logistics, generated per trip or per attendee from your schedule data.

View template
Attendee name badge template: the actual Google Slides template Google Slides

Attendee name badge template

A printed conference badge with name, organisation and ticket type, generated one per attendee from the registration list.

View template
Event ticket template: the actual Google Slides template Google Slides

Event ticket template

A printable ticket carrying the event, seat and booking reference, generated one per booking from your registration data.

View template

Common questions, answered

What happens when the schedule changes the week of the event? +
You change the session row and run the template again. Because the agenda is built from the session list rather than typed into a file, a moved talk or a swapped room is one edit in the data, and the printed agenda, the track versions and the PDF all come back consistent in a single run.
Can I produce a separate agenda per track or per day? +
Yes. Filter the session list to a track, a day or a room and each matching subset produces its own document. Organisers commonly generate one full programme plus a short agenda per track, all from the same table, so delegates on the workshop stream carry two pages rather than twenty.
Why is this a Google Doc rather than slides? +
Because the length is unpredictable. A day with nine sessions and a day with twenty-two need different amounts of space, and a Doc lets the session table grow and the pages break on their own. A fixed slide layout would need redesigning every time the programme changed size.
Can I use my own agenda design? +
Yes, and most organisers do. Build the master in Google Docs with your event branding, typography and section rules, mark the fields as placeholders, and generate against that rather than this layout. The template here exists to show which blocks are variable and how the session loop is bound, not to fix a design on you.

Generate this document from your data

Start on the free plan, connect a data source, and export a real Google Docs document. No watermark, no credit card.

Start automating See pricing