Aditum
UA EN

A form for every participant category

A speaker does not fill in the guest form, and the press does not fill in the partner form. Every category has its own fields, its own rules and its own form address — public or closed by link.

Request a demo What forms can do
Seven event forms — one per participant category
01

A form of its own for every category

Attendee, VIP, speaker, media, partner, staff, organizer — seven categories, seven forms. A speaker is asked for a bio and technical needs, the press for their outlet and beat, a partner for the company and their booth role.

  • Categories are a builder per event, not a fixed list
  • Conditional fields: a question appears only when it is relevant
  • Sections, hints and the questions themselves — in any languages
The form editor: sections, fields, display conditions
02

Public forms and forms closed by link

The attendee and media forms are visible to everyone. The VIP, speaker, partner and team forms are published but unlisted — only the link you sent opens them.

  • A closed form is not a way around approval: you still decide on the application
  • Versions: draft → published → history
  • Every application remembers which form version it was submitted on
The list of forms with versions and publication state
03

Quotas, a registration window, a waitlist

Registration opens and closes on schedule. A quota limits a category or an approver entity. When seats run out, an application can go to the waitlist instead of being refused.

  • A quota per category, country or approver entity
  • Quota fill is visible on the event dashboard
  • The registration window runs in the event’s time zone
Event quotas and their fill
04

Missing data — you request it instead of emailing back and forth

The participant gets a link and completes only the fields you asked for. An operator can correct a contact or a category themselves — and it stays in the application history.

  • A completion request — with an expiry and a repeat
  • The application history: who changed what and when
  • Duplicates and repeat applications — as a separate list
The application card: profile, form answers, history
05

The form lives on your site

Forms are headless: the event site fetches the form schema over the API and posts the application back. The design is yours, the data lands in the application catalogue at once.

  • An open API: OAuth2, an OpenAPI specification
  • Search, filters and saved views in the catalogue
  • All categories and events — in one organization database
The application catalogue with filters and statuses
What it looks like at the event

Three scenarios — the same forms

Conference Seven categories, two public forms Attendees and media register from the site. Speakers, partners and the team use closed links, with no queue among guests. Solution for conferences → Summit A form per delegation A country gets its own link. An application from it goes straight to that country’s approver. Solution for summits → Private dinner One invitation form A closed form with three fields: assistant, dietary preferences, invitation context. The quota matches the room exactly. Solution for private dinners →
Related features

What happens to the application next

Approvals & delegations Who decides who gets in Communications & Wallet The participant knows the status Security & security service P1–P4, masking, audit

We’ll show forms on your event

Your categories, your questions, your languages — we’ll build the forms at the demo for a real scenario.

Request a demo
Request a demo

Tell us about your event — we’ll show it on yours

Not slides — your scenario: categories, approvals, zones, desks. We’ll set the demo up for your event.

Or write directly [email protected]
Demo Partnership
By submitting you agree to the privacy policy. We reply within one business day.