Draw seats, tables, booths and areas

This is for event organizers drawing a seating chart. The designer has a tool for each kind of thing buyers can book: seats in rows, tables, booths and general admission areas. To open it, see Open the seating chart designer.

What you can draw

  • Rows of seats. One row or a whole block of rows, straight or curved. Seats are numbered for you, and you can set the spacing.
  • Tables. Round or rectangular, with chairs around them. A table can sell as a whole or seat by seat. See Sell a table as a whole or seat by seat.
  • Booths. For a trade show or expo. Each booth sells like any other seat.
  • Areas. A standing room section, lawn or box that holds a number of people instead of numbered seats. See Add a general admission area or box to your chart.

Some tools have a small arrow beside them. That means the tool comes in more than one shape. For example, the area tool can draw a rectangle, a circle or a polygon.

The designer's toolbar with the area tool's shape menu open (rectangle, round, polygon).

Tips for a clean chart

  1. Start from your floor plan. You can place it in the designer and trace over it, so the scale and spacing match the room.
  2. Draw one section, then copy and paste it for the next. Select several objects to change them all at once.
  3. Use snap to grid, align and even spacing to keep rows straight.
  4. Give every seat, table, booth and area a category. Each category becomes a ticket, and seats with no ticket can't sell. See Seating categories.
  5. Publish the chart when you're done. Every event that uses it gets the change, and its ticket quantities update from the chart.
The designer with a finished chart: rows of seats, round tables and one general admission area, each in a category color.

What buyers see

Buyers see the map just as you drew it, and they pick a seat, table or booth on it. A ticket for a standing area says "No assigned seat" on your event page, so buyers know before they pay.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us