Searchable
Type three letters of a name, get one answer. No scrolling past strangers.
Guest-facing
An interactive seating chart is one a guest can use rather than one they have to read. Instead of a printed board of two hundred names in alphabetical order, they open a page on their phone, type their name, and see their table.
This is not a ticketing seat map. Nobody is picking a seat or paying for one - the assignment is already made, and the interaction is a lookup.
Last updated
It opens the demo guest page for a sample event: a search box, a name, a table. That is the whole experience a guest has, and it is the same page a real event publishes.
No phone to hand? Open the same page in this tab.
Three things, and a chart with only the first is really a picture on a screen.
It responds to the person looking at it: a name search that returns their table rather than a list of everybody's. It reflects the current plan rather than the plan as it was when the file was exported. And it works on the device the guest is holding, which is a phone in a queue, not a laptop.
The distinction matters because "interactive seating chart" gets used for two very different things. One is this. The other is a ticketing seat map where the visitor picks a seat and buys it - a different product for a different audience, and not what this page is about.
Type three letters of a name, get one answer. No scrolling past strangers.
Reads the current plan. Move a guest and the answer changes without reprinting anything.
Designed for one hand, in a queue, on venue wifi.
A search that returns the guest's own result, not a browsable directory of attendees.
A page with the event name on it and a search box. They type, they see their table name or number and, where you have assigned exact chairs, their seat. If you have added it, they also see who else is at their table, which is the single most requested thing after the table number itself.
What they do not see is everyone else's assignment. The guest page is a lookup, not a directory, and that distinction is worth being explicit about with hosts who worry about it.
No app, no account, no password. The phone camera opens the page from a QR code and that is the whole journey.
The pattern is the same everywhere: a lot of people arriving at once, each needing one small piece of information.
The queue at the seating board is the reason this exists. See wedding seating chart.
Delegates who do not know anybody, arriving in a fifteen-minute window.
Sponsor tables, seated guests, and a host who cannot personally direct three hundred people.
Pair it with the event check-in app so arrivals are tracked as they are directed.
The interactive chart is produced by the plan, not built separately. Draw the room and seat the guests in the free seating chart maker, then publish - the guest page and its QR code come from the same source, so they cannot disagree with the chart.
Your first event publishes free through 250 guests.
No. They scan a QR code or open a link, and the page works in the browser their phone already has. There is nothing to install and no guest login.
No. The page is a name search that returns one guest's result. It is not a browsable list of attendees.
No. Nobody selects or buys a seat here. The assignment is made by the host in advance and the guest is looking it up. Stadium and venue ticketing maps are a different product entirely.
The next lookup returns the new table. The link and the QR code point at the event, not at a snapshot of the chart.
The plan you build produces the guest page. There is no second thing to make.
Build your chart freeNo account needed to buildFirst event free through 250Paid events refundable until 7 days after the day