Skip to main content

Event ticket template

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

Google Slides 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 Event ticket template shown in Google Slides

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.

  • Event name, date and venue lockup {{event.name}} · {{event.date}}
  • Ticket holder name {{booking.name}}
  • Admission type and price paid {{booking.type}} · {{booking.price}}
  • Seat, table or zone allocation {{booking.seat}}
  • Booking reference and scan code {{booking.ref}}
  • Stub with door times and conditions {{event.doors}}

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 printable ticket carrying the event, seat and booking reference, generated one per booking from your registration data.

Bookings · Google Sheets

BookingNameSeat
BK-2210Tom AlvarezTable 4
BK-2211Ines WeberTable 4
BK-2212Priya RamanRow C, 12

Template: Google Slides or Docs

{{event.name}}

{{booking.name}} · {{booking.type}}

{{booking.seat}}

{{booking.ref}}

{{event.doors}}

one ticket per booking row; filter to unprinted bookings for a top-up run

Generated output

SlidesPDF

Harvest Dinner 2026

Tom Alvarez · Standard admission

Table 4

BK-2210

Doors 18:30

Start automating

Who uses this template

Event and venue teams

Print a personalised ticket for every booking rather than handing out numbered generic stubs.

Read the guide

Charity and fundraising organisers

Produce seated dinner tickets from the guest list, with table allocations already on them.

Read the guide

Membership and community organisations

Generate tickets for each event from the same list you use for members and renewals.

Read the guide

A ticket is a small designed object produced once per booking. Nothing about the layout moves; everything printed on it — name, admission type, seat, reference — comes from a row. That is why it is built in Google Slides at a custom page size: the design holds exactly as drawn, and the run produces as many tickets as there are bookings.

Let the booking record decide what is printed

Tickets go wrong when allocations live in one place and the printed stub in another. Keep seat, table, admission type and reference on the booking row, generate from that, and a change is made once and reprinted rather than corrected with a pen at the door. Filtering is what makes late bookings manageable: run the tickets sold so far, then run only the new rows the day before. If door times or conditions differ by session, put them on the row too, so the stub is right for that performance rather than the season.

Related templates

All events & programs →
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
Table tent template: the actual Google Slides template Google Slides

Table tent template

A folded card that stands on a table, generated one per table, guest or dish from your event data.

View template
Membership card template: the actual Google Slides template Google Slides

Membership card template

A printable member card carrying a name, number, tier and renewal date, generated one per member from your membership list.

View template
Conference agenda template: the actual Google Docs template Google Docs

Conference agenda template

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

View template

Common questions, answered

Can I print one ticket per booking in a single run? +
Yes. Point the template at the bookings table and every row produces its own ticket, all exported as one PDF. If bookings keep arriving, filter to the rows not yet printed and run again to top up the batch rather than reprinting the lot.
Can the ticket carry a scan or QR code? +
It carries whatever your data holds. If your ticketing or registration system stores a code image or a URL against the booking, the template places it. SourceToDocs does not generate or validate ticket codes itself, so the source of truth for admission stays in the system that sold the ticket.
Can I use my own ticket design? +
Yes. Build the master in Google Slides at your ticket size — Slides takes a custom page size, so set it to your stock — lay out the stub, perforation line and branding, mark the variable text as placeholders and generate against that instead of this layout.
Where do seat and table allocations come from? +
From the booking record. Seating is usually decided in a spreadsheet or a base, and the ticket simply prints the allocation that is already there. Change a table in the data and reprint that one ticket, rather than editing a file someone has already exported.

Generate this document from your data

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

Start automating See pricing