Not built yet
Exhibitor portal
The place an exhibitor updates their own entry, and the place ops stops chasing two hundred of them by email. It is the loudest pain the ops team has, and the reason this app is worth more than a drawing tool.
Who wants it: Operations, who currently collect logos, descriptions and contacts by inbox.
What it does
- A link per exhibitor that signs them in with no password — eleven months pass between signing a contract and standing on the floor, and nobody remembers a password across that.
- They fill in their own company name, description, logo, website and categories.
- Everything they submit lands in an approval queue rather than straight on the public map.
- One grid for ops: who has filled it in, who has not, and who to chase.
- It feeds the public map directly, which is what makes the map worth embedding.
Then
- Deadlines and reminders, sent automatically.
- Documents: risk assessments, electrical certificates, stand designs.
- Several people per exhibiting company.
- A history of who changed what.
What it is waiting on
A loginAn exhibitor editing their own entry has to be told apart from anybody else on the internet. Nothing else here needs one, which is why the floor plan builder shipped first.
A databaseSupabase — Postgres, with row-level security so the boundary is enforced by the database rather than by remembering to filter a query.
A sending domainAuto-login links have to arrive as the event, not as a stranger. DNS, and it takes weeks, so it starts before the code does.